Showing posts with label VMware. Show all posts
Showing posts with label VMware. Show all posts

Wednesday, 9 January 2019

How to change VMware vSphere Update Manager’s IP Address?

Or, Re-register update manager server with vCenter Server
Or, Re-register update manager with the vCenter server after changing the IP address of update manager
Or, How to use update manager utility to re-register update manager with the vCenter server?

Descriptions:  You might need to re-register the Update Manager with vCenter Server in certain situations, for example when the IP address of vCenter Server or Update Manager changes. You do not need to worry, because it may not take more than 5 minutes if you do it correctly with the correct approach.

1. Stop the Update Manager service
2. vSphere vCenter Server administrator credentials

Error message reference:
The similar error may be reported when Update Manager has not been reconfigured after changing the vCenter Server IP address or Update manager has not been re-registered in the vCenter server after changing the IP address of Update Manager

There was an error connecting to VMware vSphere Update Manager - [x.x.x.x:443]. The request failed because of a connection failure. (Unable to connect to the remote server)


There was an error connecting to VMware vSphere vCenter Server - [x.x.x.x:443]. The request failed because of a connection failure. (Unable to connect to the remote server)

Steps: Re-register update manager with the vCenter server

1. Login to Update Manager Server
2. Go to the update manager’s installation directory path C:\Program Files(x86)\VMware\Infrastructure\Update Manager
3. Right Click on VMwareUpdateManagerUtility.exe and Choose Run as Administrator
4. Provide all the details as requested e.g. IP Address, User Name, and Password of vCenter Server
5. Click on Login

6. In the Options pane of the Update Manager Utility, click on Re-register to vCenter Server.
7. In the Configurations pane, provide the connection and authentication details as requested e.g. IP Address, User Name, and Password of vCenter Server
8. Click Apply

9. Finally, the confirmation pop-up will appear, and you would be requested to restart the Update Manager Service
10. Click OK, and Close the Utility Windows

Restart the Update Manager services, and the Update Manager server would be re-registered now.

Cheers, Please write me back if you have any query or feedback.

Wednesday, 26 December 2018

What is EVC in VMware, and how to enable it?

Or, What is EVC in VMware?
Or, How to enabled EVC in VMware?

What is EVC in VMware?
EVC stands for Enhanced vMotion Compatibility. It is used for enabling hardware compatibility between different hardware types of ESXi hosts so that we can easily migrate Virtual machines from one to another host even if the hardware of ESXi hosts are different.

If EVC is not enabled, you can't migrate a Virtual machine to an ESXi host which is having different hardware version with compare to another ESXi host.

Simply we can say that EVC ensures that all hosts in a cluster are VMotion compatible, even if they are not from the same hardware category.

How to enable EVC (Enhanced vMotion Compatibility) in VMware ESXi Cluster?
Few easy steps and you are done with EVC configuration for your ESXi cluster.

IMP Note: Before enabling EVC mode, you must shutdown your all VMs of that particular ESXi host on which you are going to enable EVC mode and migrate VMs to another ESXi host/cluster if possible.

- Log in to vCenter Server by using VMware vSphere Client
- Right Click on your Virtual Datacentre Cluster
- Go to Edit Settings
- Select VMware EVC in the left Panel
- Click on Change button to edit the EVC settings
- Select appropriate EVC settings for your Virtual Environment from the drop-down list...
- If validation succeeded with your desired CPU selection for EVC, you should be happy...
- Click OK twice to EVC mode dialog box and cluster setting dialog box...
- Power on your ESXi host.
- Migrate VMs from another host to this host to check if things are done correctly

You are done now... cheers…

Please write me back if you have any query or feedback.

Sunday, 7 May 2017

How to update vCenter server appliance

Or, Update vCenter appliance 6.0 update 3a to 6.0 update 3b
Or, Upgrading vCenter server appliance

Descriptions: Updating vCenter server appliance is very easy if you are on vCenter server appliance version 6.0 and above. In vCenter server appliance you have two consoles one is vCenter server management console that you know as vSphere web client and another is vCenter server maintenance console that is also knows as root console.

To perform update of vCenter server appliance, you need to login with root credentials on maintenance or root console or Appliance Management User Interface of vCenter server appliance.

