exchange 2003 standalone

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jason (avtechs_at_aspenview.org)
Date: 03/03/05


Date: Thu, 3 Mar 2005 09:28:52 -0700

Hi, we are in the process of migrating from windows 2000 /exchange 5.5 to
windows 2000/exchange 2003.

Our current exchange 5.5 server is broken and couldnt be migrated by
installing a exchange 2003 in the same site.

My question is would it be possible to create a 2003 exchange server in a
new domain and just recreate the users? (resource domain?)

thx jason



Relevant Pages

  • Re: Complex AD migration
    ... Are you migrating to windows 2003? ... Are you migrating to Exchange 2003? ... server domain to transfer all FSMO from my current server to that, ...
    (microsoft.public.win2000.active_directory)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... The Ldp GUI tool is included when you install Windows Server 2003 Support ... Microsoft CSS Online Newsgroup Support ... DST update for Exchange 2003 and Outlook 2003 ...
    (microsoft.public.exchange.admin)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... Majority of my users connect to Terminal Server and ... I also have users running on stand-alone PC's (Windows XP) ... run the Outlook Time Zone Data Update Tool or the Exchange calendar tool? ... 926666 Update for daylight saving time changes in 2007 for Exchange 2003 ...
    (microsoft.public.exchange.admin)
  • RE: Migrating from Win2k DCs to Win2k3 DCs; ADPrep question
    ... When you try to upgrade Windows 2000 DC to Windows 2003 while ... Exchange 2000 is installed. ... The reason is that Windows Server 2003 adprep ... 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled ...
    (microsoft.public.windows.server.migration)
  • Re: upgrade from Win2k to win 2003 + exchange
    ... 842427 How to upgrade Exchange 2000 Server to Exchange Server 2003 in an ... 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled ... > This is almost what I am looking for in order to upgrade our exchange 2000 ...
    (microsoft.public.exchange.setup)