Jorge
Tue Mar 25 06:45:31 PDT 2008
why don't you try it yourself in a test environment? do it step by step and
look at the attributes on the computer account of the DC how they change.
Use LDP to look at it
--
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
------------------------------------------------------------------------------------------
* How to ask a question -->
http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"rileymartin" <rileymartin@discussions.microsoft.com> wrote in message
news:207CBB73-74F8-4F65-8FB1-A936B73D039C@microsoft.com...
> Thanks for correcting me. I need to understand how this works. Does that
> mean the the NETDOM utility allows the recently renamed DC to be located
> by
> either the new or the old name and avoiding any potential synchronization
> issues from the new name not being repliated immediately?
>
>
>
> "Jorge de Almeida Pinto [MVP - DS]" wrote:
>
>> it has nothing to do with synchronizing more quickly. The difference is
>> that
>> NETDOM introduces a new name while keeping the old one. That gives time
>> to
>> replicate out to other DCs so that those get to know its new name. After
>> that you can remove the old name
>>
>> the GUI just replaces the old name with the new name
>>
>> --
>>
>> 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
>> ------------------------------------------------------------------------------------------
>> * How to ask a question -->
http://support.microsoft.com/?id=555375
>> ------------------------------------------------------------------------------------------
>> * This posting is provided "AS IS" with no warranties and confers no
>> rights!
>> * Always test before implementing!
>> ------------------------------------------------------------------------------------------
>> #################################################
>> #################################################
>> ------------------------------------------------------------------------------------------
>> "rileymartin" <rileymartin@discussions.microsoft.com> wrote in message
>> news:B20DCC74-9909-4038-B58E-79227DCECBCB@microsoft.com...
>> > Thank you both for the info.
>> >
>> > I read all the links and it seems that you can rename the DC both ways,
>> > by
>> > changing the name of the server and then rebooting and also by using
>> > the
>> > NETDOM utility however the NETDOM utility will 'somehow' synchronize
>> > the
>> > name
>> > change in AD more quickly. I also read that with either method you
>> > still
>> > want to use active directory users and computers to change the name of
>> > the
>> > corresponding frsmember object to avoid any future issues if reusing
>> > the
>> > old
>> > name for a new DC.
>> >
>> > Do either of you know why NETDOM synchronizes the name change more
>> > quickly?
>> > I couldn't find that information anywhere. Thanks again, this is good
>> > stuff.
>> >
>> > "Jorge Silva" wrote:
>> >
>> >> Hi
>> >> Using NETOM, Basically you rename, then reboot, then remove the old
>> >> name.
>> >>
>> >> --
>> >> I hope that the information above helps you.
>> >> Have a Nice day.
>> >>
>> >> Jorge Silva
>> >> MCSE, MVP Directory Services
>>
>>