Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

Group policy setting policy for all users

When I create a default profile on a Windows XP, it is inheriting the User Settings in Group Policy for the copied user to all users. Users are not getting the Group Policy settings that are not designated for them, but inheriting it from the default profile.
example: I have a policy that automatically locks a PC after a period of inactivity. This policy is applied to my account. If I use my account to create a local default user, all users that use that PC are getting the automatic lock regardless of what is set to their account in Group Policy.
1 Solution
Is there possibly a computer policy over  riding your user's policy that is effecting the policies?
Joseph DalyCommented:
I would agree that doesnt sound right. I would first check as stated to make sure you dont have a conflicting GPO being applied.

You could run a GPupdate /force and then a gpresult while logged in as the other user to see what is being applied.

A few other normal things to check make sure you arent trying to set user policies based on a computer or vice versa.
dale-gregoryAuthor Commented:
When I run the gpresult, under the other user's account, I get the correct settings for that user. There is normally a setting under the gpedit/Local Policy under User Settings\Windows Settings Control Panel that can be disabled to stop the locking screensaver. The Control Panel Option isn't even listed in the Local Policy now.
In any case, I have a Pc that is locking on every user after a period of inactivity. Not totally a bad thing, but the user is having a fit to have it removed and I cannot get it to apply their GPO User Settings to their local account.
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

You can run RSOP.MSC to check which is the actual policy applied on domain user.
Run gpupdate /force & check what is logged into event viewer of application or system log.
Check folder redrection in GPO as well as Loopbackpolicy enabled on domain level.
dale-gregoryAuthor Commented:
I have tried these solutions and I am awaiting feedback from my user. Thanks for your help and I will follow up as soon as I findo ut how this is working under their account logon.
dale-gregoryAuthor Commented:
After trying all of this, I still had the issue existing. I ended up logging into the device and setting the local administrator as the Default User. I then had one of my technicians who normally does the setup logon and verify settings and then log in as local administrator and assign their account as the Default User. this fixed the problem, but I still do not know why the user was inheriting my AD GPO settings instead of the one that was assigned to them.
Even when running rsop.msc with the user logged in, it reported that the user was being applied the correct GPO.
Thanks for your help.

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now