Forced transfer of the infrastructure operations master

[John_2001]

Greetings all!

In my domain I had two DC. On both DC Windows Server 2000 was installed.
Recently I've removed one DC from the domain (because it didn't work
properly), and tried to join DC with Window Server 2003.
Because I didn't remove that DC from AD when it was still connected to the
domain, I had few problems with the old data and link, but I managed to
solve all but one!
The only problem I have is that currently I don't have "Infrastructure
operations master" FSMO role. Under Infrastructure operations master stands
"ERROR" with description "The current operation master is offline. The role
cannot be transferred".
If I understand correctly I should do forced transfer of the infrastructure
operations master.
Can I do some damage to my domain with this forced transfer and what
negative consequences can occur?

PS: I've changed mixed mode to native mode on DC and started adprep
/forestprep. I couldn't finish adprep /domainprep

Best regards

John

 

[Paul Bergson]

Yeah, you need to clean up AD before you do anything else.

http://support.microsoft.com/?id=216498



Also I would do the following to check the health, I would wait a couple
hours after you have clean up your metadata

Try running dcdiag. Look for fail, error and warning errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

See for more details

http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx


--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[barabba72]

If your organization has a single domain, the loss of the IOM will have
no impact; this doesn't mean you can leave it as is, simply take your
time and when you're done cleaning up, proceed with seizing.

 

[Guest]

I noticed your post after placing one about lls. It's kinda funny but I had
the exact same issue 2 weeks ago on one of my child domains. Like you, I
didnt want to force the transfer of roles until I exhausted all other methods
first because the artical I read indicated possible problems afterwards.

I had a server(1 of 2 in the child domain) that went down "ungracefully".
After I restored an backup image onto the downed server and resetting the
burrflags for sysvol sharing , I incountered FSMO role problems. I could get
replication to occurr between parent domain and each DC in the child, but not
between the 2 DC's of that child. I kept getting an "internal error". I could
not transfer the roles between the DC's either. Both servers, through AD
Users and Computers in the Operations Master, indicated that the Infrasture
role was being held by the other DC, not sure why.
I was curious to know which DC had accurate information so I DCPROMO'ed
another W2k server into that child domain. After correcting the DNS problem
with the suffix, the new 3rd (but temporary DC) had been assigned the
Infrastructure role. I dont know why or if it was supposed to or not but
nevertheless, after replication all DC's were in sync. I was the about to
transfer roles back to the way it was supposed to be and DCPROMO'ed the 3rd
DC back out. Also I read that Infrastructure role and Global Catalog are
incompatible to each other, keep this in mind if you dont already..