flugaurj
asked on
Issues using VMWare Convertor on Exchange 2010 server, need suggestions
We are currently migrating from XenServer to VMWare and we tried to do a V2V of our Exchange 2010 Standard server and everything appeared to work fine after until we realized that no one could send mail (it all just kept piling up in their outbox). They could receive mail fine which was wierd and there were no error messages in the event logs either. I rolled back the server to the XenServer one and everything is working fine. I have read online that other people have had the same issues when they tried to migrate Exchange. Having purchased only Exchange 2010 Standard am I am to bring up another server in VMWare and migrate the mailboxes over live and then decomission the old server? Not sure what my options are or should there be something else that I look at to migrate the server?
Paul Solovyovsky
Did you change the IP on the vmware VM? When you V2V the nic migrated to dhcp by default so it may be picking dhcp address instead of the static ip needed for proper flow/firewall access
ASKER
The IP was changed in VMWare. It was wierd because users could connect to the Exhchange server and receive mail but just couldn't send. I saw a few posted on the VMWare forums with users having the same issue and no solution given.
A couple of things to check:
Make sure that the hub transport server has the correct NIC selected for mail. During the conversion it's possible the NIC was renamed.
Do you have memory reservations enabled for this server? If not, try setting a memory reservation for the full amount of memory you have allocated.
Make sure that the hub transport server has the correct NIC selected for mail. During the conversion it's possible the NIC was renamed.
Do you have memory reservations enabled for this server? If not, try setting a memory reservation for the full amount of memory you have allocated.
ASKER
I did try enabling memory reservations but that didn't do anything. How do I check if the hub transport server has the correct VIC selected for mail?
ASKER
SOrry..NIC selected for mail?
ASKER
I looked in the HUB Transport and it says all IPv4 and all IPv6 NICs
Capture.JPG
Capture.JPG
flugaurj, you mentioned that the IP was changed in VMware. The question I have is whether the necessary policies on your firewall was changed to allow the new IP address to send mail out on port 25? Having said that, when you says users can receive mail is it from anywhere or just internally from colleagues?
ASKER
The IP was changed back to the same IP before the move. They were receiving emails from the outside no problem. Not sure about the inside because no one could send mail....
try to disable IPV6.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
none