Configuring Edge Services in VMware Unified Access Gateway: VMware Workspace ONE Operational Tutorial

Before deploying Unified Access Gateway with VMware Tunnel, it is important to understand the VMware Tunnel components available to provide secure internal access to your device fleet.

VMware Tunnel consists of two major components: Tunnel Proxy and Per-App Tunnel. These components run independently as two separate services on the Unified Access Gateway appliance to enable internal access for an end-user device.

The Tunnel Proxy feature provides internal access to end-users in VMware Workspace ONE® Web (formerly VMware Browser) or other Workspace ONE UEM SDK-enabled applications by securing traffic from the application to a website with SSL encryption and certificate authentication. 

The Tunnel Proxy feature is enabled through settings in an application-specific SDK profile, which is pushed from the Workspace ONE UEM Console with the managed SDK-enabled app. Users also can access internal websites using Workspace ONE Web from non-managed devices, using the Workspace ONE application only in Mobile Application Management (MAM) mode.

The Per-App Tunnel feature enables an SSL VPN connection on a per-application basis for any public or internal application. This feature leverages the native Per-App VPN functionality of Android, iOS, and Windows 10 platforms and a device-side VPN client application to initiate a VPN connection when an enabled application is started. The VMware Workspace ONE® Tunnel client application installed on the user's device maintains a whitelist of applications that should use VPN, handle certificates for enabled applications, and initiate the VPN connection on behalf of the user.

Settings for the Per-App Tunnel feature are pushed to the device in a device profile with the VPN payload configured. Each platform offers slightly different variations of the Per-App Tunnel feature, but all platforms require the presence of the Workspace ONE Tunnel client to use Per-App VPN functionality.

The VMware Tunnel works as an edge service on Unified Access Gateway, and can automatically be configured during deployment using PowerShell, or after deployment, using the Unified Access Gateway administration console.

The Unified Access Gateway appliance OVF template contains several edge services, beyond VMware Tunnel. The template includes Content Gateway, Web Reverse Proxy, and Horizon. The appliance runs from a VMware standard hardened image.

The VMware Tunnel can be deployed in one of two configurations:

• Basic Mode consists of a single Unified Access Gateway appliance, typically situated in the DMZ, where devices can connect to the appropriate port for each feature, authenticate with a certificate issued from the Workspace ONE UEM Console, and connect to internal sites.
• The Cascade Mode option allows devices to authenticate to the front-end tunnel on the Unified Access Gateway appliance located in the DMZ, then connect to the back-end tunnel enabled on another Unified Access Gateway appliance over a single port and then access internal resources.

The following architectural diagram shows an example of two major networks that you can deploy your servers into. For this set of exercises, you deploy the Unified Access Gateway appliance on a DMZ and assign the respective NICs.

At the top of the diagram is vCenter Networking. At the bottom of the diagram is the vApp network required to support the environment. For these exercises, the focus is on the network hosted on the ESXi, and represented by the following three networks:

• VM Network & Management: Represents the dedicated network to access the Management Console
• Internal Network: Represents the internal network on 172.16.0.x range. The Control Center, ESXI, and vCenter are part of the internal network.
• DMZ Network: Represents the DMZ network on 192.168.110.x which is where the Unified Access Gateway appliance is to be deployed. The Unified Access Gateway Internet-facing NIC is associated to this network.

High-level Overview of Traffic Routing

The architectural diagram is based on two ports and two host names that route through the F5 load balancer. In this example, non-standard ports are used for these services in the 6000 - 6500 port range, due to F5 configuration for an internal network.

The next steps detail how the traffic is routed:

