Therefore, you cannot select a virtual machine source to convert.Comments 0 Log in to post a comment Document transcript VMware VMware vCenter Converter 4.2 for vCenter Server 4.1 Release Notes VMware vCenter Converter 4.2 13 Jul 2010 Build 254483 vCenter Server 4.1 13 Jul 2010 Build 258902 Last Document Update: 16 Aug 2010 Check periodically for additions and upd ates to these release notes.Whats in the Release Notes These release notes cover the following topics: Introduction to VMware vCenter Converter 4.2 Whats New Installation Notes Platforms Interoperability Supported Guest Operating Systems Prior vCenter Converter Releases Known Issues Introduction to VMware vCenter Converter 4.2 With VMware vCenter Converter, you can automate the process of creating VMware virtual machines from physical machines running Windows or Linux, virtu al machine formats that are not specific to VMware, other third - party image formats, and VMware virtual machines.Through an intuitive wizard - driven interface, vCenter Converter can convert multiple local and remote physical machines with minimum disruptio ns and downtime.
Benefits Convert physical machines running Windows or Linux operating systems to VMware virtual machines quickly and without any disruption or downtime. Convert third - party image or virtual machine formats such as Parallels Desktop, Symant ec Backup Exec System Recovery, Norton Ghost, Acronis, StorageCraft, Microsoft Virtual Server or Virtual PC, and Microsoft Hyper - V Server virtual machines to VMware virtual machines. Enable centralized management of remote conversions of multiple physical servers or virtual machines simultaneously. Ensure conversion reliability through quiesced snapshots of the guest operating system on the source machine before data migration. Enable non - disruptive conversions through hot cloning, with no source server dow ntime or reboot. VMware will continue to provide technical support for vCenter Converter through the end of its support lifecycl e. Vmware Converter Could Not Start Service Vstor2 Programs Update And SupportVMware will continue to update and support the free vCenter Converter Standalone product, which enables conversions from sources such as physical machines, VMware and Microsoft virtual machine formats, and certain third - party disk image formats. Vmware Converter Could Not Start Service Vstor2 Programs Install VCenter ConverterTop of Page Installation Notes Users with limited rights cannot install vCenter Converter 4.2 on Windows. You need to log in as an administrator to install vCenter Converter. All other source file systems are converted into ext3 file systems on the destination virtual machine. Top of Page Prior Releases of vCenter Converter Features from prior releases of vCenter Converter are described in the release notes for each release. To view release notes for prior releases of vCenter Converter, click one of the following links: VMware Converter Enterprise Update 4 for VirtualCenter 2.5 VMware Converter Enterprise Update 3 f or VirtualCenter 2.5 VMware Converter Enterprise Update 2 for VirtualCenter 2.5 VMware vCenter Converter for vCenter Server 4.0 Top of Page Known Issues The vCenter Converter 4.2 release contains the following known issu es: Installation General Windows Sources Linux Sources Third - Party Formats Localization Administration Guide and Help Top of Page Installation You must restart machines that run 64 - bit Windows Vista or later before re - installing vC enter Converter 4.2 If you uninstall vCenter Converter from a 64 - bit Windows Vista, Windows Server 2008, or Windows 7 machine and do not restart it, a subsequent vCenter Converter installation might fail with the following error message: Error 29144. Cou ld not install service Vstor2 MntApi 1.0 Driver (shared). Please reboot and try to install again. Workaround: Restart the Windows Vista, Windows Server 2008, or Windows 7 machine and try installing vCenter Converter again. ![]() The following error appears in the log file: vm.fault.AgentInstallFailed. ![]() To remove VMware Converter 3.x agent manually, use Add or Remove Programs. Remote agent installation is unsuccessful when you specify a computer or DNS name with non - ASCII characters in the Conversion wizard If you use non - ASCII characters to populate the computer or DNS name field when selecting a source in the Conversion wizard, the installation of vCenter Converter agent fails. Workaround: Use the IP address instead of the non - ASCII name. Subsequent P2V conversions of remote source machines that run 64 - bit Windows Vista or later might fail after a successful conversion If you convert succes sfully a remote source machine that runs 64 - bit Windows Vista, Windows Server 2008, or Windows 7 operating system and then try converting it again, the conversion fails with the error message vCenter Converter Agent installation failed on x.x.x.x Error cod e: 1603, where x.x.x.x is the IP address of the source machine. This error message might occur if automatic uninstall of remote vCenter Converter agent has been enabled during the first successful conversion. Workaround: Restart the remote source machine and try running the conversion task again. Top of Page General New You cannot convert source virtual machines that run on non - English Hyper - V servers If the operating system of a Hyper - V server runs in a language other than English, vCenter Converter cannot display the inventory of that Hyper - V server.
0 Comments
Leave a Reply. |