- #Remote desktop server windows 8.1 how to#
- #Remote desktop server windows 8.1 update#
- #Remote desktop server windows 8.1 Patch#
- #Remote desktop server windows 8.1 full#
Log Name: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational When transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to 8 (error code 0x80004005).
#Remote desktop server windows 8.1 update#
Visual Studio Ultimate 2013 Update 4 Windows 8.1 Enterprise (圆4) Client Log Messages I set up a VM in Azure so that I could remote in from my Surface 2 and do some development on Store apps when I am not home. Ironically, I would like to use this VM mainly on the (anything else, practically), works fine. What setting on that VM Image could prevent me from connecting ONLY from the Surface 2, but still work from iOS, other Windows computers and devices? It's embarrassing that I had to troubleshoot this with my iPad.Īnyone have any solutions that would allow me to use Remote Desktop (either of the two versions on the Surface 2 Win 8.1) from the Surface 2 to a Windows 8.1 Server? If you are looking for doing the same thing on Windows 7 or Windows 10 computers, check out the following posts.Connecting to the Azure VM Image (mentioned below) via RDP gives me an error message as if my user/password are incorrect. On the console, you will see something like this that shows two different user accounts simultaneously signed on at the same time. I fired up the patched Windows 8 and logged in through RDP client using two different user accounts. Restart Remote Desktop Services or reboot your computer.
#Remote desktop server windows 8.1 Patch#
Make a copy of original termsrv.dll file and overwrite it with one from zipped patch file downloaded on step 1.ĥ.
#Remote desktop server windows 8.1 full#
And give that user a full control permission on termsrv.dll file.Ĥ. Replace the ownership of the termsrv.dll file in Windows\System32 folder with a user account that has local admin privilege.
Download the zipped patch file (direct download link) that includes both original and patched version of termsrv.dll file for both 32-bit and 64-bit editions.Ģ. Stop Remote Desktop Services service from Services MMC console.ģ. If you are on Windows 8.1 and would like to do the same, follow the following steps.ġ. The above method works fine in Windows 8 but not in Windows 8.1. HKLM\System\CurrentControlSet\Control\Terminal Server\Īnd that’s it and enjoy. So what kind of magic this patcher did to make this happen? Basically, it did two things, one to patch the termsrv.dll to allow multi-concurrent users to log in, and one to make two registry changes to allow the TS connection in. I fired up my laptop and launched RDP client twice and was able to connect to this patched Windows 8 computer with two different user accounts I previously set up.
Save all your work, and double-click the file to launch the patcher, which applies the patch to the termsrv.dll file and automatically restarts your computer in 8 seconds.Īll done and ready to rock after the reboot.
#Remote desktop server windows 8.1 how to#
Go to the bottom of the page to check the updates how to get Windows 8.1 patched up with multi-current RDP sessions. Note that the patcher is no longer working on Windows 8.1. Once you’ve done the backup, go to this webpage and download “Windows 8 Patcher.exe” file from there. Warning: before you do the patch, create a system restore point or back up termsrv.dll file in c:\windows\system32 folder, just in case something goes wrong along the way. If you continue, they will be disconnected.īasically, it’s telling you that you can switch users while still keeping all users’ data alive but you can only access one user account at any given time.īut here is a tweaking tool that can alter this setting to literally allow unlimited concurrent user access, through remote desktop connection. Here is what you get if you are trying to log 2 or more accounts into one Windows 8 machine at the same time:Īnother user is signed in. Note: new updated info on Windows 8.1 at the bottom of this post.
0 kommentar(er)
