Vmware released a new vCenter Converter Standalone version which is now fully compatible with vSphere 4.1.
What’s New
The VMware vCenter Converter Standalone 4.3 includes the following new functionality:
- Support for VMware vSphere 4.1 as source and destination targets
- Support for importing powered-off Microsoft Hyper-V R1 and Hyper-V R2 virtual machines
- Public API and sample code for submitting and monitoring Converter jobs
- Support for importing Windows 7 and Windows 2008 R2 sources
- Ability to throttle the data transfer from source to destination based on network bandwidth or CPU
- IPv6 support
Discontinued Support
- Support of the following operating systems is discontinued:
- Support for OVF format is discontinued
- Support for VCB image sources is discontinued
- Linux installation support is discontinued
Check out the release notes after the jump and download it here
Last week I bought a brand new OCZ Agility Series 60 GB SSD for my workstation as OS disk. I started a fresh Windows 7 64-bit installation and made some software tweaks for optimal performance. Down here some of those little settings to maximize your performance.
I already upgraded the firmware to the latest level v.1.5
My computer specs: click here
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Carlo Costanzo from VMwareInfo.com has posted the following helpful article:
The SVGA II driver installed by VMware Tools doesn’t work with 2008 R2 or Windows 7. Console sessions will randomly lockup.
http://communities.vmware.com/thread/218244?start=105&tstart=0
According to the thread there is a WDDM driver in U1 that you can install manually to fix the problem by browsing to –
“C:\Program Files\Common Files\VMware\Drivers\wddm_video“
A good one 🙂
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
We already posted a solution. This is the official unofficial unsupported VMware KB
- You cannot launch the vSphere Client
- If you install the vSphere Client in Windows 7 or Windows 2008 R2 and try to connect to the vSphere server, you see the errors:
- Error parsing the server "<servername>" "clients.xml" file.
- The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.
The vSphere Client is not currently supported in Windows 7 or Windows 2008 R2 and it does not run in Compatibility Mode.
This issue may occur because of the .NET loading mechanism change in Windows 2008 R2 and Windows 7.
There are 2 possible workarounds. Perform one of these options:
- Install a Windows XP virtual machine in Windows 7 or Windows 2008 R2 using Windows XP Mode.
- Bypass the normal .NET Framework loading mechanism.
Warning: This workaround is unsupported.
To bypass the normal .NET Framework loading mechanism:
1. Download the file system.dll. This file is typically located in %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non-Windows 7 or Windows 2008 R2 machine with .NET v3.5 SP1 installed.
2. Copy the file to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib.
Note: If the lib directory does not exist, create it.
3. Open VpxClient.exe.config in a text editor. The file is located at C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher.
4. Add the following three lines to VpxClient.exe.config, just before </configuration>:
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
5. From Windows 2008 R2 or Windows 7 System Properties, click the Advanced tab > Environment Variables.
6. Create a new System variable called DEVPATH and assign the value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Note: For 32bit operating systems, replace Program Files (x86)with Program Files.
You can now launch vSphere Client from a Windows 7 or Windows 2008 R2 machine. You may have to right-click on the vSphere Client icon and choose Run as administrator.
Details:
If you plan to use Windows 7 or Windows 2008 R2 as a guest operating system, do not use the SVGA drivers included with VMware Tools. Use the standard SVGA driver instead.
Symptoms:
Freeze
Hanging Console
High CPU
Reboots
Solution:
To deselect the SVGA drivers installed with VMware Tools:
- When you install VMware Tools, select VMware Tools Custom Install and deselect the SVGA driver.
Alternatively, remove the SVGA driver from the Device Manager after installing VMware Tools
Product Versions:
VMware ESX 4.0.x
VMware ESXi 4.0.x Installable
Source: KB 1011709
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
It’s very easy..
Install the VMware vSphere Client by default from CD or from your ESX host.
Download viclient_fix.zip
Move and replace the content in “C:\Program Files (x86)\VMware\Infrastructure\”
Open the “VMware vSphere Client” from the directory
It’s working great! 🙂
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Recent Comments