0
I have Windows Server 2012 R2 installed on a desktop I use as a Media/Data/Backup server, and I've always had the problem that when it undergoes any abrupt shutdown, either due to power failure, or force shutdown due to freeze or crash, I am unable to start it back up using Remote Connection. I normally administer it using a laptop, since I don't need a monitor/keyboard as it doesn't normally see use. Even shutdowns using the remote shutdown command get buggy at times, and I need to hook up a screen to log in locally before remote access gets enabled again. How do I configure it to always be available for remote access, so I can ditch my monitor/keyboard?
Are you talking about starting it up remotely from hard off? If that's the case, then you'll need to investigate the Wake-on-Lan capability of your motherboard/NIC. – Michael Frank – 2014-10-23T21:08:21.260
No, I can physically access the desktop, and press the power button to turn it on. What i mean is that once it boots, I need to remotely log in and start the programs that run the streaming service for example, and that remote log in does not work if the shutdown was abrupt. I need to manually log in on the desktop, and not thru my laptop. – Inukun – 2014-10-23T21:33:30.173
To add to Michael Frank, you should also look at your BIOS to power on the machine inthe event of a power loss (and subsequent restoration). If the machine crashes I think this needs some attention as it shouldn't. Yes, it happens, but how frequently? If it's a few times a year (ignoring power cuts) then this is a problem. Could you have it restart on a schedule to allow it to refresh RAM and other services? To at least alleviate the inability to control the machine remotely when it freezes...? – Kinnectus – 2014-10-23T21:38:31.900
I would assume that there is some group policy or something set up by your admin that disables remote access on every reboot. Does the issue still happen when you do a normal restart? – cdavid – 2014-10-24T21:11:24.030