VMware ESXi and vSphere Cluster Management

Install and Configure the VMware Client Integration Plug-in

Learn how to install, activate, verify, troubleshoot, and safely replace the legacy VMware Client Integration Plug-in for browser-based vSphere administration.

The VMware Client Integration Plug-in (CIP) is a local software component for older browser-based VMware management clients. It connects the legacy vSphere Web Client to capabilities on the administrator's workstation, such as launching a virtual-machine console, selecting local installation media, and transferring files.

This guide applies to legacy VMware environments. Modern vSphere deployments generally use the HTML5-based vSphere Client and VMware Remote Console (VMRC), so they normally do not require a browser plug-in.

What the Client Integration Plug-in Does

ESXi is VMware's bare-metal hypervisor. It runs virtual machines directly on physical servers. vCenter Server is the centralized management platform for ESXi hosts, clusters, datastores, and virtual machines. A vSphere Client is the management interface used to administer those resources.

Older vSphere releases provided a browser-based vSphere Web Client that depended on CIP for operations requiring access to the local workstation. A Remote Console is an interactive display, keyboard, and mouse session for a virtual machine. CIP helped the browser launch that console and connect it to the selected VM.

Function	What It Enables	Example Administrative Task
Remote console launch	Hands off from the web client to an interactive VM console.	Open a VM console and use its keyboard and mouse.
Local media mounting	Makes an ISO image or local CD/DVD source available to a guest VM.	Attach a workstation ISO to a VM for operating-system installation.
File transfer	Connects browser actions with files on the administrator's computer and VMware-managed storage.	Upload an ISO image from the workstation to a datastore.

A datastore is storage used by ESXi for virtual-machine files, ISO images, and other VM-related data. CIP does not itself provide storage permissions. Your vSphere account must still have the privileges required to browse, upload, or modify datastore contents.

Compatibility and Lifecycle Considerations

CIP was associated primarily with the legacy vSphere Web Client used with older vSphere releases, including environments in the vSphere 5.x and 6.x generations. Exact support depended on the particular vCenter Server or ESXi release, client build, workstation operating system, and browser. Always use the compatibility information for the release being administered.

Environment Type	Client Integration Plug-in Status	Recommended Approach
Legacy vSphere Web Client, commonly vSphere 5.x or 6.x	May require CIP for console, local-media, and workstation file functions.	Use the plug-in version supplied by the matching management interface in a controlled, supported legacy workstation.
Modern HTML5-based vSphere Client	Generally does not require a browser plug-in.	Use the HTML5 client and the supported console workflow for the installed vSphere release.
Current browser or operating system accessing a legacy client	May block NPAPI-style or other obsolete browser integration technologies.	Do not weaken security controls on a production workstation. Use a supported legacy administration system or a current console alternative.
Production administration	Legacy plug-in use introduces compatibility and security concerns.	Prefer VMware-supported current clients and VMware Remote Console (VMRC) where available.

Modern browsers frequently disable or remove the plug-in interfaces used by older VMware clients. Current operating systems may also reject old installers, certificates, or browser add-ons. If CIP cannot be used, a supported standalone VMware Remote Console (VMRC) installation is commonly the preferred alternative for console access. Use the current VMware-supported upload and media-management methods for file operations.

Pre-Installation Requirements

Identify the VMware release and whether you are using the legacy vSphere Web Client or the modern HTML5 client.
Use a workstation operating system and browser listed as supported for that VMware release. Legacy combinations commonly included supported Windows versions such as Windows 7, Windows 8.1, or Windows 10 with Internet Explorer 10 or 11, and in some releases supported versions of Firefox, Chrome, or macOS browsers. These are examples, not a universal support list; verify the release-specific compatibility matrix.
Have local permission to install software. Depending on workstation policy, the installer may require an authorized local administrator or an elevation through User Account Control (UAC).
Have network access from the workstation to the vCenter Server or directly to the ESXi host being managed. Console and file operations can fail if the browser can reach the login page but cannot reach the required management endpoint.
Know the correct VMware management address and sign in to the appropriate web client before obtaining CIP.
Allow required browser pop-ups and download prompts for the VMware management site.
Be prepared to review certificate warnings according to organizational policy. Do not blindly bypass certificate validation on an untrusted network.
Check whether the browser requires explicit permission to run an add-on or access a trusted site.

