• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2650
  • Last Modified:

How do I use Converter to safely convert an Exchange 2003 server to virtual

We are using VMware Infrastucture/ESX Server to set up an off-site DR location of all of our servers, and am wondering what precautions need to be addressed while using VMware Converter to convert an Exchange 2003 server. I realize that a complete backup should be done prior, but other things such as taking the IS offline I can't find documentation anywhere. If anyone has experience with this, I would love to hear from you.
0
nj_becker
Asked:
nj_becker
1 Solution
 
Bart van der WeeCommented:
Hi,
Using vmware convertor built in to VMWare workstation 6 I successfully converted our Exchange Server 2003 server with about 120GB worth of information stores.

I ran the conversion overnight while the server was live. When conversion was completed I booted the vmware image up with no network connection, updated/installed vmware tools etc and all appears to be good. Very impressed with the results for now.

however as with all microsoft products - your mileage may vary :)

Bart
0
 
Luciano PatrãoICT Senior Infraestructure Engineer Commented:
Hi

I have also converted a Exchange Server 2007 to a VM, and after power on the VM i found no problem with the server.

Jail
0
 
sunshineknoxCommented:
Has anyone been able to convert exchange 2000, because of the stupid M drive it creates?
\
\
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
redseatechnologiesCommented:
That should be in it's own question.

M: isn't actually created, it is just a representation.  If the VMWare converter wants to play with it anyway, I would recommend you disable the M: - there is a reg-hack to do so.

Personally, I wouldn't use anything like converter on an Exchange server, but am intrigued by the success demonstrated here and may have to give it a go :)  What I normally do is a flat out migration - there is no downtime, and it is (IMHO) safer.

-red
0
 
Bart van der WeeCommented:
sunshineknox:

Don't select to convert the M: drive in the first place?
0
 
Luciano PatrãoICT Senior Infraestructure Engineer Commented:
Hi

You can easily converter a Exchange Serve with no problem. I have done this several times and had no problem.

You can also disable the M drive.

This is the easy way

http://www.petri.co.il/remove_the_m_drive_mapping_in_e2k.htm

Then you can restore it

http://www.petri.co.il/restore_the_m_drive_mapping_in_exchange_2003.htm

Hope this can help you all

Jail
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now