Hello TC,
You can do it that way. On the test DC you have to seize the FSMO roles and
then NEVER connet it back with the production domain.
http://support.microsoft.com/kb/255504
On the production domain you have to remove the test DC also from AD database
as you can NEVER connect it back to demote correct, FSMO of course leave
untouched here:
http://support.microsoft.com/kb/555846/en-us
For adding the Windows server 2008 machine see my blog:
http://msmvps.com/blogs/mweber/archi...r-2008-r2.aspx
There is no need to add a Windows server 2003 DC to the domain before.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Dear all,
>
> I want to copy the production DC to an separate network for migration
> testing ( from Windows 2000 to Windows 2008 R2)
> Our existing DC is an windows 2000 Server, we don't have Exchange
> server.
> Is it the step like this
>
> 1) add a windows 2000 server as the secondary domain controller.
> 2) create a new global catalog on the second domain controller
> 3) move the testing 2nd domain controller to separate network
> 4) change FSMO role the testing domain.
> 5) Add the windows 2008 R2 server as domain control
> 6) change FSMO role to the new windows 2008 R2
> Questions
> 1) Is the above step correct?
> 2) What should be prepared in the Windows 200 server before we join
> the
> windows 2008 machine as a domain controller?
> 3) One of our vendor suggested that we 1st add a windows 2003 r2
> server as
> domain controller and then upgrade it to windows 2008 R2. Is it
> necessary?
> Thanks for your help.
>