Re: Moving FSMO roles to a new DC
- From: bambooyip <bambooyip@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 27 Dec 2007 12:57:01 -0800
Yes, the name resolution method I used is lmhosts file. On that part, it's
easy to change the IP address of the PDCe and PDC on lmhosts file.
Any more input from you guys ... Thanks in advance
"Jorge Silva" wrote:
Hi.
It has benn some time since I don't play with NT4, but here it goes:
Test it first if you can, but assuming that your resolution mechanism is
updated, you shouldn't have problems, just make sure that the changes are
reflected on the configuration files or Services like WINS that you're using
for resolution.
http://support.microsoft.com/kb/150800/en-us
Also wait for others imput
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"bambooyip" <bambooyip@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D5156591-2E4A-4F0B-BCDB-A39E2A882B65@xxxxxxxxxxxxxxxx
Hello all,
I have a question regarding moving roles of FSMO from one DC to another:
Yes, I have no problem to move the roles. However, I established a 2-way
trust relationship between one DC holding PDC-emulator with the PDC of a
NT4
domain. Such 2-way trust is extremely important to the 2 domains - AD and
NT.
My question is: after I move the PDC-emulator role from one DC to another,
will the trust relationship lose?? What is the prerequsites / steps I have
to
take first?
- References:
- Re: Moving FSMO roles to a new DC
- From: Jorge Silva
- Re: Moving FSMO roles to a new DC
- Prev by Date: RE: Clients logging into the wrong DC at remote site
- Next by Date: Re: Public access
- Previous by thread: Re: Moving FSMO roles to a new DC
- Next by thread: Re: Unabe to change FSMO
- Index(es):
Relevant Pages
|
