RE: [ActiveDir] AD screw up

[Salandra, Justin A.]

Title: Message

There is no need for the .ADDomain on each OU since everyone is part of the ADDomain and logins in to that domain only.  The end user would have no idea what OU they are in     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Gainor Sent: Friday, April 16, 2004 12:32 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD screw up   With an OU structure could I do this?   ADDomain     corp.ADDomain         users     branch1.addomain         users     branch2.addomain         users -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Friday, April 16, 2004 9:18 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD screw up You could do that, but are you sure you can’t accomplish what you want to do with just one domain and a detailed OU strcture?   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Gainor Sent: Friday, April 16, 2004 12:06 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] AD screw up   Not knowing what I was doing I set up an AD at my company corporate office. I then converted everyone over to it along with my Exchange server.   Now I also have a couple of branch offices and want to create children.   The mistake I made was that I did not set up an Empty Root Domain first. I setup the corporate domain as the first server.   This is what I would like to do. Tell me if I am wrong or if you have any other suggestions.     Root - ADRoot child - corp.ADRoot child - branch1.ADRoot child - branch2.ADRoot   I do not want the domains to be internet FQDN.   Drew