Active Directory Test Environment

Hi,

I am trying to build a test environment that mimics the production
environment, I have tried a couple of scenarios to do this but neither has
worked too well. Goal is to replicate the entire schema and the AD data in
the test environment. Here is what I have tried:

1. Tried to do a bare metal recovery of the DC holding all 5 FSMO roles in
the authoritative domain using Tivoli on to a test box by following the
outlined procedures from IBM and that did not work at all.

2. Created a child domain under the forest but then the problem is that it
is not a TRULEY isolated test environment.

3. Created an isolated environment and used a product called SimpleSync
which worked great and brought in all the data but it was a trial version and
the real version costs several thousand dollars.

What I was wondering was if ldifde or csvde are able to dump the entire
directory data ALONG with the schema then i could import that in my test
environment and may be even make the procedure into a script so the test is a
day behind the production data. Can someone please recommend a simple or
RIGHT way of achieving this task. The test network is to have NO visibility
to the production network but the production network does have access on the
test network. A have put in a small firewall to separate the two with inbound
rules from certain IPs over certain ports.

Any help or direction would be greatly appreciated.

Thanks
.

Relevant Pages

  • Re: install sp1 in cluster
    ... We do the best we can for testing in our test environment. ... as it may sound, my question is directed at doing this on a production node, ... and let it run for awhile making sure all is good before I install it ... > This is fine and a great idea for your test cluster. ...
    (microsoft.public.windows.server.clustering)
  • Re: Active Directory Test Environment
    ... Move it to your isolated test environment -- and never allow it back ... >> day behind the production data. ... The test network is to have NO ...
    (microsoft.public.win2000.active_directory)
  • Re: Linux Advocates: Only bad thing is the license!
    ... +0000), Joerg Schilling wrote: ... >>in a test environment. ... Software shall not be used in a production ... "bugs", or "beta releases". ...
    (comp.unix.solaris)
  • Re: Windows 2000 System state
    ... > My production network is windows 2000 Active directory, ... On this domain controller, Exchange 2000 is installed. ... > I want to have in my test environment a member server with Exchange ...
    (microsoft.public.win2000.general)
  • Re: SBS 2008 / WS 2008 TS / Hyper-V
    ... And you're asking about a test network, so I'm assuming you also have a production network as well? ... Cris Hanna [SBS - MVP] ... Windows Small Business Server 2008 Unleashed ... Again, assuming sufficient memory and storage, but since it's a test network, you can go with just minimum requirements for memory and storage. ...
    (microsoft.public.windows.server.sbs)