1. Root credentials of vCenter server appliance
2. At least 1 hrs of downtime of vCenter server
3. Basic knowledge of vCenter components
4. Internet connectivity on vCenter server appliance (required when checking for update online)
5. Appliance management user interface URL accessible https://<FQDN-or-IP>:5480

Steps: updating vCenter server appliance

Open Maintenance console of vCenter server (https://<FQDN-or-IP>:5480) > Login with root credentials

Go to Update option

Click on Check Updates (select check URL)

Wait for update check to be completed > Once updates are visible under Available Updates section > Click on Install Updates

Accept the license terms and condition > Click on Install

Wait for installation to be completed

Upon successful completion of updates installation, click OK

Now the reboot of vCenter server appliance will be initiated > Wait for reboot to be completed

Login back to maintenance console and verify the Update Version, it must have changed to the latest selected version you had selected while performing update

Cheers, Please write me back if you have any query or feedback.

Saturday, 22 April 2017

VMware vSphere Update Manager installation and integration with vCenter appliance

Or, vCenter appliance integration with update manager
Or, Update manager with vCenter appliance
Or, How to use update manager with vCenter appliance
Or, How to install update manager
Or, Enabling Update Manger client plugin for vSphere traditional client
Or, Enabling Update Manger client plugin for vSphere web client

Description: Friends, if you were using update manager on vCenter server with windows server operating system platform and now want to use it with vCenter appliance, or if you have installed vCenter appliance and now want to use update manager with this appliance, you may get all your answers here.

 Scenario: I have recently migrated from windows based vCenter server to vCenter appliance. Now I want to use Update Manager with this vCenter appliance but the challenge is, update manager cant’t be installed on vCenter appliance or Linux based OS, it can be installed on Windows based OS only.

There are two stages in this article, in Stage-1 we will see how to install update manager and integration of update manager with vCenter appliance. In Stage-2, we will be enabling update manager plugin for vSphere web client and vCenter traditional client.

Enabling client plugin on vSphere web client and vSphere traditional client is must because only after this, you would be able to get the Update Manager icon in your vSphere clients.

So now, I have my vCenter server running on vCenter appliance and going to install update manager on windows based operating system and while the installation of Update Manager, I will integrate it with vCenter appliance. Latter in stage-2, I will be enabling Update manager plugin with my vCenter server appliance using vSphere web client and vSphere traditional client.

Stage-1/Steps:  Installation and integration of Update Manager with vCenter appliance

Download the VMware vCenter Server ISO for Windows from MyVmware download portal ( In my case its, VMware vCenter Server 6.0 3a and module for Windows )

Mount the ISO on the Windows Machine (I am having Windows Server 2012 R2)

Right Click on Autorun executable file > Choose Run ad administrator

Click on Install

Wait for the Installation of SQL Express completion

Click Next

Accept the license agreement terms > Click Next

Choose Download updates from default source immediately after installation > Click Next

Fill in all the required details/credentials of vCenter appliance server > Click Next (This is where you are integrating Update Manager with your existing vCenter server appliance)

Give IP or Name of the Update Manager server here > Click Next

If you have proxy server, fill in all the details or leave these fields blank > Click Next

Configure the Installation and Patch Repository directory > Click Next

Click on Install to proceed with the Installation

Wait for the installation to be completed

Click Finish

Now you are done with installation and integration of update manager with vCenter server appliance

Stage-2/Steps:  Enabling Update Manger client plugin for vSphere web client

Login to vSphere Web Client console > Go to Client Plug-ins > Click on Check for New plug-ins > VMware vSphere Update Manager plug-in will be installed

To be able to see the VMware vSphere Update Manager in vSphere Web Client you must have the View Compliance Status privilege.

Log off from the vSphere Web client console and login again > Go to admin Home page > you will be able to see Update Manager icon under monitoring section of the home page.

Steps: Enabling Update Manger client plugin for vSphere traditional client
Login to vSphere traditional client > Go to Plug-ins menu > Click on Manage Plug-ins

See for the Available Plug-ins > Select VMware vSphere Update Manager > Click on Download and Install hyperlink

Click on OK when prompted

Click on Next

Click on I accept the terms in the license agreement > Click Next

Click on Install

Click on Finish

It’s all done now.

Cheers, please write me back if you have any query or feedback.

Sunday, 16 April 2017

vCenter server appliance AD integration and SSO configurations

Or, How integrate vCenter server appliance 6.0 with Active Directory?
Or, How to configure SSO on vCenter server appliance 6.0?
Or, AD Integration of vCenter server appliance

Descriptions: To be able to sign-in in vCenter server with AD account or to able to use SSO you must enable AD integration with vCenter server and enable SSO. There has been multiple articles where it’s confusing to understand what is difference between SSO and AD integration of vCenter server and what you actually need to be able to use your AD credentials for login in to the vCenter server…

Friends, so far as per my understanding, the difference between AD integration and SSO configuration is as below:

AD integration is just joining your vCenter server appliance in AD domain, as you do for windows machines (joining a workgroup windows machine in domain).

SSO (Single Sign On) configuration is adding your domain in Identify Sources section under SSO configuration of vCenter server to synchronize all AD users in vCenter Users and Group section so that you can add these AD users latter in vCenter Server’s different roles to grant them access of vCenter server.

This way, you can use your single account for login in your windows machine and vCenter server. This where the SSO requirements meets.

Steps: AD integration of vCenter server

Login to vSphere web console with administrator@vsphere.local account > Go to Systems Configurations

Click on Nodes under System Configuration> Select the vCenter Server appearing under Nodes

Click on Manage > Settings > Active Directory

Click on Join

Provide all the required details as reference shown in the below screenshot and Click OK.  As soon as you click OK, the virtual appliance will be reboot to take the changes in effect.
To know more what details to provide in which field, refer the below notes:
Domain : Active Directory domain name, for example, Do not provide an IP address in this field.
Organizational unit: The full OU LDAP FQDN, for example, OU=Engineering,DC=TechiesSphere,DC=com. Use this field only if you are familiar with LDAP.
User name: User name in User Principal Name (UPN) format, for example, Down-level login name format, for example, DOMAIN\UserName, is unsupported.
Password: Password of the user.

After reboot, when you will come back to this page again, you would be able to see your domain name, Join button is grayed out, and Leave button is available.

Steps: SSO (Single Sign On) Configuration

Login to vSphere Web Client > Go to Administration

Go to Configuration > Identity Sources > Click on + sign

Select Active Directory (Integrated Windows Authentication) > Provide other required details > OK

To verify if the configuration is completed, Go to Users and Groups > Users > Under Domain section, click on Down arrow to see if your domain name is appearing there > If its appearing there means the configurations is done successfully.

Now you can add any AD users in any vSphere Roles to enable them to login in vSphere with AD credentials.

Cheers, Please write me back if you have any query or feedback.

Saturday, 15 April 2017

VMSA-2017-0006 vulnerability remediation for ESXi hosts

Or, VMware ESXi 6.0 vulnerability VMSA-2017-0006 remediation
Or, VMware ESXi vulnerability VMSA-2017-0006 remediation planning and execution

Descriptions: On Mar 28th 2017 US-CERT notified it’s users about this vulnerability with VMware ESXi hosts. The remediation of this vulnerability is to update the ESXi hosts with the patch recommended by VMware. In my case the recommended patch was as my VMware ESXi servers are running on version 6.0 U2.

Scenario: As I am using ESXi Server version 6.0 U2, the recommended patches details are as below as per the reported vulnerability security advisory reference KB.

You have to scroll down the page till the end to see these patches details as shown in the below screenshot.

Remediation Procedure/Steps:

As shown and explained in the above screenshot, please go to the VMware KB Or,

It should be containing following information as highlighted in red in the below screenshot.

Now download the required patch from VMware Site (in my case it’s the below one):

This is the same URL which was given in security advisory (can see the very first screenshot in this article for reference).

You must be logged-in in the “My VMware” portal to be able to access this patch download windows.

The download page should be looking like below:

After downloading the path file will be appearing like below in a .Zip file format.

Use this file to update the patches on all affected VMware ESXi servers. You can use either manual method of installing this patch on all affected ESXi servers or you can use the easiest method of doing it by using VMware vSphere update manager.

I am a lazy administrator so don’t expect me to do this patching activity manually. Yes, I used the easiest method of doing it by using Update manager.

I have posted all the steps in my another article How to use Update Manager for patch installation on ESXi servers? . 

You can refer this article if you want to use Update manager for installing these updates on your ESXi hosts.

Cheers, Please write me back if you have any query or feedback on this.