We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
11 days, 14 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
convert physical windows server running exchange to virtual server vmware
Posted on 2012-12-31
If we plan to convert our current exchange server to virtual server vmware, what considerations that we should look after ? I'm afraid of doing this conversion, it might wiped all of our current installed of the exchange server.
Do anyone have experienced this ? how easy to perform this conversion and what will the benefit of doing this conversion ?
Do anyone have experienced this ? how easy to perform this conversion and what will the benefit of doing this conversion ?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3
2
- +2
8 Comments
Turn off the exchange server and then use the vmware p2v converter: http://downloads.vmware.com/d/info/infrastructure_operations_management/vmware_vcenter_converter_standalone/5_0
To use the converter:
VMware vCenter Converter Standalone 5.0 Documentation
VMware vCenter Converter Standalone 5.0 User Guide
To use the converter:
VMware vCenter Converter Standalone 5.0 Documentation
VMware vCenter Converter Standalone 5.0 User Guide
Another good document on how to use the p2v converter: http://www.experts-exchange.com/Software/VMWare/A_3639-VMware-vConverter-P2V-for-Windows-Servers.html
After the conversion finished succesfully leave the phisical server turn off and turn on the virtual server. Double check the Ip Address of the virtual server and then remove unused drivers: http://communities.vmware.com/message/471384
After the conversion finished succesfully leave the phisical server turn off and turn on the virtual server. Double check the Ip Address of the virtual server and then remove unused drivers: http://communities.vmware.com/message/471384
Active today
Hi,
Is that means the exchange server also will be exist in virtual server ? when u said turn off physical server are u saying turn off by start-shutdown for physical exchange server and left only exchange server on virtual ?
what will happens if both are running ? is there any conflict with IP address and other setting ?
Is that means the exchange server also will be exist in virtual server ? when u said turn off physical server are u saying turn off by start-shutdown for physical exchange server and left only exchange server on virtual ?
what will happens if both are running ? is there any conflict with IP address and other setting ?
@motioneye - what I did when I converted my Exchange was did a P2V as mentioned by @clonyxlro, but I only P2V'd the system volume (C: drive). My Storage Groups (SGs) are on a SAN, so what I did was P2V only the C: drive, which only took about 30-60mins (and yes, stop all Exchg services, A/V services, and any other unneeded services). I then assigned the LUNs that have my SGs on them to the Storage Pool that has my ESXi Hosts and rescanned my ESXi Host HBAs.
Then, once I got my VM, (and yes, you need to power down the physical host because yes, you will have a name AND IP conflict on your network), rt-clicked on the VM > Edit Settings > Add > Hard Disk then go through the 'Add Wizard and add your storage as RDMs. Once the SG 'disks' are added to your newly created VM, you should be able to power it on and be good to go.
Regards.
~coolsport00
Then, once I got my VM, (and yes, you need to power down the physical host because yes, you will have a name AND IP conflict on your network), rt-clicked on the VM > Edit Settings > Add > Hard Disk then go through the 'Add Wizard and add your storage as RDMs. Once the SG 'disks' are added to your newly created VM, you should be able to power it on and be good to go.
Regards.
~coolsport00
If your SGs are not part of a SAN, then no biggee...just P2V it all. It will just take quite a bit longer depending on the size of your SGs for the server to convert. Once converted, power down the physical box, then power on the VM and make sure all is working.
~coolsport00
~coolsport00
Active today
See my EE Articles
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.0
HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0
if you are going to do it, stop and turn off all exchange services, and set to manual.
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.0
HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0
if you are going to do it, stop and turn off all exchange services, and set to manual.
As coolsport00 and hanccocka already mentioned, stop the exchange services before shooting down the Physical machine, then p2v and when finished successful turn on only the VM Exchange. Do NOT turn on the physical machine when the VM is running. You will have that one as a backup for a couple of weeks just in case something goes wrong with the VM.
Good luck and Happy New Year !!!
Good luck and Happy New Year !!!
Things to do.
1.Create a new local admin account in the physical server. Login and check the server again using the account.
2Verify the Names of production and backup NICs. Collect NIC teaming info.
3.Collect time zone info and NTP settings if required.
4."Execute the following commands at the cmd prompt:
mkdir c:\vm_conversion
ipconfig /all > c:\vm_conversion\ip.txt
netsh interface dump > c:\vm_conversion\netsh.txt
route print > c:\vm_conversion\routes.tx
Collect VLAN ID for every IP configured on the server"
Check if Source server has a CD-ROM /Floppy/USB Devices on it, eject and verify both are empty prior to conversion
Ensure there is at least 264MB of RAM on physical server (for hot migration)
Ensure there is minimum 300 MB free space on server OS partition (for hot migration)
Check NIC speed and duplex and correct if necessary (1 Gbps desirable).
Run Checkdisk on drives(reboot if required to complete the checkdisk run)
"Verify that the following network ports are open:
Converter VM to Physical server TCP - 445,139,9089 & UDP - 137, 138 (NetBIOS)
Converter VM to Vcenter 443
Converter VM to ESX 4.0 443
Physical server to V"
"Ensure that Simple File Sharing is turned on. (if File Sharing is not enabled)
Ensure that file and printer sharing is enabled and not blocked by Windows Firewall"
Initiate P2V
++++++++++++++++++++++++++
Reboot the physical server
Take System State backup.(Confirm Complete Backup is taken)
Stop backup client, Anti-Virus, SQL Services (only for Hot conversions) & Applicatoin services.
Run MSINFO32 and store the output to the remote location or file server
Begin Converter Process
Start Conversion Process
"Monitor Conversion to Completion
(VM-01) Verify GUI shows 100% Complete."
Open the Converter log located at the right bottom of the screen, and verify there are no errors.
Click on the “export logs” button and save the log on the Folder "Conversion Logs "
Shut down the physical server
Power on the new Virtual Machine
Login to VM using the vmware console. The VM will ask for a reboot after all virtual Hardware is properlly installed.
Install VMWare tools using the guided installation. After installation is done, vmware tools will ask for a reboot. Proceed with this.
Enable "Video Hardware acceleration" on the VM. Follow the Vmware tools on-screen instructions.
"Using the VMware Console, login to VM and Complete the following steps to ensure there is no hidden Hardware:
1. From the command prompt, type the following commands:
set devmgr_show_nonpresent_dev
start devmgmt.msc
2. From the Device Manager, list "
"Verify that all network settings are OK, and that all IP Configurations were successfully migrated. If not, use the information collected in step 4 (C:\vm_conversion\ip.txt)
-Rename NICs to their original name
-Ping default Gateway to verify"
Uninstall Teaming Software
Verify the NIC binding order.
Go to the services console, and verify that the "Converter Agent" was successfully uninstalled. If not, Go to Add/remove programs and uninstall from there.
If IP Settings were reconfigured, reboot the server to ensure that all services are started properlly. Refer msinfo32
If necessary, troubleshoot the VM and solve the issues.
Apply the new configuration if requested (Change the amount of CPU´s, Disk and RAM).
Connect Each Interface to correct VLAN (If there are multiple interfaces)
Verify routes.txt and create static routes (if any) as per the pre-migration status and check NTP settings
With regards
Karthik Rajasekaran
1.Create a new local admin account in the physical server. Login and check the server again using the account.
2Verify the Names of production and backup NICs. Collect NIC teaming info.
3.Collect time zone info and NTP settings if required.
4."Execute the following commands at the cmd prompt:
mkdir c:\vm_conversion
ipconfig /all > c:\vm_conversion\ip.txt
netsh interface dump > c:\vm_conversion\netsh.txt
route print > c:\vm_conversion\routes.tx
Collect VLAN ID for every IP configured on the server"
Check if Source server has a CD-ROM /Floppy/USB Devices on it, eject and verify both are empty prior to conversion
Ensure there is at least 264MB of RAM on physical server (for hot migration)
Ensure there is minimum 300 MB free space on server OS partition (for hot migration)
Check NIC speed and duplex and correct if necessary (1 Gbps desirable).
Run Checkdisk on drives(reboot if required to complete the checkdisk run)
"Verify that the following network ports are open:
Converter VM to Physical server TCP - 445,139,9089 & UDP - 137, 138 (NetBIOS)
Converter VM to Vcenter 443
Converter VM to ESX 4.0 443
Physical server to V"
"Ensure that Simple File Sharing is turned on. (if File Sharing is not enabled)
Ensure that file and printer sharing is enabled and not blocked by Windows Firewall"
Initiate P2V
++++++++++++++++++++++++++
Reboot the physical server
Take System State backup.(Confirm Complete Backup is taken)
Stop backup client, Anti-Virus, SQL Services (only for Hot conversions) & Applicatoin services.
Run MSINFO32 and store the output to the remote location or file server
Begin Converter Process
Start Conversion Process
"Monitor Conversion to Completion
(VM-01) Verify GUI shows 100% Complete."
Open the Converter log located at the right bottom of the screen, and verify there are no errors.
Click on the “export logs” button and save the log on the Folder "Conversion Logs "
Shut down the physical server
Power on the new Virtual Machine
Login to VM using the vmware console. The VM will ask for a reboot after all virtual Hardware is properlly installed.
Install VMWare tools using the guided installation. After installation is done, vmware tools will ask for a reboot. Proceed with this.
Enable "Video Hardware acceleration" on the VM. Follow the Vmware tools on-screen instructions.
"Using the VMware Console, login to VM and Complete the following steps to ensure there is no hidden Hardware:
1. From the command prompt, type the following commands:
set devmgr_show_nonpresent_dev
start devmgmt.msc
2. From the Device Manager, list "
"Verify that all network settings are OK, and that all IP Configurations were successfully migrated. If not, use the information collected in step 4 (C:\vm_conversion\ip.txt)
-Rename NICs to their original name
-Ping default Gateway to verify"
Uninstall Teaming Software
Verify the NIC binding order.
Go to the services console, and verify that the "Converter Agent" was successfully uninstalled. If not, Go to Add/remove programs and uninstall from there.
If IP Settings were reconfigured, reboot the server to ensure that all services are started properlly. Refer msinfo32
If necessary, troubleshoot the VM and solve the issues.
Apply the new configuration if requested (Change the amount of CPU´s, Disk and RAM).
Connect Each Interface to correct VLAN (If there are multiple interfaces)
Verify routes.txt and create static routes (if any) as per the pre-migration status and check NTP settings
With regards
Karthik Rajasekaran
Featured Post
Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
Teach the user how to delpoy the vCenter Server Appliance and how to configure its network settings
Deploy OVF: Open VM console and configure networking:
Teach the user how to edit .vmx files to add advanced configuration options
Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month11 days, 14 hours left to enroll
Earn Certification
CompTIA IT Fundamentals
$49.00$44.10
623 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.