One of the Win2k8R2 running client access Exchange as upgraded to SP1. Did the same for other servers. Only one came up with issue. Checked the version of rdpcorekmts.dll version on the server with issue
with issue: version 6.1.7600.16952
without issue with sp1 version: 6.1.7601.17514
Followed the solution from here:
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f5855b60-f29c-4c90-b364-e364589e5267
Just a quick note the file is update by Windows Update KB2667402 not KB2621440. Please see http://support.microsoft.com/kb/2667402 for more details.
1) Connect remotely to affected server using the Computer Management Console
2) Stop the Remote Desktop Services
3) Take Ownership of file C:\Windows\System32\rdpcorekmts.dll and assign full NTFS permissions to your account
4) Rename file to rdpcorekmts.old
5) Copy file rdpcorekmts.dll from a non-patched server. I used another one of our domain controllers just to be safe.
6) Start the Remote Desktop Services
7) Test RDP login to server
WORKED FINE.
with issue: version 6.1.7600.16952
without issue with sp1 version: 6.1.7601.17514
Followed the solution from here:
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f5855b60-f29c-4c90-b364-e364589e5267
Just a quick note the file is update by Windows Update KB2667402 not KB2621440. Please see http://support.microsoft.com/kb/2667402 for more details.
1) Connect remotely to affected server using the Computer Management Console
2) Stop the Remote Desktop Services
3) Take Ownership of file C:\Windows\System32\rdpcorekmts.dll and assign full NTFS permissions to your account
4) Rename file to rdpcorekmts.old
5) Copy file rdpcorekmts.dll from a non-patched server. I used another one of our domain controllers just to be safe.
6) Start the Remote Desktop Services
7) Test RDP login to server
WORKED FINE.
This worked like a champ...glad you found this and shared
ReplyDeleteIm glad that it helped you out. Thanks for leaving the comment.
DeleteGood morning, I had exactly the same. I've just run another windows update and it was fixed.
ReplyDeleteExcellent find! Thanks a bunch for posting Rahul!!
ReplyDeleteThanks! Worked like a charm for me.
ReplyDeleteThis worked for my company and one of our servers as well! Thanks for posting this Rahul!
ReplyDeleteThanks, this worked for me
ReplyDeleteThanks! After two hours this resolved an issue for a node in our xenapp server farm
ReplyDelete