How to move BES server to new hardware

Hello everyone,
Currently I have a BES server ver. 4.0.6 installed on an Exchange 2003 bridgehead server and I want to move it to a new server that will have a different hostname. I have 50 user accounts and the current data base is MSDE, I would like to use an MSDE database on the new server. I would also like to make this migration with the least amount of impact to users as possible meaning minimal down time and if possible I would like to avoid reactivating accounts as I found to be a requirement in the upgrade doc. I am planning to install BES 4.0.6 on the new server and once in place I will be updating to 4.1.4 at a later date. I have read about moving the database to the new server via running a restore from a backup of the original server and I was wondering if this is a viable solution. Also if anyone has performed this procedure successfully I would greatly appreciate a how to as I have minimal experience with BES so any help would be greatly appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I just recently did this about 6 months ago but I took a different approach to it. I decided to deploy it in a virtual machine so if and when I wanted to transition it again, I didn't have to do anything but to move the virtual machine.

I choose vmware for my virtual server because I personally like it better than Microsoft Virtual Server. I like that you have USB support for things like external hard drives or flash drives.

I took a good backup of my production server using ntbackup and stored it on an external hard drive. Then I created a vmware session without the virtual network card. Installed Windows 2003 server in a vmware session and attached an external hard disk via USB to access the backup file. I restored the backup and let the OS reboot. The OS had removed all the old hardware and installed all the new virtual hardware. I then installed vmware tools. Now I had a replica of my production server. Then I removed the network cable from my production server to prevent duplicate machine names or ip addresses on the network. I installed the NIC in vmware (bridging mode) and made sure it took over the IP address of my production server.

The new BES server took over right away and I have not had a problem with it since.

It made sense to me to use the virtual machine because if I were to ever have a hardware problem in the future, I can simply move the virtual machine to new hardware with very little downtime. I've done this with many of my servers and I couldn't be happier.
FrankNoeAuthor Commented:
Thanks for the reply Modestqeek I am also contemplating a build out on a VMware server for the new BES server but In my case don't want to restore the entire Server/OS. I want to build a new server and then restore the backup of the exiting BES servers MSDE database onto the new server. I was also hoping that I would also be able to fall back to the original server if all failed.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.