So in summary, if you want to save yourself a long trip, to most likely press a power or reset switch, you may want to try the above first.
RESTART WINDOWS SERVER 2012 REMOTE DESKTOP UPDATE
On checking the event log and windows update log I was able to verify that all the updates had installed OK, and there were no other errors worthy of note.
Thankfully, after a few minutes and another ‘configuring updates’ message, logon continued and ther server was back up and running. Again, when it was back up I tried to RDP the server again and received the ‘Please wait for the windows modules installer message’ for a second time. My RDP session then abruptly ended and the server restarted itself again. 1 DPI scaling option and the required scaling level and then restart your. The machine sat like that for quite some time, and then started ‘Configuring Updates’. 1 and Windows Server 2012 R2, Remote Desktop Connection client (mstsc. Please wait for the Windows Modules Installer I was able to enter my credentials and the logon process appeared to start, but after a few seconds the following message appeared on the screen: After the server came back up (verified by ping -t REMOTE_SERVER_NAME) I tried to RDP the box again. The operating system on this machine was Windows Server 2008 R2. I should stress that this was a last resort, and not something that I would recommend doing unless essential:Īnyway, after another few minutes the remote server did finally restart, although there are a few other things that I should mention that happened in the process. In the end I used the pskill command to stop the winlogon service on the remote server to try and release whichever process wass causing the server to hang on shutdown. To do this, the user has the following two options. This is important because it allows users to work remotely on the server.
RESTART WINDOWS SERVER 2012 REMOTE DESKTOP HOW TO
This basically meant that a system shutdown was already in progress, and therefore the command was unable to force a reboot. In this chapter, we will see how to enable the remote desktop application in Windows Server 2012. Psexec \\REMOTE_SERVER_NAME shutdown /r /t 01 Next I tried to force a reboot of the remote server using psexec and the shutdown command as follows, where REMOTE_SERVER_NAME is the name of the remote server that I was trying to reboot:
I used the PSTools command psexec to see if I could still get command line access to the remote server, and fortunately I could. I was cursing at this point, with the prospect of a long journey the following day to investigate and bring the server back online. I then considered what other steps I could take to try and force the server to reboot remotely. I will still able to ping the server, and access its file shares, but was unable to get RDP access. Once the menu is visible, click on Settings. Note: With Powershell to get help or examples for a cmdlet type (help restart-computer -examples) or (help stop-computer -examples) 3. Once connected to your Windows 2012 server with Remote Desktop, follow these steps: Position your mouse in the bottom right corner of the Remote Desktop screen of your Windows 2012 server. Type either (Restart-Computer) or (Stop-Computer) to restart or shutdown the server. I had an issue last night when a remote server that I was applying windows updates to, hung while it was shutting down. Launch an elevated windows powershell window.
0 kommentar(er)
