After the VDI workload domain creation workflow has completed, you typically launch the View Administrator Web interface to view and work with the VDI infrastructure that is configured for the workload domain. Depending on the options you selected in the creation wizard, you also must perform post-deployment tasks.

After the workflow has completed, perform one or more of the following post-deployment tasks. You must perform some of these tasks if you chose certain options in the creation wizard.

Table 1. Post-Deployment Tasks

Creation Wizard Settings

Post-Deployment Tasks


Launch the View Administrator Web interface using the connection information located in the workload domain's details page. Use the View Details button on the Dashboard page to navigate to the workload domain's details page.


As described in the vRealize Log Insight documentation, the workload domain's View Administrator installation is pre-configured to send the View Administrator logs to the vRealize Log Insight instance using the HKLM\Software\Policies\VMware, Inc.\VMware VDM\Log\SyslogSendSpec registry key. The View Administrator installation is not pre-configured with a syslog server on its Event Configuration screen. You can configure the vRealize Log Insight instance that SDDC Manager deploys for syslog forwarding. You use the Event Forwarding page of the vRealize Log Insight Web interface to configure forwarding incoming events to a syslog target. For information on logging in to the vRealize Log Insight instance, see Get Started Using the vRealize Log Insight Instance.

  • Active Directory Internal option

  • Implement App Volumes

You must log in to the created Active Directory using the Active Directory administrator account and add members to the AppVolumesAdmins group.

The deployment process creates a group named AppVolumesAdmins automatically in the auto-generated Active Directory, but does not add members to the group. Until you add members to the AppVolumesAdmins group, no one will be able to log in to App Volumes.

  • Active Directory Internal option

  • Full clones

You must manually join the created full clones to the created internal Active Directory domain. The created virtual desktops are not automatically joined to the internal Active Directory domain that was also created.

If instead you selected to use linked clones and the Active Directory Internal option, the View software customizes the linked-clone machines when they are created, including joining them to the internal Active Directory domain.

  • Implement App Volumes option

  • Active Directory External option

  • Your Active Directory domain is configured to provide secure LDAP connections (LDAPS)

When your Active Directory domain controllers are configured with TLS certificates for secure LDAP connections, you should configure the deployed App Volumes Manager instance to use secure connection port 636.

  1. From the Dashboard, navigate to the domain details for the created VDI workload domain and locate the IP address of the App Volumes Manager instance.

  2. Use that IP address in a new browser tab to launch the App Volumes Manager user interface.

  3. In the App Volumes user interface, navigate to Configuration > Active Directory.

  4. Click Edit on the Active Directory screen.

  5. In the Use LDAPS field, select the Use secure connection (port 636) check box. This option ensures that communication between App Volumes and your Active Directory domain is encrypted.

  6. Click Save to save the updated configuration.