Yep - you're right.  I did overlook the fact that the ultimate goal was to
have the two domains (source, target) with the same domain name.

Never mind.....

:o)

Rick

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 16, 2005 9:15 PM
To: [email protected]
Subject: RE: [ActiveDir] Migration between domains with same NetBios name

Rick, you are overlooking one important factor - client usually do not have
the tolerance for the method you are describing, especially not on an
existing, production domain. They don't want to disrupt the existing
infrastructure, they don't want to change what the users are used to, they
don't want to re-write all the apps they have been using for so long, and in
which they've hard-coded the existing netbios name.
 
 
Sincerely,

Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday?  -anon

________________________________

From: [EMAIL PROTECTED] on behalf of Rick Kingslan
Sent: Thu 6/16/2005 5:07 PM
To: [email protected]
Subject: RE: [ActiveDir] Migration between domains with same NetBios name



Guy,

Though it might seem trivial, it's not really easy in any way.  If you're
not
in mixed-mode, or have child domains - forget it (IIRC).  You've passed the
last bastion of 'easy' in a hard process.

The way to do this, and not have tons of lingering issues is to demote all
other DCs back to members, stand up a NT 4.0 machine as a BDC in your
domain.
Demote the last Win2k DC.  Change the Win NT 4.0 to be the PDC.  Rename the
domain.

Now you can upgrade the NT 4.0 PDC to the first DC in your new Win2k forest
-
but it now has the right NetBios domain name.  DCPromo all of the other DC
'members' in the domain.

It's a royal PITA.  I've had to do this a few times in the early days of
Win2k as some of my rollouts had last minute (or better - last minute +5
minutes) changes from upper Management in naming.

Rick

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Guy Teverovsky
Sent: Thursday, June 16, 2005 6:14 PM
To: [email protected]
Subject: RE: [ActiveDir] Migration between domains with same NetBios name

 

Guido,

 

How about:

1) rename the NetBios name of the target AD

2) perform the migration

3) rename the NetBios name of the AD back to the original

 

Because you are changing only NetBios name and not the DNS name, the fixups
at the AD side are rather minor...

 

Or are we talking about target AD being already production and/or W2K ?

 

Guy

 

________________________________

From: [EMAIL PROTECTED] on behalf of Grillenmeier, Guido
Sent: Thu 6/16/2005 8:43 AM
To: [email protected]
Subject: [ActiveDir] Migration between domains with same NetBios name

Here is a nice one - I've done quite a few migration with all kinds of
scenarios, so I hardly ask questions around this topic. 

 

But when migrating from one NT4 domain to an AD domain which both have the
same NetBios names, various issues and potential conflicts come to mind and
I
wonder if others had to do this in the past, who could share their
experience.

 

Think about an existing NT4 domain called CORP and another existing AD
domain
called CORP (with DNS=copr.company.com). And now you need to migrate all
users and resources from the NT4 CORP to the AD CORP and place AD DCs into
the same sites as the exising NT4 DCs... 

 

I can imagine various challenges, besides not being able to setup a trust
and
thus loosing various options for doing a "normal" migration. At least I have
no need to register the AD domain in WINS; all clients are XP, but I know
for
sure that I'm going to run into various other issues (the worst one being
that the account activation and the resource migration has to happend
instantaneously, since resource access won't be possible accross the
domains). But I'm also thinking of networking issues with and NT4 DC of the
one and an AD DC of the other domain in the same ip-subnet...

 

I wonder how others have tackled this challenge and what issues you ran
into.


 

/Guido

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to