DC in test enviroment

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

I am creating a test enviroment to prepare for a move to 2003 Server. We are
currently in a Windows 2000 Server/AD enviroment.
My thought was to add a server to the active domain and promote to a DC.
After AD replication - remove the server and place in my test enviroment so
that I have a DC that mimics my current enviroment.
I know I will need to manually remove the server from my active enviroment
(metadata cleanup, etc.)
Will I need to assign FSMO roles to the DC now that it is in the test
enviroment?
What potential issues would I have?
Any thoughts and suggestions are appreciated.
Thanks

 

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

You would need to seize the FSMO roles using ntdsutil for AD to run properly
and, I imagine, for the WS2003 upgrade to happen.

Just, whatever you do, make sure that box is wiped absolutely clean before
it goes anywhere near your production network again!

Oli


"rdw24" <rdw24@discussions.microsoft.com> wrote in message
news:F6F27332-F2E3-4EC0-83B4-E124ECBB383B@microsoft.com...
>I am creating a test enviroment to prepare for a move to 2003 Server. We
>are
> currently in a Windows 2000 Server/AD enviroment.
> My thought was to add a server to the active domain and promote to a DC.
> After AD replication - remove the server and place in my test enviroment
> so
> that I have a DC that mimics my current enviroment.
> I know I will need to manually remove the server from my active enviroment
> (metadata cleanup, etc.)
> Will I need to assign FSMO roles to the DC now that it is in the test
> enviroment?
> What potential issues would I have?
> Any thoughts and suggestions are appreciated.
> Thanks
>

 

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

Thanks Oli !!
Ron


"Oli Restorick" wrote:

> You would need to seize the FSMO roles using ntdsutil for AD to run properly
> and, I imagine, for the WS2003 upgrade to happen.
>
> Just, whatever you do, make sure that box is wiped absolutely clean before
> it goes anywhere near your production network again!
>
> Oli
>
>
> "rdw24" <rdw24@discussions.microsoft.com> wrote in message
> news:F6F27332-F2E3-4EC0-83B4-E124ECBB383B@microsoft.com...
> >I am creating a test enviroment to prepare for a move to 2003 Server. We
> >are
> > currently in a Windows 2000 Server/AD enviroment.
> > My thought was to add a server to the active domain and promote to a DC.
> > After AD replication - remove the server and place in my test enviroment
> > so
> > that I have a DC that mimics my current enviroment.
> > I know I will need to manually remove the server from my active enviroment
> > (metadata cleanup, etc.)
> > Will I need to assign FSMO roles to the DC now that it is in the test
> > enviroment?
> > What potential issues would I have?
> > Any thoughts and suggestions are appreciated.
> > Thanks
> >
>
>
>