We need help for a Windows Server 2019 Standard

Hi Werner,

The error you’re seeing is not actually tied to the RDS CAL count but to the way the Group Policy drive mapping is attempting to connect. The message “No further connections can be established…” typically comes from SMB session limits when the same user account is already consuming multiple connections to the same share. On a terminal server, each session can try to establish its own SMB connection, and if the backend file server enforces a per‑user limit, you’ll hit this condition even though you only have two RDS licenses in use. The secondary symptom with gpt.ini access failing is a direct consequence of that blocked SMB session, which explains why Explorer can still open the file but the policy engine cannot.

To resolve this, check the file server’s session limits under HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and confirm that MaxMpxCt or MaxWorkItems are not set too low. Also verify that the Group Policy drive mapping is not configured with “Reconnect” or “Update” in a way that forces redundant connections per session. If the same user account is being used on multiple machines, consider separating service accounts or adjusting the SMB session limit on the file server.

Give it a try and let me know the result, can't wait to hear!

Harry.

The error messages point to two separate but related issues: Remote Desktop licensing/connection limits and Group Policy processing on the terminal server.

1. Remote Desktop connection limits

The message "No further connections can be established to the remote computer because the maximum number of clients are already connected to this computer" indicates that the server is hitting a connection limit, not a Group Policy limit.

From the provided context:

• A Windows Server without the full Remote Desktop Services (Terminal Services) role supports only two concurrent remote connections for administrative purposes.
• To allow more than two administrative connections or multiple user connections, the Terminal Services/Remote Desktop Services role must be installed and appropriate client access licenses (CALs) must be in place.

Action points:

• Verify that the Remote Desktop Services role is correctly installed and configured for user sessions, not just for administrative connections.
• Confirm that the licensing mode and CALs match the intended usage (per user/per device) and that the licensing server is reachable.
• Ensure that there are no “stuck” or disconnected sessions consuming the available slots; log them off from Server Manager or Remote Desktop Services Manager.

2. Group Policy drive mapping and gpt.ini access error

The drive mapping GPO works on the local PCs but fails in the terminal server session, with an error about accessing gpt.ini. In the context, Group Policy troubleshooting for drive mappings focuses on:

• Confirming that the GPO is applicable and processed.
• Using tools such as gpresult and Group Policy operational logs to verify that the GPO is applied.

Action points based on the context:

1. Verify GPO application in the terminal server session
   • Log on to the terminal server with the affected user.
   • Run:
     • gpresult /h appliedgpo.htm and open the report to confirm that the drive-mapping GPO is listed as applicable.
   • Check the Group Policy operational log (Microsoft-Windows-GroupPolicy/Operational) for events indicating whether the GPO and the Drive Maps extension were processed successfully.
2. Collect detailed Group Policy and Procmon traces (if needed)
   • Use the TSS tool as described:
     • Download TSS and run TSS.ps1 -Start -Scenario ADS_GPOEx -Procmon before logging on with the affected user.
     • After sign-in, run gpresult /h appliedgpo.htm to confirm applicability.
     • Stop TSS and analyze the collected Group Policy operational log and Procmon trace to see whether the drive is mapped and then removed or never created.
3. Check for processes removing the mapped drive
   • If the drive appears briefly and then disappears, use Procmon with a filter on the drive letter (for example, Z:) to identify any process (such as cmd.exe or net.exe) that might be deleting the mapped drive during logon.
4. gpt.ini access
   • Even if the path to gpt.ini is accessible in Explorer, Group Policy processing may still fail if:
     • The connection is interrupted (for example, due to the Remote Desktop connection limit issue).
     • There are transient access or network issues during policy refresh.
   • Resolving the Remote Desktop connection limit and ensuring stable sessions is a prerequisite to reliable Group Policy processing.

Summary of recommended steps:

• Ensure Remote Desktop Services is properly installed and licensed for user sessions, not just admin connections.
• Clear any excess or disconnected sessions so that only the intended two user sessions are active.
• In a working session, verify GPO application with gpresult and Group Policy operational logs.
• If the drive still fails to map, collect TSS/Procmon traces to see whether another process or script is interfering with the mapped drive.

References:

• Remote Desktop disconnected or can't connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2003
• Scenario guide: GPO to map a network drive doesn't apply as expected