Are you doing this for security auditing reasons? We recently went through this and ended up creating a separate A/V management server as well as separate Exchange environment. Wasn't too bad since they are a small user base and we used all VMs when creating the new servers. It was more of a PITA when it came time to move workstations to the new domain (profiles, mailboxes, etc).
Don Guyer Systems Engineer - Information Services Prudential, Fox & Roach/Trident Group 431 W. Lancaster Avenue Devon, PA 19333 Direct: (610) 993-3299 Fax: (610) 650-5306 [email protected] From: [email protected] [mailto:[email protected]] Sent: Thursday, February 18, 2010 10:48 AM To: NT System Admin Issues Subject: network topology I work for a small company that is a collection of small companies. Currently one domain with offices in several locations in 2 states, Ok and Az. Owners want to create separate domains, not child domains. Each division would have their own DC's and independent AD structure. I am hoping someone can just give "big picture" yes/no's to where we are trying to go. More typically it would be setup like this: [email protected](parent co); [email protected]; [email protected] and [email protected]. What we want looks more like this: [email protected]; [email protected], etc. 1. Can we do this without being stupid on one physical network(all offices currently connected with IPSEC tunnels, use VLAN switching to separate domains) 2. Can we setup co1 domain as "management" domain and give exchange access to members of other domains; central AV management, etc...? LOTS of details not provided, IK, just getting started here. We are currently running w2k3 servers and E2k3. New domains will be created on W2k8R2 servers and E2K7. Thanks for any help/discussion. Jeff ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
