dcpromo

[Guest]

If I am going to setup a new domain controller to replace an nt server dc at
a site, does it matter where I authenticate it from? I work in the main site
and usually build the machines here, if I authenticate/promote it here and
then take it to the site, will I run into any problems?

 

[ptwilliams]

It doesn't matter where you build your DC. However, if you build it at the
central site and move it to another, there are one or two considerations you
should think about.

The following article briefly discusses the process of moving a DC and a
couple of points of note:
-- http://www.msresource.net/content/view/22/47/


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

If I am going to setup a new domain controller to replace an nt server dc at
a site, does it matter where I authenticate it from? I work in the main site
and usually build the machines here, if I authenticate/promote it here and
then take it to the site, will I run into any problems?

 

[Guest]

so, after reading the article, wouldn't you agree, it's much easier to simply
throw a server os on the thing and do the work from the physical site?

 

[Ryan Hanisco]

That is easier if you readily have access to it.

You can also use the system state backup to create a staged version of the
DC and prepare the server for remote deployment. This is usually only really
useful if you are doing a large number of servers and can't depend on
technical staff on site -- like to rack the server and connect it.