Force reboot of a remote server that has hung shutting down

I had a problem to reboot a remote server. I googled it and found this article. The PSKILL command solved the issue.
********************************************

I had an issue last night when a remote server that I was applying windows updates to, hung while it was shutting down. I will still able to ping the server, and access its file shares, but was unable to get RDP access. 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 used the PSTools command psexec to see if I could still get command line access to the remote server, and fortunately I could. 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:

psexec \\REMOTE_SERVER_NAME shutdown /r /t 01

alternatively you could use:
shutdown /m \\REMOTE_SERVERNAME /r /t 01

This returned the following error:
1115 A system shutdown is in progress

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:

pskill \\REMOTE_SERVER_NAME winlogon

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 2008 R2. After the server came back up (verified by ping -t REMOTE_SERVER_NAME) I tried to RDP the box again. 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:
Please wait for the Windows Modules Installer
The machine sat like that for quite some time, and then started ‘Configuring Updates’. My RDP session then abruptly ended and the server restarted itself again. 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. Thankfully, after a few minutes and another ‘configuring updates’ message, logon continued and ther server was back up and running. 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.

http://oasysadmin.com/2012/03/02/force-reboot-of-a-remote-server-that-has-hung-shutting-down/  

Chat with Bother support for adding Brother MFC7860DW as network scanner

Connecting to server...
Found available agent: Hugo  .  You can chat now.
Hugo  : Good morning!
Hugo  : How may I help you?
Jimmy: hi
Jimmy: good morning
Jimmy: I have two MFC7860DW in our office
Jimmy: When I installed CC4, it can only find one machine, not the second one
Jimmy: I can use IE to access both printers
Jimmy: I can also add both printers
Jimmy: but my computer can only find one scanner, ont the other
Hugo  : Mmm have you tried installing over it?
Jimmy: I went to my-computer->network, I can see both machines, but when I tried to install the one has problem, only printer was installed
Jimmy: What do you mean " installing over it"
Hugo  : Yes when you install it will only install one driver for the printer, and one for the scanner
Hugo  : you could add another printer driver manually but not another scanner
Hugo  : you need to isntall the disc again
Hugo  : but when you get to the connection type both machines should show up, select the one that is not already installed
Jimmy: I wil call the good machine: brother A, and the bad machine Brother B.
Jimmy: I tried to run the Windows wizard for adding scanner, but the wizard can only find Brother A
Hugo  : did you connect Brother B to the network? can you print to brother B?
Jimmy: Yes, I can use IE to remote control both A and B
Jimmy: on that web interface, ther is an option: "find devices"
Jimmy: I clicked that, from Brother B, I can see BRother A and the status is ready
Jimmy: from Brother A, I can find brother B as well, but the status is blank
Hugo  : yes what's the operating system on the computer?
Jimmy: The computer is Windows 7
Hugo  : ok and can you tell me what the LCD screen of Brother B is currently saying?
Jimmy: it is sleep
Hugo  : ok on brother B press Menu, 6, 2, 1, 2 and let me know the address
Jimmy: The printer is connected with cable
Jimmy: Brother A is connected with wireless network
Hugo  : network cable or usb cable?
Jimmy: when I tried to connected Brother B to the wireless network, I kept getting message that WLAN router cannot be detected
Jimmy: Brother B has both USB and network cable connected
Jimmy: The computer with USB cable connected has no problem to access Brother B
Hugo  : ok then press Menu, 6, 1, ,1 2 on brother B and let me know the address
Jimmy: but another computer tried to connect to it via network failed
Jimmy: the address is 192.168.40.10
Hugo  : ok, you'll need to install the mfl-pro suite again
Hugo  : either from the disc or online
Hugo  : select Wireless Connection and check Custom Install
Hugo  : when you get to a point that says Select the machine you want to isntall
Chose the one with 192.168.40.10 next to it
Hugo  : when the computer restarts you'll have both options in control center
Jimmy: OK, I will try it, thanks very much
Hugo  : No problem!
Hugo  : Let us know if there is any issue
Jimmy: Since I am not in front of the printer, I will do it later.
Jimmy: Yes, I will
Jimmy: Have a good day

Note: I think disable and enable the LAN port did the trick. I disable the LAN port and enable the WLAN posrt and try to use wireless network. Unfortunately the machine was not able to connect to my wireless network, so I have to change back to the wired network the next day. This time, when I click "find devices" for the other Brother's web interface, I can see the status of the problem machine, which was blank the other day.
I did follow the instructions given by Hugo, installed ControlCenter 4 and used Custom Install and manually put IP address. This time there is no problem to add that brother machine.