Diane,
I've been watching this thread with some interest.
:-)
Be
sure that you're current direction, for all intents, should be
successful. There is such a thing as Native and Mixed-Mode when
dealing with Exchange as well - but this has to do with Native and
Mixed-mode for the Exchange Organization. Do _NOT_ get the Win2k
Native - Mixed-mode thing confused with the Exchange 2k Native -
Mixed-mode. They are not the same.
Synopsis:
Windows 2000 Native vs. Mixed
In
Native mode:
1. No LMRepl communication with downlevel
BDCs.
2. Universal groups are available, group nesting (i.e. Global
groups into global groups, etc) is available
3. Members servers and workstations continue to work as they
did before.
In
Exchange, the distinction between Native and Mixed is present because Xech
5.5 does not have the ability to separate routing groups and administrative
groups. So, while in mixed mode an Exch 5.5 site functions as
both. Because E2K does not have this limit, and to get the full
flexibility out of the model, Native mode is used once there are no Exch 5.5
servers and full routing and administrative groups can be
leveraged.
Exchange 2000 Native vs. Mixed
In
Native Mode:
1. No Exchange 5.x servers can be supported. It's a E2K
exclusive club.
Hope this helps clear up your confusion. Your migration plan
(with the level of detail presented) looks fine.
Good luck!
Rick Kingslan - Microsoft Certified Trainer
MCSE+I
on Windows NT 4.0
MCSE on Windows 2000
MVP [Windows
NT/2000 Server]
"Any sufficiently advanced technology
is
indistinguishable from magic."
--- Arthur C.
Clarke
I know this isn't the exchange list but you got
me going. The comment "5.5 has to have a mixed somewhere in
the forest" has me concerned. Here's the scenario in a nut
shell..
Single master NT 4.0 domain model.
Multiple resource domains @ 4.0 with a single account domain. The
upgrade path so far was bring up an empty forest root (non
routable). This is running in native mode. We then began the
upgrade of our accounts domain. It's currently running in Mixed
mode. Plan is convert the domain to native once we complete the DC
replacements. After going native, we'll begin our migration of the
resources in the resource domains to AD. At the same time we will
begin the rollout of exchange 2K and migrate Ex5.5 resources to E2K.
Exchange will run in mixed mode until the migration is complete then
exchange will be converted to native mode. Once the resources in the
resource domains are migrated, the resource domains will be
retired.
Your comment makes me concerned since we will
have no "mixed mode Win2K domains" they will be all native. We'll
still have down level NT 4.0 domains with NTLM trusts but no Win2K mixed
mode domains.
Our Migration strategy was given a thumbs up by a
"well known" consulting organization hence my
confusion...
Diane
ok, I have totally screwed this one up...
Yes. E2K has to be in Native, 5.5 has to have a mixed somewhere
in the forest..
Ours is still root mixed, all others native..
lol
At least I got that part right.. That'll teach me to drink Corona
and dispense advise....
:-)
I'm assuming he means "one domain in native
mode for E2K". Our situation is that the root is native (empty
root) and the production domain is in mixed mode. Based on the
docs I read, the domain that e2K is to be installed into must be in
native mode.
If we don't have to be in native mode in our
production domain, that's going to save a heela lot of
work
Diane
Do you mean - Only ONE
domain needs to be in mixed mode for E5.5?
----- Original Message -----
Sent: Tuesday, January 22, 2002
7:37 PM
Subject: RE: [ActiveDir]
Rollback from the big bang
FYI,
Only ONE domain needs to be in mixed mode for E2K.
We have our root in
mixed all child
(production) domains in native..
-----Original Message-----
From: Ayers, Diane [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 22, 2002 5:33 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Rollback from the big
bang
All:
We are in the midst of our AD deployment and are
looking toward the day
we switch from mixed
mode to native mode. We need to do this to move
forward with our Exchange 2K rollout. We're a
single forest with an
empty forest root and
a main domain for all of our other resources.
Being an enterprise we have a lot of "unknown
applications" out there
that we no way of
testing against native mode let alone tracking down.
We have the "big ones" but the rest....
Anyway, I know the say the
switch from mixed
to native is a one way track. Baring that I was
thinking about some sort of CYA in case things go
south in a real bad
way.
Does anyone have a creative method for rolling back
from the switch to
native mode. I was
thinking along the lines of doing a restore of a
pre-native directory backup or ?? I know we could
probably bring one of
our NT 4.0 BDCs back
online, promote and rebuild the domain but that
would entail redoing all of the Win2K DCs.
All MS docs say no way.
Ideas or am I wasting thought cycles?
Diane
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/
