Re: 2003 Server Domain Controllers
- From: RC <RichJChristy@xxxxxxxxx>
- Date: Tue, 19 Feb 2008 11:30:22 -0800 (PST)
the reason I am doing this is we are building a LAB enviornment for
people to use to test before production. We are going to use VMware
Lab Manager and basically build a Library of our production AD inf. I
may have to update this "Lab Library" every 30-90 days. depending on
enviornment changes.
You gave me a good idea regarding imaging them offline or disable
replication.
We could technically bring a virtual dc up in production; one in each
domain. Once those DC's were fully operational I could temporarily
disable replication or bring them offline and then we could p2v them
or simple copy the vmdk files over to the vm lab manager. I would
still have to perform a metadata cleanup and seize the fsmo roles but
this would eliminate (I believe) the usn issue that we may run into.
It would also make it easier for us to update the AD infrastructure in
lab manager by having these vm DC's in production
.
- Follow-Ups:
- Re: 2003 Server Domain Controllers
- From: kj [SBS MVP]
- Re: 2003 Server Domain Controllers
- References:
- 2003 Server Domain Controllers
- From: RC
- Re: 2003 Server Domain Controllers
- From: Paul Bergson [MVP-DS]
- Re: 2003 Server Domain Controllers
- From: RC
- Re: 2003 Server Domain Controllers
- From: Paul Bergson [MVP-DS]
- Re: 2003 Server Domain Controllers
- From: RC
- Re: 2003 Server Domain Controllers
- From: kj [SBS MVP]
- Re: 2003 Server Domain Controllers
- From: RC
- Re: 2003 Server Domain Controllers
- From: kj [SBS MVP]
- 2003 Server Domain Controllers
- Prev by Date: Roaming Profiles
- Next by Date: Re: Roaming Profiles
- Previous by thread: Re: 2003 Server Domain Controllers
- Next by thread: Re: 2003 Server Domain Controllers
- Index(es):
Relevant Pages
|