This article explains how to build a fully isolated ProfileUnity test environment that runs alongside your production environment — allowing you to validate new builds, client tool upgrades, or configuration changes without affecting production users.
When to Use This
- You want to test a newer version of the ProfileUnity Management Console before upgrading production.
- You want to validate new client tools against your existing configuration without affecting production endpoints.
- You want to test configuration changes (portability, folder redirection, FlexApp) in a controlled pool before rolling out broadly.
Components Required
A parallel test environment requires the following components, all separate from production:
- A separate deployment share for client tools and/or configuration INI files
- A dedicated Active Directory OU for test machines
- A new or copied GPO scoped to the test OU only
- A new or copied ProfileUnity configuration (and optionally a separate user data share)
The test environment must use a completely separate deployment share and GPO from production. Sharing either between environments will cause production endpoints to receive test client tools or configuration — the exact outcome this setup is designed to prevent.
Setup Steps
Step 1 — Install the test Management Console (if testing a new version)
If you are evaluating a newer Management Console build, run the ProfileUnity Management installer on a separate server. If you are only testing new client tools against your existing console, skip this step.
Step 2 — Create a second deployment share
Create a new network share for the test environment's client tools and INI files. Keep the name distinct from production to avoid confusion.
Step 3 — Deploy client tools to the test share
Deploy the test version of the ProfileUnity client tools to the new deployment share. In the Management Console, go to Administration → ProfileUnity Tools, update the Deployment Path to the test share, and click Deploy. If testing against the existing console, deploy from the same Administration page to the new path.
Step 4 — Deploy clientsettings.xml to the test share
Deploy your clientsettings.xml to the new deployment share. If only testing client tools (not a new console), copy the existing clientsettings.xml from production. If testing a new console or configuration, deploy from the test console.
Step 5 — Set up a test user data share (if testing configuration changes)
If you are testing a new or modified ProfileUnity configuration — not just a client version upgrade — specify a separate user data share so test users do not read from or write to production profile data.
If only validating a new client version with no configuration changes, this step is optional — the test environment can point at the same user data share as production.
Step 6 — Create a test OU in Active Directory
Create a dedicated OU in Active Directory for your test machine pool. Place only the machines you intend to use for testing in this OU.
Step 7 — Create a test GPO scoped to the test OU
Create a new GPO (or copy your existing ProfileUnity GPO) and link it to the test OU only. Configure the following settings in the GPO, pointing all paths at the test deployment share:
Computer Configuration → Policies → Windows Settings → Scripts → Startup
| Field | Value |
|---|---|
| Script Name | \\domain.com\netlogon\ProfileUnity_Test\LwL.ProfileUnity.Client.Startup.exe |
| Parameters | (none required) |
User Configuration → Policies → Windows Settings → Scripts → Logoff
| Field | Value |
|---|---|
| Script Name | C:\Program Files\ProfileUnity\Client.Net\LwL.ProfileUnity.Client.Logoff.exe |
| Parameters | (none required) |
User Configuration → Policies → Administrative Templates → Classic Administrative Templates → Liquidware Labs → ProfileUnity
| Setting | Value |
|---|---|
| Enabled | Enabled |
| INI File Path | \\domain.com\netlogon\ProfileUnity_Test\Startup |
Step 8 — Create the test machine pool
Move or add the machines you want to use for testing into the test OU. The GPO linked in Step 7 will apply automatically. On the next reboot, the Startup script will run from the test deployment share, configuring those machines with the test client tools and INI path.
Environment Summary
| Component | Production | Test |
|---|---|---|
| Deployment share | \netlogon\ProfileUnity | \netlogon\ProfileUnity_Test |
| Active Directory OU | Computers\ProfileUnity | Computers\ProfileUnity_Test |
| GPO | Production GPO (links to prod OU) | Test GPO (links to test OU only) |
| INI File Path | \netlogon\ProfileUnity\Startup | \netlogon\ProfileUnity_Test\Startup |
| User data share | Production share | Separate test share (if testing config changes) |
| Product | Liquidware ProfileUnity with FlexApp |
| Applies To | ProfileUnity 6.8.x and later |
| Updated | August 12, 2026 |