While the console redirection was a nice way to connect to a server when the existing two sessions were in use, it had its limitations. The number one problem with session zero is interactive device driver installations that occur via a plug and play enumeration of multiple devices.
This most frequently occurs when adding multi-port serial adapters, a USB hub with multiple ports, or any other device that has a controller and subsequent individual devices. The root device would install correctly, but whenever the individual ports were enumerated, this functionality would not work correctly via a console redirected remote desktop session. For the newest version of the remote desktop client software 6. These changes are outlined in the Microsoft KB article Stay on top of the latest Windows Server and Windows Server tips and tricks with our free Windows Server newsletter, delivered each Wednesday.
Automatically sign up today! Active Oldest Votes. Improve this answer. TLud TLud 11 1 1 bronze badge. Also when this balck screen happens, I cant even log on while sitting in front of the server itself. Also trying to log on with different user accounts gives the same results. Sounds like your server is seriously hozed. It sounds like something at the kernel-level is seriously screwed up.
Have you tried logging in at the console with the same credentials? Same results? There is no easy programmatic way of overriding the sequence Show 3 more comments. Sign up or log in Sign up using Google.
Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science.
Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 0. If you connect to server, after running task manager users tab , there is a session column which say what kind of session we currently are running and what kind of sessions other users connected are running. If it is physical contact, you'll get 'console'; if it is remote, you'll get 'RDP-Tcp x' where x is the number of remote connection. So it cannot be that in Win console and remote sessions are treated as the same.
I haven't tried the hotfix, but it probably simply creates new session for remote connection, leaving console session intact. In our case, using VMWare will be the console session, and mstsc will be the additional sessions. Also I use Remote desktop connection Manger free tool from MS that allows you to manage and connect to multiple Remote desktops. I am having the same issue. To continue this discussion, please ask a new question. Spiceworks Help Desk.
The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Hi, Have Microsoft changed the way that remote desktop to server R2 works? Regards, Dan. Best Answer. Ian Jan 27, at UTC.
View this "Best Answer" in the replies below ». Thai Pepper. Rune This person is a verified professional.
0コメント