[GDKitty]

Background first, we were testing BES with 4.1 on current hardware (stand alone server), working fine, descided to finaly roll the project forward, but to get free BES with registrations, had to be 5.0. Installed ok, all users (about 25) set up. Problem is, the hardware on the stand alon is not the greatest and GRINDS the server to a halt almost when alot of activity.

We have recently aquired a server and have set up with ESXi 4.0. Running our printer server off it only right now, but wish to move the BES server over to it.

Now, i use the VMware standalone converter tool, which is suposed to live move everything over the virtual machine.

Machine moves over fine, all data, etc, but we are having a problem with the 4 following services:

BB mailstore
BB Policy
BB Sycronization
Lotus datastore

Now on the working old hardware, these 4 are on manual, but they startup correctly when the server does. On the new server, they do not start up as they should.. the lotus datastore can be started maualy fine after the fact, but the other 3 fail (as if some other pre-requisite is not met).

Does anyone have any ideas?

[CanuckBB]

The only sure-fire way to do this is to:

stop and disable all BES services on the old server
migrate
shutdown the old server
start the new server
start the services and set them to auto or manual, whatever thery were originally at.

[Harry Azol]

I would recommend the VMware Converter bootable cold clone CD instead of a migration where the OS is running