Re: Exchange 2003 Native Mode Benefits

From: Steve Antonio [MSFT] (steveant_at_online.microsoft.com)
Date: 02/12/04


Date: Thu, 12 Feb 2004 11:32:34 -0500

Chris,

Answers are inline:

-- 
Cheers,
Steve Antonio
Microsoft Exchange Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.
"Chris" <anonymous@discussions.microsoft.com> wrote in message
news:25C0ADD5-3FA9-4CEC-8CA8-BB8858D42696@microsoft.com...
> Thanks for your response Steve.  Let me clarify my question.  I am going
to install Exchange 2003 on a Windows 2003 cluster.  Logistically, I'll have
to delay my implementation of Exchange 2003 a few weeks if I need to switch
to a Windows 2003 native mode domain and/or forest prior to implementation.
I am upgrading my FSMO servers to Windows 2003 this weekend and my AD will
be in Windows 2000 native mode.
>
> Here are my questions:
>
> 1.  Assuming that I have a mixture of Windows 2003 and Windows 2000 SP3
domain controller, is there any reason that I should wait until all domain
controllers are upgraded to Windows 2003 and the domain is converted to
Windows 2003 native mode before I begin my Exchange 2003 implementation.
Obviously, there are a couple optimizations that I'll receive once I can
convert to Windows 2003 native mode.
At this point you could move to Windows 2000 Native mode, but can't go to
2003 Native mode until all DC's are at 2003. However, this should not have
any effect on when you choose to introduce Exchagne 2003 (you just won't get
some of the "extras").
322692 HOW TO: Raise Domain and Forest Functional Levels in Windows Server
2003
http://support.microsoft.com/?id=322692
> 2.  If I start my Exchange 2003 implementation (i.e. run ForestPrep,
DomainPrep, Upgrade the ADC/SRS, Run Setup on a server) before I complete
upgrading the remaining servers to Windows 2003 and convert to Windows 2003
native mode, are there any complications that may arise due to being in
Windows 2000 native mode?
None
>
> 3.  Assuming that I complete my Exchange 2003  implementation (using
Windows 2003 servers) while my Active Directory is in Windows 2000 Native
Mode (running Windows 2003 on the FSMO servers), are there any features that
will not work correctly or complications after promoting my domain to
Windows 2003 native mode (once the rest of my domain controllers have been
upgrade)?
No features that will not work correctly, but again, you wouldn't have the
"extras" that are available in Windows 2003 native mode.
You can, at this point, continue on with your migration plans and not push
to go Native until you are ready to do so.
>
> Thanks for you help,
> Chris
>
>      ----- Steve Antonio [MSFT] wrote: -----
>
>      This article provides some details: 822178 Overview of Dependencies
and
>      Requirements for Exchange Server 2003
>      http://support.microsoft.com/?id=822178
>
>      In addition, the Exchange 2003 Technical Library will have some info
as well
>      (www.microsoft.com/exchange/library)
>
>      Some of this includes query-based distribution groups, single-value
>      replication, full support for InetOrgPerson.
>
>      Hope this helps.
>
>      -- 
>      Cheers,
>
>      Steve Antonio
>      Microsoft Exchange Support
>
>      This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>      Note: Please do not reply to this e-mail address. It is used for
newsgroup
>      purposes only.
>
>
>      "Chris" <anonymous@discussions.microsoft.com> wrote in message
>      news:D49C40E1-AD05-4EA1-BDE2-C71ED332F021@microsoft.com...
>      > Background:  I am planning a migration from Exchange 2000/Windows
2000 to
>      Exchange 2003/Windows 2003.  I currently have a Windows 2000 Native
Mode
>      Domain and a Mixed-Mode Exchange 2000 org.  I have multiple Exchange
5.5
>      sites in my org that are running on NT 4.0 domains that are trusted
by my
>      Native Mode Windows 2000 domain.  I want to upgrade my Exchange 2000
servers
>      to Exchange 2003.
>      >> Question:  I am planning my upgrade right now.  Is there any
benefit to
>      converting my native mode Windows 2000 domain to Windows 2003 native
mode
>      prior to installing Exchange 2003 or can this be done after upgrading
to
>      Exchange 2003?  I'm aware of the AD benefits of promoting my domain
and
>      forest to Windows 2003 native mode.  Is there anything
Exchange-related that
>      I would be giving up by staying in Windows 2000 native mode for
awhile?
>
>
>


Relevant Pages

  • Exchange 2003 to Exchange 2007 Migration options
    ... In our Active Directory which is implemented in Windows 2003 we have setup ... controller; ... Our exchange 2003 environment consists of the following: ... 3 OWA servers in NLB ...
    (microsoft.public.exchange.setup)
  • Re: Native and Mixed Mode Question sorry
    ... So in the setup instructions is it talking about Exchange native mode ... I have no 5.5 servers and no NT 4.0 servers. ... Windows 2000 servers. ... Windows native mode, then native Exchange mode between the current two ...
    (microsoft.public.exchange.admin)
  • Re: DST 2007 Question on Exchange 2003 SP2 - time off 1 hour
    ... Update Windows Servers and Windows client operating systems with the ... Exchange Servers: Apply the Feb. 2007 Cumulative Time Zone Update to ... All the appointments were created months ago using DST 2006 rules. ...
    (microsoft.public.exchange.admin)
  • Re: Keeping NT4 servers in 2003 Native Domain
    ... I thought I was pretty clear in describing the NT4 servers as Member servers ... I suspect you are using Windows 2000 mix mode other than Windows 2000 ... native mode since you still keep Windows NT 4.0 BDC. ...
    (microsoft.public.windows.server.migration)
  • Re: Keeping NT4 servers in 2003 Native Domain
    ... The switch to native mode only affects the replication between the NT 4.0 ... BDCs and the AD DCs. ... I thought I was pretty clear in describing the NT4 servers as Member ... I suspect you are using Windows 2000 mix mode other than Windows 2000 ...
    (microsoft.public.windows.server.migration)