User Tools

Site Tools


microsoft:terminalserver

Microsoft - Terminal Server / Remote Desktop

Documentation

MS KB Articles

Server 2012

Firewall

RD Licensing

“Terminal Server Licensing uses Remote Procedure Call (RPC) over port 135, and a dynamically assigned port above 1024.”
Source: Microsoft Windows Server Forum - Does anyone know the appropriate firewall rules to allow RD License Server access?

Articles/Blogposts

Windows Server 2012 / R2

Blogs

Clients

rdesktop A Remote Desktop Protocol Client for accessing Windows NT Terminal Server.
Jacco's rdesktop page for the OS/2 port and links to other rdesktop.
properJavaRDP Java based RDP client based on rdesktop.
Elusiva - Open Source JavaRDP Java based RDP client based on rdesktop and properJavaRDP.
Lixia-JavaRDP GNU GPL v3 licensed Java RDP client for Windows Terminal Services based on properJavaRDP.
FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license.

Licensing

Printer Redirection

Miscellaneous

Remotely turn on RDP

Open regedit create a connection to the registry of the remote machine. Change the following key value to 0:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"fDenyTSConnections"=dword:00000000

Now the system has RDP enabled. An RDP connection should now be possible if no further (network)restrictions like (Windows) firewall are in place.

No valid software license was available

A Windows Server 2003 Terminal Server is set to use the license server that grants per user licenses. After logging in to a Juniper SA and setting up an RDP session the following message appeared:

Windows Terminal Server Proxy
No valid software license was available.

Forgot to specify “Per User” with the license server settings on the Terminal Server.
The first error on TechNet - Troubleshooting Remote Desktop Licensing Error Messages gave the clue.

Update the shadow key timestamp

Sometimes you need to update or add registry keys to the shadow key on a Terminal Server.
To let the new keys apply to new user logins, you have to manually update the timestamp key after adding/modifying the registry keys.

Do this:

  1. Modify/add the registry keys
  2. Calculate the number of seconds since 1 januari 1970 (see UTC calculator link)
  3. Modfiy the value of the LatestRegistryKey DWORD below HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\IniFile Times with this new value

Sources:
Ask the Performance Team - Terminal Services - Exploring the Shadows
UTC seconds calculator

Copying files from RDP results in corrupt files

Query the Session Broker / Connection Broker via WMI

Clusters:

Get-WmiObject Win32_SessionDirectoryCluster | Select-Object ClusterName,NumberOfServers | Format-Table -AutoSize

Servers:

Get-WmiObject Win32_SessionDirectoryServer | Select-Object ServerName,ClusterName,NumberOfSessions,ServerWeight | Format-Table -AutoSize

Via: Microsoft - Windows Server Forum - How to read the RD Connect Broker DataBase!!!!

See also:
Microsoft - Windows Dev Center - Win32_SessionDirectoryServer class
Microsoft - Windows Dev Center - Win32_SessionDirectoryCluster class

Server 2012 R2 RemoteApp connects to RDWeb/Gateway instead of session host

Problem: When starting a RemoteApp from the RDWeb page that connects via an RD Gateway to 1 of 2 session hosts the RemoteApp tries to connect to the host address of the RDWeb/Gateway server instead of one of the session hosts / the farm address.

If you download the rdp file that gets downloaded from the RDWeb page (don't use IE, use Firefox), open it in Notepad, and change the RDWeb/Gateway address in the line “full address:s:Name OF RDWeb/Gateway server” to the FQDN farm address the RemoteApp works.

Workaround (fix?): Add the full address of the RD Farm to the CustomRdpProperty on the Session Collection with powershell:

Set-RDSessionCollectionConfiguration -CollectionName "Name of RD Session Collection" -CustomRdpProperty "use
 redirection server name:i:1 `n full address:s:rdfarm.domain.com" 

Replace “Name of RD Session Collection” with the name of your RD session collection.
Replace rdfarm.domain.com with the FQDN of your (internal) RD Farm.

Source for the PowerShell option: Server Fault - RDS, RDWeb, and RemoteApp: How to use public certificate for launching apps on session host?

microsoft/terminalserver.txt · Last modified: 2020/07/23 14:38 by bas