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

Cannot Open a Console Session in the VMware VI Client on Windows 8

KB ID 0000677 

Problem

Mostly my conversion to Windows 8 has been pretty painless, the only thing that wont work is the VMware VI client cant open a console session to the VMs on my ESX server.

Error
The VMRC console has disconencted…attempting to reconnect

This happens because the IE10 that comes with Windows 8 does NOT LIKE the requests the VI client is sending to the Internet Explorer plug-in.

Update 08/03/13 – This problem has now been fixed! Download the latest 5.1 version of the VI client. (see screenshot).

Solution

Work-Around 1 Use VMware workstation (Note: scroll down for a permanent fix)

Until either Microsoft or VMware change something then we are stuck! however there is a work around. if you have VMware Workstation (download the trial it will keep you ticking over till the problem is fixed!).

1. Launch VMware workstation > File > Connect to Server > Enter your ESX/vCenter server details > Connect.

Note: You may need to accept the certificate warning if you are using self signed certificates.

2. Now you can open a console session to your virtual machines.

Work-Around 2 Use VMware Guest Console

Download and run VMware Guest Console > Connect to to a host or vCenter, and you can access the guest machines consoles from there.

Permanent Fix

Sorry, the only way to fix this (at time of writing) is to upgrade to vSphere 5.1 AND install the 5.1 version of the vSphere client. (You can’t point the 5.1 client at a 5.0 host, it automatically launches the 5.0 version of the VI client).

Note: You will need to update vCenter to 5.1 as well for that to work!

Problem Resolved

Update to the latest VI client, and the problem will cease.

 

Related Articles, References, Credits, or External Links

NA

vSphere Web Client – Options Greyed Out (Cannot install Client Integration Plug-in)

KB ID 0001064

Problem

While working on the vSphere Web Client in Google Chrome, I was unable to ‘Open Console’, the option was on the right click menu, but disappeared and was then greyed out after a second or so.

Essentially this happens because the plug-in has either not been installed, (from the login page) or a pop-up blocker is stopping the plug-in working.

Solution

1. With Chrome there’s an extra hoop to jump though, the plug-in uses NPAPI, and Chrome disabled that beginning with version 42. To enable it open a new tab and navigate to;

[box]chrome://flags/#enable-npapi[/box]

In the NPAPI section select ‘Enable’.

2. Click ‘Relaunch Now’.

3. At this point you will be able to install the Client Integration Plug-in.

4. Now you need to make sure the plug-in will run, click the plug-in warning and select ‘Always allow plug-ins on localhost’, refresh the page.

5. You can now tick the box to login with Windows session authentication.

6. The first time you try and launch something the pop-up blocker will suppress it you will need to disable the pop-up blocker for this site.

7. The vSphere Web Client should now perform correctly in Google Chrome.

 

Related Articles, References, Credits, or External Links

NA

Cisco ASA – Java RDP Error – Connection Exception Wrong modulus size! Expected64 +8got:264

KB ID 0000452

Problem

Seen while attempting to connect to to a Windows machine via the RDP plug in on a Cisco ASA firewall.

Error:
properJavaRDP error
Connection Exception Wrong modulus size! Expected64 +8got:264

Solution

1. I’ve seen some posts indicating that this can be caused by the version of Java that’s installed, however in my case that was NOT the problem.

2. Connect to the ASDM of the ASA firewall > Configuration > Clientless SSL VPN Access > Portal > Client Server Plug-ins. Ensure your RDP plug in is up to date, download and import the latest one (Cisco CCO account and valid support agreement required).

Note: At time of writing the latest is rdp2-plugin.090211.jar (released 14/08/09).

3. Ensure that the bookmark you are using is set to use rdp2 (not rdp). Under Portal > Bookmarks > Your bookmark list > Edit.

4. Your RDP session should now connect.

 

Related Articles, References, Credits, or External Links

NA