Hi,
take a look at
VMware vCenter Converter Standalone Release Notes
It says with converter 6.0 , windows server 2003 R2 is supported with SP2
For the 2003 without R2, you need to use converter 5.0.1
It supports server 2003 SP2:
Tim
Hi,
take a look at
VMware vCenter Converter Standalone Release Notes
It says with converter 6.0 , windows server 2003 R2 is supported with SP2
For the 2003 without R2, you need to use converter 5.0.1
It supports server 2003 SP2:
Tim
Hi
Microsoft Windows Server 2008 R2 Enterprise & windows 2003 r2 will support latest vCenter converter edition
thanks
Sakthivel R
Yes, For the 2003 without R2, you need to use converter 5.0.1
Hello
There has always been some confusion about what is stated in the guide and release notes about 2003 and 2003 R2.
From a technical point of view - they are both supported. That means there is nothing in Converter code base that prevents them to be used, also the tests have been done with both 2K3 and 2K3R2. (I mean Converter 5.x and 6.0)
I am not quite sure which service packs have been tested but the general approach is that it is recommended to have the latest SP.
In general our guideline is to support all OS versions still supported by the vendor by Converter GA date. (which implies 6.0 still supports 2K3 but expect it to dropped with the next release; and don't regard that as a commitment, exceptions may apply :-).
HTH,
Plamen
Thank you all, most helpful
Hi all,
I have a converting task created in VMware converter. I ran first synchro and I plan to do final synchro laster. Between these two steps, admin password has been changed on my VMware infra.
So, when I want to run synchro, I get the following error: Cannot complete login due to an incorrect user name or password. I can't restore initial password on the VMware infra. So, how can I change password memorized into VMware Converter ?
Thanks for help
Vm is windows 2003 or 2008?
Ummmm, SARAVANA... what do you think will be difference if OS is 2k3 versus 2k8?
Or "just asking"?
If you have no idea what the question and answer is please do not mess the forum's thread.
Windows 2012
The short answer is - you can't change the username and/or password for running jobs.
Just restart the conversion again...
HTH
Hi,
same with me - error at 98% during creation of the vm, then retried only configuration of the vm --> same error. Bluescreen when starting the VM. After reading this thread I made sure there is plenty of RAM available and retried the configuration of the VM, which ran through successfully. The VM works fine now. In my opinion this is worth being added to the knowledge base (there is already an entry, but it is kind of misleading).
Regards
R.
Hi,
This is not a running job but an active job waiting for manual synchro
Thanks
Hi,
I'm trying to virtualize a Windows 2008 R2 server.
it fails at 97% with the following error : "Unable to proceed since the sysprep parameters provided are not correct"
I tried to run converter "as administrator" but I got the same error twice.
Here are the logs export.
Thanks for your help !
The problem is:
2015-08-31T00:06:00.240+02:00 warning vmware-converter-agent[09080] [Originator@6876 sub=Default] Unable to get GetShortPathName for 'C:\Windows\TEMP\vmware-temp\vmware-Système\deploypkgntgqeqbujbcmalvf\deployPkg.cab', error 'Le chemin d’accès spécifié est introuvable. --> '[3]
2015-08-31T00:06:00.240+02:00 error vmware-converter-agent[09080] [Originator@6876 sub=task-6] Error while creating Customization deploy File: ERR: FileIO=0
You can customize only your VM in separate task, once the conversion complete. Seems that current problem is French Windows, so try to do this task from English Windows, or activate short-file-names (8.3) and try again.
HTH
Thanks for this answer.
Yes, the physical machine I'm trying to convert is a French Windows.
Do you mean I have to install Converter Standalone on a English Windows and activate short-file-names (8.3) on the server side ?
I think that the problem you found is rather on the client side.
There are 2 options for you:
- install the Converter on English Windows and do reconfig only
- activate 8.3 name on your C: (run "fsutil 8dot3name set c:" and follow instructions), restart services and try reconfig again.
HTH
Hi Guys,
I am trying to understand why some servers we convert (all using same process) have an Incremental P2V - Bootable snapshot created.
Description: This snapshot was taken by Incremental P2V after configuring the VM to be bootable.
Trends: I cannot pinpoint a trend with source, some are SQL, some are standard app, some are physical and/or virtual
Few questions.
Thanks
B
The bootable snapshots are created at every incremental update to ensure that reconfigured VM will work.
They should be removed at next incremental step, but it's safe to remove because the next increment is done on previous snapshot not on reconfigured/bootable snapshot.
HTH
Thanks, any ideas why its created on some servers and not others? - I honestly cant see a link between any of the servers we have converted and have these snapshots - done over 100 in last few weeks, around 10% have snapshots - would really help me to understand why they are being created (or not being deleted automatically)
Thanks
B
These snapshots are created when perform P2V and 'Synchronization' is selected before convert.
About creation and removal of snapshots - look at worker's log and VC logs - there should be an explanation
HTH