Configuration Manager 2007 R3 introduced new Power Management features for gaining greater control over device power consumption. While Group Policy provides a fairly robust range of power management options, the additional capabilities 2007 R3 provided add more granularity and flexibility with respect to scheduling and dynamic level control than Group Policy settings alone.
Internet Clients can be particularly difficult to troubleshoot for several reasons. Foremost, they are usually off-site, so that can present logistical challenges.
Mobile device support in Configuration Manager 2007 is not as robust as it is with Configuration Manager 2012, but there are customers who depend on this in their 2007 sites.
Configuration Manager uses Wake-On-LAN (WOL) to awaken a powered-off device, perform requested actions (install or remove applications, install updates, etc.) and then power the computer OFF again, if desired. It’s a compromise between energy efficiency and management efficiency, and if configured correctly, does a great job in most cases. In Part 6 of my SCCM 2007 Client troubleshooting series I cover WOL problems.
Most sites I’ve seen and heard of are using Native Mode. If you ask many administrators what that means, you get some pretty interesting responses. Basically, Native Mode means that the communications channel is encrypted via SSL between the Client device and the Management Point (MP), and other site system servers, except for communicating with Server Locator Point (SLP), and Fallback Status Point (FSP) servers.