Only a guess, but it was probably designed and implemented before client settings packages were in 2012. The power management piece was back-ported for inclusion in 2007 R3 and so probably got bumped to the top of the priority list and was also designed to work with 2007 which of course didn't have client settings.
File a DCR (because you're right, it does make more sense in client settings). J From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Wednesday, April 16, 2014 5:04 PM To: [email protected] Subject: [mssms] Power management in SCCM 2012 Does anyone know why power management is not included in the client settings schemes, and rather is set as a property of a collection? It seems to me like the power management configs would be a natural fit with the client settings scheme and their ability to set priorities. To me this seems like a really odd design choice, so I was wondering if anyone know the reason for it. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
