Posted on 2010-08-31
Medium Priority
Last Modified: 2012-07-09
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.
Question by:seven45
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
  • 2
  • 2
  • 2
  • +3
LVL 11

Expert Comment

ID: 33572686
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.

Expert Comment

ID: 33572706
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.

Author Comment

ID: 33572735
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.
Does Your Cloud Backup Use Blockchain Technology?

Blockchain technology has already revolutionized finance thanks to Bitcoin. Now it's disrupting other areas, including the realm of data protection. Learn how blockchain is now being used to authenticate backup files and keep them safe from hackers.

LVL 11

Expert Comment

ID: 33572749
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.

Assisted Solution

Saineolai earned 500 total points
ID: 33572766
You may run into licensing issues if the Windows 2003 Server is running an OEM license.  When the virtual machine boots it will ask to be reactivated due to the significant change in hardware.

It is a breach of the OEM license to continue to use the VM in this fashion,
LVL 40

Accepted Solution

coolsport00 earned 500 total points
ID: 33573475
Sysprep is typically part of the P2V process and you'll receive an error stating it's needed. Yes, your phys host will need to be powered down or you will have an IP Addy conflict on your domain. "Saineolai" is correct in that if your phys host has an OEM W2K3 install, you will get a Windows activation error upon bootup of the VM. Other than those things, P2V is pretty much a seamless process. For the most part, you have down what needs to be done.

You can place the W2K3 sysprep files on the workstation you run Converter from in the following location:
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\

See this Vmware KB for more info:


Expert Comment

ID: 33573833
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.

Expert Comment

ID: 33580528
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.

Author Comment

ID: 33739316
Sorry for the late reply; I will try it this weekend and report back.

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

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.
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
Suggested Courses

741 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question