Member Avatar for DAS-03590

I'm looking into a possibility of using Windows Server 2003 to manage computers Power Schemes through Group Policy. We have many computers that are out in use and need to stay on 24/7 basically.

I have had issues where somehow the users are able to change the power settings on these stations, which they are not supposed to, I already have a policy setup and in place that should prevent them from changing any settings on the machine including screen saver and desktop background, along with many other features.

What I want to do with these computers is the following:
Do not turn off Monitor
If Power is pressed, Do nothing
Standby after, Never
Sleep after, Never
Turn off HDD after, Never
and so on...

Basically these stations should stay running all day, everyday, unless power itself is pulled. Is there a way to do this in Server 2003? I've been through plenty of the settings in the GPO Editor and have yet to find anything about Power Schemes. Any help would be appreciated. Thanks.

  • 2 Contributors
  • 7 Replies
  • 336 Views
  • 4 Months Discussion Span
  • Latest Post Latest Post by DAS-03590

Dani AI

Generated

Short answer: you're not missing a switch on the 2003 DC — the built‑in GPO editor on Windows Server 2003 does not show the newer "Preferences" power options. Group Policy Preferences (the node that includes Power Plan / Power Scheme items) were introduced with Server 2008 and must be authored from a management station that exposes the Preferences node (Server 2008 GPMC or a workstation with RSAT). (support.microsoft.com)

Recommended (clean) solution — Group Policy Preferences

  • Create the GPO from a Server 2008/RSAT management machine and edit: Computer Configuration (or User Configuration) → Preferences → Control Panel Settings → Power Options.
  • Add a Power Plan / Power Scheme item, set the action to Replace (or Create/Update as needed), and set monitor/disk/standby/hibernate values to Never (0). Use item‑level targeting or OU linking to scope by machine group.
  • On Windows XP / Server 2003 clients you must install the Group Policy Preferences client‑side extensions (and the XmlLite prerequisite) so those machines process the new preference items. (learn.microsoft.com)

Fallback / alternative: script

  • If you cannot deploy the CSEs, use a logon (per‑user) or startup (computer) script that calls powercfg to create/import a scheme and set it active. Test on the exact XP build you have: powercfg supports import/export and setactive, but power schemes are per‑user on XP so a user logon script is commonly needed unless you use a computer‑level preference. Example (concept only — test before deploy): 
    powercfg /import \\share\AlwaysOn.pow
powercfg /setactive <GUID or scheme name from /list>

    Always test commands on a lab machine first. (learn.microsoft.com)

Important caveats and quick checklist

  • Preferences are not policies — users with sufficient local rights can change them; GPP will normally reapply at refresh. If you need true enforcement, remove local admin rights or use policy controls that lock UI elements. (learn.microsoft.com)
  • Installing the GPP client update replaces PolicyMaker CSEs — check for that before mass rollout. Test one OU first, verify CSE install, run gpupdate /force and gpresult /r on a test client. (support.microsoft.com)

Notes tied to this thread: pointed toward the TechNet guidance (GPP is the right direction). For — if upgrading your DC isn't an option, build a single Server2008 or RSAT workstation to author the GPO, deploy the CSEs to your XP/2003 clients, and use Computer‑level Power Plan preferences so machines boot with the required "Always On" values even when nobody is interactively logged in.

Recommended Answers

All 7 Replies

Member Avatar for DAS-03590

Well, I see what they are doing but I don't see those options in 2003... By default those options are there on the Group Policy Management Editor... But we have the Group Policy Object Editor on our DC. I can't find these options anywhere inside of the GPOE.

Member Avatar for DAS-03590

That doesn't help with what we're looking to do. I understand about how the power settings and schemes are by user... Though what these computers do is log in automatically as one user, and we are looking at forcing the chosen settings upon log in and start up.

Here is what we have:
25 Computers logged in under user1 (by auto log on), Collect info and report.
30 Computers logged in under user2 (by auto log on), Collect different info and report.
17 Computers logged in under user3 (by auto log on), Report and look over previous info and reports upon status of production.

All of the computers listed above all use different in house applications to do its job, these are the computers that should stay on 24/7 and we are looking into forcing a power policy upon the computers and users that are logged in. This would give us the ability to deploy our computers and replace them as needed without having to go in and reset and change the settings every time we add a new computer to the domain, its just add the computer to a Group/OU and the Policy takes over the rest.

Member Avatar for jbennet

?

Member Avatar for DAS-03590

Well, that covers the Per computer portion. How would you go about doing this with the User power settings such as screensaver and so on?

Member Avatar for DAS-03590

Okay... I'm killing the article and even though it says solved, There really is no clear answer ecxept to move up to MS SVR 2008 DC and control them that way. Thanks for the assistance for those that tried.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.