1. The host names ( pool##.airwlab.com) are CNAMEs that point to the external IP of the F5.  When these host names are resolved, they are routed to the F5 to be inspected and forwarded to the internal networks.
2. If the request includes only the host name ( pool##.airwlab.com), the F5 uses the Hostname iRule. This Hostname iRule inspects inbound traffic to the F5 over port 443 (HTTPS). The traffic is decrypted using the *.airwlab.com SSL certificate and chain. The Hostname iRule then inspects the traffic, re-encrypts the traffic using the SSL certificate and chain, and then routes the inbound request to the appropriate destination server based on the host name of the request. This process is known as SSL Bridging, which is not supported by Per-App Tunnel.
3. If the request includes the host name and port ( pool##:airwlab.com:6000), the F5 uses the Port iRule. This Port iRule inspects inbound traffic to the F5 over non-443 ports. Unlike the Hostname iRule, the Port iRule parses the request for the port number and then routes the inbound request to the appropriate destination server based on the port of the request. This process does not involve decrypting or re-encrypting the traffic; it forwards the request to the desired destination. This process uses SSL Passthrough.
4. From the F5 Hostname or Port iRules, the traffic is forwarded to the configured IP address.
5. The vPodRouter is configured to forward Unified Access Gateway traffic to the 192.168.110.20 IP address over the DMZ Network.
6. The Nested DMZ Network (192.168.110.0 on vmnic2) is provided by NIC 2 on the ESXi-01 Host (192.168.110.160).
7. The request reaches the nested Unified Access Gateway appliance deployed on 192.168.110.20.

Avoid SSL Bridging

In this example, non-443 ports are used for VMware Tunnel and Content Gateway to avoid decrypting and re-encrypting the traffic because this is not supported with Per-App Tunnel. In other scenarios, you would use the standard ports where possible. This exercise demonstrates that the ports for both services can be configured to work within the architecture.

Unified Access Gateway supports deployments with one, two, or three NICs. This means that the server can be partitioned to receive traffic on a single interface or to route traffic to different interfaces, based on the source of the request. Most often, if you need to implement multiple NICs, you already follow this standard with other web applications in your organization.

You must determine what is appropriate for your environment when selecting the number of NICs during installation. It is important for you to understand the expected behavior when two or three NICs are enabled.

To explore these options, see Deploying VMware Unified Access Gateway: VMware Workspace ONE Operational Tutorial.

In the exercises for deploying the Unified Access Gateway server through vSphere, the vCenter setup is hosted in a nested template. This is not usually the case when working with users in a live environment.

User environments can include multiple networks and can optionally have a Network Protocol Profiles (NPP) that corresponds to the networks to connect to the Unified Access Gateway. Prior to version 3.3, NPP was a requirement. Since version 3.3, NPP is no longer required.

Note: Keep in mind that the Unified Access Gateway requires a netmask, default gateway, and subnet to be defined for each network enabled during deployment.

Double-click the Google Chrome browser icon on the desktop.

1. Launch the Chrome browser from your desktop and click the bookmark for vSphere.
2. Enter the username, such as administrator@vsphere.local.
3. Enter the password, such as VMware1!.
4. Click Login.

After completing the login, you are presented with the vSphere Web Client.

On your desktop, double-click the Google Chrome icon.

For example, navigate to https://<WorkspaceONEUEMHostname> where WorkspaceONEUEMHostname is the host name of the Workspace ONE UEM console.

1. Enter your Username. This is the name provided in the activation email.
2. Enter your Password. This is the password provided in the activation email.
3. Click the Login button.

Note: If you see a Captcha, be aware that it is case sensitive.

1. On your iOS device, in the web browser, navigate to http://awagent.com.
2. Tap Go to Apple AppStore.

Tap the cloud icon to install the agent.

To start the agent, tap the Agent icon.

Tap Server Details.

1. In Workspace ONE UEM Console, hover your mouse over the Organization Group tab at the top of the screen.
2. Your Group ID is displayed at the bottom of the Organization Group pop up.

Note: The Group ID is required when enrolling your device in the following steps.

After the agent launches, you can enroll the device.

1. Server – Enter your Workspace ONE UEM tenant name. For example, hol.awmdm.com
2. Group ID – Enter {YourGroupID}. Your Group ID was noted in the previous exercise.
3. Tap Next.

On this screen, enter the user credentials for a basic user account.

1. Username – Enter the user name.
2. Password – Enter the password.
3. Tap Next.

The agent redirects you to Safari and starts the process of enabling MDM in the device settings.

Tap Redirect & Enable.

If prompted to allow the website to open Settings to show you a configuration profile, tap Allow.

Note: If you do not see this prompt, ignore this and continue to the next step.  This prompt appears only for iOS Devices on iOS 10.3.3 or later

If a PIN is requested, enter your device PIN.

Tap Install in the upper-right corner of the Install Profile dialog box.

Tap Install when prompted at the Install Profile dialog box.

You should now see the iOS Profile Installation warning explaining what this profile installation will allow on the iOS device.

Tap Install in the upper-right corner of the screen.

You should now see the iOS request to trust the source of the MDM profile.

Tap Trust when prompted at the Remote Management dialog.

You should now see the iOS Profile successfully installed.

Tap Done in the upper right corner of the prompt.

Your enrollment is now complete. Tap Open to navigate to agent.

Tap Done to continue.

Tap Allow if you get a prompt for Notifications.

You may be prompted to install a series of applications. If prompted, tap Install to accept the application installation.

1. Select Groups & Settings.
2. Select All Settings.

1. Select System.
2. Select Enterprise Integration.
3. Select VMware Tunnel.
4. Select Configuration.
5. Change the setting to Override.
6. Select Enabled for VMware Tunnel.
7. Click Configure.

The INI file contains all the configuration settings required to deploy the Unified Access Gateway appliance.

This exercise uses the uag-Tunnel.ini file and is configured for a Unified Access Gateway appliance called UAG-TUNNEL, that has two NICs—NIC one is set to internet facing and NIC two for back end and management.

The INI file is located in the Unified Access Gateway installer ZIP package downloaded in the previous exercise.

Navigate to your Unified Access Gateway INI file. In this example, the INI file is located in UAG Resources.

1. Click the File Explorer icon from the task bar.
2. Select Desktop.
3. Select UAG Resources.
4. Right-click the INI file, for example, uag-TUNNEL.ini.
5. Select Edit with Notepad++.

In this example, the settings are already filled out. The General section includes details such as deployment location and network configuration for the Unified Access Gateway appliance.

The SSLCert and SSLCertAdmin sections contain SSL certificate location for the administrator and Internet interfaces.

The AirWatch section contains the required parameters to enable the VMware Tunnel edge service on your Unified Access Gateway appliance.

1. Enter the apiServerUsername, for example,  apiuser.
2. Enter your  Group ID for the Organization Group.
3. Enter the apiServerUrl, for example, https://v9.airwlab.com. 
4. Enter the airwatchServerHostname, for example,  https://pool##.airwlab.com.

During the Unified Access Gateway deployment, the PowerShell script prompts you for the apiServerUsername password.

Click the PowerShell icon.

After you run the script, it prompts for input.

1. Navigate to the folder containing your INI file. For example, enter cd '.\Desktop\UAG Resources' then press Enter.
2. Enter .\uagdeploy.ps1 .\<uag-tunnel>.ini <password1> <password2> false false no then press Enter.
   Replace <uag-tunnel> with your INI file name.
   Replace <password1> with the root password for the Unified Access Gateway appliance.
   Replace <password2> with the administrator password for  REST API management access.
   The first false is to not skip the validation of signature and certificate.
   The second false is to not skip SSL verification for the vSphere connection.
   The no is to not join the VMware CEIP program.
3. Enter the password for the certificated that will be used on the following fields SSLcert and SSLcertAdmin.
4. Enter the password for the apiuser previous defined on the INI file, which will allow Unified Access Gateway to obtain the VMware Tunnel settings from Workspace ONE UEM.

To avoid a password request for the certificate, remove the pfxCert values and provide a PEM certificate in the INI file. Set the pemCerts and pemPrivKey for the SSLCert and SSLCertAdmin sections in the INI file.

The deployment starts and you can follow the progress in the same window or on your vSphere Web Client.

1. Confirm the deployment has been completed successfully. The Completed successfully text is shown in the output.
2. Click Close.
3. After a successful deployment, the script automatically powers on the VM UAG-2NIC-TUNNEL.

The Received IP address presented by the script log is a temporary IP; the final IPs for NIC one and NIC two are assigned to the Unified Access Gateway appliance during the first start. Return to the vSphere Web Client and validate the IP address in the next step.

1. Click VM and Templates.
2. Click your VM, for example, UAG-2NIC.
3. Click View all 2 IP addresses.

Important: If the Unified Access Gateway appliance does not finalize the configuration during the first startup, you receive an error message from vSphere Web Client. If that happens, wait for the appliance to finalize, and refresh the entire Google Chrome browser.

1. Click the New Tab button to open a new tab.
2. Navigate to the Unified Access Gateway administration console URL, for example,  https://uagmgt-int.airwlab.com:9443/admin.
3. Enter the username, for example, admin .
4. Enter the password, for example, VMware1!.
5. Click Login.

A successful login redirects you to the following screen. Keep this window open as you will return to the administration console later.

Click Select to configure settings manually.

1. Click SHOW, after you click SHOW, it changes to HIDE.
2. Click the gear icon next to VMware Tunnel Settings. The circle should be green, which means the Unified Access Gateway appliance and Workspace ONE UEM Console can communicate.

The VMware Tunnel edge service is enabled based on the configuration defined in the INI file.

You can change the configuration any time, or choose not to configure settings in the INI file and later enable the settings through the Unified Access Gateway administration console.

Each time you change the configuration and Save, the changes are applied to the configuration files and the VMware Tunnel edge service restarts automatically. Devices cannot communicate with the service during the restart.

Click Cancel.

1. In the Workspace ONE UEM Console, select GROUPS & SETTINGS.
2. Select All Settings.

1. Select System.
2. Select Enterprise Integration.
3. Select VMware Tunnel.
4. Select Network Traffic Rules.

In this step, you create a specific rule that is applied only to Safari; any requests to *.corp.local are routed through the VMware Tunnel. All other requests are not routed through VMware Tunnel.

1. Click Add.
2. Click Add.
3. Select Safari-iOS.
4. Enter a Destination Hostname, for example,  *.corp.local.
5. Click Save & Publish. (The PIN number that you created during the first console login, is requested to confirm this operation.)
6. Click X to close.

The message Device Traffic Rules Published! displays in the console.

This exercise helps you to create and push the VPN Profile to the device.

This exercise helps you to configure the Workspace ONE Tunnel client application to be deployed to your device through Workspace ONE UEM.

Repeat the steps in this exercise, this time for the Google Chrome application.

Google Chrome is used later in this exercise to confirm that Safari is the only browser authorized to access internal websites.

On your iOS device, tap Tunnel to start the Workspace ONE Tunnel client.

Tap Safari Browser.

Navigate to https://www.vmware.com.

You can access the VMware website and no VPN is requested.

1. Navigate to an internal website, for example, http://intranet.corp.local/intranet.
2. You should see a VPN icon, indicating the connection is active. The Workspace ONE Tunnel client application identified a rule that applies to this situation, which you created in Define Device Traffic Rules.
3. The website should load successfully.

Next, verify that you cannot access the intranet from other browsers, even though the VPN connection is active for Safari.

Before deploying the Unified Access Gateway with Content Gateway, it is important to understand the Content Gateway architecture and deployment models available to provide secure internal access to file repositories from your device fleet.

The Content Gateway works as a edge service on the Unified Access Gateway appliance, and can be configured automatically during deployment of the appliance using PowerShell or after deployment, using the Unified Access Gateway administration console.

The Unified Access Gateway appliance OVF template product, contains several edge services, beyond  Content Gateway. The template includes VMware Tunnel, Web Reverse Proxy, and Horizon. This appliance runs from a VMware standard hardened image.

The Content Gateway can be deployed in one of two configurations:

• Basic Mode consists of a single Unified Access Gateway appliance, typically situated in the DMZ, where devices can connect to the appropriate port for each feature, authenticate with a certificate issued from the Workspace ONE UEM Console, and connect to internal sites.
• The Cascade Mode option allows devices to authenticate to the front-end Content Gateway on the Unified Access Gateway appliance located in the DMZ, then connect to the back-end Content Gateway enabled on another Unified Access Gateway appliance over a single port and then access internal resources.

The following architectural diagram shows an example of two major networks that you can deploy your servers into. For this set of exercises, you deploy the Unified Access Gateway appliance on a DMZ and assign the respective NICs.

At the top of the diagram is vCenter Networking. At the bottom of the diagram is the vApp network required to support the environment. For these exercises, the focus is on the network hosted on the ESXi, and represented by the following three networks:

• VM Network & Management: Represents the dedicated network to access the Management Console
• Internal Network: Represents the internal network on 172.16.0.x range. The Control Center, ESXI, and vCenter are part of the internal network.
• DMZ Network: Represents the DMZ network on 192.168.110.x which is where the Unified Access Gateway appliance is to be deployed. The Unified Access Gateway Internet-facing NIC is associated to this network.

High-level Overview of Traffic Routing

The architectural diagram is based on two ports and two host names that route through the F5 load balancer. In this example, non-standard ports are used for these services in the 6000 - 6500 port range, due to F5 configuration for an internal network.

The next steps detail how the traffic is routed:

1. The host names ( pool##.airwlab.com) are CNAMEs that point to the external IP of the F5.  When these host names are resolved, they are routed to the F5 to be inspected and forwarded to the internal networks.
2. If the request includes only the host name ( pool##.airwlab.com), the F5 uses the Hostname iRule. This Hostname iRule inspects inbound traffic to the F5 over port 443 (HTTPS). The traffic is decrypted using the *.airwlab.com SSL certificate and chain. The Hostname iRule then inspects the traffic, re-encrypts the traffic using the SSL certificate and chain, and then routes the inbound request to the appropriate destination server based on the host name of the request. This process is known as SSL Bridging, which is not supported by Per-App Tunnel.
3. If the request includes the host name and port ( pool##:airwlab.com:6000), the F5 uses the Port iRule. This Port iRule inspects inbound traffic to the F5 over non-443 ports. Unlike the Hostname iRule, the Port iRule parses the request for the port number and then routes the inbound request to the appropriate destination server based on the port of the request. This process does not involve decrypting or re-encrypting the traffic; it forwards the request to the desired destination. This process uses SSL Passthrough.
4. From the F5 Hostname or Port iRules, the traffic is forwarded to the configured IP address.
5. The vPodRouter is configured to forward Unified Access Gateway traffic to the 192.168.110.20 IP address over the DMZ Network.
6. The Nested DMZ Network (192.168.110.0 on vmnic2) is provided by NIC 2 on the ESXi-01 Host (192.168.110.160).
7. The request reaches the nested Unified Access Gateway appliance deployed on 192.168.110.20.

Avoid SSL Bridging

In this example, non-443 ports are used for VMware Tunnel and Content Gateway to avoid decrypting and re-encrypting the traffic because this is not supported with Per-App Tunnel. In other scenarios, you would use the standard ports where possible. This exercise demonstrates that the ports for both services can be configured to work within the architecture.

Unified Access Gateway supports deployments with one, two, or three NICs. This means that the server can be partitioned to receive traffic on a single interface or to route traffic to different interfaces, based on the source of the request. Most often, if you need to implement multiple NICs, you already follow this standard with other web applications in your organization.

You must determine what is appropriate for your environment when selecting the number of NICs during installation. It is important for you to understand the expected behavior when two or three NICs are enabled.

To explore these options, see Deploying VMware Unified Access Gateway: VMware Workspace ONE Operational Tutorial.

In the exercises for deploying the Unified Access Gateway server through vSphere, the vCenter setup is hosted in a nested template. This is not usually the case when working with users in a live environment.

User environments can include multiple networks and can optionally have a Network Protocol Profiles (NPP) that corresponds to the networks to connect to the Unified Access Gateway. Prior to version 3.3, NPP was a requirement. Since version 3.3, NPP is no longer required.

Note: Keep in mind that the Unified Access Gateway requires a netmask, default gateway, and subnet to be defined for each network enabled during deployment.

Double-click the Google Chrome browser icon on the desktop.

1. Launch the Chrome browser from your desktop and click the bookmark for vSphere.
2. Enter the username, such as administrator@vsphere.local.
3. Enter the password, such as VMware1!.
4. Click Login.

After completing the login, you are presented with the vSphere Web Client.

On your desktop, double-click the Google Chrome icon.

For example, navigate to https://<WorkspaceONEUEMHostname> where WorkspaceONEUEMHostname is the host name of the Workspace ONE UEM console.

1. Enter your Username. This is the name provided in the activation email.
2. Enter your Password. This is the password provided in the activation email.
3. Click the Login button.

Note: If you see a Captcha, be aware that it is case sensitive.

1. On your iOS device, in the web browser, navigate to http://awagent.com.
2. Tap Go to Apple AppStore.

Tap the cloud icon to install the agent.

To start the agent, tap the Agent icon.

Tap Server Details.

1. In Workspace ONE UEM Console, hover your mouse over the Organization Group tab at the top of the screen.
2. Your Group ID is displayed at the bottom of the Organization Group pop up.

Note: The Group ID is required when enrolling your device in the following steps.

After the agent launches, you can enroll the device.

1. Server – Enter your Workspace ONE UEM tenant name. For example, hol.awmdm.com
2. Group ID – Enter {YourGroupID}. Your Group ID was noted in the previous exercise.
3. Tap Next.

On this screen, enter the user credentials for a basic user account.

1. Username – Enter the user name.
2. Password – Enter the password.
3. Tap Next.

The agent redirects you to Safari and starts the process of enabling MDM in the device settings.

Tap Redirect & Enable.

If prompted to allow the website to open Settings to show you a configuration profile, tap Allow.

Note: If you do not see this prompt, ignore this and continue to the next step.  This prompt appears only for iOS Devices on iOS 10.3.3 or later

If a PIN is requested, enter your device PIN.

Tap Install in the upper-right corner of the Install Profile dialog box.

Tap Install when prompted at the Install Profile dialog box.

You should now see the iOS Profile Installation warning explaining what this profile installation will allow on the iOS device.

Tap Install in the upper-right corner of the screen.

You should now see the iOS request to trust the source of the MDM profile.

Tap Trust when prompted at the Remote Management dialog.

You should now see the iOS Profile successfully installed.

Tap Done in the upper right corner of the prompt.

Your enrollment is now complete. Tap Open to navigate to agent.

Tap Done to continue.

Tap Allow if you get a prompt for Notifications.

You may be prompted to install a series of applications. If prompted, tap Install to accept the application installation.

1. Select Groups & Settings.
2. Select All Settings.

1. Select System.
2. Select Enterprise Integration.
3. Select Content Gateway.
4. Change the setting to Override.
5. Select Enabled for Content Gateway.
6. Click Save.
7. Click Add.

1. Select UAG for Installation Type.
2. Select Basic (Single-Tier) for Choose Configuration Type.
3. Enter a Name, for example, Content Gateway on UAG.
4. Enter the Content Gateway server host name (for example, https://contentgateway.vmware.com) for Content Gateway Endpoint Address.
5. Enter a port number for Content Gateway Endpoint Port.
6. Click Upload and select your certificate.
7. Click Save.

1. Select the Content Gateway configuration that you just added.
2. Select More Actions and select Download Unified Access Gateway, which redirects to the Workspace ONE Resources portal where the Unified Access Gateway virtual appliance OVF package is hosted.
3. Copy the Content Gateway Configuration GUID—this is required to enable the Content Gateway edge service on Unified Acces Gateway.

Extract the ZIP file on the Windows machine where you will install Unified Access Gateway.

The next section helps you to deploy the Unified Access Gateway appliance OVF through PowerShell and configure the Content Gateway edge service based on the settings configured in Workspace ONE UEM.

The INI file contains all the configuration settings required to deploy the Unified Access Gateway appliance.

This exercise uses the uag-CG.ini file and is configured for a Unified Access Gateway appliance called UAG-CG, that has two NICs—NIC one is set to internet facing and NIC two for back end and management.

The INI file is located in the Unified Access Gateway installer ZIP package downloaded in the previous exercise.

Navigate to your Unified Access Gateway INI file. In this example, the INI file is located in UAG Resources.

1. Click the File Explorer icon from the task bar.
2. Select Desktop.
3. Select UAG Resources.
4. Right-click the INI file, for example, uag-CG.ini.
5. Select Edit with Notepad++.

In this example, the settings are already filled out. The General section includes details such as deployment location and network configuration for the Unified Access Gateway appliance.

The SSLCert and SSLCertAdmin sections contain SSL certificate location for the administrator and Internet interfaces.

The AirWatchContentGateway section contains the required parameters to enable Content Gateway edge service on your Unified Access Gateway appliance.

1. Paste the Content Gateway configuration GUID for cgConfigId. You copied this value in the previous exercise.
2. Enter the apiServerUsername, for example, apiuser.
3. Enter the apiServerUrl, for example, https://v9.airwlab.com.
4. Enter the apiServerPassword, for example, VMware1!.
5. Enter the airwatchServerHostname, for example, https://pool###.airwlab.com.

If you do not provide the apiServerPassword as part of the INI settings, the administrator must enter the password in the Unified Access Gateway administration console.

Click the PowerShell icon.

After you run the script, it prompts for input.

1. Navigate to the folder containing your INI file. For example, enter cd '.\Desktop\UAG Resources' then press Enter.
2. Enter .\uagdeploy.ps1 .\<uag-tunnel>.ini <password1> <password2> false false no then press Enter.
   Replace <uag-tunnel> with your INI file name.
   Replace <password1> with the root password for the UAG appliance.
   Replace <password2> with the administrator password for  REST API management access.
   The first false is to not skip the validation of signature and certificate.
   The second false is to not skip SSL verification for the vSphere connection.
   The no is to not join the VMware CEIP program.
3. Enter the password for the certificated that will be used on the following fields SSLcert and SSLcertAdmin.
4. Enter the password for the apiuser previous defined on the INI file, which will allow Unified Access Gateway to obtain the VMware Tunnel settings from Workspace ONE UEM.

To avoid a password request for the certificate, remove the pfxCert values and provide a PEM certificate in the INI file. Set the pemCerts and pemPrivKey for the SSLCert and SSLCertAdmin sections in the INI file.

The deployment starts and you can follow the progress in the same window or on your vSphere Web Client.

1. Confirm the deployment has been completed successfully. The Completed successfully text is shown in the output.
2. Click Close.

After a successful deployment, the script automatically powers on the VM UAG-2NIC-CG.

The Received IP address presented by the script log is a temporary IP; the final IPs for NIC one and NIC two are assigned to the Unified Access Gateway appliance during the first start. Return to the vSphere Web Client and validate the IP address in the next step.

1. Click the New Tab button to open a new tab.
2. Navigate to the Unified Access Gateway administration console URL, for example,  https://uagmgt-int.airwlab.com:9443/admin.
3. Enter the username, for example, admin .
4. Enter the password, for example, VMware1!.
5. Click Login.

A successful login redirects you to the following screen. Keep this window open as you will return to the administration console later.

Click Select to configure settings manually.

1. Click SHOW, after you click SHOW, it changes to HIDE.
2. Click the gear icon next to Content Gateway Settings. The circle should be green, which means the Unified Access Gateway appliance and Workspace ONE UEM Console can communicate.

The Content Gateway edge service is enabled based on the configuration defined in the INI file.

You can change the configuration any time, or choose not to configure settings in the INI file and later enable the settings through the Unified Access Gateway administration console.

Each time you change the configuration and Save, the changes are applied to the configuration files and the Content Gateway edge service restarts automatically. Devices cannot communicate with the service during the restart.

Click Cancel.

1. Select Content.
2. Select Repositories.
3. Select Admin Repositories.
4. Click Add.

1. Enter a Name, for example, Corp Files.
2. Select Network Share for Type.
3. Enter the Link, for example, \\intranet.corp.local\Corp Files.
4. Enter the Organization Group, for example, Exercise 02.
5. Select USER for Authentication Type.
6. Enter the User name, for example, corp\administrator.
7. Enter the Password, for example, VMware1!.
8. Select your Content Gateway, for example, Content Gateway on UAG. Access to this internal repository goes through the Content Gateway that you set up in the previous exercise.
9. Click Continue.

Click Save.

1. Select Content.
2. Select Content Locker.
3. Select List View.
4. Select Corporate File Servers.
5. Select Corp Files.
6. Select the IT folder.

You can see the files available in this folder and in sync with Content Management.

The Installed/Assigned column lists the number of devices where the files are available. Click the quantity to see a list of each device that can access the file.

Although you configured the security configurations on the network file share, Workspace ONE UEM allows you to set up a new layer of security for the content on mobile devices.

1. Navigate back to the Corp Files folder.
2. Click Edit for one of your folders.

There are a number of configurations that you can apply to increase security of the asset on the mobile devices. In this example, you edit security for the IT folder, however, you can override the security properties on multiple levels, such as navigating to a specific file.

In this example, you allow the end-user to print any content under the IT Folder from a managed mobile device using Workspace ONE Content.

1. Select Override.
2. Select the Allow Printing check box.
3. Click Save.

1. Select Apps & Books.
2. Select Applications.
3. Select Native.
4. Select Public.
5. Click Add Application.

1. Select Apple iOS for Platform.
2. Enter Content Locker for Name.
3. Click Next.

Click Select.

Click Save & Assign.

Click Add Assignment.

1. Enter your assignment group, for example, Exercise 02.
2. Select AUTO for App Delivery Method.
3. Select Enabled for Managed Access.
4. Click Add.

Click Save & Publish and then click Publish.

After you click Publish, you should receive a prompt on your device requesting confirmation to install the Workspace ONE Content application. Confirm and launch the application after the installation completes.

Tap Content to open Workspace ONE Content.

1. Tap the Repositories icon.
2. Tap Corp Files.

1. Enter a User ID, for example, CORP\jdoe.
2. Enter the Password, for example, VMware1!.

Repeat the following steps for each folder you see under Corp Files. You can see the available files in each folder.

Tap the IT folder.

Tap a file to open it.

1. Tap the Share icon. The Print option is available based on the security properties previously defined for the IT folder.
2. Tap < to return to Corp Files.

1. Tap another folder in Corp Files, for example, Finance.
2. Tap a file to open it.

The file is downloaded to your device and opened.

1. Tap the Share icon. The Print option is not available for this file.
2. Tap < to return to Corp Files.