Reconnect a Remote Desktop connection after rebooting the host

Write "don't forget about $ServerName" on a sticky note and put it on your monitor.

Look at this function that start an RDP Session and at this piece of script for PowerShell .

Look at this piece of script code :

#This piece waits for the Server to come back online . do{$result = $ping.send("ServerName");write-host "." -NoNewLine -ForegroundColor "Red"} until ($result.status -eq "Success")

you could easily add the start RDP call after the loop that wait the host to come back on line . It could be not so difficult to achieve what you want with this two script.

Quick and dirty Powershell script that I use daily:

<#
.Synopsis
Checks for and connects to RDP on a given server.
.Description
This script tests for an open port 3389 (standard Windows RDP), and if it finds it, passes the IP to mstsc.exe. Otherwise it retries indefinitely. Ctrl+C will halt the script.
.Parameter ip
IP or FQDN of a Windows machine to test. Only takes one argument.
.Parameter wait
Will assume that the machine is still up, wait until it stops responding (even once), and then try to connect. Good for machines that are about to reboot.
.Parameter Verbose
Will print a line each time it tries unsuccessfully.
.Example
rdpupyet.ps1 ITG-SRV-INF01 -Verbose
#>
[CmdletBinding()]
param($ip, [switch]$wait)

function Get-DownYet ($ip) {
    Write-Verbose "Waiting for $IP to shut down."
    do {
        try {$up = New-Object System.Net.Sockets.TCPClient -ArgumentList $ip,3389}
        catch {$up = $false}
    }
    until ($up -eq $false)
    Write-Verbose "$IP no longer responding."
}

Write-Verbose "Testing RDP Connection... Ctrl+C to quit."

if ($wait) {Get-DownYet $ip}
do {
    try {$success = New-Object System.Net.Sockets.TCPClient -ArgumentList $ip,3389}
    catch {Write-Verbose "RDP not active. Retrying."}
}
while (!$success)

mstsc.exe /v:$ip /admin

Doesn't time out, I'm afraid. But that could be easily added, along with a quick beep on successful response.
The bit I'm more happy with (taken from a currently unremembered source on the internet) is that this won't try and connect when the server comes responds to ping - instead, only when the standard RDP port is accessible.

OK, I don't know of anything that will call your cell phone, but if you open a command box, and do "ping -t" minus the quotes, it will keep pinging...not just the 4 times. It is hard to ignore that in the middle of your screen when you get back.

In the alternative, I strongly suggest you use choline daily as your mind is frying at a relatively young age.

I have a simple script on each of my servers that emails me when the server has rebooted. It's a batch file using blat on Windows, perl scripts on Mac and Linux. They are triggered by whatever means is appropriate to the OS. e.g. a Machine startup script on Window.

you could create a script that loops

QWINSTA /SERVER:myserver "RDP-TCP"

this is a quick way to see what users are connected to a server, this particular syntax would looks specifically for the RDP listen session on that server, once that visible it should be possible to logon, i use the command slightly differently in a script that actually crawls around 60 servers, and identifies where on the network a user is logged in.

There are a couple of scripts available for this now, see:

• http://www.justaprogrammer.net/2012/01/07/making-an-rdp-connection-to-a-server-you-just-rebooted-with-powershell/ (LINK DEAD. Archived here.)
• and my script (having seen neither of the others): http://www.akaplan.com/blog/?p=999