Category: VMWARE

Installing vSphere 6.0 Update Manager

vSphere Update Manager (VUM) is a tool which enabled VMWare administrators to automate and streamline process of applying updates to vSphere environment.VUM is integrated to vCenter server and offers the ability to scan and remediate ESXi hosts. In this example i used SQL server database ( for storing updates,VUM will be installed on separate Windows Server […]

via Installing vSphere 6.0 Update Manager — geekdudes

VMware Basics to Advanced

VMware Basics to Advanced

Free Vmware Vsphere training(vmware 5 and 5.5) link given below. Follow the same. Each and every chapter is clearly described by Train Signal.
Practical video is also too good.
Proud to share this.
Feel free to share your friend’s and colleague also.Lesson 01 Getting Started with VMware vSphere Training Course

Lesson 02 Lab Setup VMware vSphere

Lesson 03 Course Scenario VMware vSphere

Lesson 04 Overview of VMware vSphere

Lesson 05 Installing VMware ESXi VMware vSphere

Lesson 06 Installing vCenter VMware vSphere

Lesson 07 Installing vCenter as a Linux Appliance vCSA- VMware vSphere

Lesson 08 Using the vSphere Web Client- VMware vSphere

Lesson 09 What’s New in vSphere -VMware vSphere

Lesson 10 Navigating vSphere Using the vSphere Client-VMware vSphere

Lesson 11 vCenter Configuring Your New Virtual Infrastructure- vmware vsphere

Lesson 12 Creating and Modifying Virtual Guest Machines- vmware vsphere

Lesson 13 Installing and Configuring VMware Tools -vmware vsphere

Lesson 14 Understanding and Using Tasks, Events, and Alarms -vmware vsphere

Lesson 15 Virtual Storage 101 and Storage Terminology -vmware vsphere

Lesson 16 vSphere Storage Appliance VSA -vmware vsphere

Lesson 17 Creating a Free iSCSI SAN with OpenFiler -vmware vsphere

Lesson 18 Administering VMware ESXi Server Security -vmware vsphere

Lesson 19 vSphere Virtual Networking -vmware vsphere

Lesson 20 Using the vSphere Distributed Virtual Switch dvswitch -vmware vsphere

Lesson 21 Moving Virtual Machines with vMotion- vmware vsphere

Lesson 22 Moving Virtual Storage with svMotion- vmware vsphere

Lesson 23 Performance Optimization with Distributed Resource Scheduler DRS- vmware vsphere

Lesson 24 Implementing High Availability with VMware HA VMHA- vmware vsphere

Lesson 25 Super High Availability with VMware Fault Tolerance FT- vmware vsphere

Lesson 26 Upgrading from VMware vSphere 4 to vSphere 5- vmware vsphere

Lesson 27 vSphere Command Line Interface CLI Options -vmware vsphere

Lesson 28 vSphere Auto Deploy- vmware vsphere

Lesson 29 Storage DRS- vmware vsphere

Lesson 30 Policy driven Storage – vmware vsphere

Lesson 31 Understanding the New vSphere vRAM Pooled Pricing -vmware vsphere

Lesson 32 Network IO Control NIOC- vmware vsphere

Lesson 33 Storage IO Control SIOC -vmware vsphere

Lesson 34 ESXi Firewall- vmware vsphere

Lesson 35 VMware Data Recovery VDR 2- vmware vsphere

Lesson 36 Administering vSphere Using an iPad- vmware vs


Indradeep Kama: Distributed Resource Scheduling DRS Configurations- vmware vsphere

Advanced Storage Management– vmware vsphere

Automation Using PowerCLI- vmware vsphere

Configure and Inspect vSphere Log Files- vmware vsphere

Configuring and Using VLANs and PVLANs- vmware vsphere

Custom ESXi Installations- vmware vsphere

Getting Started with VCAP DCA Training- vmware vsphere

Managing the vSphere Distributed Switch- vmware vsphere

Managing VMware Fault Tolerance- vmware vsphere

Managing VMware High Availability- vmware vsphere

Monitoring and Troubleshooting Host and VM Performance- vmware vsphere

Monitoring and Troubleshooting Networking- vmware vsphere

Monitoring and Troubleshooting Storage- vmware vsphere

Monitoring and Troubleshooting vCenter Server and vSphere Hosts- vmware vsphere

Monitoring vSphere Performance- vmware vsphere

Next Steps- vmware vsphere

Optimizing Virtual Machines- vmware vsphere

Physical Network Connectivity- vmware vsphere

Securing Your ESXi Hosts- vmware vsphere

Storage Capacity Management- vmware vsphere

Storage Connectivity and Multipathing- vmware vsphere

Tuning vSphere Performance- vmware vsphere

Using Auto Deploy for ESXi Deployment- vmware vsphere

Using Host Profiles- vmware vsphere

Using the vSphere Management Assistant vMA- vmware vsphere

Using Update Manager- vmware vsphere

Virtual Network Management and Implementation- vmware vsphere

vmware vSphere 5.1 New Features – Course Introduction

vmware vSphere 5.1 Distributed Switch Improvements

vmware vCloud Suite 5.1 – What’s New

vCenter Server Appliance Installation

vCenter Operations Manager Foundation

Upgrading to vSphere and vCenter 5.1

How to Build a vSphere Lab Environment Updated for 5.1

vmware vSphere 5.1 Single Sign On SSO

vmware vSphere 5.1 Virtual Machine Enhancements

vmware vSphere 5.1 vMotion Enhancements

vmware vSphere Data Protection – Backup and Recovery

vmware vSphere Data Protection – Introduction and Installation

vmware vSphere Multi Hypervisor Manager MHM Lesson 15

vmware vSphere Replication – Introduction and Installation

vmware vSphere Replication – Replicating and Recovering VMs



vSphere Web Client Lesson 5

What’s New in VMware Certification as of Jan 2013 Lesson 13 vmware vsphere

Introduction to VMware Virtual SAN VSANVirtual SAN Beta Webinar

Network Virtualization Moving Beyond the Obvious VMworld 2013 Session NET7388 S

VMware Virtual SAN VSAN VMworld 2013 Session STO5391

Tuesday, April 4, 2017 —

[11:03:14 PM]Sheikvara
Posted by Sheikvara
+919840688822, +919003270444

Installing vSphere 6.0 Update Manager

vSphere Update Manager (VUM) is a tool which enabled VMWare administrators to automate and streamline process of applying updates to vSphere environment.VUM is integrated to vCenter server and offers the ability to scan and remediate ESXi hosts. In this example i used SQL server database ( for storing updates,VUM will be installed on separate Windows Server […]

via Installing vSphere 6.0 Update Manager — geekdudes

Posted by Sheikvara

+919840688822, +919003270444


How To Reset ESXi Root Password via Microsoft AD

By | Last Updated: March 13, 2017


When you’re in front of a host where the ESXi root password has been lost, how to reset an ESXi root password might be the first question you’re asking, right? A while back we have posted a way of doing it via VMware Host profiles. But not everyone has Enterprise Plus licensing which includes host profiles.

This post will teach you how to reset the ESXi root password, but there is one condition. The host is managed via vCenter server and you still have an access to your vCenter. You can gain administrative access to your ESXi host via Microsoft AD by adding the host to the AD and we’ll show you how (plus some troubleshooting tips).

If the host is not managed via vCenter then the only supported way is to reinstall your host. I know that there are other methods (with Linux boot CD) but remember that the only official way to reset the ESXi root password, according to VMware  KB1317898, is reinstalling the ESXi host.

Let’s continue with today’s post where we’ll show the steps for ESXi Password Reset via Microsoft AD. Without further wait, here are the steps:

Step 1: First, log in to your vCenter with the vSphere Web Client and Select your ESXi host >Configure > System > Authentication Services > Join Domain.

ESXi Password Reset via Microsoft AD

Enter the domain name and user credentials for your environment > click OK 

The window looks like this.

Reset password for ESXi host

Note: At this moment your host should appear in the default computer account in your AD.  You can check your Microsoft AD console on your domain controller for that. Make sure that you refresh your view.

If you’re experiencing problems, verify that you have configured correctly your DNS settings, such as Domain, preffered DNS server or Search Domains. You can find those settings by selecting your host > Configure > TCP/IP configuration > DNS tab

ESXi DNS settings

You should also make sure that on your DNS server you have created static forward AND reverse DNS records for your host. DNS can be a pain if configured wrong. A good DNS resolution is a good start on healthy vSphere setup.

NTP is also an important configuration step. ESXi should use, when possible, an external source of time.

TIP: How to configure ESXi 6.5 Network Time Protocol (NTP) via Host Client?

Let’s get back to our article where we originally discussed the possibility to reset ESXi root password via Microsoft AD.

Step 2: Go to your Domain controller and create a Global Security group called “ESX Admins” > Make a domain administrator part of this group.

ESX Admins group

Note: The name of this group can be changed (for security purposes). I’ll show you at the end of the post….

Step 3: Login directly the host using vSphere client or vSphere Host client and use the domain admin account for that. Then go to the Users TAB > Right click > Edit > Check the box “Change password” and change the local root password.

Change ESXi lost root password o

We have successfully changed a root password.

Use different name than the default “ESX Admins”

For some environments yo might need to use a different name than the default one – “ESX Admins”. To use different group name, before joining the host to a domain, go to your Microsoft AD and Create the group with the name you want. Then login to your vCenter server via vSphere Web client > Select your host > Configure < Advanced system Settings > Edit.

ESX Admins group can be changed ESXi security settings

Enter this to the search box to filter:


Change the name.


It may happen that the ESX Admins group does not show up through the Permissions TAB on the ESXi host. I had an issue on one fo my lab hosts. I had to add this permission manually. Right-click the white space > Add > select your domain from the drop-down menu >  Seek for the group in your AD.

How to reset ESXi root password via Microsoft AD

I have also recorded a short video to document the process. Best to watch in Full Screen and HD (1080p). Thanks for watching.

Check more articles from ESX Virtualization:

Reference Link –

Posted by Sheikvara


Vmware 6.5 Services by Ranjna

Service Name

Service Name Description


 VMware Image Builder Manager


 VMware Component Manager


 VMware vCenter Server


 VMware vSphere Profile-Driven Storage Service


 VMware Appliance Management Service


 VMware Appliance Monitoring Service


 VMware HTTP Reverse Proxy


 VMware vAPI Endpoint


 Likewise Service Manager


 VMware Authentication Framework


 VMware vService Manager


 VMware Service Lifecycle Manager API


 VMware Performance Charts


 VMware Update Manager


 VMware Service Lifecycle Manager


 VMware VSAN Health Service


 VMware vSphere Web Client


 VMware Postgres


 VMware ESX Agent Manager


 VMware vSphere Authentication Proxy


 VMware Message Bus Configuration Service


 VMware vCenter High Availability


 VMware vSphere Client


 VMware Content Library Service


 VMware Service Control Agent


 VMware vSphere ESXi Dump Collector


 VMware vCenter-Services


 VMware vSphere Auto Deploy Waiter

Posted by Sheikvara +919840688822


VMware vCenter Server 6.5 HA in a easy way

As every administrator knows, VMware vCenter Server is a great tool for managing ESXi because it allows you to manage multiple servers and VMs from a single console application. However, vCenter isn’t infallible; if the administrator doesn’t have the foresight to restrict vCenter to a specific number of hosts, she will be faced with a long day of logging in to each host trying to locate the vCenter in a large cluster of hosts.

Fortunately, VMware recognized this shortcoming and developed a new product to address it. VCenter Server High Availability (HA) requires vSphere Appliance 6.5 and the hosts in the cluster must be ESXi 5.5 or later. VCenter also needs to be self-managed; basically, vCenter needs to be in the cluster it’s managing.

Before deploying vCenter HA, it’s important to understand how it works. When the vCenter HA feature is enabled, an additional vCenter Server instance is created on another host akin to a hot standby. Another clone functions as a witness for the first two vCenters. In the event of a failure, the witness decides which vCenter should be live, preventing split brain scenarios.

Obviously, such a setup is sensitive to network issues. The maximum acceptable network delay is 10 milliseconds. Therefore, a second private network is used to communicate between vCenter HA-enabled nodes. Each host needs to have an additional network port group. This port group manages the traffic for the vCenter HA replication traffic. This is used as a private heartbeat network.

Prior to setup, the administrator needs to set up a standard network port group specifically for the heartbeat network on each host. I’d advise keeping the traffic on an isolated network to avoid potential latency/congestion issues. This network must be different to the one that the vCenter normally listens on. As an example, I am using the network range 172.16.0.x for the heartbeat.

To set up a fully functioning vCenter HA setup, you should have a minimum of three hosts because not only is there a full live clone of vCenter, there’s also a witness vCenter that works to prevent split-brain issues.

Setting up vCenter High Availability

To set up vCenter HA, start by opening the vSphere Web Client using your administrator account, navigate to the top level of vCenter and over to the Configure tab, as shown in Figure A.

Configuring vCenter HA.
Figure A. Configuring vCenter HA.

Navigate to the vCenter HA link in the left hand menu. It will initially inform you that vCenter HA is not configured, as shown in Figure B.

VCenter HA topology.
Figure B. VCenter HA topology.

To configure, click Configure vCenter HA on the right side. This will present you with two options, basic and advanced, as shown in Figure C. Selecting the basic settings will do all of the hard work for you, including cloning vCenter. You can change options from the standardized default later if necessary.

VCenter HA configuration options.
Figure C. Selecting a vCenter HA configuration.

Click Next to get to the next page which will ask for IP details for the new heartbeat network interface card. Remember, this needs to be a different network than the standard public interface of the appliance. Don’t forget to select the appropriate vSwitch, which you should have created earlier.

On the next page, you will need to configure additional addresses for the Passive and Witness nodes, as shown in Figure D, and then click Next.

Selecting node IP settings.
Figure D. Selecting IP settings for Passive and Witness nodes.

On the last page you’ll see an overview of the deployment configuration. If necessary, you can edit details pertaining to the Passive and Witness nodes — such as location — by clicking Edit on the right side. The reason you see warnings in Figure E is because I’m only using one shared storage data store.

Deployment configuration overview.
Figure E. VCenter HA deployment configuration overview.

Finally, click Finish and the deployment will begin. Be aware that it may take a significant amount of time to deploy and configure the setup.

Something to keep in mind when using vCenter HA: When doing maintenance on the vCenter network, you should suspend the vCenter HA functionality. To do so, navigate to the vCenter HA screen and click Edit. This will present you with a number of options and descriptions of what each option does.

Assuming you’re working in a nonproduction lab environment, you can even initiate failover by clicking Initiate Failover. Once the failover is finished, you can log in to the vCenter Server just as before, but on the alternative vCenter.

This new functionality presents a long-desired utility that addresses the old issue of having HA for the vCenter itself. It wasn’t possible before due to the fact that fault tolerance only ever supported a single CPU at the time.



+919840688822, +919003270444

VMware vSphere Update Manager in a easy Way

VMware vSphere Update Manager is patching software included in vSphere that simplifies the patching process for ESX and ESXi hosts, VMs, virtual appliances and VMware Tools. The latest version of vSphere Update Manager improves flexibility by allowing administrators to control every step of the patching process — with no downtime.

With vSphere Update Manager (VUM), you can define the level to which you want to patch your clusters and the level to which the patching, updating and upgrading of your hosts can be automated. Before starting the patching process, you must evacuate all VMs to another host within a vSphere cluster; this host will then enter maintenance mode. You can use vMotion to move VMs back to the host you intend to patch once you have rebooted it and removed it from maintenance mode. This process can be quite lengthy if you perform it manually, but VUM can save you time and stress by automating the process using its user interface rather than scripting.

VUM is traditionally installed on a separate VM in a separate database. However, VUM is built into the latest version of vSphere — specifically into vCenter Server Appliance (vCSA) 6.5, which runs on Photon OS — and VUM shares the schema of the vCenter PostgreSQL database but uses its own PostgreSQL database instance. This is a first, and gives the administrator the option of installing an All-in-One vCenter.

The VUM remediation wizard allows you to save any customizations you may have made during the walkthrough as default cluster remediation options, shown in Figure A.

VUM remediation wizard
Figure A. Saving default cluster remediation options.

You can also use VUM to selectively patch components within hosts. Let’s say you have a cluster of servers that have the exact same storage controller, which needs an update. The process of updating that controller would look something like this: First, update the driver through the VUM to the patch repository. Next, create the host extension by selecting “Host Extension” under Baseline type, shown in Figure B.

VUM Create a host extension.
Figure B. Create a host extension with VUM.

Finally, attach this baseline to the host as seen in Figure C.

Patch components with VUM
Figure C. Attach Baseline or Baseline Group.

That’s it — your cluster is ready to be patched with the updated driver. You can do that by clicking the Remediate button.

Thanks to the simplification of vCSA, vSphere Update Manager is now more efficient than ever.

VSphere 6.5 also brings graphical utility, allowing users to create personalized images. This process lets you slip-stream the latest drivers from your hardware manufacturer. These personalized images can then be deployed to certain hosts or clusters during the upgrade process via VUM. You can also export those images as ISO files, which can be used by stateless hosts — hosts configured with the Autodeploy function — to boot from images through local network.



+919840688822, +919003270444