$olución de problema$ & Escenarios

1. PDC is crashed but there was no impact thanks to ADC. How can i configure DC using ADC ?

If the DC goes down , Then there is no need to configure DC using ADC. Please follow below procedure

1.Have to make sure to seize the FSMO roles to Additional domain controller. (Note – this action should performed only if Primary DC holds FSMO roles , In case you Additional domain controller hold the FSMO roles then No need to perform step 1 and 2)

http://support.microsoft.com/kb/255504

2. Once all the roles seized , go ahead the configure time service on new PDC Emulator holding DC ( i.e on addititonal domain controller where seized the roles).
Refer beliow link which explains how to configure time service on PDC emulator

http://social.technet.microsoft.com/wiki/contents/articles/8863.time-service-configuration-on-dc-with-pdc-emulator-fsmo-role.aspx
3. Once this is done run netdom query fsmo to make sure my ADC holds all the FSMO roles

4.Perform metadata cleanup in primary DC which has got failed (Refer below link) and also make sure that none of the old DC DNS entries exists in the domain(refer 2nd link to check where to find out the old DC entries in DNS)

http://support.microsoft.com/kb/216498

http://blogs.msmvps.com/awinish/2011/05/08/metadata-cleanup-of-a-domain-controller/

5. After accomplishing this , go ahead and rebuild primary DC by installing server OS in it and run dcpromo on it and wait for replication

6. Once this is done transfer back all FSMO roles from my ADC ( You need to configure time service once again if you are transferring the roles)

2. METADATA Cleanup

https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

http://kpytko.pl/active-directory-domain-services/metadata-cleanup-over-gui/

NTDSUTIL – option 1 (step by step, complete commands)
.

PS C:\> ntdsutil
C:\Windows\system32\ntdsutil.exe: activate instance ntds
Active instance set to “ntds”.
C:\Windows\system32\ntdsutil.exe: metadata cleanup
metadata cleanup: connections
server connections: connect to server DC5
Binding to DC5 …
Connected to DC5 using credentials of locally logged on user.
server connections: quit
metadata cleanup: select operation target
select operation target: list domains
Found 1 domain(s)
0 – DC=mynet,DC=lan
select operation target: select domain 0
No current site
Domain – DC=mynet,DC=lan
No current server
No current Naming Context
select operation target: list sites
Found 1 site(s)
0 – CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
select operation target: select site 0
Site – CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
Domain – DC=mynet,DC=lan
No current server
No current Naming Context
select operation target: list servers in site
Found 2 server(s)
0 – CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
1 – CN=DC5,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
select operation target: select server 0
Site – CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
Domain – DC=mynet,DC=lan
Server – CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
DSA object – CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
DNS host name – DC2.mynet.lan
Computer object – CN=DC2,OU=Domain Controllers,DC=mynet,DC=lan
No current Naming Context
select operation target: quit
metadata cleanup: remove selected server

Transferring / Seizing FSMO roles off the selected server.
Removing FRS metadata for the selected server.
Searching for FRS members under “CN=DC2,OU=Domain Controllers,DC=mynet,DC=lan”.

Removing FRS member “CN=DC2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=mynet,DC=lan”.

Deleting subtree under “CN=DC2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=mynet,DC=lan”.

Deleting subtree under “CN=DC2,OU=Domain Controllers,DC=mynet,DC=lan”.
The attempt to remove the FRS settings on CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan failed because “Element not found.”;
metadata cleanup is continuing.

“CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan” removed from server “DC5”

metadata cleanup: q
C:\Windows\system32\ntdsutil.exe: q
PS C:\>
NTDSUTIL option 2 – abbreviated commands

Note: the commands entered in the previous section can be more or less abbreviated, as shown below, as long as there is no ambuguity with other ntdsutil commands. Once again, I have made minor edits (font size and spacing) for readbility.

PS C:\Users\ufc> ntdsutil “act ins ntds” “meta clean” conn “co to ser DC5” q “s o t” “l d”

C:\Windows\system32\ntdsutil.exe: act ins ntds
Active instance set to “ntds”.
C:\Windows\system32\ntdsutil.exe: meta clean
metadata cleanup: conn
server connections: co to ser DC5
Binding to DC5 …
Connected to DC5 using credentials of locally logged on user.
server connections: q
metadata cleanup: s o t
select operation target: l d
Found 1 domain(s)

Note: we stopped the command above at “list domains” or “l d” since the choices that follow depend on the number of domains and the names of the sites and servers, which we may not know beforehand. If we do, we can enter all the information on a single line as shown in the next example.

0 – DC=mynet,DC=lan
select operation target: sel dom 0
No current site
Domain – DC=mynet,DC=lan
No current server
No current Naming Context
select operation target: list sites
Found 1 site(s)
0 – CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
select operation target: sel site 0
Site – CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
Domain – DC=mynet,DC=lan
No current server
No current Naming Context
select operation target: list serv in site
Found 2 server(s)
0 – CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
1 – CN=DC5,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
select operation target: sel ser 0
Site – CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
Domain – DC=mynet,DC=lan
Server – CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
DSA object – CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan
DNS host name – DC2.mynet.lan
Computer object – CN=DC2,OU=Domain Controllers,DC=mynet,DC=lan
No current Naming Context

select operation target: q
metadata cleanup: rem sel ser

Transferring / Seizing FSMO roles off the selected server.
Removing FRS metadata for the selected server.
Searching for FRS members under “CN=DC2,OU=Domain Controllers,DC=mynet,DC=lan”.

Removing FRS member “CN=DC2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=mynet,DC=lan”.

Deleting subtree under “CN=DC2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=mynet,DC=lan”.

Deleting subtree under “CN=DC2,OU=Domain Controllers,DC=mynet,DC=lan”.
The attempt to remove the FRS settings on CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan failed because “Element not found.”;
metadata cleanup is continuing.

“CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mynet,DC=lan” removed from server “DC5”
metadata cleanup:
NTDSUTIL – option 3 (single command)

Note: in fact, we have to enter three commands before entering the “remove selected server” command with the path to the server to remove.
PS C:\Users\ufc> ntdsutil
C:\Windows\system32\ntdsutil.exe: activate instance ntds
Active instance set to “ntds”.
C:\Windows\system32\ntdsutil.exe: metadata cleanup
metadata cleanup: remove selected server cn=DC2,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=mynet,dc=lan

Binding to localhost …
Connected to localhost using credentials of locally logged on user.
Transferring / Seizing FSMO roles off the selected server.
Removing FRS metadata for the selected server.

You can then verify everything has gone well with the metadata cleanup  by running the following checks at an elevated command line on an Active Domain Controller.

Dcdiag /a /c /v /f:C:\logfile.log

Repadmin /showrepl * /verbose /all /intersite > C:\repllog.log

 

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s