What is the best practice to upgrade ProfileUnity within live production environment? (How To Upgrade To ProfileUnity 6.x)

Product: ProfileUnity-FlexApp

Product Version: 6.x.x

Expires on: 365 days from publish date

Updated: September 16, 2017



I would like to upgrade ProfileUnity within my VDI environment, avoiding any scheduled downtime.



Before proceeding, back up / snapshot the ProfileUnity server and back up the ProfileUnity share (usually \\domain\NETLOGON\ProfileUnity).

Step 1. Upgrade the software on ProfileUnity server. (where ProfileUnity console is installed)


  • A) ProfileUnity Console with internet connection (Online Mode):
    • From the ProfileUnity Management Console, hover over your username in the top right corner of the console, then click About.
    • On the About screen, the version number you are currently running is displayed. If an update is available, there will be a special message box with the version number of the update.
    • Click the Update button to install the latest version of the software.



  • B) Direct Installer Upgrade: If the Update button is not available, download the executable using the link in the console and run it on the ProfileUnity console server, installing atop the existing version.


Step 2. Update the ProfileUnity Client on the ProfileUnity network share (usually \\domain\NETLOGON\ProfileUnity)

  1. From the ProfileUnity Management Console, hover over your username in the top right corner of the console, and click on Administration.
  2. On the Settings page, scroll down to the ProfileUnity Tools section and click on Download Client Tools.
  3. Delete all files in  \\\netlogon\ProfileUnity with exception of ProfileUnity.lic and any .ini files
  4. Extract the to \\\netlogon\ProfileUnity on your domain controller


Step 3a. Update ProfileUnity Client on Desktops.

Verify that the ProfileUnity GPO is pointed to "LwL.ProfileUnity.Client.Startup.exe" in computer startup script section (not startup.vbs)

While the desktops are refreshed/restarted new client is deployed/updated each time desktop is restarted implementing ProfileUnity GPO thus executing "LwL.ProfileUnity.Client.Startup.exe"

Note: This may last over several days.  For quicker deployment reset all desktops which are not used and if your setting is set to "reset/recompose after each logon" by next day all VDI desktops should have the new client installed/updated.

Step 3b. Update ProfileUnity Client on Desktops through Gold Image/Master Image.

If you need to update your client on "Master/Gold image" open the image

1. Log in as local or domain admin.
2. Open command prompt as administrator (ideally domain admin).
3. Run lwl.profileunity.client.startup.exe /uninstall.
4. Verify that C:\Program Files\ProfileUnity directory was removed if not delete it manually.
5. Watch for errors in red, if none, proceed to run lwl.profileunity.client.startup.exe to install.
6. Perform any pre-snapshot tasks such as ipconfig /release, then shut down, snapshot, and recompose.

Note: For the new features in 6.xx to work properly, the desktops need .Net 4.5.2 or newer installed on the base image. 

Note: The .Net 4.5.2 installer is located in netlogon\profileunity directory. (NDP452-KB2901907-x86-x64-AllOS-ENU.exe)

Step 4. Verify ProfileUnity Client is updated on ALL Desktops.

After all desktops are recomposed and restarted all client machines should have the new version of the client. To verify, right-click on the client.exe file and click Properties, then Details. Make sure the file versions match.


Note: If the versions do not match, there may be a problem with Group Policy or something else preventing LwL.ProfileUnity.Client.Startup.exe from executing. Stop here before you download and deploy configuration (.ini). (For errors running LwL.ProfileUnity.Client.Startup.exe, look in the C:\Windows\Temp\ProfileUnity - startup.log) 

Important Note: If you were using ProfileUnity 5.0 or earlier, update the client AND the configuration .ini at the same time. There are problems with running an .ini file from 5.5.1818 and earlier with newer clients. 


Step 5. Update Configuration (.ini)

After you are certain that all clients computer/VDI machines and master images (if available) are updated, download and update your Default.ini

  1. Go to the Configuration Management area and for each configuration in the list:
  2. Click on Download Configuration.
  3. Save this INI file to the same location where the ProfileUnity Client is installed.


Step 6. Update your FlexApp Packaging console. (Optional)

  1. In ProfileUnity Administration page download FlexApp Packaging console
  2. FPC.jpg
  3. Revert to clean snapshot without any 3rd party software. (With exception of FPC)
  4. Run install on the system which has old version of FPC
  5. For ProfileUnity 6.5 Please also make sure that .net 4.5.2 is installed on FPC as well
  6. Take snapshot after upgrade.


Note: Because Client.exe is backwards (up to version 5.5.1818) compatible with the versions of Configuration.ini it should be updated first. On contrary Configuraion.ini is not. when Configuration.ini is updated before the Client.exe it may cause unknown behavior.

Note: For ProfileDisk deployment pool refresh is necessary, this would most likely require scheduled down time. 

Note: ProfileUnity Version Matrix is here for your reference: ProfleUnity Version Matrix


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.