My Technet

In this post, I am sharing a recent experience with Roaming profile and group policy.

Let’s assume the following scenario

UserA exists in OU OrgA

Group Policy applied on OrgA with c: drive blocked

UserA moved to OU OrgB

OrgB do not have any GPO which blocks c: drive

In a normal case, if you will update group policy on client or logoff and login, you should be able to see the the changes. In above example, c: should have been accessible.

However, the problem sometime may come that you still see that old GPOs/settings are getting applied. If you will run GPResult and look at the RSOP result, you find that GPOs from the new OU are being applied. Still, why we have settings from the GPOs on the old OU?

Very irritating

The problem here is with Roaming Profile. I haven’t dig in to find why, but creating a new profile and moving the data from old to new (only user data, not the system data), solved the issue.

The issue may be similar to the one described in following KB. Not sure though.

http://support.microsoft.com/kb/830464

If you want to resolve the problem but do not want to find the root cause, this post might help you!

Tags: Old group policy settings, roaming profile

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.