{"id":13041,"date":"2011-08-11T00:01:00","date_gmt":"2011-08-11T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/08\/11\/configure-a-network-adapter-to-wake-a-computer-via-powershell\/"},"modified":"2011-08-11T00:01:00","modified_gmt":"2011-08-11T00:01:00","slug":"configure-a-network-adapter-to-wake-a-computer-via-powershell","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/configure-a-network-adapter-to-wake-a-computer-via-powershell\/","title":{"rendered":"Configure a Network Adapter to Wake a Computer Via PowerShell"},"content":{"rendered":"

Summary<\/strong>: Learn how to use Windows PowerShell to configure a remote computer’s network adapter to wake the computer.<\/p>\n

 <\/p>\n

\"Hey,Hey, Scripting Guy! At work, we have been trying to get our automation solution put into place. One problem is that on many of the computers, the network adapter is not configured to allow it to wake up the machine. This means that when someone shuts down the computer in the evening, that is it until the next day. I would like to be able to do maintenance at night when the users have gone home, but to do so, I need to be able to wake up the computer. I found an article on the Internet, but basically the article talked about hacking the registry, and I did not feel like I could trust the article. Can Windows PowerShell configure a computer’s network card to allow it to wake up the computer?<\/p>\n

—TS<\/p>\n

 <\/p>\n

\"Hey,Hello TS,<\/p>\n

Microsoft Scripting Guy Ed Wilson here. One thing to keep in mind about Windows PowerShell is that it can only do what is available. In other words, if no mechanism exists for automating a particular problem, Windows PowerShell will not be able to automate a solution. Windows PowerShell can certainly make working with registry keys easier because of the existence of the registry provider, and it can make working with WMI classes easier as well. However, if the underlying technology does not expose the functionality, we are out of luck.<\/p>\n

TS, in this particular case, I am not certain you are out of luck. I was looking over my list of WMI classes that have settable properties and implemented methods, and I ran across the MSPower_DeviceWakeEnable<\/b> WMI class. This particular WMI class exists in the Root\\WMI namespace, and is not documented on MSDN. Because the WMI class is not documented, this means that it is not supported. It does not mean that it will not work, but that it is not supported. As a matter of a fact, it does not work on my Windows 7 Ultimate 64-bit desktop computer; I believe that is because I have a custom network adapter card driver that supports port teaming for better throughput.<\/p>\n

The WMI class does work on my 32-bit Windows 2008 server, which is using an inbox network card driver. Because the class is not documented, it means that I cannot tell you if the class exists on Windows XP or Windows Server 2003. I know it exists on Windows Server 2008 R2, Windows Server 2008, and Windows 7.<\/p>\n

TS, I am going to show you how to use the MSPower_DeviceWakeEnable<\/b> WMI class to enable the network card to wake the machine. If the technique does not work on all your devices, there is nothing I can do—the class is unsupported (although you might be able to use the powercfg<\/b> utility to configure your network cards to wake up the computer).<\/p>\n

The first thing I need to do is to store credentials for my remote WMI connection. Remember, I am working against a remote server. I use the Get-Credential<\/b> cmdlet to retrieve the credentials for the remote computer, and I store the returned credential object in the $cred<\/b> variable. This is shown here:<\/p>\n

$cred = Get-Credential nwtraders\\administrator<\/p>\n

Next, I use WMI and the Get-WmiObject<\/b> cmdlet to look for a network card on the remote server that is netenabled<\/b>.<\/i> This property of the Win32_NetworkAdapter<\/b> class<\/a> should return True<\/b> only if the network interface is enabled. If there are multiple network cards that are enabled, you might want to query for the NetConnectionStatus<\/b> of 2 (means that it is connected). If you are still having difficulity finding the correct network adapter, you might want to try the netconnectionid<\/b> <\/i>property. That is the name of the connection (for example “Local Area Connection”), and if you have named all your network adapters the same, it will be easy to pick them up with this property.<\/p>\n

When I query the netenabled<\/b> property on my remote server, only one network adapter is returned. The command and associated output are shown here:<\/p>\n

PS C:\\> gwmi win32_networkadapter -filter “netenabled = ‘true'” -cn dc1 -cred $cred<\/p>\n

ServiceName      : E100B<\/p>\n

MACAddress       : 00:07:E9:7C:A7:5F<\/p>\n

AdapterType      : Ethernet 802.3<\/p>\n

DeviceID         : 6<\/p>\n

Name             : Intel(R) PRO\/100 VE Network Connection<\/p>\n

NetworkAddresses :<\/p>\n

Speed            : 100000000<\/p>\n

 <\/p>\n

Now I repeat the above command, and store the returned WMI object in a variable named $nic<\/b>. This command is shown here:<\/p>\n

$nic= gwmi win32_networkadapter -filter “netenabled = ‘true'” -cn dc1 -cred $cred<\/p>\n

I next query the MSPower_DeviceWakeEnable<\/b> WMI class to see what type of date it returns. The WMI class resides in the Root\\WMI namespace, so I need to specify the namespace <\/i>parameter when making the query. I am still working on a remote machine, so I also specify the computername<\/i> (alias is cn<\/i>) and the credential<\/i> (shortened to cred<\/i>) parameters. The command and associated output appear here.<\/p>\n

PS C:\\> gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi -cn dc1 -cred $cred<\/p>\n

 <\/p>\n

__GENUS          : 2<\/p>\n

__CLASS          : MSPower_DeviceWakeEnable<\/p>\n

__SUPERCLASS     : MSPower<\/p>\n

__DYNASTY        : MSPower<\/p>\n

__RELPATH        : MSPower_DeviceWakeEnable.InstanceName=”PCI\\\\VEN_8086&DEV_105<\/p>\n

                   0&SUBSYS_01571028&REV_02\\\\4&1c660dd6&0&40F0_0″<\/p>\n

__PROPERTY_COUNT : 3<\/p>\n

__DERIVATION     : {MSPower}<\/p>\n

__SERVER         : DC1<\/p>\n

__NAMESPACE      : root\\wmi<\/p>\n

__PATH           : \\\\DC1\\root\\wmi:MSPower_DeviceWakeEnable.InstanceName=”PCI\\\\V<\/p>\n

                   EN_8086&DEV_1050&SUBSYS_01571028&REV_02\\\\4&1c660dd6&0&40F0_0<\/p>\n

                   “<\/p>\n

Active           : True<\/p>\n

Enable           : True<\/p>\n

InstanceName     : PCI\\VEN_8086&DEV_1050&SUBSYS_01571028&REV_02\\4&1c660dd6&0&40<\/p>\n

                   F0_0<\/p>\n

 <\/p>\n

__GENUS          : 2<\/p>\n

__CLASS          : MSPower_DeviceWakeEnable<\/p>\n

__SUPERCLASS     : MSPower<\/p>\n

__DYNASTY        : MSPower<\/p>\n

__RELPATH        : MSPower_DeviceWakeEnable.InstanceName=”ACPI\\\\PNP0303\\\\4&1506<\/p>\n

                   bb2e&0_0″<\/p>\n

__PROPERTY_COUNT : 3<\/p>\n

__DERIVATION     : {MSPower}<\/p>\n

__SERVER         : DC1<\/p>\n

__NAMESPACE      : root\\wmi<\/p>\n

__PATH           : \\\\DC1\\root\\wmi:MSPower_DeviceWakeEnable.InstanceName=”ACPI\\\\<\/p>\n

                   PNP0303\\\\4&1506bb2e&0_0″<\/p>\n

Active           : True<\/p>\n

Enable           : False<\/p>\n

InstanceName     : ACPI\\PNP0303\\4&1506bb2e&0_0<\/p>\n

 <\/p>\n

The InstanceName<\/b> <\/i>properties look weird, but they also look familiar. They look like the PNPDeviceID<\/b> <\/i>property from the Win32_NetworkAdapter<\/b> WMI class. I can therefore use the PNPDeviceID<\/b> <\/i>property value from my network adapter and filter out only a matching instance from the MSPower_DeviceWakeEnable<\/b> WMI class. So I take the PNPDeviceID<\/b> property value and attempt to use it in a Where-Object<\/b> command. Unfortunately, an error results. The command and associated output are shown here.<\/p>\n

PS C:\\> gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi | where {$_.instancena<\/p>\n

me -match $nic.PNPDeviceID }<\/p>\n

 <\/p>\n

Bad argument to operator ‘-match’: parsing “PCI\\VEN_8086&DEV_1050&SUBSYS_015710<\/p>\n

28&REV_02\\4&1C660DD6&0&40F0″ – Unrecognized escape sequence \\V..<\/p>\n

At line:1 char:82<\/p>\n

+ gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi | where {$_.instancename -m<\/p>\n

atch <<<<  $nic.PNPDeviceID }<\/p>\n

    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException<\/p>\n

    + FullyQualifiedErrorId : BadOperatorArgument<\/p>\n

 <\/p>\n

Bad argument to operator ‘-match’: parsing “PCI\\VEN_8086&DEV_1050&SUBSYS_015710<\/p>\n

28&REV_02\\4&1C660DD6&0&40F0″ – Unrecognized escape sequence \\V..<\/p>\n

At line:1 char:82<\/p>\n

+ gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi | where {$_.instancename -m<\/p>\n

atch <<<<  $nic.PNPDeviceID }<\/p>\n

    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException<\/p>\n

    + FullyQualifiedErrorId : BadOperatorArgument<\/p>\n

 <\/p>\n

Bad argument to operator ‘-match’: parsing “PCI\\VEN_8086&DEV_1050&SUBSYS_015710<\/p>\n

28&REV_02\\4&1C660DD6&0&40F0″ – Unrecognized escape sequence \\V..<\/p>\n

At line:1 char:82<\/p>\n

+ gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi | where {$_.instancename -m<\/p>\n

atch <<<<  $nic.PNPDeviceID }<\/p>\n

    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException<\/p>\n

    + FullyQualifiedErrorId : BadOperatorArgument<\/p>\n

 <\/p>\n

Bad argument to operator ‘-match’: parsing “PCI\\VEN_8086&DEV_1050&SUBSYS_015710<\/p>\n

28&REV_02\\4&1C660DD6&0&40F0″ – Unrecognized escape sequence \\V..<\/p>\n

At line:1 char:82<\/p>\n

+ gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi | where {$_.instancename -m<\/p>\n

atch <<<<  $nic.PNPDeviceID }<\/p>\n

    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException<\/p>\n

    + FullyQualifiedErrorId : BadOperatorArgument<\/p>\n

 <\/p>\n

The problem, it seems, is that the PNPDeviceID<\/b> <\/i>property contains characters that have a meaning in a regular expression. The PNPDeviceID<\/b> <\/i>is shown here:<\/p>\n

PS C:\\> $nic.pnpdeviceid<\/p>\n

PCI\\VEN_8086&DEV_1050&SUBSYS_01571028&REV_02\\4&1C660DD6&0&40F0<\/p>\n

The special characters need to be escaped before submitting to the Regex engine. This could be a tedious problem. But, then I remembered there is an escape<\/b> method from the REGEX<\/b> class. The Regex<\/b>.Escape<\/strong> method<\/a> is documented on MSDN and is easy to use. It will escape any invalid character in a string, and permit easy use of that string. This is exactly what is needed here. I place the call to the escape<\/b> method just in front of the PNPDeviceID<\/b> property. I store the returned object in a variable called $nicPower<\/b> and I query the variable to ensure I contain the proper network adapter. Notice that the status of the enable<\/b> property is set to false<\/b>. The command and associated output are shown here:<\/p>\n

PS C:\\> $nicPower = gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi -cn dc1 -cred $cred | where {$_.instancename -match [regex]::escape($nic.PNPDeviceID) }<\/p>\n

PS C:\\> $nicPower<\/p>\n

 <\/p>\n

__GENUS          : 2<\/p>\n

__CLASS          : MSPower_DeviceWakeEnable<\/p>\n

__SUPERCLASS     : MSPower<\/p>\n

__DYNASTY        : MSPower<\/p>\n

__RELPATH        : MSPower_DeviceWakeEnable.InstanceName=”PCI\\\\VEN_8086&DEV_105<\/p>\n

                   0&SUBSYS_01571028&REV_02\\\\4&1c660dd6&0&40F0_0″<\/p>\n

__PROPERTY_COUNT : 3<\/p>\n

__DERIVATION     : {MSPower}<\/p>\n

__SERVER         : DC1<\/p>\n

__NAMESPACE      : root\\wmi<\/p>\n

__PATH           : \\\\DC1\\root\\wmi:MSPower_DeviceWakeEnable.InstanceName=”PCI\\\\V<\/p>\n

                   EN_8086&DEV_1050&SUBSYS_01571028&REV_02\\\\4&1c660dd6&0&40F0_0<\/p>\n

                   “<\/p>\n

Active           : True<\/p>\n

Enable           : False<\/p>\n

InstanceName     : PCI\\VEN_8086&DEV_1050&SUBSYS_01571028&REV_02\\4&1c660dd6&0&40<\/p>\n

                   F0_0<\/p>\n

Now, all I need to do is to change the value of the Enable<\/b> property from False<\/b> to True<\/b>. After I have done that, I need to call the Put<\/b> method from the base WMI object so that I write the changes back to the WMI database. These two commands and their associated output are shown here:<\/p>\n

PS C:\\> $nicPower.Enable = $true<\/p>\n

PS C:\\> $nicPower.psbase.Put()<\/p>\n

 <\/p>\n

 <\/p>\n

Path          : \\\\dc1\\root\\wmi:MSPower_DeviceWakeEnable.InstanceName=”PCI\\\\VEN_<\/p>\n

                8086&DEV_1050&SUBSYS_01571028&REV_02\\\\4&1c660dd6&0&40F0_0″<\/p>\n

RelativePath  : MSPower_DeviceWakeEnable.InstanceName=”PCI\\\\VEN_8086&DEV_1050&S<\/p>\n

                UBSYS_01571028&REV_02\\\\4&1c660dd6&0&40F0_0″<\/p>\n

Server        : dc1<\/p>\n

NamespacePath : root\\wmi<\/p>\n

ClassName     : MSPower_DeviceWakeEnable<\/p>\n

IsClass       : False<\/p>\n

IsInstance    : True<\/p>\n

IsSingleton   : False<\/p>\n

 <\/p>\n

It takes a reboot for the changes to take effect. Because I am working remotely and using WMI, I decide to use the Reboot<\/b> <\/i>method from the Win32_OperatingSystem<\/b> WMI class. When calling the Reboot<\/b> method from Win32_OperatingSystem<\/b>, it seems to be a bit confusing. For example, if I use the [WMICLASS]<\/b> type accelerator, the Reboot<\/b> and Shutdown<\/b> methods appear as shown here:<\/p>\n

PS C:\\> [wmiclass]”Win32_OperatingSystem”<\/p>\n

 <\/p>\n

   NameSpace: ROOT\\cimv2<\/p>\n

 <\/p>\n

Name<\/span>                                       Methods<\/span>                       Properties<\/span><\/p>\n

Win32_OperatingSystem             {Reboot, Shutdown         {BootDevice, BuildN…<\/p>\n

 <\/p>\n

But, when I attempt to use the Invoke-WmiMethod<\/b> cmdlet to reboot the computer, an error occurs. The error is shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

Before I actually reboot the system, I connect via Remote Desktop and view the status of the network adapter. As shown in the following figure, it is not configured to allow the device to wake the computer.<\/p>\n

\"Image<\/a><\/p>\n

Okay, I have verified the baseline configuration. Now I need to figure out why my reboot command did not work. The reason it failed is because the Reboot<\/b> method is an instance method, not a static method. The easiest way to reboot the machine is to use the Get-WmiObject<\/b> cmdlet, and call the method directly from the resulting object. This command and its associated output are shown here:<\/p>\n

PS C:\\> (gwmi win32_operatingsystem -CN dc1 -cred $cred).reboot()<\/p>\n

  <\/p>\n

__GENUS          : 2<\/p>\n

__CLASS          : __PARAMETERS<\/p>\n

__SUPERCLASS     :<\/p>\n

__DYNASTY        : __PARAMETERS<\/p>\n

__RELPATH        :<\/p>\n

__PROPERTY_COUNT : 1<\/p>\n

__DERIVATION     : {}<\/p>\n

__SERVER         :<\/p>\n

__NAMESPACE      :<\/p>\n

__PATH           :<\/p>\n

ReturnValue      : 0<\/p>\n

 <\/p>\n

After waiting an indeterminable amount of time, the remote domain controller is back up and running. I connect once again with Remote Desktop to see if my changes actually took. As shown in the following figure, it worked.<\/p>\n

\"Image<\/a><\/p>\n

 <\/p>\n

The complete sequence of commands could be placed easily in a single script and used to perform this configuration change in an automated fashion. Here are the commands:<\/p>\n

EnableNicToWakeMachine.ps1<\/strong><\/p>\n

$cred = Get-Credential nwtraders\\administrator<\/p>\n

$nic= gwmi win32_networkadapter -filter “netenabled = ‘true'” -cn dc1 -cred $cred<\/p>\n

$nicPower = gwmi MSPower_DeviceWakeEnable -Namespace root\\wmi -cn dc1 -cred $cred |<\/p>\n

  where {$_.instancename -match [regex]::escape($nic.PNPDeviceID) }<\/p>\n

$nicPower.Enable = $true<\/p>\n

$nicPower.psbase.Put()<\/p>\n

(gwmi win32_operatingsystem -CN dc1 -cred $cred).reboot()<\/p>\n

 <\/p>\n

TS, that is all there is to using WMI to set the ability of a NIC to wake up a computer. This also concludes WMI Method Week. Join us tomorrow when we have a guest blog article by Robert Robelo.<\/p>\n

 <\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Learn how to use Windows PowerShell to configure a remote computer’s network adapter to wake the computer.   Hey, Scripting Guy! At work, we have been trying to get our automation solution put into place. One problem is that on many of the computers, the network adapter is not configured to allow it to […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[36,37,31,173,3,4,45,6],"class_list":["post-13041","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-client-side-management","tag-networking","tag-operating-system","tag-power-management","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

Summary: Learn how to use Windows PowerShell to configure a remote computer’s network adapter to wake the computer.   Hey, Scripting Guy! At work, we have been trying to get our automation solution put into place. One problem is that on many of the computers, the network adapter is not configured to allow it to […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/13041","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=13041"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/13041\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=13041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=13041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=13041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}