Resizing (Shrinking) Drives With VMware Standalone Converter

KB ID 0000185

Problem

Using: vSphere 6.7 and VMware Standalone Converter Version 6.2.0

I’m performing this procedure on vSphere 6.7, back ith the release of vSphere 5, This process changed, with vSphere 4 and VI3, you had to install VMware Converter on the vCenter Server then download and enable the plugin in your VI client software (like this).

VMware now only has the “standalone converter“, so now you DONT install anything on the vCenter server, the converter runs on a client machine/server.

Note: This article is primarily concerned with shrinking guest hard drives, If you want to make your drives larger you can also use this process but the following article will be easier. Resizing Windows Volumes / Drives in VMware vSphere / ESX

Also if space is your consideration, you also might want to consider; VMware ESXi – Converting ‘Thick’ Provisioned Drives to ‘Thin’

Solution

Resizing (Shrinking) Guest Hard Drives in vSphere

Before you start:

Remember you are cloning a machine, don’t have clients writing data to the machine while this is going on, or there is the potential for data to be lost. If possible disable any services that will accept data, e.g. Exchange, SQL, Oracle, etc, prior to cloning.

Licensing: Only really applicable if you’re cloning a physical machine, but make sure you DO NOT have OEM Licensing. Also if you have Windows Storage Server, or Windows Appliance Edition, you should speak to a license specialist.

Installing VMware converter is pretty straightforward, run the install file accept the EULA, select. local installation, and I opt out of the ‘User Experience’, when complete it will open the Converter client by default, (as shown).

When the program opens > Convert machine > Type in the name of the machine you are going to convert, and credentials to logon and install the converter agent > Next.

 

Type in the name of the machine you are going to convert, and credentials to logon and install the converter agent.

If you’re going to retire the target machine afterwards, this it does not really matter, but I leave it on the defaults > Yes.

5. Now enter the vSphere/ESX target details that you are going to create the cloned copy on. > Next.

Give the new VM a name, select which folder to place the new VM into > Next. (Note: You may get a certificate warning, if so click ignore).

7. Chose a Cluster/Host > Choose which storage to place the files into. > Next.

8. In the ‘Data to Copy’ section > Edit.

9. Here you can select the NEW sizes for the drive(s) on the cloned machine. > Next.

10. Finish.

11. Depending on the size of the VM it can take a while.

12. Now power of the original, and power on the new machine and TEST IT THOROUGHLY, when you are happy you can delete the source machine.

Resizing (Shrinking) Guest Hard Drives in vSphere 4 (and older)

The following procedure was done with VSphere4 but the process is the same in VI3. Before you start ensure that VMware Converter has been installed on the Virtual Center Server.

 

Related Articles, References, Credits, or External Links

VMware Converter ‘A file I/O Error Occurred’

VMware Converter Slow!

VMware Converter ‘Unable to Connect to the Network Share’

VMware Converter – Unable to Deploy Agent

VMware Converter Slow!

KB ID 0001584

Problem

I was P2Ving a server for a client this week. I did a ‘trial run’ just to make sure everything would be OK, and got this;

Yes, that says 13 days and 29 minutes! Suddenly doing this at 1700hrs on a Friday became a moot point! (Note: I was using VMware vCenter Converter Standalone version 6.2)

Solution

At first I assumed this was a network problem, so I moved everything onto the same Gigabit switch, and made sure all the NICs were connected at 1Gbps. Still no improvement. I then shut down as many services on the source machine as I could, still it was terribly slow 🙁

Firstly, make sure Concurrent Tasks, and Connections per Task are set to ‘Maximum’.

Then locate the converter-worker.xml file and edit it;

Usually located at “C:\ProgramData\VMware\VMware vCenter Converter Standalone

Note: ProgramData is, (by default) a hidden folder!

Locate the section, <useSsl>true</useSsl>, change it to <useSsl>false</useSsl> then save and exit the file.

Then restart the ‘VMware vCenter Converter Standalone Worker‘ service.

Boom! That’s better.

Related Articles, References, Credits, or External Links

NA

VMware Converter – Unable to Deploy Agent

KB ID 0001345

Problem

I still think P2V conversions are cool, and I’ve been doing them since version 3! It seems though every time I try and do one with the standalone converter though I get this error;

VMware vCenter Converter Standalone
Unable to complete installation/uninstallation of converter agent on ‘{target}’

Solution

I always spend five minutes messing with firewalls, checking remote registry services, credentials, and the fix is nearly always the same;

Locate VMware-Converter-Agent.exe in  C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone, copy it to the target machine, and install it manually. Then try the conversion again.

If it gets this far, your problem is solved.

Related Articles, References, Credits, or External Links

NA

Cisco – Using a Mini USB Console Cable

KB ID 0001073 

Problem

A colleague asked me if I had a USB console cable, because the switch he was working on had a failed RJ45 console port. I thought it was just the same cable that charged my phone (USB A to micro USB). But it isn’t, it’s mini USB.

I thought, that might happen to me at some point, and rather than carry yet another cable I got onto eBay and got a female micro USB to male mini USB converter for about 99p. Then all I needed to do was test it.

Solution

Use Cisco USB Console Cable on Mac OSX

1. Just plug it in and the Mac detects it without the need for drivers, (providing the other end is plugged into a device!). You may see something like the following popup, if you run VMware Fusion;

Note: if you want to find out what device it is being called by macOS, simply issue the following command;

[box]ls -ltr /dev/*usb*[/box]

2. You can then can connect directly to it (using 9600 baud as usual), with the following command (your device name in red will differ);

[box]screen /dev/tty.usbmodem1411 9600[/box]

3. Or if you use an application;

RoyalTSX

Using SecureCRT

4. And we are in.

Use Cisco USB Console Cable on Windows

Things are a little more convoluted on Windows, you need to install a driver (which involves a reboot).

1. Download the Windows Cisco USB Console Cable Driver.

2. When installed and connected to a Cisco device, you should see something like the following in device manager (devmgmt.msc).

3. Now using your preferred terminal emulation software (below I’m using PuTTY) connect using the COM port you identified above.

 

Related Articles, References, Credits, or External Links

NA