**No Domain controller (URGENT)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All

I had 2 DCs and the master crashed. I'm left with the one that I would like
to make the master. Each time I try to change the Operations Master it tells
me the 2nd server is not available. Also my DNS is all wrong. the
_msdc(domain) forward zone is gone and the SRV record obviously is gone. I
cannot add PCs to the domain. I have 17 users on the Domain. What is the best
way to do this without reinstalling the server? I have looked everywhere for
help.

Thanks
 
Hi All

I had 2 DCs and the master crashed. I'm left with the one that I would like
to make the master. Each time I try to change the Operations Master it tells
me the 2nd server is not available. Also my DNS is all wrong. the
_msdc(domain) forward zone is gone and the SRV record obviously is gone. I
cannot add PCs to the domain. I have 17 users on the Domain. What is the best
way to do this without reinstalling the server? I have looked everywhere for
help.

Thanks
Click to expand...

to seize the roles:-

http://support.microsoft.com/kb/255504
 
Thank you both for your help. I am extremely grateful. I seized all the roles
and did the DNS as directed and the domain is ack to normal.

Thanks again
 
Hi All

I had 2 DCs and the master crashed. I'm left with the one that
I would like
to make the master. Each time I try to change the Operations
Master it tells
me the 2nd server is not available. Also my DNS is all wrong.
the
_msdc(domain) forward zone is gone and the SRV record
obviously is gone. I
cannot add PCs to the domain. I have 17 users on the Domain.
What is the best
way to do this without reinstalling the server? I have looked
everywhere for
help.

Thanks
Click to expand...

instead of transfering the FSMO roles, you should SEIZE them. The old
server must NEVER come back online again!
For information on transfering or seizing FSMO roles see:
http://support.microsoft.com/?id=324801 (How to view and transfer FSMO
roles in Windows Server 2003)
http://support.microsoft.com/?id=255504 (Using Ntdsutil.exe to
transfer or seize FSMO roles to a domain controller)
http://support.microsoft.com/?id=255690 (How to view and transfer FSMO
roles in the graphical user interface)
http://support.microsoft.com/?id=197132 (Windows 2000 Active Directory
FSMO roles)
http://www.petri.co.il/transferring_fsmo_roles.htm
http://www.petri.co.il/seizing_fsmo_roles.htm

There is one FSMO role however you might need to reconfigure! If it is
the PDC FSMO of the forest root domain you are moving you need to
reconfigure the NEW FSMO role owner DC with an external time source
and reconfigure the OLD FSMO role owner DC to use the domain hierarchy
On the old FSMO role owner DC run:
--> NET TIME /QUERYSNTP
Configure the new FSMO role owner DC with
--> NET TIME /SETSNTP[:ntp server list]
or --> W32tm /config /manualpeerlist:â€<time server 1> <time server
2> <time server n>†/syncfromflags:manual

To update the “Windows Time Service†configuration:
--> W32tm /config /update
OR
--> Net stop w32time & net start w32time

To resync time:
--> W32tm /resync

To clear the NTP configuration on the old PDC
--> NET TIME /SETSNTP

Fore more info
MS-KBQ816042_How to configure an authoritative time server in Windows
Server 2003

Don’t forget to clean the metadata of the old server
For more info on that see:
How to remove data in Active Directory after an unsuccessful domain
controller demotion
--> http://support.microsoft.com/?id=216498

Clean up server metadata
-->
http://www.microsoft.com/technet/pr...ons/012793ee-5e8c-4a5c-9f66-4a486a7114fd.mspx

Delete extinct server metadata
-->
http://www.microsoft.com/technet/pr...elp/1a7522c3-ac6e-4f83-af5b-9be87b47a95d.mspx

How can I manually delete a server object from the Active Directory
database in case of a bad DCPROMO procedure?
--> http://www.petri.co.il/fix_unsuccessful_demotion.htm

How can I delete a failed Domain Controller object from Active
Directory?
--> http://www.petri.co.il/delete_failed_dcs_from_ad.htm


Concerning DNS...
If the zone was AD integrated and it followed the domain replication
scope just install DNS on the remaining server. Otherwise Install DNS
and recreate the zones. Don’t forget to point other servers and
client to the new DNS server

Final tip: install a second DC again!
 
Back
Top