Microsoft RDP client (aka “Remote Desktop Connection” or “Terminal Services Client”) allows you to connect from your Windows station to other Windows servers. Version 6.1 was released in 2008 and nowadays many popular tools (such as mRemoteNG) state it as a requirement. Unfortunately, this version is available for Windows XP/Vista and Windows Server 2008, but not for Windows Server 2003.
So, how can you install RDP client 6.1 on Windows Server 2003?
It appears that in March 2011 Microsoft released security update for RDP client 6.0 and 6.1 – which can be installed on Windows Server, since the original RDP client 6.0 is supported there. Now, pay attention to this note in the “more information” section:
Bottom line? Take the official RDP client 6.0, download KB 2481109 for Windows Server 2003 (the security update mentioned above) – and you are ready to run with RDP client 6.1 on your Windows Server 2003!
11 thoughts on “How to install RDP 6.1 on Windows Server 2003”
Works GREAT! Thanks for the help.
Greetings! Very helpful advice in this particular article!
It’s the little changes which will make the most significant changes.
Thanks a lot for sharing!
It doesn’t work for me 🙁
I get this logfile:
0.656: Condition succeeded for section Presence.RDCInstallBlock.Section in Line 1 of PreRequisite
0.656: FileVersion of C:\WINDOWS\system32\mstscax.dll is Greater or Equal To 6.0.6000.0
0.656: FileVersion of C:\WINDOWS\system32\mstscax.dll is Greater Than 6.0.6001.0
0.656: Second Condition in Test.RDCInstallBlock.Section Failed
0.656: Condition Check for Line 2 of PreRequisite returned FALSE
Looks like you have version newer than 6.1 on your server:
FileVersion of C:\WINDOWS\system32\mstscax.dll is Greater Than 6.0.6001.0
You’re right: it seems i have 6.0.6001.18564
But i can’t connect however to a tsweb gateway server 🙁
I get every time the “certificate subject name does not match” error 🙁
Well, this is not related to RDP…
Maybe it is because the “certificate subject name does not match” – that is, the name in the certificate that your TSWeb server presents to the client does not match the name of the TSWeb server as known to the client? 🙂
Ok. I read a topic like this and i thought the problem was related to RDP6.0/6.1
I continue my investigation 🙂
Do you know if there’s an incompatibility through Windows 2003 RDP clients and the ts gateway running on more recent windows servers?
(sorry for my bad English…)
I never used TSWeb gateway, so nothing to add here. Sorry 🙁
the certificate i’m using is a *wildcard certificate.
On Windows 7 is working well, but on Windows 2003 i’m getting this error: http://blogs.technet.com/blogfiles/sbs/WindowsLiveWriter/ReceivingCertificateErrorsWhenConnecting_DC81/clip_image014_thumb.jpg
I see some TechNet posts that sound related, for example this one and this one. Maybe there are more… Good luck there!
Thanks for this great tip, long live XP & Server 2003; the best OS ever created out of Redmond 🙂