Migrating with Exchange 5.5 in own domain

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We are prepapring to perform our migration. Our problem though lies with
Exchange. We have Exchange 5.5 in its own domain and on a system that is a
PDC. What is the best path for upgrading our NT network, upgrading the
network Exchange lives on and flattening the domains?
.

Relevant Pages

  • Re: Upgrade to W2K3 AD with E2K3 already installed
    ... you would don't has problem because the mangled problem appear migrating AD ... > planning on upgrading my DCs to W2K3 in th next couple of weeks. ... Global Catalog to the Windows Server 2003. ... > Considering the Exchange issue, you should pay attention to following ...
    (microsoft.public.exchange2000.active.directory.integration)
  • RE: Upgrading Windows 2000 Domain to Windows 2003
    ... I understand you have run domainprep and forestprep on AD when upgrading ... Based on my experience, when upgrading Exchange, the commands you have run ... folder of the Windows Server 2003 media and this prepares for a Windows ...
    (microsoft.public.windows.server.migration)
  • RE: Owned vs Hosted Exchange
    ... hosted solution is the business criticaliry of the hosted data. ... I don't think it will be easy to convince them of upgrading the ... > the end of this year and Exchange 5.5 support will only be availible ...
    (microsoft.public.exchange.design)
  • Re: Exch 2000 to 2003 Upgrade??
    ... If you feel more comfortable running the inetorgpersonfix script prior to ... upgrades first (Exchange 2003 forestprep). ... > Windows Server 2003 adprep /forestprep Command" ... >>> We are thinking about upgrading Active Directory first, ...
    (microsoft.public.exchange.admin)
  • RE: 2000 to 2003 with Exchange
    ... Thanks for your feedback. ... You can refer to the Exchange Server 2003 Message Security Guide for OMA ... > schema then the inetorg object will not get mangled. ... > prevent it getting managled prior to upgrading the forest ...
    (microsoft.public.windows.server.migration)