The GPTalk Mailing List

The GPTALK mailing list is where you can send and receive email related to Windows Group Policy. You must subscribe to the list to send and receive mail from the list. The purpose of the list is to provide a forum for asking and answering technical questions related to Group Policy. Any question is fair game as long as it is related to Windows Group Policy. The Archives for this list can be found on this page.

List Posts

Unanswered Active Topics

Forums Search

Forums >GPTalk >GPTalk Mailing List

Subject: [gptalk] XP Power Management & Loopback

Prev Next

You are not authorized to post a reply.

Author

Messages

acjuelich

Posts:147

12/08/2010 7:08 PM
Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

dmarelia

Posts:441

12/08/2010 7:11 PM
Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

acjuelich

Posts:147

12/08/2010 7:20 PM
How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

dmarelia

Posts:441

12/08/2010 7:22 PM
The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

acjuelich

Posts:147

12/08/2010 7:34 PM
Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

dmarelia

Posts:441

12/08/2010 7:56 PM
Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

acjuelich

Posts:147

12/08/2010 8:49 PM
So you can get GPP User Properties to apply to a Computer without using Loopback and just using ILT (Item-Level Targeting)? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:58 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

acjuelich

Posts:147

12/08/2010 9:03 PM
So I can create a GPP User Power Scheme and set it up with ILT to target an OS with Windows XP and it'll work like Loopback? If so, this is huge! From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 1:02 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Yep, by leveraging a per-computer attribute that you supply as a targeting criteria for a per-user setting, you effectively get the kind of behavior you are after with loopback, without using loopback. From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 10:53 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So you can get GPP User Properties to apply to a Computer without using Loopback and just using ILT (Item-Level Targeting)? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:58 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

jsclmedave User is Offline

Posts:67

12/08/2010 9:03 PM
Sounds like a nice article in the works Darren... Tim Bolton 148 2nd Street North Central City Iowa, 52214 SMS - xxxxxxxxxxxxxxxx Microsoft Certified IT Professional Blog - Http://timbolton.net/ "Applying computer technology is simply finding the right wrench to pound in the correct screw." ~ Steve Riley On Wed, Dec 8, 2010 at 1:11 PM, Adam C Juelich <xxxxxxxxxxxxxxxx>wrote: > So I can create a GPP User Power Scheme and set it up with ILT to target an > OS with Windows XP and it’ll work like Loopback? If so, this is huge! > > > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia > Sent: Wednesday, December 08, 2010 1:02 PM > > To: xxxxxxxxxxxxxxxx > Subject: RE: [gptalk] XP Power Management & Loopback > > > > Yep, by leveraging a per-computer attribute that you supply as a targeting > criteria for a per-user setting, you effectively get the kind of behavior > you are after with loopback, without using loopback. > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich > Sent: Wednesday, December 08, 2010 10:53 AM > To: 'xxxxxxxxxxxxxxxx' > Subject: RE: [gptalk] XP Power Management & Loopback > > > > So you can get GPP User Properties to apply to a Computer without using > Loopback and just using ILT (Item-Level Targeting)? > > > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia > Sent: Wednesday, December 08, 2010 11:58 AM > To: xxxxxxxxxxxxxxxx > Subject: RE: [gptalk] XP Power Management & Loopback > > > > Well, there could be one way to do it. If you’re using GP Preferences to > deliver power settings, you could do something like this. Let’s assume you > have a set of computers that you want to apply a particular power scheme to. > You could create an environment variable on those computers that indicates > they get the power settings. Then using GP Preferences item-level targeting > to filter on the value of that environment variable. The user power settings > would only apply on that machine if that environment variable was set. > > > > Darren > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich > Sent: Wednesday, December 08, 2010 9:38 AM > To: 'xxxxxxxxxxxxxxxx' > Subject: RE: [gptalk] XP Power Management & Loopback > > > > Well that just makes life harder J > > > > If only there was another way……… Thanks for the clarification, though. I > think it has finally ‘clicked.’ > > > > > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia > Sent: Wednesday, December 08, 2010 11:28 AM > To: xxxxxxxxxxxxxxxx > Subject: RE: [gptalk] XP Power Management & Loopback > > > > The only way to do that is to ensure that the list of GPOs processed by the > computer under loopback, don’t contain any other user settings. This might > be accomplished by setting Block Inheritance on the OU where the loopback > computers are, by moving the computer accounts, or by ensuring that GPOs > don’t contain both user and computer settings, making them harder to > segregate in these kinds of scenarios. Keep in mind that by setting Block > Inheritance, you could also be blocking important per-computer settings > upstream if those GPOs also contain user settings. > > > > Darren > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich > Sent: Wednesday, December 08, 2010 9:24 AM > To: 'xxxxxxxxxxxxxxxx' > Subject: RE: [gptalk] XP Power Management & Loopback > > > > How can I accomplish what I want if I just want a certain User GPO to be > affected by Loopback and nothing else? > > > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia > Sent: Wednesday, December 08, 2010 11:18 AM > To: xxxxxxxxxxxxxxxx > Subject: RE: [gptalk] XP Power Management & Loopback > > > > Adam- > > When a machine is set to loopback processing, then all GPOs that are > processed by that machine account (based on its location in AD) that also > contain user policy, will be processed. In other words, the user policy that > is applying based on loopback does not just include the GPO that is enabling > loopback. So, you could definitely see “weird” behavior based on whether you > are using merge or replace mode in loopback. If your goal is to have power > settings differ by machine type, then loopback in combination with per-user > based power settings is a good strategy, but you do need to ensure that you > understand the full effect of loopback in that case. RSOP Modeling may help > here. > > > > Darren > > > > From: xxxxxxxxxxxxxxxx [mailto: > xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich > Sent: Wednesday, December 08, 2010 9:15 AM > To: 'xxxxxxxxxxxxxxxx' > Subject: [gptalk] XP Power Management & Loopback > > > > Hello, > > > > I’ve read that when managing Power Management settings via GPP for XP > Machines it is recommended that you set them as User Settings and then > enable Loopback. I have tested this but had a lot of weird stuff happening > concerning my drive mapping. I was told that Loopback will only affect the > policy that it is enabled on, but then it seemed like some people were > saying that it would affect every User Policy including those in other > GPOs. Why am I so confused? How have others successfully managed XP Power > Settings? Thanks! > > > > > > ------------------------------------------------------------------ > > Adam C. Juelich > > A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging > > Application and Hardware Specialist/Technician > > Pulaski Community School District > > 920-822-6075 > > > > "If you never venture outside the box, you will probably not be creative. > But if you never get inside the box, you will certainly be stupid" > > - Christopher Peterson > > >

