![]() ![]() I converted both C: (boot partition) and (system partition) successfully but anyway the converter cannot find (?). I tried to "Configure machine" with the button, but received "unable to locate system volume". After another 2 hours conversion was finally successful! But the virtual Windows failed to start - it gave "Inaccessible boot device". Then I found that I have to look for agent logs about the reason - Other fix # 2: had to increase manually the maximum registry size with 20 MB.ĥ. I installed VMware vCenter Converter Standalone 4.0.1 server and client on the old PC and converted local machine. I downloaded them and copied them where needed but after 2 hours the conversion failed again.Ĥ. There was a warning that I have no sysprep tools. I connected to the agent but conversion failed after 2 hours at reconfiguration stage. I had to manually edit a Other fix #1: D:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\converter-agent.xml file and to change Config/plugins/ufa_agent/enableRemoteAccess to true.ģ. After starting the service, agent listened only on 127.0.0.1 (localhost). Downloaded VMware vCenter Converter Standalone 4.0.1 for Windows and manually installed agent. ![]() Bug #1: Linux version of VMware vCenter Converter Standalone 4.0.1 doesn't try to install agent on the remote machine.Ģ. I checked with Wireshark - no one IP packet was sent to the remote PC. After waiting about 1-2 minutes deployment failed. It detected that my old PC with Windows 2000 started has no agent installed by trying to connect to TCP port 9089 and then asked to deploy agent. Installed VMware vCenter Converter Standalone 4.0.1 on my new PC with kubuntu. I had an old PC with AMD CPU, VIA KT333 chipset and with Windows 2000 Professional dual/triple booting Windows 98 and kubuntu. This should be considered also request for adding features. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |