Setting Up a VMDK for Application Layering at the OS Level

Follow these directions to use a VMDK at the OS level for assigning applications at computer startup with FlexApp. These instructions are based on starting and using ProfileUnity as a Service, which is needed for setting user or group assignments later in the procedure. FlexDisk also offers computer-level assignment of VMDK-based FlexApp packages that can be used without ProfileUnity as a Service. If ProfileUnity as a Service is used, FlexApp packages are played back on service boot, making them available before the user logs in. If ProfileUnity as a Service is not used, playback of the FlexApp packages occurs at user login.

  1. Log in to the ProfileUnity Management Console.
  2. Hover over your username in the top right corner of the screen.
  3. In the drop-down menu that appears, click the Administration option.

  4. Note: If you have not already done so, follow the directions provided earlier in the Setting Up ProfileUnity Clustering for FlexDisk section of this guide to configure FlexDisk for your vCenter.

  5. The Administration screen opens with the Settings tab displayed.
  6. Scroll down to the Client Settings section.
  7. In the ProfileDisk and FlexDisk VMDK Mode drop-down list, select the FlexDisk VMDK FlexApp Only option.
  8. In the Deployment Path field, enter your NETLOGON path.
  9. Click the Update button in the top right corner of the screen.
  10. Click the Download or Deploy Client Settings button to send a copy of the client configuration file to the specified location.
  11. On the screen that pops up, select the Platform for deployment.
    • If you choose the Domain or Cloud option, this will place the client configuration file in the directory you specified for the Deployment Path.
    • If you are not logged in as an Active Directory user, choose the Download option and manually place the client configuration file, clientsettings.xml, in the Deployment Path.
  12. Click the Deploy button.
  13. Scroll down to the ProfileUnity Tools section and click Download or Deploy Client Tools to copy the ProfileUnity Client files to the NETLOGON share on your domain controller.
  14. Scroll down to the ProfileUnity Tools section.
  15. In the Run Client Tools As Service field, enter a domain\username and password. The user you enter DOES NOT need to be an administrator. To use a local account, enter it in the form of ".\username" instead of "domain\username". If the local account does not exist, it will automatically be created as a non-administrator account.
  16. In the ProfileUnity Tools section, click the Download or Deploy Service Configuration button.
  17. The deployment path should be:\\dc.local\netlogon\ProfileUnity
  18. Using the FlexApp Packaging Console, create a package selecting “FlexDisk” as the Package Type and choose which FlexDisk datastore to which the package will be saved.
  19. In the ProfileUnity Management Console, instead of using the FlexApp Configuration Module click FlexDisk Management in the left column.

    • Note: Beginning with version 6.8.5, FlexDisk Management is hidden by default. If you do not see it in the left column, hover the cursor over your username in the top right corner of the screen and click the Administration option. In the Settings tab, scroll down to and click to open the Miscellaneous section. Deselect the Hide FlexDisk checkbox, then click Update in the top right corner of the screen. Lastly, refresh your screen and the FlexDisk Management option should appear in the left column.

  21. Click the FlexApp tab and then click the (Assignments) icon to create an assignment for users or groups.
  22. Select the user that was entered in for Step 22.
  23. If you have VMware Horizon and have added your Horizon credentials to the Administration > FlexDisk section, you can limit the application to the user, group, and/or the pool. Click the Add Assignment button to add it to the list of current assignments.
  24. When you have finished, click the X button.
  26. Reboot or refresh all user desktops.

  27. Note: Changes to the ProfileUnity as a service account credentials require re-processing by the ProfileUnity Startup Script GPO, also known as startup.exe.