Tim Bolton

dmarelia

Posts:441

12/08/2010 9:09 PM
Loopback does a specific thing-which is that it changes the way user policy is processed for that machine to either ignore or subjugate a user's "normal" policy settings in favor of those targeted to the machine account. What I'm suggesting is a little less complete but accomplishes the same goal in some cases. That is, you define a per-user GPP setting (in this case Power Scheme) and use Item-Level Targeting to only apply it if a per-computer criteria (e.g. an environment variable value) is true. There are likely still situations where you would still need to use loopback (e.g. kiosk machines, Terminal Servers, etc.) but for your particular situation, this approach may work. Note that you still have to do something on these computers to identify them as "special" in the eyes of GPP-in this case, by adding an environment variable on the machine. Hope that helps. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 11:12 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So I can create a GPP User Power Scheme and set it up with ILT to target an OS with Windows XP and it'll work like Loopback? If so, this is huge! From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 1:02 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Yep, by leveraging a per-computer attribute that you supply as a targeting criteria for a per-user setting, you effectively get the kind of behavior you are after with loopback, without using loopback. From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 10:53 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So you can get GPP User Properties to apply to a Computer without using Loopback and just using ILT (Item-Level Targeting)? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:58 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

dmarelia

Posts:441

12/08/2010 9:17 PM
Yep, by leveraging a per-computer attribute that you supply as a targeting criteria for a per-user setting, you effectively get the kind of behavior you are after with loopback, without using loopback. From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 10:53 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So you can get GPP User Properties to apply to a Computer without using Loopback and just using ILT (Item-Level Targeting)? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:58 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

acjuelich

Posts:147

12/09/2010 6:45 PM
Darren, does it have to be the 'environment variable' option, or can one use one of the default Item-level Targeting options? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 1:19 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Loopback does a specific thing-which is that it changes the way user policy is processed for that machine to either ignore or subjugate a user's "normal" policy settings in favor of those targeted to the machine account. What I'm suggesting is a little less complete but accomplishes the same goal in some cases. That is, you define a per-user GPP setting (in this case Power Scheme) and use Item-Level Targeting to only apply it if a per-computer criteria (e.g. an environment variable value) is true. There are likely still situations where you would still need to use loopback (e.g. kiosk machines, Terminal Servers, etc.) but for your particular situation, this approach may work. Note that you still have to do something on these computers to identify them as "special" in the eyes of GPP-in this case, by adding an environment variable on the machine. Hope that helps. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 11:12 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So I can create a GPP User Power Scheme and set it up with ILT to target an OS with Windows XP and it'll work like Loopback? If so, this is huge! From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 1:02 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Yep, by leveraging a per-computer attribute that you supply as a targeting criteria for a per-user setting, you effectively get the kind of behavior you are after with loopback, without using loopback. From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 10:53 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So you can get GPP User Properties to apply to a Computer without using Loopback and just using ILT (Item-Level Targeting)? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:58 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

