[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 253
  • Last Modified:

Migrate from Exchange 5.5 to 2003

I have a Windows 2000 DC and a Windows NT 4 Exchange 5.5 server.  We have a 2003 Standard server built with Exchange 2003 Standard and want to migrate to the new server for exchange.  We would like to keep the 2000 server our primary DC.  I would like to keep exchange 5.5 and 2003 running at the same time to easily move users from one server to the next.  Also, are there going to be any difficulties adding the 2003 server to our DC group?  I have not yet installed Exchange 2003 just in case there are any special installation instructions.  Any help would be appreciated.
0
tonykman
Asked:
tonykman
  • 13
  • 12
  • 2
  • +1
1 Solution
 
amaheshwariCommented:
Hi,

First run ADC setup from Exchange 2003 CD so that your ADC Connector from exchange 5.5 to exchange 2003 will come into picture .Then install exchange 2003 in same site of exchnage 5.5 .

You can use this link for your reference.
http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/84fd1f06-cf90-43fe-b836-f21b2fa88d4d.mspx?mfr=true

0
 
tonykmanAuthor Commented:
Do we need to add the 2003 server to our AD group first?
0
 
rakeshmiglaniCommented:
the new windows 2003 server should be a part of the AD
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
amaheshwariCommented:
yes sure.
0
 
tonykmanAuthor Commented:
What do we need to do to get our current AD ready for the 2003 server?
0
 
rakeshmiglaniCommented:
TechNet Support WebCast: Strategies for migrating from Microsoft Exchange Server 5.5 to Exchange Server 2003
http://support.microsoft.com/kb/884081/en-us

A comparison of the migration methods for migrating from Exchange Server 5.5 to Exchange Server 2003 or to Exchange 2000 Server
http://support.microsoft.com/kb/327928/en-us

How to switch outgoing Internet e-mail connectors when you migrate from Exchange Server 5.5 to Exchange 2000 Server or to Exchange Server 2003
http://support.microsoft.com/kb/883407/en-us

How to roll back a failed migration from Exchange Server 5.5 to Exchange 2000 Server or to Exchange Server 2003
http://support.microsoft.com/kb/839356/en-us

Common Mistakes When Upgrading Exchange 5.5/2000 To a Exchange 2003
http://support.microsoft.com/kb/555262/en-us

How to remove the last Exchange Server 5.5 computer from an Exchange Server 2003 administrative group
http://support.microsoft.com/kb/822450/en-us
0
 
rakeshmiglaniCommented:
you can add this new 2003 server as a member server to the existing 2000 AD domain or set this up as a DC in the 2000 domain
0
 
vangipeCommented:
Just to clear things up - are you planning to make the 2003 server a DC as well?

To install Exchange 2003 you'll have to do a domainprep and forestprep first, but if you use the Exchange Deployment Tools (which is autostarted when you insert the cd) then you'll be guided through those steps. Keeping the 2000 server as a DC is not a problem at all, although you won't be able to use some functionality as long as your Active Directory is still 2000 instead of 2003. But those are the more 'advanced' topics which you might not need at all.

If you wish to migrate from Exchange 5.5 to 2003 then make sure you pick the right option in the Deployment Tools (coexistence with Exchange 5.5).
Then use ADMT to create Active Directory accounts (download ADMT from http://www.microsoft.com/downloads/details.aspx?FamilyId=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en) and make sure you use version 3! There's a whitepaper on http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookchp9.mspx although it's for version 2.0.
Finally use ADC to sync Exchange 5.5 and AD (ADC is included on the Exchange 2003 cd, look here for an overview: http://www.msexchange.org/tutorials/Overview-Active-Directory-Connector.html).

A migration from Exchange 5.5 to 2003 is certainly not easy if you do it the first time, but there are loads of step-by-step manuals on the net (especially on www.msexchange.org). Remember that every environment is different so think before you click!

Good luck,
Peter
0
 
tonykmanAuthor Commented:
When I run the DSScopeScan I get this log:

#*** Exdeploy began: 05/02/2006 08:55:02 ***#
+ Exchange 5.5 Server: 10.10.10.50
+ Global Catalog Server: 10.10.10.55
+ Tools run: DSScopeScan, and OrgNameCheck.

-2147467259 Error in Initialize: .
#*** Exdeploy finished: 05/02/2006 08:55:06 ***#

Is this acceptable or do I need to fix some things first?
0
 
rakeshmiglaniCommented:
To run the DSScopeScan group of tools, your account must have Exchange Server 5.5 administrator permissions and the rights to view objects in the Exchange directory.

http://support.microsoft.com/kb/812593/en-us
0
 
tonykmanAuthor Commented:
The user already has domain admin rights, what user has exchange permissions?
0
 
rakeshmiglaniCommented:
the account that you are using to run these tools should have "service admin rights" on the Exchange 5.5 ORG level, SITE level, Configuration level and servers level. you can check this by opening the exchange administrator on the Exchange 5.5 server.
0
 
tonykmanAuthor Commented:
I believe the domain administrator has service rights on these levels, where in the exchange admin screen can i check?  I am getting this log now:

#*** Exdeploy began: 05/02/2006 08:55:02 ***#
+ Exchange 5.5 Server: 10.10.10.50
+ Global Catalog Server: 10.10.10.55
+ Tools run: DSScopeScan, and OrgNameCheck.

-2147467259 Error in Initialize: .
#*** Exdeploy finished: 05/02/2006 08:55:06 ***#

#*** Exdeploy began: 05/02/2006 09:24:52 ***#
+ Exchange 5.5 Server: 10.10.10.50
+ Global Catalog Server: 10.10.10.55
+ Tools run: DSScopeScan, and OrgNameCheck.

-2147467259 Error in Initialize: .
#*** Exdeploy finished: 05/02/2006 09:24:56 ***#

Also, should I be running this tool from the exchange 5.5 server or from the server that I will be putting exchange 2003 on?

0
 
rakeshmiglaniCommented:
run the tool from the new exchange 2003 server

click on the Exchange ORG and then file menu and then properties and check the permissions tab. the account that you are using should have the service admin account rights.
check the same for the site, configuration and server levels also
0
 
tonykmanAuthor Commented:
Every level had service level admin rights.  This is the log that I end up with:

[10:05:43]  ********** Beginning Exchange Deployment Tools **********
[10:05:43] Starting Exchange 6944 Deployment Tools on Windows 5.2.3790 at 10:05:43 05/02/2006
[10:05:43] Entering HrDirPreReq_Initialize
[10:05:43] Init called with Domain Controller 10.10.10.55 and Exchange 5.5 server 10.10.10.50.  Setup's language ID is 0.  ActiveX Path is (null)
[10:05:43] Entering HrRegisterAXDLL
[10:05:43] Leaving HrRegisterAXDLL
[10:05:43] Leaving HrDirPreReq_Initialize
[10:05:43] Entering HrRegisterAXDLL
[10:05:43] Leaving HrRegisterAXDLL
[10:05:45] Entering HrDirPreReq_ConfigInit
[10:05:47] Leaving HrDirPreReq_ConfigInit
[10:05:47] HrDirPreReq_CmdLine (f:\titanium\dsa\src\deploy\dsintegchk\cmdline.cpp:2159).  Error code 0X80004005(16389).
[10:05:47] Entering HrDirPreReq_Terminate
[10:05:47] Leaving HrDirPreReq_Terminate


next log:

#*** Exdeploy began: 05/02/2006 10:05:43 ***#
+ Exchange 5.5 Server: 10.10.10.50
+ Global Catalog Server: 10.10.10.55
+ Tools run: DSScopeScan, and OrgNameCheck.

-2147467259 Error in Initialize: .
#*** Exdeploy finished: 05/02/2006 10:05:47 ***#

I'm really lost now!
0
 
tonykmanAuthor Commented:
I put in the server names instead of the IP address and the tools started.
0
 
rakeshmiglaniCommented:
good..keep me posted of the developments.. i am here for another 2 hours
0
 
tonykmanAuthor Commented:
Here is my current log:

#*** Exdeploy began: 05/02/2006 10:24:14 ***#
+ Exchange 5.5 Server: mercury
+ Global Catalog Server: mars
+ Tools run: DSScopeScan, and OrgNameCheck.

- Error: Could not connect to the Exchange 5.5 server 'mercury'. Tools that require an Exchange 5.5 server will not run.

+ Planning Your Deployment (DSScopeScan)

      - Existing Org Report (OrgReport)
            OrgReport checks Active Directory for an existing organization.

            Test completed successfully.  No organization was found in Active Directory.
      - Global Catalog Server Version Check (GCVerCheck)
            GCVerCheck verifies the availability of a global catalog server or domain controller running SP3 or later in the current or adjacent site.  Details are logged in gcvercheck.log.

            GCVerCheck completed successfully.  All domain controllers and global catalog servers in the current and adjacent Windows sites are running Windows 2000 SP3 or later.

#*** Exdeploy finished: 05/02/2006 10:24:14 ***#


Everything seems to be okay except for the part about "Could not connect to the Exchange..."  Any ideas?
0
 
rakeshmiglaniCommented:
try running the ORG name check tool.. the exchange 5.5 org should not have any special characters
0
 
tonykmanAuthor Commented:
Our org name does not have any special characters.  I have the following log:

----------------------------------------------------------------------------
#*** Exdeploy began: 05/09/2006 08:56:59 ***#
+ Exchange 5.5 Server: mercury
+ Global Catalog Server: mars
+ Tools run: DSScopeScan, and OrgNameCheck.

- Error: Could not connect to the Exchange 5.5 server 'mercury'. Tools that require an Exchange 5.5 server will not run.

+ Planning Your Deployment (DSScopeScan)

      - Existing Org Report (OrgReport)
            OrgReport checks Active Directory for an existing organization.

            Test completed successfully.  No organization was found in Active Directory.
      - Global Catalog Server Version Check (GCVerCheck)
            GCVerCheck verifies the availability of a global catalog server or domain controller running SP3 or later in the current or adjacent site.  Details are logged in gcvercheck.log.

            GCVerCheck completed successfully.  All domain controllers and global catalog servers in the current and adjacent Windows sites are running Windows 2000 SP3 or later.

#*** Exdeploy finished: 05/09/2006 09:00:59 ***#
----------------------------------------------------------------------------

I'm not sure how to overcome this?  This tool cannnot see my exchange server.  The server name is mercury.  Our domain name is parallel.  I would appreciate any help.
0
 
rakeshmiglaniCommented:
are you able to ping this server "mercury" by name and ip address from the exchange 2003 server?
0
 
tonykmanAuthor Commented:
yes, it responds back with correct IP.
0
 
rakeshmiglaniCommented:
do you see any error in the exchange setup progress log?
0
 
tonykmanAuthor Commented:
Here is what I received:

[08:56:59]  ********** Beginning Exchange Deployment Tools **********
[08:56:59] Starting Exchange 6944 Deployment Tools on Windows 5.2.3790 at 08:56:59 05/09/2006
[08:56:59] Entering HrDirPreReq_Initialize
[08:56:59] Init called with Domain Controller mars and Exchange 5.5 server mercury.  Setup's language ID is 0.  ActiveX Path is (null)
[08:56:59] Entering HrRegisterAXDLL
[08:56:59] Leaving HrRegisterAXDLL
[08:56:59] Leaving HrDirPreReq_Initialize
[08:56:59] Entering HrRegisterAXDLL
[08:56:59] Leaving HrRegisterAXDLL
[09:00:59] HrDirPreReq_CmdLine (f:\titanium\dsa\src\deploy\dsintegchk\cmdline.cpp:2092).  Error code 0XFFFFFFFF(65535).
[09:00:59] Entering HrOrgReport
[09:00:59] Test completed successfully.  No organization was found in Active Directory.
[09:00:59] Leaving HrOrgReport
[09:00:59] Entering HrGCVerCheck
[09:00:59] GCVerCheck completed successfully.  All domain controllers and global catalog servers in the current and adjacent Windows sites are running Windows 2000 SP3 or later.
[09:00:59] Leaving HrGCVerCheck
[09:00:59] Entering HrDirPreReq_Terminate
[09:00:59] Leaving HrDirPreReq_Terminate

No org found in AD seems strange.
0
 
rakeshmiglaniCommented:
>No org found in AD seems strange.

this is correct because at present exchange 2003 is not installed and exchange 5.5 does not reside in AD. Exchange 5.5 resides in dir.edb.
once exchange 2003's forest prep is run then the org is created in AD.. so there is nothing to worry about this error.

is exchange 5.5 installed on NT?
0
 
tonykmanAuthor Commented:
yes it is.
0
 
rakeshmiglaniCommented:
check the following link and let me know if it is applicable in your case.

http://support.microsoft.com/kb/322051/en-us
0
 
tonykmanAuthor Commented:
You can no longer get the hotfix for this issue.  I decided just to install exchange and migrate each mailbox one at a time through exchange migration tool.  
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 13
  • 12
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now