AD Design Recommendation


hi,

i'd communities recommendation being challenged @ our company.  our company designed single domain , have development team has need join & disjoin test servers & applications on daily basis domain.  these servers , applications dsijoined correctly , of time not, of course leaving lots of residuals around in ad, etc.  saying of that, somehow provide development team a seperate domain environment have admin control over, not admin control over our corporate production domain.  may want same thing our sales/demo team, have environment prevent them from messing corp domain/structure.  have 2 dc's in environment now, 1) windows 2003 server std sp2 , 2) windows 2008 server std sp1.  please recommendation on best practice accomplishing our goal , basic steps should take in order implement?

please let me know if need additional information our current environment.

thank you.

hello,

the question have answer first is, must work on production domain or not? if not built lab domain production , there can without interfering production one. here articles how it:

http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/105.aspx

http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/107.aspx

http://www.pbbergs.com/windows/articles/testdomain.html

if isn't opion create either child domain them or separate domain tree in same forest. way trust production domain exist, can share/access @ least data but work still in there own domain.


best regards meinolf weber disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.


Windows Server  >  Directory Services



Comments

Popular posts from this blog

Schannel Issue

Indexing Server

oclist /xml or /?