One of the key advantages to a management suite is that you can schedule maintenance to happen automatically and during “off” hours. This means that the computer needs to be running and the management system needs to have user permissions and access through the Windows Firewall to operate correctly. These settings include choosing the correct Power Management Plan, making some additional adjustments to Power Management, and making the necessary Group Policy changes.
The steps Below can be done with some simple commands and even automated by script with the proper preparation.
Windows has a built-in Power Management API and utility program called “powercfg”. After manually configuring the first computer you can export the configuration to a “.pow” file and setup the remaining computers with a simple command line. See THIS PAGE for detail on how the configurations are exported or Imported.
Here is the .pow file that results from the settings below: highperformance.pow
Most Group Policy settings are stored in the registry. So in many cases you can make Group Policy changes with registy edits. Yes I know “VERY DANGEROUS” and May require a reboot to take effect. SO BE CAREFULL!!
Here are the settings for the Windows Firewall: windowsfirewall.reg
Because the settings for non-domain computers involve creating a local user and then granting permissions for that user in Group Policy the registry settings are not simple. Since non-domain configurations will usually involve few computers it is easier to just use the gpedit.msc tool to make these settings.
The Power Management Plan can also be set from an elevated Windows command prompt with the following:
for /f "tokens=4,5 skip=1" %%a in ('powercfg -l') Do (if "%%b"=="(High" set pquid=%%a) powercfg -s %pquid% powercfg -lThis method only sets the base plan, the “additional edits” must still be configured manually.
In ADDITION to the domain settings above …