Exchange 55 to 2003 Upgrade Questions

From: Eric (Eric_at_discussions.microsoft.com)
Date: 07/23/04


Date: Fri, 23 Jul 2004 12:53:17 -0700

I have a Windows 2000 AD & Exchange 5.5 infrastructure
today. The Windows 2000 ADC CA is configured as well.

I plan to replace the W2K domain controllers with new
W2K3 machines as well as replace the Exchange 55 boxes
with Exchange 2K3 boxes. These changes will all take
place over a 2-day period when no users will be working.

Questions-

1. I would like the new domain controllers to have the
same IP addresses as the old machines because they run
DHCP, WINS, and DNS services. Can I change the IP
addresses of the existing machines, add the new machines
to the network with the IP address of the previous
machines, then run DCPROMO and migrate the DNS & DHCP?

2. Since I plan to decommision the Exchange 55 servers
at the end of the procedure & no mail needs to flow
during this time do I need to hassle with the ADC or can
I simply remove it? I plan to add the Exchange 2k3
servers to the Exchange 55 Organization and use the move
mailbox method to move mailboxes.



Relevant Pages

  • RE: Outlook 2007 to Exchange 2003, just stopped connecting
    ... Microsoft MVP - Tablet PC ... I set up just one account - the Exchange account and it ... connected to the Exchange server. ... just different machines and I am using Exchange to keep all ...
    (microsoft.public.outlook.installation)
  • RE: Office 2007 send to email
    ... Exchange Manager as that would be more work than adding attachments manually. ... It is unfortunate that install via GPO is no ... I had this problem with two seperate machines. ... I've tried uninstalling the exchange components, but that has proven to not ...
    (microsoft.public.office.misc)
  • RE: Outlook 2007 to Exchange 2003, just stopped connecting
    ... I set up just one account - the Exchange account and it ... connected to the Exchange server. ... Just 7 clients running Outlook 2007. ... just different machines and I am using Exchange to keep all ...
    (microsoft.public.outlook.installation)
  • CDOEXM Interop problem on non-Exchange machines
    ... but perhaps better resources (machines of different ... Using Visual Studio 2003, user cannot reference Exchange ... A reference to 'Microsoft CDO for Exchange Management Library' could not be ... (ADODB 2.8); and uses the CDO COM defined interface for some of its work. ...
    (microsoft.public.dotnet.languages.csharp)
  • CDOEXM Interop problem on non-Exchange machines
    ... but perhaps better resources (machines of different ... Using Visual Studio 2003, user cannot reference Exchange ... A reference to 'Microsoft CDO for Exchange Management Library' could not be ... (ADODB 2.8); and uses the CDO COM defined interface for some of its work. ...
    (microsoft.public.dotnet.languages.vb)

Loading