you need download a sysprep for w2k3 and descompact at this folder
*If you found this information useful, please consider awarding points for "Correct" or "Helpful"*
I went to
Then copy that file to
C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\sysprep\svr2003
After extracting the windowsServer2003-KB926028-v2-x86-ENU.exe, I still get that error.
It seems that this WindowsServer2003-KB926028-v2-x86-ENU.exe, is so sort of "update"; the real sysprep, I tracked down to C:\WINDOWS\system32\deploy.cab
I unzipped deploy.cab; still no luck when I run Vmware vcenter Converter Standalone
If so what options should I select?
the options are:
- don't reset grace period for activation
- Don't generate security identifiers
- detect non-plug and play hardware
Thanks for your help
1 person found this helpful
I was tripped up for as minute as well. It states it in that article, I had to read it like 3 times because I thought just extracting it was key.
After you unpack it in that directory, then you have to find the "deploy.rar" file. In my case it was hising in C:\ProgramData\Application Data\VMware\VMware vCenter Converter Standalone\sysprep\svr2003\SP2QFE.
But you will only find it after you extract the main files. Then take what's in "deploy.rar" and extract that in C:\ProgramData\Application Data\VMware\VMware vCenter Converter Standalone\sysprep\svr2003 as well.
Like it would have killed them to have that already unpacked ???
Anyway..... After that it took off
This worked great for me. Thanks
I know it's an old thread but I've just experienced this issues P2V'ing an old 2003 Server system.
This thread was very useful, thanks Cire3
I just ran into an issue with this as well, but when I went to copy the files I got an access denied message.
Strange problem, everything looked fine, but once I re-applied the permissions to the destination folder I was able to copy the files no problem.
Converter ran fine after that.
This is a very old thread but I've just followed the steps to resolve this issue for an old Windows Server 2003 SP2 Server that I am P2V'ing and it worked a treat :-)
It is year 2016, and your method works like a charm @ Cire3
Actually the VMware KB: Sysprep file locations and versions sums it up nicely, except for the paths of course.
So anyone and every one please refer to the paths from this post and map them to your environment.