Using ProfileUnity with Dizzion Frame

Configuring Dizzion Frame for full ProfileUnity and FlexApp

This document describes the process require to implement full ProfileUnity and FlexApp for Dizzion Frame environments, with or without Enterprise Profiles enabled.  This article applies to ProfileUnity and FlexApp version 6.8.5 and newer.

What You’ll Need

• ProfileUnity Console installed
• Optional - Any required Cloud Storage credentials added to the “Cloud Storage” section of the Administration screen
• ProfileUnity Configuration INI stored somewhere accessible, ie a file-share or Cloud Storage
• Frame account and sandbox with the following:
  • REQUIRED - Fully-update first using the latest Frame Agent Setup Tool:
    https://docs.dizzion.com/downloads#frame-agent-setup-tool-fast
  • Any desired supporting software installed
  • Any required security policies applied
  • Full access to start sessions, take backups and publish to production
• At least one Frame test user account – different from the account used for the sandbox
• ProfileUnity and FlexApp Client Tools - Downloaded from your ProfileUnity Console or latest hot-fix
  
• REQUIRED - Additional files: (included in the below-linked zip unless otherwise specified)
  • Clientsettings.xml (generated from your ProfileUnity Console)
  • Full-ProfileUnity-on-Frame.reg
  • FGA User Scripts\definition.yml  (or use as example and modify your own)
  • FGA User Scripts\ProfileUnity-Logon.ps1
  • FGA User Scripts\ProfileUnity-Logoff.ps1

Configuring the Sandbox

1. Start a session to the sandbox – you are logged in as the local administrator account “Frame”.
2. Download or copy the following items into a new folder outside of the Frame user’s profile. Because the sandbox can use the same local user that production machines use, you need to keep Frame’s user profile clean and consistent.
   1. ProfileUnity Client Tools
      1. If using the client-tools.zip from the hot-fix page or the “ProfileUnity Tools” section of the Administration screen of your ProfileUnity Console, extract the contents into a new folder.
   2. Clientsettings.xml
      1. On the Administration screen of your ProfileUnity Console, find the “Client Settings” section and change the “Communication Type to Broker Messages” dropdown to “FlexDisk VMDK ProfileDisk and FlexApp” and click the blue “Update” button at the top-right.
      2. In “Client Settings” section, click the “Download or Deploy Client Settings”. 
      3. Place the clientsettings.xml file in the same folder as the ProfileUnity client-tools were extracted.
   3. FGA User Scripts\definition.yml, ProfileUnity-Logon.ps1, ProfileUnity-Logoff.ps1
      1. Place these 3 files into “C:\ProgramData\Nutanix\Frame\FGA\Scripts\User”, overwriting the original, empty definition.yml.  (make sure this isn't a custom xml first!)
   4. On the sandbox, right-click the Start button, select “Apps and Features”, find “ProfileUnity Client” and click the “Uninstall” button.
   5. Navigate to the folder where the client-tools were extracted.
      1. Right-click “LwL.ProfileUnity.Client.Startup.Update.exe” and “Run as administrator”.
         Full ProfileUnity client-tools will now be installed.
      2. Next, double-click “Full-ProfileUnity-on-Frame.reg” to import the settings into the Registry.
   6. Within your Group Policy, if you haven't created one yet, or using “gpedit.msc” locally:
      1. Right-click “Administrative Templates” and click “Add/Remove Templates…”.
      2. Click the “Add…” button, browse to the path where the client-tools were extracted, select the “ProfileUnity.adm” file, click the “Open” button and then the “Close” button.
      3. Expand User Config, Classic Administrative Templates, Liquidware, click on ProfileUnity.
         1. Edit the “Enabled” setting and change to “Enabled”.
         2. Edit the “INI File Path” setting and specify the location where you have or will deploy your Configuration (INI) file(s) to.
         3. If using cloud storage, continue with the following 2 steps:
            1. Back in your ProfileUnity web console, Administration screen, Cloud Storage where you’ve already populated your cloud credentials and click the Copy to Clipboard icon for the corresponding client-side cloud storage credential.
            2. Paste that value into the appropriate cloud credential setting in "gpedit.msc" of the sandbox.
   7. Close the session to the sandbox, publish it to production and take a manual backup.

Creating and Deploying a ProfileUnity Configuration

1. From your ProfileUnity Console’s “Configuration Management” screen, click the red “Create” button at the top-right.
   1. Click “Guided”, select the appropriate template for your needs and click “Next”.
   2. If using Cloud Storage, and you have not already added your console and client cloud credentials, click the “Add Cloud Credentials” button and fill in all required fields, once for your console-level credentials and once for your client-level credentials.
   3. When prompted, specify the path where user profiles will be stored and click “Next”.
      1. NOTE - The screen mentions the path should end with “%USERNAME%”, but for non-domain joined Frame we instead need to use “%FRAME_USER_EMAIL%” on the end.
   4. On the “Confirm Your Settings” screen, copy the deployment path shown to your clipboard, click “Finish” and “Yes” to the question in the dialog about proceeding without deploying. You will now have a new Configuration listed.
   5. Navigate to Filter Management on the left bar and click the "Create" button at the top-right.
      1. Name the new Filter "Frame Pool-Type is Production"
      2. Change the first drop-down from "And" to "Or".
      3. Under the Condition drop-down, select "Registry Value"
      4. Under Value, enter:  (the | before production is a "pipe" character)
         HKEY_CURRENT_USER\Environment\FRAME_POOL_GROUP_TYPE|production
      5. Click "Add".
      6. Repeat with new value data, under the Condition drop-down, select "Registry Value"
      7. Under Value, enter:  (the | before persistent is a "pipe" character)
         HKEY_CURRENT_USER\Environment\FRAME_POOL_GROUP_TYPE|persistent_desktop_production
      8. Click "Add".
      9. Click "Save".
   6. Navigate to Configuration Management, click the name of the new Configuration.
      1. Click “Main”
         1. Above "Require Filter for Execution" setting, click the "Enable Filter" checkbox.
         2. Select the new Filter "Frame Pool-Type is Production".
            This Filter ensures that ProfileUnity and FlexApp do not run within the sandbox.
         3. Click the “Return” arrow button at the top to go back to the Module list.
      2. Click “User Defined Scripts”
         1. Click "Add User Defined Script Rule".
            1. Set "Description" to “End explorer.exe”.
            2. Set "Type" to Executable
            3. Paste the following text into the File field:
               taskkill.exe /F /FI "USERNAME eq %username%" /IM explore.exe
            4. Click “Save” to add the new rule.
            5. Click the “Update” button at the top-right.
   7. From Configuration Management, click the “Deploy Configuration” (circled down-arrow) icon toward the right of your new config to deploy it to your configuration path.

You’re now ready to start using full ProfileUnity and FlexApp on Frame, with or without Enterprise Profiles.