asked on

SYSVOL Policies

In May 2007 I backed up the System State copied it to one of our banch office, restore it to a temp folder on c: drive and did a DCPROMO /ADV on a Windows 2003 R2 server. Everything works great. But last night I was on Branch server copying over some files when I notice the c:\temp folder still have these old restored files -- so I deleted the contents of the Temp folder. Now I'm getting "Windows cannot access the file gpt.ini for GPO CN={6AC1786C-016F-11D2-945F-00C04fB984F9},CN=Policies,CN=System,DC=arcticgroup,DC=local. The file must be present at the location <\\arcticgroup.local\sysvol\arcticgroup.local\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted."

The question is, why would the \\domain\sysvol\ point to the temp folder?

PlaceboC6

Check this registry key on the server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysVol

That shows the location of the sysvol share. The error you posted is pointing at the default domain controller policy in particular.

PlaceboC6

Additionally, this KB is great for troubleshooting these errors:

http://support.microsoft.com/default.aspx?scid=kb;en-us;887303

scrathcyboy

these errors are typical of not following the exact rules of M$ for DC promo and demote of the old DC. WHat is in these for W2K is much the same as 2003, the DCs need to be promoted/demoted the same

support.microsoft.com/kb/238369
support.microsoft.com/kb/296882
www.howtonetworking.com/articles/dchowto.htm
technet2.microsoft.com/windowsserver/en/library/702e903a-c2c6-4039-88dd-9379c062edcf1033.mspx
http://search.techrepublic.com.com/search/Microsoft+Windows+Active+Directory+and+Microsoft+Windows+Server+and+domain+controller.html

PlaceboC6

Hi agihelp, were you still needing assistance with this issue?

ASKER CERTIFIED SOLUTION

agihelp

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

agihelp

ASKER

I resolved the problem by demoting the domain controller, removed it from the domain, delete the Temporary files (old state backup), rejoin the domain, restore a fresh backup of the state data, promo the machine to domain controller and delete the restored state data.