Enable right click WOL a device from inside the console
Allow the built in use of WOL, and right click to wake up a machine or a collection at anytime. Also fix ConfigMgr's native WOL technology to work on common network infrastructure (no Mac-Flapping.)
This is fixed and available in #sccm 1810.
While you're at it, can you make the other actions available for individual machines in the main Devices list? To get one computer to do a application eval, I need to find a collection it's in and do the entire collection.
Greg Isett commented
I can't run the 1810 Tech Preview. Does 1810 fix "Mac Flapping"?
I'd like to again note the problem with "Mac-Flapping". We have had multiple networks here where we enabled Cisco port locking. SCCM Wake on Lan solution caused many ports to lock due to changing MAC addresses of the PC causing site outages. We had to disable SCCM wake on lan agent.
Adam Juelich commented
This isn't the right venue for that. Please post such items in a related forum (TechNet, etc.).
Aman Kahlon commented
Not sure if this is right forum to post my question. So I have Intel MC installed. when I try to connect to device using Intel MC from SCCM, it throws me an exception and the exception is that 'Specified cast is not valid in local registry'. Not sure where to go from here... Can anyone help?
So we use WOL successfully via subnet directed broadcasts, on a custom port from a known source. Our network has many sites and many subnets, our network restricts this traffic from any other host, so that was enough for the network/security team.
As for console integration, we setup a root collection with a recurring advert (every three mins) that simply runs a silent wuauclt command, it's set with WOL on the properties, so right click, add to collection, WOL collection at the most three mins later the machine is awake.
We've partnered w/ Intel for their add on to integrate well with ConfigMgr. They will be able to keep it up to date w/ newer versions of VPro/AMT, as well as newer versions of ConfigMgr current branch.
Would be a great idea, i currently have to deploy a fake program to pcs. That should not be necessary
Thanks for this Info.
Also the Intel SCS Addon for SCCM was updated for Current Branch:
And it must be possible from a DP/server within the PC boundary, fully automatically or specifying the server. Thanks
kevin willis commented
yes, without having to add 3rd party tools
Intel have released a new tool called "Intel Manageability Commander". This as an add-on to SCCM 1511 or later that will bring back many of features removed by Microsoft:
Intel® Manageability Commander is a light weight console used to connect with and utilize the features of Intel® Active Management Technology (Intel® AMT). Through this software, users will be able to connect to activated Intel® AMT devices to perform functions such as power control, remote desktop, hardware inventory, remote terminal, and more. Additionally, this software will plug into Microsoft* System Center Configuration Manager (SCCM) version 1511 and later. When task based wake events are triggered in SCCM, Intel® Manageability Commander will also attempt to perform an Intel® AMT power on action. Collections in SCCM can be manually powered on using Intel® Manageability Commander using the collection right click context menu. Intel® Manageability Commander can be launched on a per system basis by using the right click system context menu to get access to all of the supported Intel® AMT features directly from SCCM.
Cliff Richardson commented
Could this feature be triggered via remote AMT management tool, examples are Intel RCS and/or McAfee ePO Deep Command.
Lou Ponesse commented
The fact that many organizations have exhausted efforts and rely on this technology for security compliance for it to be taken away is not serving your customers with their best interest in mind. To now have to possibly incorporate another technology set is extremely frustrating.
Ben H commented
adding this functionality back into SCCM would make life easier for us. We can hack broadly equivalent functionality with scripts, but it's kind of defeating the purpose of SCCM to have to build extra tools to recover lost functionality
Patrik Holmqvist commented
+1 on this!
The key reason why we need the capability to integrate the Intel AMT Power functions with SCCM relates to providing the capability to wake up workstations out of hours for patching, software deployment or build/rebuild scenarios minimising disruption to clients. The network security controls in place require devices/clients to authenticate to the network before getting any connectivity. This prevents us from being able to use the simple Wake on LAN packet to wake machines up. Intel AMT allows us to configure the authentication using the AMT computer object in AD resolving this problem.
SCCM continues to include the option to send a Wake on LAN packet but as mentioned above this approach does not work on our network. Previously SCCM also had the option to use Intel AMT to power on the workstation. The work-around options discussed in the case with Bryan do not provide anything close to the same level of capability to trigger a wake up request to the workstation when the deadline for the SCCM package is reached. Instead it would rely on us scheduling a powershell script to run at a given time, read the membership of the collection the SCCM package is targeted to and sending the Intel AMT power on command.
We recognise that Microsoft has chosen not to update the Intel AMT integration since AMT v6 due to the architecture changes Intel made to their product. This would have forced Microsoft to completely update the SCCM Intel AMT integration component and continue to be beholden to architecture changes made by Intel. Decoupling SCCM and Intel AMT/SCS makes sense however losing the capability to integrate the wake up command with the package deadline causes problems. Another approach might be to provide the capability to execute a powershell script as an alternative to the Wake on LAN option. This would leave the integration to the power management tool (in this case Intel AMT) to the client rather than having to include the integration directly inside SCCM.
Just adding another one to the list. It would be extremely useful if Microsoft could re-add the remote power on commands.
Michael Jantzen commented
To add to this - it would be really helpful if Microsoft could comment or commit to looking into this. We developed AMT support for SCCM 2007 and then 2012 and it worked well enough - it has been helpful for use to do nightly maintenance reliably on client PC's.
Citrix is relying on Configuration Manager to power manage RemotePCs; with the recent changes, only devices up to AMT version 6.1 and running up to Windows 8.1 can be supported.
Add to "Client Notifications" context menu in the console.