AD qa environment

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I am working on interfacing with AD and modifying some AD data like
displayName and telephoneNumber (using vb.net and System.DirectoryServices
class). My issue is that any change I make is done live in AD => very
dangerous because I can damage data for the entire company. I need to have a
qa environment where I can test changes to AD first.

My SAs are no help, they tell me that's the way it is. I just wanted to
check with tech community out there if anybody knows of any AD tool that
allows to test AD changes without risking live data. I would think that MS
had envisioned similar scenarios.

Any help would be really appreciated.
Thank you.
 
Alexis said:
Hi,
I am working on interfacing with AD and modifying some AD data like
displayName and telephoneNumber (using vb.net and System.DirectoryServices
class). My issue is that any change I make is done live in AD => very
dangerous because I can damage data for the entire company. I need to have a
qa environment where I can test changes to AD first.

A single server can be a DC for an entirely self-contained domain-forest.

As Simon says, this can be on VPC or VS, or on a real hardware server.

If you use VPC with a virtual server, your local client can even
address this server on the virtual network adapter.

But you may need a client machine in the same domain so that
is also possible and you only need a PC with enough RAM to
support it all.

BTW said:
My SAs are no help, they tell me that's the way it is. I just wanted to
check with tech community out there if anybody knows of any AD tool that
allows to test AD changes without risking live data. I would think that MS
had envisioned similar scenarios.

You can also install ADAM for general testing, but that is a
standalone (server specific) non-Domain Active Directory
and thus won't have the exact same objects and path names
by default.

ADAM->Active Directory Aplication Mode (free from MS site.)
 
Back
Top