Diagnose remote Windows Client installation failures — admin share access, UAC, DNS, Active Directory trust issues — and common uninstallation errors.
IN SAAS ONLY: the Windows Client can only be installed locally — none of the remote-installation issues below apply.
Most remote Windows Client installation and uninstallation issues trace back to network configuration or system settings. Before troubleshooting further, confirm the user account has administrative permissions on the target computer, and that it meets the installation prerequisites.
”The user does not have the required permissions on the remote host”
There is no access to network shares
Remote installation needs access to the target computer’s administrative shares.Check it:
1
Try opening the admin share
In Windows Explorer, enter \\<target_computer_IP_or_name>\admin$ in the address bar and press Enter.
2
Enter credentials
In the Enter Network Password window, enter administrator credentials.
3
Confirm access
If accepted, the system folder (by default C:\Windows) opens.
If step 1 fails:
Run ping <target_computer_name_or_IP> from a command prompt. No replies → check the network connection. Replies but still no share access → confirm the firewall is disabled on the target, that the Sharing Wizard is disabled, and that the Server system service is running on the target.
If step 3 fails (login error):
Confirm the credentials are correct and belong to a domain or local administrator account, that the account’s password isn’t empty, and try entering the username as <domain_name>\<username> (domain-joined) or <computer_name>\<username> (workgroup).
Fix — enable the Local Account Token Filter Policy (a known Windows issue that blocks remote installs):
1
Open Registry Editor
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
2
Set the value
If LocalAccountTokenFilterPolicy exists, set it to 1. If it doesn’t exist, create a new DWORD Value named LocalAccountTokenFilterPolicy and set it to 1.
The DNS service is unavailable
Run ping <computer_name>. No response means the DNS service may be unavailable on your network — try the target’s IP address instead of its name. To fix DNS itself, see your Windows Server troubleshooting documentation (on Windows Server 2003, netdiag.exe can help).
UAC is enabled (Windows 11/10/8/7)
If admin shares are reachable but remote Client installation still fails, User Account Control (enabled by default) may be blocking it.
1
Open Registry Editor
Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System.
2
Disable UAC
Set the EnableLUA value to 0.
3
Reboot
Restart the Client computer to apply the change.
Active Directory errors
Caused by a missing trusted domain object (TDO) representing the trust relationship between a parent and child AD domain — typically seen with two or more replicated domains.Fix: in Active Directory Users and Computers, open the System container. If no TDO is present, reset the trust between the parent and child domain controllers.
Errors in the Service Principal Name (SPN) for the domain
Happens when the SPN for the domain hosting a replica hasn’t yet propagated to the domain containing the account used to run Dcpromo.exe — often just replication latency.Fix: log in with the child domain’s admin, or wait for replication to complete and use the root admin account instead.
Two computers have the same name
A computer in the child domain shares a name with one in the parent domain.Fix: rename the computer in the parent domain.
"The host is unavailable now or turned off. Try again later."
Shown when clicking Uninstall Client(s) for a Client that’s offline or can’t reach the Application Server. Either wait until it shows online, or uninstall it locally on the Client computer:
