My understanding is that eventually this buisness unit will have its own employees and will be a "sub-company" fromthe parent company. Creating a child domain now allows me to prepare for that.
________________________________ From: Don Ely [mailto:[email protected]] Sent: Sunday, January 25, 2009 10:20 AM To: NT System Admin Issues Subject: Re: Child Domain A child domain isn't going to facilitate a simple split... It will make it more difficult if anything... The child domain is part of the overall forest, how will you separate them? On Sun, Jan 25, 2009 at 10:14 AM, Jeremy Anderson <[email protected]<mailto:[email protected]>> wrote: You may ask that. Eventually the buisness unit is going to spin off into its own "Thing" . The goal is to catch this now before 2 years from now and I am looking back wondering why I didnt split this out. Eventually the need will be there, I am just catching it early. ________________________________ From: MarvinC [mailto:[email protected]<mailto:[email protected]>] Sent: Saturday, January 24, 2009 8:54 PM To: NT System Admin Issues Subject: Re: Child Domain May I ask why child domains instead of using OU's? On Sat, Jan 24, 2009 at 5:20 PM, Jeremy Anderson <[email protected]<mailto:[email protected]>> wrote: I am setting up a child domain for a new buisness unit. We want to keep them seperate in the future, but at the beginning, all the users will still exist in the parent domain. My two questions are 1) what are the implications of having the child domain on the same subnet of the parent domain. The second question is, is there any pros or cons to having the child domain controller server 2008, when every server in the parent domain is still 2003? Any input, advice, is greatly appriciated. Thanks Jeremy ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
