Question Locked

Active Directory Guru

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm currently having an issue with my Active Directory. I have 1 domain with
2 DC's.
DC1 has the Scema Master,Domain Naming Master,RID Master, PDC installed &
DC2 has the Infrastructure Master Installed. DC2 failed and was not demoted
from the network. It was fixed and put back into the network with the same
name as before. When I run dcdiag /test:Knowsofroleholders /v I will receive
a warning stating CN=NTDS Settings\cn attribute blah blah is the
Infrastructure Update Owner, but is deleted.

If I go into ADSIedit.msc, then go to configuration\sites\servers\Our
Server\CN=NTDS Settings the cn attribute is different than the one that was
in the warning message when running dcdiag.

If I run metadata cleanup will it clean out the old cn attribute that is out
there from the old DC or will it mess up the new cn attribute that I see in
ADSI. Just want to remove the old data, but since the DC2 was brought back
into the network with the same computer name was wondering if it would mess
up my Active Directory. Sorry so long, just trying to include everything I
can.

8 replies

by cg it

depends on what you did in "fixing"

if you wiped and reinstalled NEW , not from a backup, then it's a new server regarless of the same name. so you have a NEW attribute. Basically a NEW server so you would have to join it to the domain.

if you replaced failed hardware and reinstalled from a backup of that server, you should NOT have a new attribute. Further you should NOT have had to rejoin the domain.

so really the question is what did you do to fix it that would answer whether or not cleaning up AD would have an impact.

In either case the old new server seems to have generated a new object in AD therefore the old object isn't any good [tombstoning comes to mind].

Added: there are SIDs assigned which are unique to the computer. once you wipe and reinstall not from a backup, you get rid of the SID. so you need to join the domain and the domain then assigns a new SID.

restoring from a backup including system state [hope in includes system state] so that you aren't getting rid of the old SID. Therefore AD already knows the computer.

by helpdesk

The computer was running Windows 2000 server and the server ended up with a bad hard drive. So the hard drive was replaced and Windows 2003 server was installed on the server using the same computer name as before. The only role that was and is now on the server is the Infrastruture Master role, and running the dcdiag /test:KnowsOfRoleHolder I get a warning stating CN=NTDS Settings blah blah is the Infrastructure Update Owner, but is deleted. I go into adsiedit CN=Configuration\CN=Sites\Servers\Our Actual Server\CN=NTDS and the cn attribute is totally different from what was shown with the warning. I hope someone can help me out witht this matter. Thanks

by cg it

new computer.

Having the same server name with a new computer/server doesn't really mean anything in Active Directory. As far as it's concerned, it's a new object and has assigned it a unique identifier and SID.

There's 2 courses of action. you can grab the infrastructure master role with the first DC. Then assign it to the new server, so that your AD metadatabase doesn't think the old server which is no longer there is supposed to have it,

or you can get a another HDD, install W2K Server, do a restore from backup and place it on the network. AD will see that the old server with is the Infrastructure Master role is back online. Then transfer the role to the new DC [W2003 server]. demote the old server to a member server and remove it from the network .

This second suggestion is the most graceful way of moving around FSMO roles in a network without having to resort to seizing roles that are left hanging when a server dies and a new one is installed. It's also the better way of removing old DCs. Though its some effort, objects that are no longer needed aren't left hanging around in the AD. database

Here is a great article on FSMO roles, their function, and some of what happens when one or more of the roles go missing.

http://www.windowsnetworking.com/articles_tutorials/Networking-Basics-Part8.html

by helpdesk

Thanks for all your help. In your reply you mentioned 2 courses of action that I could take. Could you explain in more detail what I would need to do in order to grab the infrastructure master role with the first DC. That you meationed in the first course of action that I could take. Thanks again for all your time.

by cg it

here's an article on it:

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

see the notes on which course: transfer or seize roles. it explains what senario happened to a DC that held a role and which course of action to take.

in your case a new operating system was installed, so seizing the role is required because the old server is not available [again see the seize role notes]: I would recommend that you sieze the Infrastructure master role with the DC that remained on the network. run the metadata cleanup option.
Note: you mention that the new server seems to have the infrastrucutre master role.. so I'll assume that you tried to transfer the Infrastructure master role to the new W2003 DC without seizing the role from the old one. Best course I would recommend is, to DC promo demote the W2003 server to a member server. That will effectively get rid of the infrastructure master role on that server. Then follow the sieze role procedure, metadata clean up, dc promo promote the W2003 server then transfer the role to it.

the idea is to keep AD metadata as clean as possible.

by helpdesk

Thanks again for taking time out to lend me a hand.

by cg it

most questions on a Windows Platform can be answered via MS KB either from help and support or technet.

This discussion is closed to new replies.