Nothing has worked. The message associated with error code 1920 reads.Because of a legacy control app, we cannot just retire the XP system, but we feel the need to get the system off the existing machine because of its age.
Vmware Converter Standalone Could Not Start Service Install The ConverterWhen I try to install the converter on the system, it stops at starting the services and fails with an error code of 1920.
If I check the services that are installed at this point, I can see all three VM services are installed (server, client, and agent) but not running. If I try to start a service from windows, it fails with an error code of 1053. Finally, if I try to convert the systems remotely through an installation on a Windows 7 system, it fails with an error code of 1603. I have read through many different forums for solutions to this, and have tried them all, with no success. I am hoping that someone else has had this problem and found a way to resolve it. Thanks. Most things are technically do-able, but Microsoft require specific licenses for what you want to do. If your XP machines are OEM, you cannot move them, period, they must remain on the hardware they come with - you can virtualize them, but it needs to remain on the same tin it came with. Virtualizing a desktop requires SA or VDA licenses, as well as the OS license itself, both come at a cost and VDA licenses are not typically bought for a handful of devices, they generally get used for larger scale VDI setups. All of this aside to show willing - what version or VMware are you migrating to, workstation or ESXi and what version What version is the convertor, you need older ones to convert XP From a security perspective XP should be contained and away from the main network and definitely the internet, virtualizing them may put you at a greater risk if not secured properly. When I try to P2V an old PC (required for safe-keeping), these are the steps I would take. Vmware Converter Standalone Could Not Start Service Software On XPUninstall AV or any security software on XP - Uninstall MS Office (you can reinstall it later) - set page file to 1024mb (you can set to no page file if you can) - do a clean up for unnecessary files (temp, Windowstemp, paging file, hibernation file, Windows Update folder) Then the standalone converter is installed on a VM that is on the same ESXi host as the VCSA and the P2V is to a VM on the same ESXi host (literally everything is on the same host as to have less network transfers). The version of vCenter Converter Standalone I am using is version 6.2.0 - build 8466193. This is the exact same version that I used for the other 4 conversions. All anti-virus software is removed from the system, but that wasnt a problem with any of the other conversions. I also had no problem with Office on the other systems. In fact, I did nothing to the other systems before conversion, just installed and ran. I checked that all the service dependencies listed on vmWares website were running. I tried logging on to the domain using the users logon (which is the way the other 4 systems were running when converted), and the domain controller. I also tried logging on locally using the administrator account. All got to the point where the services were loaded, but could not be started. I am, however, able to remote desktop onto the system using the exact same credentials I used when running the remote conversion. Ive compared the network configuration from a successful conversion against this system and found no difference. When I Google searched this, I found others with the same problem. Whatever solution was proposed to the others, I checked, tried, changed. Nothing has worked. The message associated with error code 1920 reads.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |