A licensing error message will appear at logon when the ProfileUnity client tools are unable to communicate with the ProfileUnity License Server.
The most common cause is that ClientSettings.xml has not been deployed to the client deployment share, or the client tools have not been updated to read it.
⚠️ Example Error Message
No ProfileUnity License Server defined. Please contact your system administrator.
Example error message displayed at logon on the ProfileUnity client machine
Follow the steps below in order.
Step 1 — Deploy ClientSettings.xml
ClientSettings.xml contains the connection string the client uses for license communication. It must be present in the deployment share before client tools can locate the License Server.
- Log in to the ProfileUnity Management Console and navigate to the Administration page.
- In the Client Settings section, verify the following:
- ProfileDisk and FlexDisk VMDK Mode — Set to Disable ProfileDisk and FlexDisk VMDK only if you are not currently using ProfileDisk.
- Deployment Path — Confirm this matches the location where your ProfileUnity client tools are stored.
- Click Deploy Client Settings. This uploads
ClientSettings.xmlto your Deployment Path. This file contains ProfileDisk information and the connection string used for license communication.
If the client settings path is configured in Group Policy, set the Deployment Path to the same share that is configured in the GPO policy.
Step 2: Option A — Update Client Tools to Read the New ClientSettings.xml
With ClientSettings.xml deployed, use one of the following options to push the update to your endpoints:
Option 1 — GPO Computer Startup Script (recommended)
If the GPO Computer Startup Script is configured, restart or refresh your desktops or pool. The client will automatically pick up the new ClientSettings.xml on next startup.
Option 2 — Re-run the ProfileUnity Installer
If there is no GPO Computer Startup Script, with ClientSettings.xml in place, re-run the ProfileUnity installer from an elevated Command Prompt:
Then recompose the pool.
Step 2: Option B — Deploy the License Server Connection String through Group Policy
Within the ProfileUnity management console, navigate to Administration > Client Settings.
Click on the Manage Connection Strings button.
Click on the Copy to Clipboard button to copy the License Server Connection String.
Edit your ProfileUnity GPO.
- Go to Computer Configuration > Policies > Administrative Templates > Classic Administrative Templates (ADM) > Liquidware Labs > ProfileUnity.
A list of settings for 32-bit and 64-bit computers is displayed.
Note: The 32-bit values must match the 64-bit values, regardless of what architecture is in use. - Enable the License Server Connection String setting and paste in the copied the License Server Connection String in the options section.
After the changes have been made to your ProfileUnity GPO. restart or refresh your desktops or pool.
Test Connectivity to the License Server
If the issue persists after completing both steps, verify network connectivity between the client and the ProfileUnity Console server using the commands below. Run from an affected desktop session.
ProfileUnity 6.8.5 and later (port 443):
ProfileUnity 6.8.4 and earlier (port 5672):
ℹ️ If the connection test fails
Confirm the following three services are running on the ProfileUnity Console server:
- Liquidware Labs ProfileUnity Service
- Liquidware Labs ProfileUnity License Service
- MongoDB
Also check for any proxy or firewall rules blocking outbound port 443 TCP from client machines to the ProfileUnity Console server.
ProfileUnity Network Port Reference
ProfileUnity Network Ports — *Port 8000 is default but can be modified in the Administration section of the ProfileUnity Management Console
The following table summarizes the ports required for ProfileUnity communication. Port 8000 is the default console port and can be modified in the Administration section of the ProfileUnity Management Console.
| Port | Protocol | From → To | Purpose |
|---|---|---|---|
| 443 | TCP | Desktops → ProfileUnity Servers | License communication (6.8.5+). Also Admin PC → ProfileUnity Servers. |
| 8000 | TCP | Desktops, Admin PC, FlexApp Packager → ProfileUnity Servers | ProfileUnity Management Console web interface. Default port; can be changed in Administration settings. |
| 27017 | TCP | ProfileUnity Servers (inter-node) | MongoDB. Required for clustered ProfileUnity server communication. |
| 445 | TCP / UDP | Desktops, Admin PC, ProfileUnity Servers → File Shares / Domain Controllers | SMB. Required for deployment share access (ClientSettings.xml, client tools, profiles, FlexApps, ProfileDisks). |
| 389 | TCP / UDP | ProfileUnity Servers → Domain Controllers | LDAP. Active Directory queries for user and group lookups. |
| 5672 | TCP | Desktops → ProfileUnity Servers | License communication for ProfileUnity 6.8.4 and earlier only. Not required for 6.8.5+. |
In a clustered deployment, ports 443, 8000, and 27017 must be open between all ProfileUnity server nodes in addition to the client-facing ports above.
If the Issue Persists — Files to Send to Support
If you are still experiencing licensing issues after completing both steps and verifying connectivity, open a support case at support.liquidware.com and attach the following three files:
Example: Client licensing service log highlighted in C:\Windows\Temp\ProfileUnity
| File | Location |
|---|---|
| Client License Service log | C:\Windows\Temp\ProfileUnity\clientlicensingservice_*.log |
| License Service config | C:\Program Files\ProfileUnity\Client.NET\LwL.ProfileUnity.Client.License.Service.exe.config |
| ClientSettings.xml | \netlogon\profileunity\ (your deployment share) |
The ProfileUnity Diagnostic Tool can collect these files automatically. See: How to Collect Logs Using the Diagnostic Tool