We currently have a WAN that spans multiple cities and includes a site at out hosting facility that houses our internet application servers. We are considering creating a separate domain, using NTFS security, for the developers to use for their production needs - which would include 2 thousand new user accounts - which we don't want polluting our existing infrastructure.
Is this what we should do? In other words, if we are ABC.com, should we create a new domain XYZ.com or create the child DEV.ABC.com? Now to add a further wrinkle. One application needs "ultimate security". Perhaps it even needs its own domain as the top execs have said they want only 1 or 2 people to have any administrative access to the servers running the specialized application. Any ideas? Would like to hear feedback and perhaps some implementation strategies. Thanks, David List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
