Brilliant. Had to add my thanks. I also had RDP borked by this update and the fix by x28x worked. After the script ran, I added Read and Execute and Read permissions for network service to termsrv.dll.
@ x28x Would be it possible to also patch the x86 file for windows 7 ? The files (original unpatched/patched and new) are uploaded into a zip here: pm me for link If you are able to i dont mind updating the previous batch auto patcher to include the x86 and x64 auto deploy. Can someone please confirm with existing x64 patch provided your able to get more than 2 active sessions.
Did the patterns from the last release remain the same in this one? There are a couple weird things about KB2984972, which is an update for RDC 7.1: First, the article doesn't mention (as of right now) which files are updated. Obviously, termsrv.dll is, but.... Second, KB2923545 is an update to RDC 8.1 (for Win7). This article does list which files are updated, and guess what's not on the list? That's right, termsrv.dll. Is it possible that the 8.1 patch doesn't involve termsrv.dll? And would anyone want to be on 7.1 when 8.1 is out (again, not talking version of Windows but rather RDC)?
For the relative novices among us (ie me), could you explain how to change the permissions correctly? I assume there is something wrong with the cacls command--how did you fix it? Thanks!
I made patched binary file for x86 version and fixed install script. anonfiles dot com/file/b34724f065313cbb745f31d73edf3597
Success Well done *** this worked *** file: anonfiles dot com/file/421d8221e150cd696759121280986968 Run as administrator This worked very well and i did not need to remove the KB2984972 . I needed to update the Security Permissions to the termsrv.dll and i added System, Network service, SERVICE, administrators YEA -->> THANKS
Ran as admin on w7 x32, and I get this: Code: SUCCESS: The file (or folder): "C:\Windows\System32\termsrv.dll" now owned by us er "PC\username". C:\Windows\System32\LogFiles\WMI\RtBackup\*: Access is denied. Successfully processed 1 files; Failed processing 1 files 1 file(s) copied. C:\Windows\System32\LogFiles\WMI\RtBackup\*: Access is denied. Successfully processed 1 files; Failed processing 1 files C:\Windows\System32\LogFiles\WMI\RtBackup\*: Access is denied. Successfully processed 1 files; Failed processing 1 files The Remote Desktop Services service is starting. The Remote Desktop Services service was started successfully. Concurrent sessions is working again, though.
@ x28x Would it be possible to maybe update the install script to maybe included the filewall options and registry keys (multi login and blank passwords). Attached is the code from the previous patch. Although it was never included in the original patch, ive got a text file saved that has: Additionally to enable multiple logins you may need: 1 = allow multiple logins 0 = dont allow multiple logins [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core] "EnableConcurrentSessions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "EnableConcurrentSessions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AllowMultipleTSSessions"=dword:00000001 Which i cant remember as being required or not (maybe its only required on server 200x), there is also : reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v MaxDisconnectionTime A "disconnected" session is different from an "idle" session. This setting above is for a session that has disconnected, yet is still logged in and how long until it should be terminated. For session idle disconnect time: reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v MaxIdleTime then to change, (example to give yourself an hour): reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v MaxIdleTime /t REG_DWORD /d "3600000" /f from: social dot technet.microsoft.com/Forums/windowsserver/en-US/facfd1f9-3c1d-4f8e-8090-c6b538ee4bef/terminal-services-rdp-session-timeout?forum=winservergen Which im not sure if it would work, but it would be cool to have an additional option on the batch file to set it if it does (so that disconnected sessions are killed after x period), like i said i don't now if the option is supported (probably not). Finally and most importantly one issue i had with the original patch was RDP was set to listen on a non standard port, the old scripts hard coded to 3389, so it would also be groovy if it was possibly to also be able to prompt/set/specify the listening port in the install script: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber and then set the firewall accordingly: NETSH advfirewall firewall add rule name="Remote Desktop (TCP-In)" program=System profile=public,private,domain dir=in localport=3389 protocol=tcp action=allow description="Inbound rule for the Remote Desktop service to allow RDP traffic. [TCP 3389]" Becomes: NETSH advfirewall firewall add rule name="Remote Desktop (TCP-In)" program=System profile=public,private,domain dir=in localport=%PORTNUMBER% protocol=tcp action=allow description="Inbound rule for the Remote Desktop service to allow RDP traffic. [TCP %PORTNUMBER%]" support dot microsoft.com/kb/306759#LetMeFixItMyselfAlways
you can also patch yourself using hex editor 6.1.7601.18540 64bit search for 8b 87 38 06 00 00 39 87 3c 06 00 00 0f 84 2f c3 00 00 replace with B8 00 01 00 00 90 89 87 38 06 00 00 90 90 90 90 90 90 search for 4c 24 60 bb 01 00 00 00 replace with 4c 24 60 bb 00 00 00 00 search for 83 7c 24 50 00 74 18 48 8d replace with 83 7c 24 50 00 eb 18 48 8d
Actually, I updated the permissions to c:\windows\win32\termsrv.dll manually, did not bother to correct the script In my case, I added permissions read and read/execute to network service I also removed all other permissions. I am guessing the new script takes care of this, though?
Update october 15-18 2014 broke it looks like i have file version 6.2.9200.17048 can anyone please help me with a new hex value or dll. All my computers run on rdp and now they are all broken. If anyone has a new dll/ hex value PLEASE. The workaround with the 63_RDPWrap does not work for me either. Any advice would be fantastic. thank you so much!
That worked for win7x64--Thanks! Though I screwed up the permissions--I'm sure there is a "right" way to do it, but I did it manually like 000111 said--here's a link which sort of explains how, or at least the reverse: www dot askvg dot com/guide-how-to-restore-trustedinstaller-as-default-owner-of-a-file-or-folder-in-windows. The permissions are now looser--now the System and admins have full control. Oh well--there are worse risks. I also stopped/started manually as well, in the Services GUI "Remote Desktop Services", before making swap. For those looking for a hex editor, HxD worked the best for find/replace. Would love the Win8.1x64 hex edits if anyone knows them.
I'm pretty stuck to tell you the truth. I've got a Window 8 Pro box which is now broken by this latest windows update and I need to get multiple concurrent RDP users working. Can anyone please point me to the exact steps required, as well as which patch will reliably work on Windows 8. Thanks in advance for any assistance.
NO, move away from Win 8 & update to 8.1 Update1 Then you will have version of termsrv.dll that is easily correctable