Obtain the Correct Installer

Open the legacy VMware web client and sign in to vCenter Server or the ESXi host. The client commonly displays a Client Integration Plug-in download prompt when you first select an action that needs local integration, such as launching a console or uploading a local file.

Sign in to the appropriate legacy web client.
Select a virtual machine and choose its console-launch action, or open a datastore and choose an upload action.
When the client reports that CIP is missing, select the download or installation link shown in the prompt.
Save the installer to a known local folder rather than running an unexpected file from an untrusted source.
Where possible, use the installer presented by the same VMware management interface and version that you will use. Mixing plug-in versions from unrelated vSphere releases can cause detection or compatibility problems.

Browser security may block the download, hide a download notification, or prevent a new window from opening. Allow the management site's download or pop-up only when the site is known and approved.

Install CIP on the Workstation

Close all browser windows that use the VMware web client. Closing them prevents the installer from replacing files that are currently in use.
Locate the downloaded installer and run it. If required by workstation policy, use an authorized administrator account or approve the UAC elevation prompt.
Review the publisher and security information. Continue only when the installer is the expected VMware package approved for your environment.
Accept the license or installation terms presented by the installer.
Choose the default installation options unless your organization's deployment procedure specifies another location.
Allow the installer to copy the integration component and complete registration with the workstation.
Finish the installation. Restart the browser so it can load the new component.
Restart the workstation only when the installer, endpoint policy, or troubleshooting procedure requires it.

A publisher-verification message or UAC confirmation is a workstation security control, not a vSphere configuration step. If the publisher cannot be verified, stop and validate the installer through your normal software-approval process.

Activate the Browser Component

A browser add-on or plug-in is a browser-integrated component that extends what a web page can do. Installing CIP does not guarantee that the browser will permit it to run.

Reopen the legacy browser and browse to the VMware management URL.
If the browser displays an add-on bar, permission prompt, or run-component notification, allow the VMware integration component for the approved management site.
Open the browser's add-on management view and confirm that the VMware integration component is enabled rather than disabled.
If the legacy browser uses security zones, add the approved VMware management URL to Trusted Sites only when required by the release and permitted by security policy.
If the browser uses compatibility settings for older web applications, apply the documented compatibility configuration for that VMware release.
Allow pop-ups for the VMware management site when console launch opens a separate window or application handoff.

Trusted Sites is a browser security-zone configuration used by some legacy browsers to permit functionality from approved management sites. It should not be used as a general method for making unknown sites trusted.

Verify the Installation

Test a virtual-machine console

Sign in to the legacy VMware web client.
Select a powered-on or powered-off virtual machine for which you have console privileges.
Choose the console-launch action.
If prompted, allow the browser to run CIP or permit the console handoff.
Confirm that a console window or supported console application opens.
Click inside the console and verify that keyboard and mouse input reaches the guest.

A successful test normally produces a console window or VMRC handoff instead of another installation prompt. A blank window, repeated prompt, or no response indicates that browser activation, pop-ups, certificates, networking, or version compatibility still needs attention.

Test a datastore upload

Browse to a datastore through the management client. If needed, review browsing VMFS datastores.
Choose the upload action.
Use the local file picker to select a small test ISO or other approved file on the workstation.
Monitor the upload until it reports completion.
Refresh the datastore contents and confirm that the file appears.

Successful local-file integration means the client can open a workstation file picker and complete the transfer. A successful upload still depends on datastore permissions, available storage, and network connectivity.

Test local media attachment