dmarelia

Posts:441

12/09/2010 6:51 PM
Really you can use any criteria that is machine-specific, as long as its accessible from a per-user setting. For example, you CAN'T use security groups because when you're focused on an ILT for a per-user GPP setting, only user groups are exposed. From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Thursday, December 09, 2010 8:48 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Darren, does it have to be the 'environment variable' option, or can one use one of the default Item-level Targeting options? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 1:19 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Loopback does a specific thing-which is that it changes the way user policy is processed for that machine to either ignore or subjugate a user's "normal" policy settings in favor of those targeted to the machine account. What I'm suggesting is a little less complete but accomplishes the same goal in some cases. That is, you define a per-user GPP setting (in this case Power Scheme) and use Item-Level Targeting to only apply it if a per-computer criteria (e.g. an environment variable value) is true. There are likely still situations where you would still need to use loopback (e.g. kiosk machines, Terminal Servers, etc.) but for your particular situation, this approach may work. Note that you still have to do something on these computers to identify them as "special" in the eyes of GPP-in this case, by adding an environment variable on the machine. Hope that helps. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 11:12 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So I can create a GPP User Power Scheme and set it up with ILT to target an OS with Windows XP and it'll work like Loopback? If so, this is huge! From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 1:02 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Yep, by leveraging a per-computer attribute that you supply as a targeting criteria for a per-user setting, you effectively get the kind of behavior you are after with loopback, without using loopback. From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 10:53 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback So you can get GPP User Properties to apply to a Computer without using Loopback and just using ILT (Item-Level Targeting)? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:58 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Well, there could be one way to do it. If you're using GP Preferences to deliver power settings, you could do something like this. Let's assume you have a set of computers that you want to apply a particular power scheme to. You could create an environment variable on those computers that indicates they get the power settings. Then using GP Preferences item-level targeting to filter on the value of that environment variable. The user power settings would only apply on that machine if that environment variable was set. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:38 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback Well that just makes life harder If only there was another way......... Thanks for the clarification, though. I think it has finally 'clicked.' From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:28 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback The only way to do that is to ensure that the list of GPOs processed by the computer under loopback, don't contain any other user settings. This might be accomplished by setting Block Inheritance on the OU where the loopback computers are, by moving the computer accounts, or by ensuring that GPOs don't contain both user and computer settings, making them harder to segregate in these kinds of scenarios. Keep in mind that by setting Block Inheritance, you could also be blocking important per-computer settings upstream if those GPOs also contain user settings. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:24 AM To: 'xxxxxxxxxxxxxxxx' Subject: RE: [gptalk] XP Power Management & Loopback How can I accomplish what I want if I just want a certain User GPO to be affected by Loopback and nothing else? From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Wednesday, December 08, 2010 11:18 AM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] XP Power Management & Loopback Adam- When a machine is set to loopback processing, then all GPOs that are processed by that machine account (based on its location in AD) that also contain user policy, will be processed. In other words, the user policy that is applying based on loopback does not just include the GPO that is enabling loopback. So, you could definitely see "weird" behavior based on whether you are using merge or replace mode in loopback. If your goal is to have power settings differ by machine type, then loopback in combination with per-user based power settings is a good strategy, but you do need to ensure that you understand the full effect of loopback in that case. RSOP Modeling may help here. Darren From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Adam C Juelich Sent: Wednesday, December 08, 2010 9:15 AM To: 'xxxxxxxxxxxxxxxx' Subject: [gptalk] XP Power Management & Loopback Hello, I've read that when managing Power Management settings via GPP for XP Machines it is recommended that you set them as User Settings and then enable Loopback. I have tested this but had a lot of weird stuff happening concerning my drive mapping. I was told that Loopback will only affect the policy that it is enabled on, but then it seemed like some people were saying that it would affect every User Policy including those in other GPOs. Why am I so confused? How have others successfully managed XP Power Settings? Thanks! ------------------------------------------------------------------ Adam C. Juelich A+, Network+, MCTS:Vista, MCSE: Server 2003, MCSA: Messaging Application and Hardware Specialist/Technician Pulaski Community School District 920-822-6075 "If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid" - Christopher Peterson

acjuelich

Posts:147

dougdelaney User is Offline

Posts:43

dmarelia

Posts:441

acjuelich

Posts:147

dmarelia

Posts:441

acjuelich

Posts:147

You are not authorized to post a reply.

Forums >GPTalk >GPTalk Mailing List > [gptalk] XP Power Management & Loopback

ActiveForums 3.7

Ads

The GPTalk Mailing List

List Posts

Members

Ads