seven45
asked on
P2V
Quick question:
On a P2V using the Converter, once you P2V to an Esxi server, does the physical server need to be shutdown completely since the Virtual Server is now online? I'm asking In terms of the SID---does that need to change? Any sysprep needed? or just the fact that we converted a P 2 a V, we can shutdown the P and bring the V online with nothing else that needs to be done. This is in a microsoft windows 2003 environment.
On a P2V using the Converter, once you P2V to an Esxi server, does the physical server need to be shutdown completely since the Virtual Server is now online? I'm asking In terms of the SID---does that need to change? Any sysprep needed? or just the fact that we converted a P 2 a V, we can shutdown the P and bring the V online with nothing else that needs to be done. This is in a microsoft windows 2003 environment.
Ross-C
I'm not 100% sure what you are asking with regards to the SID. If it helps we P2V'd all our windows server DC/DNS, exchange etc and provided your virtual switche(s) in your virtual environment are on the same network it should just be a case of shutting down the original and powering on the new virtualized machine.
Yes the original Physical machine needs to be shut down or disconnected from the network once you power up the new Virtual Machine.
The converted virtual machine will have the same IP address, hostname etc once it is powered on.
The converted virtual machine will have the same IP address, hostname etc once it is powered on.
ASKER
so, no sysprep is needed?
I'm planning on using the P2V on a terminal server running 2003. I'm assuming we dont have to do anything special for terminal servers either.
I'm planning on using the P2V on a terminal server running 2003. I'm assuming we dont have to do anything special for terminal servers either.
providing the P2V doesn't throw any errors it will work in exactly the same way regardless of the server function. It takes a bit of getting used to just how good vmware is but trust me, it just works.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sysprep is not mandatory.
It depends whether you would like to customize target VM or you want the VM identical to the Physical system (in case you have a Plan to replace the Physical with Virtual machine)
So you can decide whether the conversion will Replace the existing server or add a VM to the existing setup.
One problem you might encounter problem is "Terminal Server License" since this is tied to Hardware ID
Also I would like to mention that when you have Windows 2003 enterprise license you are allowed to Run 4 instances of the operating system (virtual machines), provided you run them on the same Hardware.
It depends whether you would like to customize target VM or you want the VM identical to the Physical system (in case you have a Plan to replace the Physical with Virtual machine)
So you can decide whether the conversion will Replace the existing server or add a VM to the existing setup.
One problem you might encounter problem is "Terminal Server License" since this is tied to Hardware ID
Also I would like to mention that when you have Windows 2003 enterprise license you are allowed to Run 4 instances of the operating system (virtual machines), provided you run them on the same Hardware.
Just so everyone knows the free version is now called VMware vSphere Hypervisor.
The difference between ESX classic and ESXi is ESXi doesn't have a console. Both allow for the same functionally. Version 4.1 is the last version where ESX classic will be available.
The difference between ESX classic and ESXi is ESXi doesn't have a console. Both allow for the same functionally. Version 4.1 is the last version where ESX classic will be available.
ASKER
Sorry for the late reply; I will try it this weekend and report back.