Re: FMSO question
- From: PRMolina <prmolina@xxxxxxxxx>
- Date: Thu, 26 Oct 2006 14:49:01 -0700
No prob. My hardware support wants me to replace the hard drives to see if
that doesn't cure the intermittant lockups.
Thanks for the advice, really helps me get on track with this.
"Jorge de Almeida Pinto [MVP - DS]" wrote:
I do say: "install and promote a new DC (make a GC as needed)".
you could also do a FORCE DEMOTION offline and promote after the cleanup of
the metadata and replication of the cleanup
you cn of course try a normal demotion but I suspect that will not
succeed...
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"PRMolina" <prmolina@xxxxxxxxx> wrote in message
news:0A4D649F-0D3E-40A2-A60F-A928DDB84655@xxxxxxxxxxxxxxxx
Thanks for the help, I think I'm begining to get my head around this one.
Jorge, when you say disconnect the promoted DC, I assume you mean the new
DC1 I threw in the mix. Can I just pull the ethernet cable, clean and
reconnect - that doesn't seem right; I would rather not wipe and reinstall
windows... I'm thinking I should demote it with dcpromo, then delete it
from
AD, then when AD is clean and running on DC2 rejoin the domain and
repromote
it to be the new DC1. Does that sound reasonable?
"Jorge de Almeida Pinto [MVP - DS]" wrote:
you did not clean the AD metadata of the DC that died as you should!
just deleting the computer account is not enough
see: http://blogs.dirteam.com/blogs/jorge/archive/2005/12/03/213.aspx
in your case I would:
* disconnect the promoted DC
* clean the AD metadata as needed
* seize FSMO roles as needed to another live DC
* install and promote a new DC (make a GC as needed)
* relocate the FSMO roles as needed
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"PRMolina" <prmolina@xxxxxxxxx> wrote in message
news:5477FF3F-D4F4-4996-B5E4-C98626002F46@xxxxxxxxxxxxxxxx
I have two DCs in a Win 2003 AD network, DC1 and DC2. DC1 crashed. I
removed it from Active Directory by right clicking on it in dsa.msc and
choosing delete. Then I rebuilt it, naming it DC1 again joined it to
the
domain and ran dcpromo. Everything works, although its only been a
couple
of
days so give it time.
I started thinking about it, and am wondering who my FMSOs are.
Checked
system log on DC1 and sure enough got an error 16651 "The directory
service
is missing mandatory configuration information, and is unable to
determine
the ownership of floating single-master operation roles". Also getting
some
warnings in the Directory Services logs in both servers, NTDS 1232
replication errors all relating to an inability to find the server with
these
roles.
It looks like there are risks if you introduce into a domain two
servers
with these roles, so I would like to keep them on DC1 "just in case"
even
though it has been wiped and reinstalled. This server is still
randomly
locking up on me, more than likely a hardware problem, so I have to
consider
the possibility that it will be out of commission at some point.
Should I just go in and seize the roles onto the new unimproved DC1?
Any advice/comments/sympathetic laughter would be greatly appreciated!
-Paul
- References:
- Re: FMSO question
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: FMSO question
- From: PRMolina
- Re: FMSO question
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: FMSO question
- Prev by Date: Re: Exchange replication in Active Directory.
- Next by Date: Re: Creating a Computer Object in ADAM
- Previous by thread: Re: FMSO question
- Next by thread: Re: FMSO question
- Index(es):
Relevant Pages
|
