从计算机上托管的ASP.Net页重新启动计算机

Question

I have a computer A which hosts different kind of things:

• A website (is developped using C# and ASP.Net )
• Applications

Our customers have access to the website and sometimes, they will want to reboot the computer A (knowing that it will cut the website during the reboot).

My question is simple : does it exist a way of :

• Rebooting a computer by simply clicking a button on an ASP.Net page ? How would I manage to do so ?
• The same way, is it possible to execute some batch script (executes on the Computer A) when clicking on a button on an ASP.Net page ?

Thanks for your help!

Answer 1

This is secure enough way to do it (as long as password is stored securely)

ProcessStartInfo startInfo = new ProcessStartInfo("shutdown /r /f /t 5");
startInfo.UserName ="user with enough rights";
startInfo.Password ="password";
Process.Start(startInfo);

// /r - restart
// /f - force
// /t 5 - wait 5 seconds

Answer 2

You can do it using System. Diagnostics.Process namespace, Please look at the following link for full process.

http://www.c-sharpcorner.com/UploadFile/yuanwang200409/RemoteRestartWindows09252006141003PM/RemoteRestartWindows.aspx

Answer 3

It would be pretty easy to implement, but the question is if IIS will allow it. You will also open up for exploits, since if someone managed to exploit this, they could chain restart your server.

If you really want to go ahead and implement this, you could simply set up a Web Service call that triggers the following code.

System.Diagnostics.Process.Start("shutdown.exe", "-r -t 0");

Although, it does sounds more like you are looking for a management tool to handle this. I would recommend that you look at one of many tools available to help manage servers remotely. It is important for security that the management software has the ability to give the user specific privileges, like restricting them with access to only reboot the server.

Answer 4

You can execute "shutdown -r" command from C# in command line, see this SO question how to do it. Mind you that the application has to be very well secured, and the application running under IIS will have to have enough user rights.

Edit: Fuji's proposed way works well and doesn't even require elevated process (I didn't expect it to work, whoops ;))