mrhyperlinkukplain Get a free Giffgaff Sim

Posts Tagged ‘vSphere’

VMware vSphere Client (C#) R.I.P

Wednesday, May 18th, 2016

Today VMware have announced the VMware vSphere Client (C#) is deprecated. This has been on the cards for many years.

Going forward the HTML 5 Web Client will be the only supported method of managing VMware vSphere.

Goodbye vSphere Client for Windows (C#) – Hello HTML5

Post to Twitter

HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.5

Sunday, October 27th, 2013
HOW TO:  P2V, V2V for FREE - VMware vCenter Converter Standalone 5.5

If you need to complete a Physical to Virtual (P2V), Virtual to Virtual (V2V) conversion to a VMware product (VMware Workstation, Player or vSphere) for FREE, then there is some good news…

VMware vCenter Converter Standalone 5.5 was released on 22 October 2013, and this latest version has new support for the following:-

  • Support for virtual machine hardware version 10
  • 62TB disks, virtual SATA controllers, etc.
  • Support for RedHat KVM virtual machines as a source
  • A new option for selecting the network adapter for the target virtual machine
  • Support for additional guest operating systems
  • Parallel disk conversions
  • Virtual SAN support

Also fixes numerous issues with crashing and conversion issues, when converting physical or virtual computers to VMware vSphere vCenter Server 5.5 and VMware Hypervisor ESXi 5.5.

  • VMware vCenter Converter Standalone v5.5

VMware vCenter Converter Standalone v5.5

While I would recommend and use VMware vCenter Converter Standalone 5.5, there are other commercial products that do exist, and I have used.

If you have a large estate of physical machines to migrate, these products have a scheduler and can perform automated workflows, but these are commercial products and not FREE like VMware vCenter Converter Standalone 5.5

NETIQ Platespin Migrate

Acronis vmProtect

Storagecraft Shadow Protect

Symantec System Recovery Server Edition

If the operating system is Windows 2003, Windows 2000 or Windows NT 4.0, select and earlier version of VMware vCenter Converter Standalone version 3.0.3 or 4.0, support for early operating systems has been removed now from v5.5.

if you have recently upgraded to vSphere vCenter Server 5.5, and are looking for the Convert/Import vCenter plugin which existed with 4.x, it’s now longer available, and has been removed, and you will need to use  VMware vCenter Converter Standalone 5.5 for your conversions.

and if you do use VMware vCenter Converter Standalone 5.5, and you want to make your transfers 60% faster checkout my EE article here

HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0

Download VMware vCenter Converter 5.5 here
VMware vCenter Converter Standalone 5.5 Documentation
VMware vCenter Converter Standalone 5.5 User Guide


If you have issues, you may want to consult the following articles and guides

Read fellow Expert Bestway’s article.

Best Practice Video Guide here

Some Videos I’ve developed for Experts Exchange members to show the VMware vCenter Converter process.

A Tutorial video by me:- Restore a Virtual Machine using the FREE VMware vCenter Converter to VMware vSphere 4.x, 5.0 ESXi 4.x, ESXi 5.0, ESX 4.0

A Tutorial video by me:- Backup VMware vSphere 4.x, 5.0 ESXi 4.x, ESXi 5.0, ESX 4.0 for FREE using VMware vCenter Converter

A Tutorial video by me:- VMware vCenter Converter Standalone Process at work

A Tutorial video by me:- VMware vCenter Converter Standalone 5.0 Convert monolithic sparse to monolithic flat for use with VMware vSphere 4.x 5.0 ESXi 4.x 5.0

Post to Twitter

Virtualisation Snapshot Hell!

Monday, September 9th, 2013

Whatever you call them in VMware circles, they are known as “Snapshots”, in Microsoft circles, Hyper-V they are known as “Checkpoints”.

Snapshots are evil things, I wrote an Article last year on Experts Exchange called - HOW TO: VMware Snapshots :- Be Patient,

the following two clients, clearly had not read my article, but they have now!

VMware vSphere Exchange Virtual Machine with two snapshots, one snapshot size of 250GB, with a parent disk of 500GB

VMware vSphere Exchange Virtual Machine with two snapshots, one snapshot size of 250GB, with a parent disk of 500GB. Exchange performance would have been poor, this snapshot has been present for many months, and eventually took 33 hours to delete, ,merge and commit the snapshot, with 33 hours of Exchange downtime!

Microsoft Hyper-V Virtual Machine

Microsoft Hyper-V Virtual Machine, with 9 nested snapshots, totally 170GB, more of an issue, performance is poor, and deleting these snapshots will cause issues, and delay!

The one thing you need to know about Snapshots, is if you use them, or find a virtual machine using one is Be Patient, if you decide to delete them!!!

or Ask an Expert First!!!!

It can take a very long time, for the process to complete and merge the child (delta) disk into the parent disk.

Post to Twitter