To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. So I have two servers that for some reason stopped allowing rdp connections this morning. I would like to not have to restart the servers. Popular Topics in Windows Server. Which of the following retains the information it's storing when the system power is turned off? Submit ». Pure Capsaicin. Would you like to put your stamp on the shutdown?
Let people know who is in charge, who is restarting their server? Personally, I would avoid this switch, the syntax is tricky the numbers obscure, and it does nothing exciting. That said the idea is sound, it enters a reason for the shutdown in the event log.
For me, this switch is an option, an option that I do not take. Note 2: Here is another example of Shutdown in action. VM Monitor is a clever desktop tool that not only tests that your server is online, but also displays the CPU and memory utilization for each node. Consider making a shortcut to shutdown. The benefit is that you have a GUI to control your remote server restarts.
This must be the first option. After the system is rebooted, restart any registered applications. This can only be used during the time-out period. I then considered what other steps I could take to try and force the server to reboot remotely. I used the PSTools command psexec to see if I could still get command line access to the remote server, and fortunately I could. This basically meant that a system shutdown was already in progress, and therefore the command was unable to force a reboot.
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. I should stress that this was a last resort, and not something that I would recommend doing unless essential:. Anyway, 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. The operating system on this machine was Windows Server R2.
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:. My RDP session then abruptly ended and the server restarted itself again. 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.
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. Filed under Windows Tagged with A system shutdown is in progress , Force reboot , Please wait for the windows modules installer , psexec , pskill , remote server , Windows Server , winlogon.
Thank you for the very useful info. Excellent suggestion. I ran into exactly this problem, the remote system was partially unresponsive and was clearly not responding to reboot commands. Thanks for this tip! But server is reachable thru ping. Does the account you are logged in with have admin rights on the server you are trying to kill the process on? I get the following error message when i try to pskill winlogon.
Pingback: Force reboot of a remote server Linewalker Tech Blog. Pingback: Confluence: ITdoc Import. Pingback: Remote shutdown itdamage. Worked for me as well. Worth noting for me however is how earlier in my career this was really make or break stuff.
This tool worked well! Killing the winlogon process worked for me, thanks for the tip. Looks like it turned out to be Windows Updates that was the culprit that caused the botched reboot. Thanks for the tip, remotely killing the winlogon process using PSkill worked for me and the server rebooted shortly thereafter. I had to kill the winlogon and trustedinstaller.
Daniel Winks Daniel Winks 1 1 silver badge 2 2 bronze badges. So far this is the only answer that actually answered the question. I know all about kvms and hard reboots. I did NOT know about the killing lsass. For my hung Server machine killing csrss did the trick.
It initiated a BSOD event, which took a very long time to memory dump, but afterwards the machine came back up more or less operational. At least operational enough that I could log in and begin troubleshooting the underlying cause. I found the pskill advice here: community. Log into your KVM unit Trigger a hard reset. Bryan 7, 14 14 gold badges 67 67 silver badges 92 92 bronze badges. TomTom TomTom I don't have my hands on the purse strings, and the system is still up. So I'm looking for a way to soft cycle it.
Thee is none. This is why tehre is special tech that is - when bought wihth a server - very cheap. Someone on your end botchered that, now live with it. In otherwords a relay that closes momentarily when you ping it with a code. Wire it across the reset switch and give it a thump when the server dies.
Then you can have a "Real Server".
0コメント