Re: Duplicate Production AD to Test
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 16 May 2007 16:35:59 -0500
"Chelis Guifoyle" <ChelisGuifoyle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:289D0997-36C1-4808-9C25-DBC72A03A66C@xxxxxxxxxxxxxxxx
Hmm sounds easy enough.. what about child domains, IP addressing, sites,
etc.. all the little things that add up. How much of this do we need to
duplicate?
You have to make the server work on the new net where you move it so
I am presuming you know to change the IP address.
Child domains are done the same way IF you must but you didn't mention
them. They add complication but nothing really hard.
You didn't mention WHY you are doing this.
It is usually for the wrong reasons but you MAY have good ones.
When refreshing.. do you mean adding a new DC to the production and
pulling it, or reintroducing the formerly removed one?
I mean adding a new DC (but was assuming you would use the same
server each time.)
First REMOVE the AD from the "test" box, then put it back on the
net and start the process fresh again.
You do this to keep from "polluting" the production with whatever
you have been doing to the offline version.
If you really just want backups ready to go you should just be adding
DCs to production.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- Re: Duplicate Production AD to Test
- From: Herb Martin
- Re: Duplicate Production AD to Test
- Prev by Date: Re: delegate add and remove programs DC
- Next by Date: Re: Check the user account expire date
- Previous by thread: Re: Duplicate Production AD to Test
- Next by thread: Re: Duplicate Production AD to Test
- Index(es):