Remote Desktop/Terminal Services Resources

Cadzow Knowledgebase Articles

• Obtaining Remote Desktop Client

• Using Microsoft Remote Desktop on MacOS X

• What Is Terminal Services?

• How safe is Terminal Services?

• Using Non-Standard Ports in Terminal Services/Remote Desktop

• Connecting to a Terminal Services session (using the Standalone Remote Desktop client)

• Connecting to a Terminal Services session (using the web-based Remote Desktop client)

• Copying files from a Terminal Services session

• Logging off from a Terminal Services session

• Closing a Disconnected Terminal Services session

• Configuring Windows XP for Remote Desktop

• Windows XP Concurrent Users in Service Pack 2

Issues, Problems & Remedies

• Windows 2003 Post-Setup Steps for Remote Desktop Services

• Terminal Services Loses Printer After Disconnect

• Terminal Services/Remote Desktop Inaccessible After Reboot

• Cannot Connect to Terminal Services (Remote Desktop) Server: No Client Access Licences Available

• Remote Desktop/Terminal Services Unavailable After Reboot

• Cannot Connect to Windows 2008/R2 Remote Desktop Services from Windows 2000

• Remote Desktop Print Jobs Vanish

• Cadzow 2000 Terminal Services issues

Microsoft Knowledgebase Articles

• Smart-Sizing the Remote Desktop Client

• Details of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server

• Differences between Remote Desktop in Windows XP Home and Windows XP Professional

• Description of Terminal Services utilities

• Description of Terminal Services printer architecture

• How to configure the client to redirect only the default printer

• Locking down Terminal Services in a domain environment

• Webcast about new features in Windows 2003 Terminal Services

• Document discussing using Terminal Services in a Small Business Server 2003 environment

  Note: SBS 2003 does not support Terminal Services on the main SBS 2003 server, which is different from SBS 2000. It does, however, allow the two concurrent administrative terminal services logins.

• Description of User CALs (Client Access Licenses) and Device CALs in Windows 2003

  The main point from this article is that a Terminal Services Licensing Server can only supply Device CALs or User CALs, not both, and the CAL type being used must be set in the Terminal Services Configuration applet:

  

  If not, the Terminal Services Licensing Server will issue temporary CALs which will appear as Temporary Licenses for Windows Server 2003 - Terminal Server Per Device CAL Token or Temporary Licenses for Windows Server 2003 - Terminal Server Per User CAL Token.

• Event ID 1009 is logged on a Terminal Server License server in a Windows Server 2003-based domain

• Remote desktop is not displayed in Full-Screen mode with screen resolution of 1366x768

• Collection of hotfixes for Remote Desktop Services on Windows Server 2008 R2 SP1

• Windows XP systems may need a .NET Framework 3.0 update if unable to print (“Windows Presentation Foundation terminal server print W has encountered a problem and needs to close”)

Other

• Dshield analysis of traffic on default Terminal Services port