Skip to main content

How to create separate (test) ProfileUnity environment running parallel to production environment.

Glen Porter
  • Created:
  • Updated:

Product: ProfileUnity-FlexApp

Product Version: 6.8.x+

Expires on: 365 days from publish date

Updated: November 11, 2024

Problem:

How to create a separate (test) ProfileUnity environment that runs parallel to your production environment. 

Symptoms:

You need to test a new build or configuration changes in an environment that is completely separate from production

Possible Resolution(s):

Create a duplicate environment to test any changes or client tools upgrades.

The components of this new environment will include:

  • New deployment share for client tools and\or configuration ini files.
  • New OU (for test machines)
  • New GPO or copy of current
  • New or copy of current config

Here is a list of detailed steps to follow to create separate parallel ProfileUnity environment: 

  1. If you are testing a newer management console, run the ProU management installer on a separate server.
  2. Create a 2nd deployment share 
    Example: "\\domain.com\netlogon\ProfileUnity2"
  3. Deploy the new client tools to the new deployment share.
  4. Deploy your new (or copy your current) ClientSettings.xml to the new deployment share.
  5. If testing a new configuration, specify a new user data share.
    Example: "\\FileServer\ProfileUnity2_UserShare\%username%"
    Copy the current configuration if only testing new client version. 
  6. Create a new OU in Active Directory for your test pool
    Example: "Computers\ProfileUnity2"
  7. Create (or copy the current ProfileUnity GPO) a GPO which will only apply to this test OU.
    https://docs.liquidware.com/profileunity/en-us/686/installation-guide/manually-preparing-your-environment-to-use-the-profileunity-client.htm
    • Edit Computer Configuration->Policies->Windows Settings->Scripts->Startup script. Enter the file path to the new deployment share's startup exe -  \\domain.com\netlogon\ProfileUnity2\LwL.ProfileUnity.Client.Startup.exe 
    • Edit User Configuration->Policies->Windows Settings->Scripts->Logoff script. Enter the file path to the new deployment share's logoff exe -  C:\Program Files\ProfileUnity\Client.Net\LwL.ProfileUnity.Client.Logoff.exe
    • Edit User Configuration) > Policies > Administrative Templates > Classic Administrative Templates (ADM) > Liquidware Labs > ProfileUnity
      • Enabled
      • INI File Path - Enter your test deployment path
  8. Create a new pool with machines in the test OU.

 

Related articles