Server 2003 Group Policy, Not functioning correctly.
Posted on 2012-08-14
I have a single Server 2003 R2 SP2 that is acting as a DC.
Two weird things are occurring that I'm not familiar with:
MORE IMPORTANT ISSUE:
1) I have a GPO that maps a few drives. I edited the mapdrive.bat that this points to to remap the F: drive to another shared location. We manually went to each workstation and changed the F: drive to the new shared location. Upon restarting or logging off and logging back on any of the computers they somehow remapped the F: drive to the old location. I double checked the mapdrive.bat that the GPO was pointed to and it did not have the old location in it. Its as if the old mapdrive.bat is somehow stuck in limbo in the GPO or the old F: drive map is stuck in limbo and keeps getting mapped even though its not defined.
I even denied the GPO to one user and when restarting her computer after disconnecting the old share it reconnected itself to the old share under F:!!! running RSOP.msc showed that the mapdrive.bat startup script GPO was not effecting the computer anymore, however, somehow F: was being automatically mapped? I checked for startup and tasks on the user profile and there's nothing defined.
I checked the DC event log and there's no errors or problems. I'm stumped.
LESS IMPORTANT ISSUE:
2) In Group Policy Management, when creating a new Organizational Unit, it is not automatically using senior GPOs linked to senior OUs. For example, I have an "Employees" GPO right under the domain which has the "Default Domain Policy". I edited the default domain policy to enable RDP on all workstations. It wouldn't take effect until I manually linked the "Default Domain Policy" GPO to that OU. That OU only has a "mapdrive" GPO so there's no GPO conflicting with "Default Domain Policy". Its as if inheritance is blocked but its not? I had to manually right click the OU and link the "Default Domain Policy" to it to make the RDP map work. I'm used to it just inheriting the changes.