Skip to main content

No ProfileUnity License Server Defined. Please contact your system administrator

Steve Ku
  • Created:
  • Updated:
No ProfileUnity License Server Defined

⚠️ Error Message

No ProfileUnity License Server defined. Please contact your system administrator.

No ProfileUnity License Server defined error popup

The error message displayed at logon on the ProfileUnity client machine

This message appears at logon because 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.

Follow the two steps below in order. Most environments are resolved after Step 1.

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.

  1. Log in to the ProfileUnity Management Console and navigate to the Administration page.
  2. 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.
  3. Click Deploy Client Settings. This uploads ClientSettings.xml to your Deployment Path. This file contains ProfileDisk information and the connection string used for license communication.
ℹ️ GPO Client Settings Path
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 — 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:

lwl.profileunity.client.startup.exe

Then recompose the 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):

powershell Test-NetConnection -Port 443 -ComputerName <IP or FQDN of ProfileUnity Server>

ProfileUnity 6.8.4 and earlier (port 5672):

powershell Test-NetConnection -Port 5672 -ComputerName <IP or FQDN of ProfileUnity Server>
ℹ️ 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 diagram

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+.
Clustered ProfileUnity Servers
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 file in Windows Explorer

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)
💡 Tip
The ProfileUnity Diagnostic Tool can collect these files automatically. See: How to Collect Logs Using the Diagnostic Tool

Related Articles

Related articles