If we right-click on any collection we can set power policy for the collection. Notice the power management setting – in my no power policy collection I first enable power management settings and explicitly configure to never apply power management to systems in the collection.
Our XP test system also has applied the SCCM power settings but notice that with XP the user has no ability to change the settings.
Also notice that in XP the SCCM options show up as customized. Check compliance and report savings R3 power management includes a good number of reports that help track through these phases.
OK, so lets look at the settings for power management where we do have configured power policy.
Here we have configured power settings – the peak plan will be high performance and the non-peak plan will be power saver.
In addition, there is a requirement to deploy a client side hotfix for R3 – this is described in KB977384.
R3 won’t allow the install to proceed until this hotfix has been applied.
Once you have SQL Server Reporting Services integration enabled all you have to do is import the R3 reports.
Select to copy reports to Reporting Services from the right-click menu Walk through the wizard to the ‘select reports’ screen and you have two choices – either select classic reports to migrate to SSRS or choose to import reports to SSRS (an option that was added as part of the R3 installation).
The reports that come along with R3 will not work with classic reporting. Classic reporting is at the end of life – all future reporting work is focused on SQL Reporting Services so the R3 reports will only be usable if SCCM SQL Server Reporting Services integration is enabled.
If you haven’t started working toward SQL Server Reporting Services integration, take a look at my technet article that discusses how to do this and some of the advantages.
The per collection power management settings is where the configuration is done.