The ability to rename is no substitute for figuring things out right in the
first place. But it is good that MS is working on making the functionality
better and better for those poor souls who do indeed have to go through
it... Say they are going into a company whose previous admins weren't quite
as enlightened as the membership of this list and have no other options.

   joe

 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, April 16, 2004 7:33 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] AD screw up

OK, now I'm confused. I've always known about the problems with renaming a
Domain that has Exchange in it, because I've personally verified it in
tests.
I've always preached this to people who got hooked on the "Domain Rename"
claim. I've always told them to pretend that they never heard or read that
claim.
 
So..... imagine my shock when I was told last week that "it works" by people
whom I trust to know such things. My feeble attempt to disagree with that
claim was muted by the question "have you tried it recently?". Of course,
since I hadn't tried it recently, I sheepishly grinned and said "Wow! I must
be slacking". I took their words for it.
 
Short story long, I've since tried it "recently" after this thread shows up,
and it still breaks Exchange. I admit I was hoping to surprise everyone on
this list by being the first to respond "Hey, dude, have you tried it
recently?". Well, burst my bubbles. It still does NOT work!!! After reading
the list of breakable stuff, I am still more confused as to why MS has not
deemed it necessary to stop talking about this "Domain Rename" thingy. Most
people I know that would want to rename their domain are people that have at
least one "breakable" application already in production in their Enterprise.
Some of them will not read the fine prints of this claim, no matter how much
you tell them about it. All they hear is "MS says it's now possible to
rename a domain in Windows 2003! Wow! Cool! Hang 10!!" and shortly
thereafter they'd go "Oooopsie! where's that latest copy of my resume?"
 
I seriously hope that we can just dump this claim and let's go back to
accepting the fact that if you screw up your domain name, well then just
treat it like your own name - parents don't have a "renaming" ceremony after
the original naming ceremony, no matter how much the kid hates the name
afterwards :)
 
 
Sincerely,

D�j� Ak�m�l�f�, MCSE MCSA MCP+I
Microsoft MVP - Active Directory
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday?  -anon

________________________________

From: [EMAIL PROTECTED] on behalf of Lou Vega
Sent: Fri 4/16/2004 11:26 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] AD screw up



True - you can rename a Windows 2003 domain (again not really advised),
here's a link to the 80 page "step-by-step" :-)
(http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90
a
2a2e2/Domain-Rename-Procedure.doc). Also as noted in Bruce's post, if you
have Exchange, the domain rename is not supported in any forest that has any
version of Exchange.

 

 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bruce Clingaman
Sent: Friday, April 16, 2004 2:02 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] AD screw up

 

No. The domain name is not tied to the OU structure. I have read that you
can change the domain name (not advised) in 2003, unless you are running
Exchange, then you would be left with rebuilding the domain from scratch.

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Drew Gainor
Sent: Friday, April 16, 2004 12:54 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] AD screw up

Ok, how about this. I create a new child OU in my existing domain called
corp. I then move all users and objects from the root domain to the corp
child. Then I rename the root domain. Does that sound like it will work?

        -----Original Message-----
        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A.
        Sent: Friday, April 16, 2004 10:03 AM
        To: [EMAIL PROTECTED]
        Subject: RE: [ActiveDir] AD screw up

        Create the new OU, then right click on the child OU and click Move

         

        -----Original Message-----
        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Drew Gainor
        Sent: Friday, April 16, 2004 12:41 PM
        To: [EMAIL PROTECTED]
        Subject: RE: [ActiveDir] AD screw up

         

        I don't know where I get these stupid questions from. ok It looks
like OU will work ok. I found info at Microsoft
http://www.microsoft.com/windows2000/techinfo/reskit/deploymentscenarios/sce
n
arios/ou_design_implement_ou_structure.asp

         

        now my question is - Since I already created an AD containing an OU
of what I would like to be a child how can I create the parent to insert the
child into. Or is that even possible?

                -----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

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/

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/

Reply via email to