Windows 10: RDP - how can I reboot remote machine

Hi there

It's been AGES since I've done this - but is there any way of rebooting a remote Windows machine from RDP.

The problem probably needs Windows login as it boots so how to connect ??

I'm sure it's possible without having things like Network boot in a Nic.

(I've seen people run Windows servers essentially headless so it must be possible).

Easy enough in Linux - there's all sorts of daemons / processes that can start at boot so ssh and all sorts of other things possible but I'm a total stranger to most of Windows networking apart from basic home LANS.

Cheers
jimbo

:)

 

am I being scammed?

how does "Turn off Remote Access to your machine" have anything to do with someone that has allowed suspicious remote access ... This is not RDP...

 

Windows10 Home

It's actually the opposite: You can launch an RDP session from a Windows 10 Home machine but only a Windows 10 Professional machine can act as an RDP host.

 

I restart my Windows remote hosts in this simple way:




Command: shutdown /r /t 0 -- OR -- shutdown -r -t 0

You can then reconnect to remote host as soon as it has booted to Welcome / sign-in screen (network will be reconnected latest at this point).

 

Hi there
@Kari

Thanks !!!

It's so easy to forget this type of stuff if you don't do it regularly

Works fine -- I was thinking that I wouldn't get Logon screen and network connection - but it's working now.

Cheers
jimbo

 

You are welcome Jimbo *Smile

 

I have moved from RDP to using Teamviewer for working with headless systems, just for the convenience, I have a group of systems at home and can switch to any or all at will. you just need to use the setup options for unattended access and make sure that Teamviewer is set to run at boot

 

I openly admit being a Microsoft and especially Windows 10 fan boy. I have no shame, no issues in admitting that, no reason to deny facts *Wink

What it means to me in practical terms is that I never use third party solutions when native Windows apps, tools or features can do the same, even if using native Windows tools would require me to use a few more mouse clicks or an extra command or two. The only advantage I can think of in using TeamViewer is that when disconnecting a remote session it leaves local user signed in whereas RDP by default leaves remote host locked, showing the Welcome / sign-in screen. There might of course be other features in TeamViewer I do not know but as far as I know and what my needs are, I can do anything I need to / want to with RDP.

Even that single advantage I can think of (as told above) is easy to fix in RDP. Here's a post of mine from another thread a year ago to show the fix:

This will end the remote session and unlock the remote host, restoring the current local user's desktop.[/quote]
Instead of disconnecting the remote connection as usual, run the tscon command on remote host. If you want to make it simpler you can create a shortcut for the tscon command on remote host desktop.

 

You simply RDP into the remote machine and issue a Reboot command the same way you'd do it on a physical machine. Nothing special about it.

Older versions of Windows used to prevent direct access to Reboot and Shutdown commands from the GUI when logged in through RDP (so we had to work around it by manually issuing a command-line 'shutdown' command). However, this restriction is gone from Windows 10 - just open the menu, click the power icon and you will see the Reboot command right there. I don't know what is the reason behind this change (and I'd say that the former approach - no Reboot and Shutdown in GUI - made more sense).

Of course, if you are talking about a LAN machine and you have the required credentials you can reboot it without RDP: just use the '/m \\computer' option of 'shutdown' command.