How to setup separate ProfileUnity configuration to execute on machine startup for XenApp/RDSH or non persistent desktop.

Product: ProfileUnity

Product Version: 6.5+

Expires on: 365 days from publish date

Updated: Oct 8, 2015

Problem:

ProfileUnity has an ability to execute separate configuration to execute on startup. This will allow faster user's logon and allow ProfileUnity to prepare the desktop during system startup.This could be applied to RDSH, XenApp or Windows non persistent desktop pool. (Run ProfileUnity as a service)

Some of the features/changes that could be done to the machine during startup:

• Installation of DIA applications (ie - XenApp)
• Configuration of HKLM registry keys
• Execution of cmd, vbs and Bat Scripts during system startup
• Any other system level changes

Symptoms:

Pre installation checklist:

• .Net 4.5.2 is installed on the base image
• GPO is configured to use "LwL.ProfileUnity.Client.Startup.exe"

Possible Resolution(s):

Step 1) Go to Configuration Management in console and create a separate configuration with settings that need to be applied during system startup.

Note: Only system level filters for the configuration can be applied here. Example: Computer name begins with...

Step 2) Deploy this secondary (ini) configuration to your Startup folder located in ....netlogon\ProfileUnity\Startup

Step 3) In ProfileUnity Console go to "Administration" page.

Go to "ProfileUnity Tools" section and fill our the missing information "Run Client Tools As Service" 

Use any domain user or create service account.

Step 4) Select "Deploy Service Configuration or Download Service Configuration

Note: This will download "LwL.ProfileUnity.Client.Service.exe.creds" file to ...netlogon\ProfileUnity (Deployment) directory (same directory where "lwl.ProfileUnity.Client.Startup.exe" is located)

Note: When lwl.ProfileUnity.Client.Startup.exe will run (GPO or manual on domain join base image) it will read the .creds file and setup ProfileUnity client to run as a service on the machine. 

Step 5)GPO - Add Computer Configuration Administrative Template (if missing in AD - Step 1-7)

1. Logon to Domain controller and Open Group Policy Management
2. Edit "ProfileUnity" GPO
3. Expand Computer Configuration, Policies, Administrative Template, (Add/Remove Templates)
4. 
5. Add, Browse to ..netlogon\profileunity directory and select. "ProfileUnity.adm" > Open
6. 
7. Close
8. Browse to: Computer Configuration > Administrative Templates > Classic Administrative Templates > Liquidware Labs > ProfileUnity > 32 Bit or 64 Bit
• Note. If "Liquidware Labs" Template is not visible, go to "Action" and un-select "Filter On" 
9. Enable and specify paths:
   • System INI FIle Path: Default: ..Netlogon\ProfileUnity\Startup
     Note: This is path where is the secondary (Startup) ini will be located
     

Step 7) Close Group Policy Management Editor

Step 6) Refresh Desktops or RESTART Server!

FlexApp DIA:

To deploy VHD DIA applications just add the FlexApps to the FlexApp DIA module in startup configuration that needs to be created and placed in "System INI File Path" for ProfileUnity to read during system boot.