Moving 5.5 to new site

[hannahsh]

ok had some trouble with a couple of sites

logon exchange systems account
stop MTA
Backup !!!!! important

Isolate server by removing site connectors
Wait for site to vanish - replication complete

Remove site event service by running setup add/remove

Reboot

then run mvexsrvr (installed new folder)

During site move - crashes during private information transfer ?????

anything we have missed or could try as this happens on 2 boxes

Cheers
stewart

 

[zbnet]

I've done lots of Move Server Wizard runs and never had the problem you're having.

When you say you logon with the Exchange systems account, I presume you mean the Service Account for the site of the server you're moving?

This is a single server site your moving (ie last server in site)?

At the point of the crash, presumably it's done all the directory work - are there any problems with this in the MSW logfile?

What exact error is the MSW displaying?

Are you moving it to a brand new site that doesn't exist before the move? We've had problems with this, you could consider creating the site in advance using a temporary server.

 

[netometer]

Hi!
Do you have enough free space (at least 500 Mb) on the server?
What are the error messages that you get in eventlog?

NetoMeter

http://www.netometer.net

 

[netometer]

Just another idea - run ESEUTIL /G /ISPRIV and ISINTEG –TEST ALLTESTS to make sure that the private information store does not have any problems.

NetoMeter

http://www.netometer.net

 

[hannahsh]

in answer to the above

The site there moving to is the main "HQ" which already has a number of servers. We found to problems - the version of mvexsvrv is different from the previous ones we used and we pointed the server to a newer server at HQ and not the first original one

So how do we remove the original server - not used anymore as mailboxes have been moved to a new box?

Also after migration the users outlook was unable to find their mail server - wasnt able to realise it had moved sites although server name was still the same.

 

[zbnet]

Okay, you've raised a few issues here.

Firstly, using a version of MSW that isn't compatible with your version of the store will definitely cause the sort of problems you're getting (although you still haven't posted the error message you are getting so we can't confirm this).

http://support.microsoft.com/kb/q248838/

has details of store versions. The 3 key files to check the versions of are store.exe, mdbmsg.dll, and mvstore.dll

When moving a server to an existing site, it shouldn't matter which reference server you use in the new site - they should all have the same directory on them. Incidentally they should all also have the same SP and hotfix level.

Removing the original server from the HQ site is covered in

http://support.microsoft.com/default.aspx?kbid=152959

Finally, the issue that users cannot connect to the Exchange server after a move is covered fully in the MSW documentation that comes with the software. The server name doesn't change, but all the GUIDs associated with that name change, so the profile needs to be repointed to the new server. Microsoft's recommendation is that you recreate each client's MAPI profile, although we have had some success by removing the server name from the MAPI profile and replacing it again, which then necessitates a new CheckNames, which should then find the server in its new location and then reconnect to the mailbox on the moved server. See the MSW documenttion for all the otjher things that will have broken, though (like delegate access, off-server mailbox permissions etc).