deleting a Ghost PDC

Access2000

Honorable
Aug 26, 2013
5
0
10,510
Hi everyone,
I have problems and i can't figure out what to do.I used to have 3 servers running; PDC(server200) and the other two running (server 2000) and a New one with (Server2008). Then one day 2 servers die the PDC and the other one running (server2000). SO I ended running only one(server2008) a GC with funcinality server2000.
I bought a new Server with (server2012) but i can get it to be a DC because the funcionality. so I try to get raise the funcionality on the GC(server 2008) but it wont let me it said that it can't find the PDC.
I also try to put the new server(server2012) as a DC on the same domain but it said it can find the other Domian controller.. I am stuck!!
If anyone have any ideas. or a sire where i can read of how to do this I would really appreciated..
thanks
JAC
 
Solution
Not necessarily. A GC is a global catalog, and so it should be a domain controller.
There are roles that run on domain controllers. Typically these roles are run on only 1 DC - not all the dc's. If a DC dies, and it is running one of these roles, this role needs to be moved to another DC.
So you need to move all the roles to the only DC.
http://support.microsoft.com/kb/255504

Also you've had some DC's that are orphaned (they were on the domain, but not removed from the domain - they were just turned off, or died). These are still in the catalog, and machines will try to access them. The orphaned dc's need to be removed.
http://support.microsoft.com/kb/555846

Once this has been done, you should have 1 domain controller with all the...
You need to do some serious reading about domains and domain controllers. First you need to have certain roles running on a domain controller somewhere on your domain. They can all be on 1 DC, or spread out. When a DC dies, there's some clean-up that needs to be done to keep the domain running smooth, and the database free of garbage. There are likely machines in your domain looking for DC's that are no longer there. Also a 2000 DC is an old box, but the domain forest level is probably still at the 2000 domain level. This needs to be upgraded before you can add a 2012 domain controller.
 

Access2000

Honorable
Aug 26, 2013
5
0
10,510
So my problem is that i have only on Machine running as right now and it is a GC running (Server 2008)
I do not have any Domain controller running anywhere.. am I doomed?
 
Not necessarily. A GC is a global catalog, and so it should be a domain controller.
There are roles that run on domain controllers. Typically these roles are run on only 1 DC - not all the dc's. If a DC dies, and it is running one of these roles, this role needs to be moved to another DC.
So you need to move all the roles to the only DC.
http://support.microsoft.com/kb/255504

Also you've had some DC's that are orphaned (they were on the domain, but not removed from the domain - they were just turned off, or died). These are still in the catalog, and machines will try to access them. The orphaned dc's need to be removed.
http://support.microsoft.com/kb/555846

Once this has been done, you should have 1 domain controller with all the FSMO roles, and the global catalog. This is a 2008 domain controller running on a 2000 domain. You need to move the domain functional level to 2003, then to 2008.
http://support.microsoft.com/kb/322692
http://technet.microsoft.com/en-us/library/cc730985.aspx

Once the domain is at a 2008 level, you can add a 2012 domain controller. the you'll have 2 domain controllers. I'd make them both global catalog servers (the global catalog is the database that includes everything on your domain). This way you can lose a domain controller and still function.

I think I've included everything.
 
Solution