asked on

Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9}

Recently promoted a windows 2003 server in our AD, transferred all roles, including GC, and then demoted the old 2000 server. After a reboot last week, I get this error in event viewer every 5 minutes.

Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=geowire,DC=net. The file must be present at the location <\\geowire.net\sysvol\geowire.net\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted.

It seems as if it was a result of after deleted the old domain controller from AD

What can be the cause of the error I am getting. the file is in the location specified.

stafi

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

ASKER CERTIFIED SOLUTION

scrathcyboy

membership

This solution is only available to members.

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

Start Free Trial

shankshank

ASKER

still need to resolve this

scrathcyboy

The links I posted should have given the solution. Even though the file is there, the role of the server is no longer a domain controller, so the new servers are still looking for a domain controller with that gpt.ini file because it had data in that the other servers were using. You should be able to remove this server from DC status in the new DCs setup, even the registry if you have to.

shankshank

ASKER

The new server is the DC though, and I did remove the olde server

scrathcyboy

You say the file is in the location specified, but now you say you removed the old server. The {long key name} relates to the OLD server, not the new one, yes? Or something in the INI file is still looking to the old server.

If you cant track it down, rebuild the AD for the new server only.

shankshank

ASKER

Ok now I am really confused, lol

Here's what I did.

I added a new server, 2003, promoted as DC and all other roles. Retired the old 2000 server.

I can see the file on the new server, but I get those errors

scrathcyboy

{31B2F340-016D-11D2-945F-00C04FB984F9}
{31B2F340-016D-11D2-945F-00C04FB984F9}

Those are coded key names to refer to a specific machine (not just a machine name) and data in the registry that refers to the old system. You might have to manually go through those keys in the registry, or in the second key case, this is a folder on the hard drive, and change the reference to match the similar (but not identical) key name on the NEW machine. Copying those hex coded keys from one system to the other does not usually work, unless the setup and hardware is identical. That is not the case with two different DCs.