Open the virtual machine hardware settings, such as the workflow described in editing virtual machine settings.
Select the VM's CD/DVD device.
Choose the local media or ISO source offered by the legacy interface.
Connect the device and power on or restart the VM when appropriate.
Confirm from the guest operating system or boot screen that the media is visible.

Local media mounting means making an ISO image, CD/DVD drive, or other workstation media available to a guest VM. The operation can be slower than using an ISO already stored on a datastore because the data must cross the management connection.

Uninstall and Reinstall CIP

Remove CIP when the installation is damaged, the version is incompatible with the management client, or a clean replacement is required. Do not uninstall a working component from a shared administrative workstation without checking which legacy environments depend on it.

Close every browser window and any VMware console process.
Open the workstation's software management interface.
Find the VMware Client Integration Plug-in and select the uninstall or remove action.
Approve administrator prompts and complete the removal.
Restart the workstation if requested, or at minimum restart all affected browser processes.
Sign in to the intended VMware web client and download the installer it supplies.
Install the intended version, reopen the browser, enable the component, and repeat the console and file-operation tests.

If reinstalling does not help, remove stale disabled browser add-ons and clear cached components associated with the legacy VMware client according to the browser and operating-system procedures for that workstation. Then repeat the installation with all browser processes closed. Do not delete unrelated browser data or system files without an approved procedure.

Common Installation and Browser Issues

Symptom	Likely Cause	Resolution
The web client repeatedly asks to install CIP.	The browser was not restarted; the add-on is disabled; the version is incompatible; or the browser cannot run the plug-in technology.	Restart the browser, confirm the add-on is enabled, then remove and reinstall the matching version. Use a supported legacy browser only in an approved environment, or use a current console alternative.
The virtual-machine console does not open.	Pop-up blocking, a disabled component, a certificate or trusted-site interruption, or missing network access to vCenter Server or ESXi.	Allow approved pop-ups, review add-on and security prompts, validate trusted-site and certificate handling according to policy, and test DNS and network access to the management endpoint.
Datastore upload or local-file selection fails.	CIP is inactive, the browser cannot invoke local integration, the account lacks datastore permissions, or the file cannot be read.	Confirm installation and activation, test with a small readable file, verify browse and upload privileges, and use a supported alternative upload method when necessary.
Installation fails or asks for administrator credentials.	The user lacks local installation rights, endpoint security blocks the installer, or a previous installation is incomplete.	Use an authorized administrator account or request endpoint support. Follow policy for allowing the signed installer, then remove prior versions and retry with browsers closed.
The console opens but keyboard or mouse input does not work.	The console window has not captured input, the handoff is incomplete, or the console component is incompatible.	Click inside the console, verify the correct console application is installed, restart the browser, and use VMRC or another supported console method if the legacy handoff remains unreliable.

Security and Operational Guidance

Limit legacy plug-in use to a controlled administrative workstation or isolated lab system.
Do not use obsolete browsers or unsupported operating systems for general web browsing, email, or unrelated administration.
Keep the workstation protected with approved endpoint security controls and restrict access to trusted VMware management sites.
Use least-privilege vSphere accounts. CIP does not bypass permissions, and console or datastore actions remain subject to vCenter Server or ESXi authorization.
Prefer the modern HTML5-based vSphere Client and VMware-supported standalone console tools for production administration.
Plan migration away from browser plug-ins. A successful legacy installation does not make an obsolete browser technology secure or supported indefinitely.

Exam-Relevant Notes

CIP is a client-side workstation component, not an ESXi host package and not a VM guest component.
Its classic purpose is to enable browser-to-workstation integration: remote-console launch, local media mounting, and local file transfer.
Installing the component and enabling the browser add-on are separate steps.
Modern HTML5 vSphere clients generally do not require CIP.
Console launch can fail even when CIP is installed if pop-ups, certificates, browser permissions, network paths, or vSphere privileges are incorrect.
VMware Remote Console is a common supported alternative when browser plug-ins are unavailable.