1. Home
  2. Windows
  3. How to Remotely Manage Windows Server 2016

How to Remotely Manage Windows Server 2016

How to Remote Start Windows Server 2016
How to Remote Start Windows Server 2016

How can you start a server when you’re physically offsite?

server 2016 remote management is a daunting task; Let’s learn what options exist for remote-start in Windows Server 2016.
Here’s the scenario: you receive a high-priority voicemail message from your boss in which she tells you that nobody in the office can access the company database anymore. You immediately identify two problems:

  • (1) the infrastructure server in question has likely fallen into a hibernation state due to a previous misconfiguration, and
  • (2) you are offsite and the only person who has access to the server.

There are quite a few problems here, but let’s focus specifically on one: Is it possible for us to remote-start a Windows Server computer?
Let’s assume in this example that the server in question is a hardware server running Windows Server 2016.
Also I have talked about the Windows server 2016 I earlier, the details of which you can read in these articles:

  1. How to Install a Docker Container in Windows Server 2016
  2. Backup a Windows Server Domain Controller

Power States and the Windows Operating System

The Advanced Configuration and Power Interface (ACPI) specification defines the following power states for physical computers:

  • S0: The system is powered on and usable
  • S1: The system is in standby (sleep) mode
  • S2: The system is in a deeper sleep state in which CPU context and system cache contents are unavailable
  • S3: The system is in hybrid sleep mode; the system state is saved to disk in case the computer loses power while in sleep
  • S4: The system is in hibernation mode. System state is stored on disk, and power consumption is almost nil
  • S5: The system is completely shut down and consuming no power

The server consumes gradually less power as we move from power states S0 to S5. The bad news for Windows Server administrators, however, is that according to the Microsoft documentation, Windows Server 2016, Windows Server 2012 R2, Windows 10, and Windows 8.1 cannot be remote-started using Wake-on-LAN from the S5 state.
Given that we can remotely start Windows Server 2016 only from sleep (S3) or hibernation (S4), you’ll need to learn what WOL is and how it works.

Configuring Wake-on-LAN

Wake-on-LAN (WOL) is an industry standard originally created by Intel and IBM that allows a computer system to be awakened by receiving a specially formed Ethernet message.
This “magic” packet has a specially crafted Layer 2 payload that consists of:

  1. 6 bytes of hexadecimal Fs
    16 repetitions of the target node’s Media Access Control (MAC) hardware address
  2. WOL “magic” packets are typically transmitted as User Datagram Protocol (UDP) datagrams on ports 0, 7, and 9.

To enable WOL on your Windows Server 2016 servers, you need to restart the computers into UEFI/BIOS setup. This is because, at the base,  motherboard firmware level controls WOL functionality.


Next, boot back into Windows and inspect the Properties of your server’s network interface card (NIC). Navigate to the Advanced tab and find the setting that corresponds to WOL. The specific setting name depends on your NIC manufacturer; in Figure 1, I show you the robust WOL settings for my Intel NIC driver.
You will  need to disable fast startup as well, because WOL doesn’t work in Windows’ default hybrid shutdown mode.
Here’s the relevant Group Policy path:

  • Computer\Configuration\Policies\Administrative
  • Templates\System\Shutdown\Require use of fast startup

You’ll either need to configure port forwarding on your home or small office router or create access rules on your corporate firewall to allow WOL traffic into your LAN.
Remember that WOL typically communicates on UDP ports 7-9.

Sending the Magic Packet

  • First-party (Microsoft) configuration management solutions such as System Center Configuration Manager or Operations Management Suite allow you to wake up sleeping or hibernating Windows Server managed nodes with WOL magic packets.
  1. Many third-party systems management tools include WOL functionality as well. Here are three such products:
  • LogMeIn
  • TeamViewer
  • Parallels Access

In Figure 2, you can see SolarWinds Wake-on-LAN, a freeware tool. In Figure 3, you can see LogMeIn, a commercial product. As you’d expect, the free tool requires that you have the target node’s MAC and IP address on-hand; LogMeIn can send a magic packet over the Internet with a single button click.
In Figure 3, the power icon to the left of my “Susan-iMac” system indicates that the computer is in an S3 or S4 state and WOL magic packet will awaken it.
Do let us know if you want to add any specific Linux VPS hosting or Windows hosting topics into this tutorial series.

Updated on July 24, 2018

Was this article helpful?

Related Articles

Leave a Comment

[apsl-login-lite login_text='Please login with a social account']