<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx</link><description>We get quite a few questions about enabling Wake-on-LAN (WoL) so I thought I'd post this document that was created by one of our Microsoft Consultants.&amp;#160; It's a good overview of what WoL is and how to implement it so hopefully if this is something</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#2963965</link><pubDate>Wed, 05 Mar 2008 15:00:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2963965</guid><dc:creator>Joseph Hinkle at MyITForum.com</dc:creator><description>&lt;p&gt;J.C. put together a nice article describing all that is necessary to implement Wake-on-LAN in ConfigMgr&lt;/p&gt;
</description></item><item><title>To save energy, send your PCs to sleep, then shake them (nicely) awake with Wake on Lan (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3059032</link><pubDate>Thu, 22 May 2008 08:18:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3059032</guid><dc:creator>Little Miss Enviro Geek</dc:creator><description>&lt;p&gt;The team at The Manageability Team Blog have posted a very comprehensive article on how to setup Wake&lt;/p&gt;
</description></item><item><title>re: ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3068913</link><pubDate>Tue, 10 Jun 2008 12:05:31 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3068913</guid><dc:creator>naweedanjum</dc:creator><description>&lt;p&gt;Hi and Thanks for such an informative article.&lt;/p&gt;
&lt;p&gt;My question is related to the script that has been provided to enable WOL for Network Adapters.&lt;/p&gt;
&lt;p&gt;When I ran this script on a test computer from command prompt, I get the following Error:&lt;/p&gt;
&lt;p&gt;Enabling WOL for the following Adapter:&lt;/p&gt;
&lt;p&gt;Packet Scheduler Miniport [MAC ADDRESS]&lt;/p&gt;
&lt;p&gt;C:Program Files\LANSCRIPT\lanscript.vbs (27,13):0x8004100C&lt;/p&gt;
&lt;p&gt;Now when I checked this error, It gives me the defination &amp;quot; NOT SUPPORTED &amp;quot; SOURCE : WMI&lt;/p&gt;
&lt;p&gt;What is wrong with the script and how can it be fixed.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;NAveed&lt;/p&gt;
</description></item><item><title>re: ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3197192</link><pubDate>Thu, 05 Feb 2009 01:17:08 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3197192</guid><dc:creator>twgage</dc:creator><description>&lt;p&gt;Late to comment here, but nonetheless...&lt;/p&gt;
&lt;p&gt;It is quite a relief to find this article.&lt;/p&gt;
&lt;p&gt;The explanation or SCCM trying to ARP a machine *before* sending a WOL packet (????) explains the erratic behavior I have seen (I have had my site settings set for unicast WOL packets, for the very reasons discussed in the article above.)&lt;/p&gt;
&lt;p&gt;Also- this is an EXCELLENTLY written script. &lt;/p&gt;
&lt;p&gt;In case someone from development sees this:&lt;/p&gt;
&lt;p&gt;I REALLY hope that this attempt to ARP before sending a unicast WOL packet is dropped in bugfix or SCCM update sometime if at all possible.&lt;/p&gt;
</description></item><item><title>re: Packet Scheduler Miniport (27,13):0x8004100C  " NOT SUPPORTED " SOURCE : WMI</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3268401</link><pubDate>Mon, 27 Jul 2009 16:11:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3268401</guid><dc:creator>glock-a-pile rock</dc:creator><description>&lt;p&gt;This script must be run with wscript.exe. &amp;nbsp;If you use cscript.exe then you will get a wmi not supported error and the script will not work.&lt;/p&gt;
</description></item><item><title>re: ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3268405</link><pubDate>Mon, 27 Jul 2009 16:25:04 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3268405</guid><dc:creator>glock-a-pile rock</dc:creator><description>&lt;p&gt;Disregard my previous comment, the script will work with both wscript.exe and cscript.exe. &amp;nbsp;I am having trouble getting it to work remotely using psexec but it does work if I run it locally.&lt;/p&gt;
</description></item><item><title>re: ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3268417</link><pubDate>Mon, 27 Jul 2009 17:21:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3268417</guid><dc:creator>glock-a-pile rock</dc:creator><description>&lt;p&gt;I was able to get this to work remotely by not using psexec and instead replacing //./ with //computername/. &amp;nbsp;Author please feel free to delete my previous two comments.&lt;/p&gt;
</description></item><item><title>re: ConfigMgr 2007: Implementing Wake-on-LAN (WoL)</title><link>http://blogs.technet.com/smsandmom/archive/2008/03/04/configmgr-2007-implementing-wake-on-lan-wol.aspx#3292878</link><pubDate>Tue, 10 Nov 2009 17:05:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3292878</guid><dc:creator>Terence Durning</dc:creator><description>&lt;p&gt;The script works by running it interactively, but when we tried to implement it using SCCM or running under the SYSTEM context in psexec, we got error code 0x8004100c. &amp;nbsp;To get this to work we had to add the LoadDriver constant in the GetObject/ExecQuery WMI calls, i.e., instead of:&lt;/p&gt;
&lt;p&gt;{impersonationLevel=impersonate}&lt;/p&gt;
&lt;p&gt;we put in&lt;/p&gt;
&lt;p&gt;{impersonationLevel=impersonate, (LoadDriver)}&lt;/p&gt;
&lt;p&gt;and it works.&lt;/p&gt;
</description></item></channel></rss>