Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Restore Domain Controller

Status
Not open for further replies.
Apr 5, 2006
33
NG
Hi All,

I set up two windows 2003 server domain controllers in a domain. namely sever1.coy.com (the first domain controller in the domain) and server2.coy.com (the second domain controller in the domain).

server2 DC is load balancing for server1 DC. Now server1 has crashed. I have installed fresh windows 2003 server on it.

How can I re-instate the status of server1 (i.e. What can I do to get server1 back to its global catalogue status)

I will appreciate every time spent to contribute to this.

Thank you.

Omotomilola
 
First thing to do is track down which server holds the FSMO Roles.


Then, if your old server1 held the fsmo's you should make sure it is not now named the same as it was before.

Run DCpromo on your fresh install of win 2003.

then if neseccary, seize the FSMO's back to this server.


Then, you need to make it a GC.


I think this should just about cover it.

Don't forget about other roles this server may have been running, like DNS or DHCP.



Windows and NT Admin.
 
Hi Scott,

Thanks for the response.

Like I said, I have lost the first DC in my domain which means I have lost both Schema master and Domain Naming FSMOs.

However, I still have the second DC that host Infrastructure, Relative ID and PDC emulator FSMO.

Is it posible to regain the FSMO (Schena and Domain Naming FSMOs or configure/promote the second domain controller to the status of the crashed DC.

Thanks.

Omotomilola.
 
surely you have a backup of the 1st server, restore AD from tape. work through the remaining issues and all should be golden. if you dont have a backup of the 1st AD server you can seize the roles you lost, MS has good docs on how to do that.
 
You can seize the roles, The link I supplied earlier shows how to do this.

Although, you probably won't notice the lack of these 2 roles until you either try to extend the schema or create a child domain.

Somebody please correct me if I'm wrong on this.

Windows and NT Admin.
 
I'm happy to hear that there is solution to this problem.

Though I do not have backup of the crashed DC but I will search for information on how to seize roles from microsoft.com to resolve the problem.

However, I will so much appreciate your information on how to seize FSMO role and resolve the problem.

Thank you very much.

Omotomilola.
 
Thanks Mark,

This link is the solution to how to remove metadata of crashed DC
Like I said, Ive already installed new windows 2003 server using the hostsame of the crashed DC.

During the dcpromo wizard, after selecting new Domain controller in the new domain and domain in a new forest. It prompted me to supply Full DNS name for the new domain.

When i entered the same Full domain name I used for the crashed DC, it did not accept it, rather it suggested another domain name for me to use.

Is there anything I can do to use the hostname of the crashed DC on the new server? I don't want to change the hostname or domain name on the new server.

I will appreciate your solution on this.

Omotomilola.
 
Hi all,

After removing the crashed DC metadata on the functioning domain and siezed all the five FSMOs running on it, I decided to join my newly installed windows 2003 server to the domain.

I got an error message when trying to join a windows 2003 server to a domain.

When I checked the Net logon service on the client, I found out that the Net Logon on it (client) is not started.

I then change the start up type to automatic and click START botton to start. I got this error message:

"The Netlogon service on the local computer started and then stoped.Some services stop outomatically when the have no work to do, for example, the Performance log and alert services"

I also restarted the machine to see if my changes will be validated, it gives same error message. But all along, I could join other client machines to the domain, this confirms the functionality of the DNS.

What should I do to make this service run automatically.

I will appreciate your contribution.

Thanks.

Leke
 
Thank you all,

My problem was basically firewall that was enabled on the domain controller.

I was able to join windows 2003 server to the domain ahen I disabled the firewall.

Note that windows 2003 server can not be joined to domain whose domain controller is firewall enabled.

Once again, I say thank you.

Leke.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top