Command to get the ESXi host information from a running VM

Posted on Updated on


Not able to find the VM in the vCenter/inventory? here is a way, there is a Command to get the ESXi host information from a running VM.

To get ESXi host name:

C:\>”C:\Program Files\VMware\Vmware Tools\vmtoolsd.exe” –cmd “info-get guestinfo.hypervisor.hostname”

To get the ESXi Build details:

C:\>”C:\Program Files\VMware\Vmware Tools\vmtoolsd.exe” –cmd “info-get guestinfo.hypervisor.build”

Advertisements

How to cancel a hang task in vCenter or ESXi host?

Posted on Updated on


Sometime we may need to cancel an hung task like active vmotion/backup which may show as disabled from the vSphere client.

  1. First check if there is an active task running for the VM in the Task and Events Tab.
  2. Log in to ESXi host via SSH (using e.g. putty). If the SSH service is not running on ESXi host, please enable it.
  3. Run ps command. use grep e.g. ps | grep VM_name
  4. Kill the parent process by running the command kill id_parent e.g. kill 859467
  5. The hang task should be canceled now and will reflect in the Tasks and Events in the vCenter.

 

Zerto Certified Professional Training

Posted on Updated on


zcp_badge_red_360Are you a Master of Disaster? Join the ranks of masters worldwide who have taken our Zerto Certified Professional (ZCP) training and are now using Zerto to minimize data loss and maximize uptime. Zerto has just released our business continuity certification, ZCP Basic for Zerto Virtual Replication (ZVR) 4.5, the latest version of Zerto’s award-winning business continuity software.

ZCP Basic 4.5 is a free introductory technical course that is self-paced and easily accessible online via the MyZerto platform. If you don’t already have an account, sign-up for one here and then log-in to start your training.

The latest ZCP course includes training on some of our exciting new features such as Journal File-Level Restore, ZVR 4.5’s game-changing feature that lets you recover specific folders or simply one single file that was accidentally deleted.

If you are a newbie though, don’t worry, ZCP 4.5 still covers all the tools you need to reach Master of Disaster status, including: ZVR installation, configuration, and key recovery operations such as test & live failovers.

The e-learning in ZCP Basic 4.5 is estimated to take around 1 hour and 15 minutes, and there is a certification exam at the end. Passing the exam with 75% or higher awards you the ZCP Basic business continuity certification—and officially recognizes you as a Master of Disaster, ready to face any outage and manage your IT environment with confidence.

Additionally Zerto is excited to announce that they are taking our training to the next level! This May, at ZertoCON, they will be offering for the first time ever the ZCP Advanced certification exam! So for those of you who are interested in really putting your skills to the test, and looking for official proof of your elite BC/DR status, sign up for ZertoCON now.

(Please note at this time that ZCP is only available to Zerto customers and partners)

– See more at: http://www.zerto.com/blog/general/zerto-certified-professional-training/

How to fix corrupt image profile issues on an ESXi host?

Posted on Updated on


Recently I happen to deal with such an issue while installing the patches on an ESXi host using vSphere Update Manager. This issue is rare and will occur if you interrupt the patches remediation task abruptly, in my case thanks to one of my colleague.

I will mention the steps which helped me to recover the image profile for the ESXi host.

Issue: No image profile is found on the host or image profile is empty. In my case image profile shows Unknown – no profile defined

image profile issue

Resolution:

This issue has been seen on systems where the image database file, imgdb.tgz, is corrupt. An image profile is required to install or remove VIBs.

How to confirm if you are proceed with the mentioned solution:

To confirm that the imgdb.tgz file is corrupt:

Connect to the ESXi host via an SSH session.

Change directory to /vmfs/volumes by cd /vmfs/volumes

Search for the imgdb.tgz file: find * | grep imgdb.tgz

 

Note: This command normally results in two matches. For example:

0ca01e7f-cc1ea1af-bda0-1fe646c5ceea/imgdb.tgz

edbf587b-da2add08-3185-3113649d5262/imgdb.tgz

 

Run this command on each match:

ls -l match_result

For example:

ls -l 0ca01e7f-cc1ea1af-bda0-1fe646c5ceea/imgdb.tgz

-rwx——   1 root root  26393 Jul 20 19:28 0ca01e7f-cc1ea1af-bda0-1fe646c5ceea/imgdb.tgz

 

The default size for the imgdb.tgz file is approximately 26 KB. If one of the files is only a couple of bytes, it indicates that the file is corrupt.

 

There are 2 ways you can fix this issue. To work around this issue, perform one of these options:

1. Rebuild the ESXi host

OR

2. Copy an imgdb.tgz file from a known good ESXi host to the host having the issue

 

You may rebuilt if you want but that is not what you are looking for!

Now let us see how we can proceed with the second option:

 

To copy the imgdb.tgz file from a known good ESXi host perform the following:

On the working ESXi host, copy a good copy of imgdb.tgz by perform the following

cp /bootbank/imgdb.tgz /vmfs/volumes/<shared-LUN>

On the corrupt host, copy the good copy of the imgdb.tgz to /tmp:

cp /vmfs/volumes/<shared LUN>/imgdb.tgz /tmp

cd /tmp

tar -xzf imgdb.tgz

Copy the good profile files to the profile directory:

cp /tmp/var/db/esximg/profiles/* /var/db/esximg/profiles/

Copy the good VIBs to the VIB repository:

cp /tmp/var/db/esximg/vibs/* /var/db/esximg/vibs/

Remove the corrupt imgdb.tgz from the bootbank:

rm /bootbank/imgdb.tgz

Move the good copy of imgdb.tgz into the bootbank:

cp /tmp/imgdb.tgz /bootbank/

Backup configuration changes made:

/sbin/auto-backup.sh

Restart the ESXi host, Attempt to install or patch the host again using vSphere Update Manager.

How to reset ESXi 5.x root password using Host Profiles

Posted on Updated on


According to VMware, the only supported way to reset a lost password is to do a fresh install. However, there are ways around it if your host is already connected to vCenter.

If you do NOT know the host password but it’s currently connected to vCenter, you can use Host Profiles to reset the password. This is only possible because the vpxa user on each ESXi host, added when the ESXi host is connected to vCenter Server, has root privileges.

Host Profiles are a feature of Enterprise Plus licensing only.

The is a VMware KB which mentions root password recovery is this one and it clearly states that it’s not supported to reset passwords on ESXi 5.x and ESXi in general as there is no longer the Linux console where you would use the single-user mode for the job:

Reinstalling the ESXi host is the only supported way to reset a password on ESXi. Any other method may lead to a host failure or an unsupported configuration due to the complex nature of the ESXi architecture. ESXi does not have a service console and as such traditional Linux methods of resetting a password, such as single-user mode.

But using host profiles to change the root password on ESXi host is supported and if you got the appropriate licensing then you should be able to change the root password.

Steps:

1. Right click the host, choose All vCenter Actions, Host Profiles, and select Extract Host Profile. Run through the wizard to create the new profile.

2. At the top of the vSphere client, click Home and Host Profiles under the Management section. Right click the newly created profile and choose Edit.

3. Click Next to the Edit Host Profile step and expand Security and Services, then expand Security Settings. Click on Security Configuration. Modify the dropdown list and select the “Configure a fixed administrator password” option. Enter the new password.

4. Complete the wizard which will save all your changes.

5. Back in the Hosts and Clusters view, right click your host and go to All vCenter Actions, Host Profiles, and Attach Host Profile. Select your profile you created and customized and finish the wizard.

6. Put your host in maintenance mode.

7. Right click the host again, All vCenter Actions, Host Profiles, and Remediate. If your host is not in maintenance mode, you’ll get the message “Remediate operation is allowed only for hosts in maintenance mode”

8. Once the Host Profile is applied, the host will reboot and your password will now be updated.

How to Remove Storage Devices from ESXi Hosts

Posted on Updated on


Unmounting a LUN checklist

Before unmounting a LUN, ensure that:

  • If the LUN is being used as a VMFS datastore, all objects (such as virtual machines, snapshots, and templates) stored on the VMFS datastore are unregistered or moved to another datastore.Note: All CD/DVD images located on the VMFS datastore must also be unregistered from the virtual machines.
  • The datastore is not used for vSphere HA heartbeat.
  • The datastore is not part of a datastore cluster.
  • The datastore is not managed by Storage DRS.
  • The datastore is not configured as a diagnostic coredump partition.
  • Storage I/O Control is disabled for the datastore.
  • No third-party scripts or utilities running on the ESXi host can access the LUN that has issue. If the LUN is being used as a datastore, unregister all objects (such as virtual machines and templates) stored on the datastore.
  • If the LUN is being used as an RDM, remove the RDM from the virtual machine. Click Edit Settings, highlight the RDM hard disk, and click Remove. Select Delete from disk if it is not selected, and click OK.Note: This destroys the mapping file, but not the LUN content.
  • Check if the LUN/datastore is used as the persistent scratch location for the host.This PowerCLI script can be used to check the current scratch location:

$vcServer = “vCenter01”
$cluster = “CL01”
$esxCred = Get-Credential
Connect-VIServer $vcServer | Out-Null
#Connect to ESX hosts in cluster
foreach ($esx in Get-Cluster $cluster | Get-VMHost) {
Connect-VIServer $esx -Credential $esxCred | Out-Null
Get-VMHostAdvancedConfiguration -Name “ScratchConfig.ConfiguredScratchLocation”
}

Note: When using the vSphere Web Client with vSphere 5.1, 5.5 and 6.0, only these checks are performed during the datastore unmount operation:

  • Host should not have any virtual machines residing on this datastore
  • Host should not use the datastore for HA heartbeats

Obtaining the NAA ID of the LUN to be removed

From the vSphere Client, this information is visible in the Properties window of the datastore.

From the ESXi host, run this command:

# esxcli storage vmfs extent list

You see output similar to:

Volume Name VMFS UUID Extent Number Device Name Partition
———– ———————————– ————- ———————————— ———
datastore1 4de4cb24-4cff750f-85f5-0019b9f1ecf6 0 naa.6001c230d8abfe000ff76c198ddbc13e 3
Storage2 4c5fbff6-f4069088-af4f-0019b9f1ecf4 0 naa.6001c230d8abfe000ff76c2e7384fc9a 1
Storage4 4c5fc023-ea0d4203-8517-0019b9f1ecf4 0 naa.6001c230d8abfe000ff76c51486715db 1
LUN01 4e414917-a8d75514-6bae-0019b9f1ecf4 0 naa.60a98000572d54724a34655733506751 1

Make a note of the NAA ID of the datastore to use this information later in this procedure.

Note: Alternatively, you can run the esxcli storage filesystem list command, which lists all file systems recognized by the ESXi host.

Unmounting a LUN using the vSphere Client

To unmount a LUN from an ESXi 5.0 host using the vSphere Client:

  1. If the LUN is an RDM, skip to step 2. Otherwise, in the Configuration tab of the ESXi host, click Storage. Right-click the datastore being removed, and click Unmount.A Confirm Datastore Unmount window appears. When the prerequisite criteria have been passed, click OK.Note: To unmount a datastore from multiple hosts in the vSphere Client, click Hosts and Clusters > Datastores and Datastore Clusters view (Ctrl+Shift+D). Perform the unmount task and select the appropriate hosts that should no longer access the datastore to be unmounted.
  2. Click the Devices view (under Configuration > Storage):                          
  3. Right-click the NAA ID of the LUN (as noted above) and click Detach. A Confirm Device Unmount window is displayed. When the prerequisite criteria are passed, click OK. Under the Operational State of the Device, the LUN is listed as Unmounted.Note: The Detach function must be performed on a per-host basis and does not propagate to other hosts in vCenter Server. If a LUN is presented to an initiator group or storage group on the SAN, the Detach function must be performed on every host in that initiator group before unmapping the LUN from the group on the SAN. Failing to follow this step results in an all-paths-down (APD) state for those hosts in the storage group on which Detach was not performed for the LUN being unmapped.
  4. Confirm if the LUN is successfully detached. The LUN can then be safely unpresented from the SAN. For more information, contact your storage array vendor.
  5. Perform a rescan on all ESXi hosts which had visibility to the LUN. The device is automatically removed from the Storage Adapters.

When the device is detached, it stays in an unmounted state even if the device is re-presented (that is, the detached state is persistent). To bring the device back online, the device must be attached.

If you want the device to permanently decommission from an ESXi host, manually remove the NAA entries from the host configuration:

  1. To list the permanently detached devices, run this command:# esxcli storage core device detached listYou see output similar to:Device UID State
    ———————————— —–
    naa.50060160c46036df50060160c46036df off
    naa.6006016094602800c8e3e1c5d3c8e011 off
  2. To permanently remove the device configuration information from the system, run this command:# esxcli storage core device detached remove -d NAA_IDFor example:# esxcli storage core device detached remove -d naa.50060160c46036df50060160c46036df

VMware vCenter Release and Build Number History

Posted on Updated on


vCenter Build Numbers
Name Version Release Build Installer Version
vCenter Server 6.0.0 Update 1 6.0 U1 9/10/2015 3018524 3040890
vCenter Server 6.0.0b 6.0.0b 7/7/2015 2776511 2800571
vCenter Server 6.0 Express Patch 1 6.0.0a 4/16/2015 2656758 2656757
vCenter Server 6.0 6.0 GA 3/12/2015 2494585 2562643
vCenter Server 5.5 Update 3 5.5 U3 9/16/2015 3000241 3000346
vCenter Server 5.5 Update 2e 5.5 U2e 4/16/2015 2646482 2646481 5.5.0.44687
vCenter Server 5.5 Update 2d 5.5 U2d 1/27/2015 2442329 2442328 5.5.0.43769
vCenter Server 5.5 Update 2b 5.5 U2b 10/9/2014 2183111 2183112 5.5.0.43013
vCenter Server 5.5 Update 2 5.5 U2 9/9/2014 2001466 2105955 5.5.0.42389
vCenter Server 5.5 Update 1c 5.5 U1c 7/22/2014 1945274 1945270 5.5.0.42156
vCenter Server 5.5 Update 1b 5.5 U1b 6/12/2014 1891310 1891314 5.5.0.41927
vCenter Server 5.5 Update 1a 5.5 U1a 4/19/2014 1750795 1750787 5.5.0.41222
vCenter Server 5.5c 5.5c 4/19/2014 1750596 1750597 5.5.0.41218
vCenter Server 5.5 Update 1 5.5 U1 3/11/2014 1623101 1623099 5.5.0.40799
vCenter Server 5.5b 5.5b 12/22/2013 1476327 1476387 5.5.0.39885
vCenter Server 5.5a 5.5a 10/31/2013 1378903 1378901 5.5.0.38845
vCenter Server 5.5 5.5 GA 9/22/2013 1312298 1312299 5.5.0.38036
vCenter Server 5.1 Update 3b 5.1 U3b 10/1/2015 3070521 3072311
vCenter Server 5.1 Update 3a 5.1 U3a 4/30/2015 2669725 2670344
vCenter Server 5.1 Update 3 5.1 U3 12/4/2014 2306353 2308386 5.1.0.43263
vCenter Server 5.1 Update 2c 5.1 U2c 10/30/2014 2207772 2212977 5.1.0.43068
vCenter Server 5.1 Update 2a 5.1 U2a 7/7/2014 1882349 1917403 5.1.0.41903
vCenter Server 5.1 Update 2 5.1 U2 1/16/2014 1473063 1474365 5.1.0.39867
vCenter Server 5.1 U1c 5.1 U1c 10/30/2013 1364037 1364079 5.1.0.38659
vCenter Server 5.1 U1b 5.1 U1b 8/1/2013 1235232 1235309 5.1.0.37189
vCenter Server 5.1 U1a 5.1 U1a 5/22/2013 1123961 1123966 5.1.0.36098
vCenter Server 5.1 Update 1 5.1 U1 4/25/2013 1064983 1065152 5.1.0.35539
vCenter Server 5.1b 5.1b 12/20/2012 947673 947939 5.1.0.34460
vCenter Server 5.1a 5.1a 11/19/2012 880146 880471 5.1.0.33762
vCenter Server 5.1 5.1 GA 9/11/2012 799731 799735 5.1.0.32743
vCenter Server 5.0 Update 3e 5.0 U3e 10/1/2015 3073236 3073234
vCenter Server 5.0 Update 3d 5.0 U3d 4/30/2015 2656067 2692807
vCenter Server 5.0 Update 3c 5.0 U3c 11/20/2014 2210222 2215678 5.0.0.43079
vCenter Server 5.0 Update 3a 5.0 U3a 7/1/2014 1917469 1923446 5.0.0.42044
vCenter Server 5.0 Update 3 5.0 U3 10/17/2013 1300600 1343691 5.0.0.37933
vCenter Server 5.0 Update 2 5.0 U2 12/20/2012 913577 923238 5.0.0.34130
vCenter Server 5.0 U1b 5.0 U1b 8/16/2012 804277 804276 5.0.0.32829
vCenter Server 5.0 U1a 5.0 U1a 7/12/2012 755629 757163 5.0.0.31955
vCenter Server 5.0 Update 1 5.0 U1 3/15/2012 623373 639890 5.0.0.29542
vCenter Server 5.0 5.0 GA 8/24/2011 456005 456005 5.0.0.16964
vCenter Server 4.1 U3a 1/31/2013 925676 978694
vCenter Server 4.1 U3 8/30/2012 799345 816786
vCenter Server 4.1 U2 10/27/2011 491557 493063
vCenter Server 4.1 U1 2/10/2011 345043 345042
VUM-KB-1023962 7/19/2010 275390
vCenter Server 4.1 7/13/2010 259021 259021
vCenter Server 4.0 Update 4b 4.0 U4b 2/7/2013 934016
vCenter Server 4.0 U4 11/17/2011 496403
vCenter Server 4.0 U3 5/5/2011 385281
vCenter Server 4.0 U2 6/10/2010 258672
vCenter Server 4.0 U1 11/19/2010 208111
vCenter Server 4.0 Patch 1 2/25/2010 183347
vCenter Server 4.0 5/21/2009 162856
VirtualCenter 2.5.0 U6b 3/8/2012 598800
VirtualCenter 2.5.0 U6a 5/5/2011 341471
VirtualCenter 2.5.0 U6 Localized 1/29/2010 227640
VirtualCenter 2.5.0 U6 English 1/29/2010 227637
VirtualCenter 2.5.0 U5 Localized 7/10/2009 174835
VirtualCenter 2.5.0 U5 English 7/10/2009 174768
VirtualCenter 2.5.0 U4 Localized 2/23/2009 147704
VirtualCenter 2.5.0 U4 German 2/23/2009 147697
VirtualCenter 2.5.0 U4 English 2/23/2009 147633
VirtualCenter 2.5.0 U3 10/3/2008 119598
VirtualCenter 2.5.0 U2 7/25/2008 104215
VirtualCenter 2.5.0 U1 4/10/2008 84767
VirtualCenter 2.5.0 12/10/2007 64192

How to configure a Dell iDRAC card without rebooting

Posted on Updated on


First of all download the Racadm tool from the this link. It is included in Dell OpenManage DRAC Tools. The Dell Remote Access Controller (DRAC) console is management station software designed to provide remote management capabilities for the Dell systems. You can remotely connect to the DRAC hardware and access the DRAC features either by using a web browser or the RACADM Command Line Interface (CLI). RACADM CLI is the command line user interface to the DRAC.

Syntax Usage

The following shows an example of a simple RACADM subcommand, getsysinfo, used with each RACADM utility. See the end of this article for links to documentation containing the full list of RACADM commands.

Remote RACADM

Remote RACADM commands must include the ip address or hostname of the idrac, and the idrac username and password.

racadm -r <ip address or hostname> -u <username> -p <password> <subcommand>

racadm -r 10.1.1.1 -u root -p calvin getsysinfo

NOTE: Remote racadm uses the web server SSL certificate of the iDRAC to authenticate the session. You will receive a warning message if certificates have not been configured or if the certificate is invalid. However, the command will execute normally following the message. If you wish to halt the command on certificate errors, use the -S option in the command. For information on configuring certificates on the iDRAC, see the user’s guide for your iDRAC linked at the end of this article.

Local RACADM

You do not have to specify the ip address, username, or password in Local RACADM commands.

racadm <subcommand> eg. racadm getsysinfo

racadm getniccfg

racadm setniccfg –s 172.17.2.124 255.255.252.0 172.17.0.5
or
racadm getconfig -g cfgLanNetworking
racadm config -g cfgLanNetworking -o cfgNicIpAddress 172.17.2.124
racadm config -g cfgLanNetworking -o cfgNicNetmask 255.255.252.0
racadm config -g cfgLanNetworking -o cfgNicGateway 172.17.0.7
racadm config -g cfgLanNetworking -o cfgDNSServer1 172.17.0.6
racadm config -g cfgLanNetworking -o cfgDNSServer2 172.17.0.5
racadm config -g cfgLanNetworking -o cfgDNSRacName ServerName-DRAC
racadm config -g cfgLanNetworking -o cfgDNSDomainName corp.company.com

SSH/Telnet/Serial (Firmware) RACADM

You do not have to specify the ip address, username, or password in Firmware RACADM commands.

racadm <subcommand>   eg. racadm getsysinfo

or

racadm <Enter> – takes you to a racadm>> prompt  eg. racadm>>getsysinfo

Raising a support case for ProLiant/Blades Series Servers, the step by step approach!

Posted on Updated on


Now a days HP has segregated the support types, the server support comes under Hewlett Packard Enterprise.

Select your product

HP ProLiant BL Server Blades

HP ProLiant CL Servers

HP ProLiant DL Multi Node Servers

HP ProLiant DL Servers

HP ProLiant MicroServer

HP ProLiant ML Servers

HP ProLiant Packaged Cluster Servers

HP ProLiant Scalable Systems

HP ProLiant WS Workstation Blades

HP Server tc Series

Or

if you are not able to find your product, check the below link to manually search the server model/ number in the Hewlett Packard Enterprise Products: eg. ProLiant DL360 Gen9

 

HP warranty and support

You will get log of results like below:

 

HP Support
Select the appropriate one, for me it is in yellow as above. Clicking it will land you to the product page as below. You will find Top issues, Most viewed solutions, manuals, Trouble a problem links which are very useful from troubleshooting point of view as all the known issues will be captured there. Apart from these you will find the latest drivers links with respect to the OS on the server etc. Most importantly, You can check the product warranty information from this page.

 

hp support page

 

Finally if the above of these do not help then you can raise case by clicking the below link. You need to create a HP passport login in case you do not have an account. HP Passport is a single sign in service that lets you use one User ID and password for all HP Passport-enabled websites.

Submit or manage support cases

hp support manager

You may also check existing ticket updates by providing the case ID.

I hope techies find it useful 🙂

 

Connections and Ports in ESX and ESXi

Posted on Updated on


Ports

A high resolution pdf can be downloaded here Connections and Ports in ESX and ESXi

VMware ESXi Release and Build Number History – A must for confirming your ESXi hosts are up to date!

Posted on Updated on


The following listings are a comprehensive collection of the flagship hypervisor product by VMware. All bold versions are downloadable releases.

vSphere ESXi 6.0

Name Version Release Build
ESXi600-201511001 ESXi 6.0 Express Patch 4 2015-11-25 3247720
ESXi600-201510001 ESXi 6.0 Update 1a 2015-10-06 3073146
VMware ESXi 6.0 Update 1 ESXi 6.0 Update 1 2015-09-10 3029758
ESXi600-201507001 ESXi 6.0b 2015-07-07 2809209
ESXi600-201505001 ESXi 6.0 Express Patch 2 2015-05-14 2715440
ESXi600-201504001 ESXi 6.0 Express Patch 1 2015-04-09 2615704
VMware ESXi 6.0 ESXi 6.0 GA 2015-03-12 2494585

 vSphere ESXi 5.5

Name Version Release Build
ESXi550-201512001 2015-12-08 3248547
ESXi550-201510001 ESXi 5.5 Update 3a 2015-10-06 3116895
VMware ESXi 5.5 Update 3 ESXi 5.5 Update 3 2015-09-16 3029944
ESXi550-201505002 ESXi 5.5 Patch 5 2015-05-08 2718055
ESXi550-201504002 Recalled 2015-04-30 2702864
ESXi550-201504001 ESXi 5.5 Express Patch 7 2015-04-07 2638301
ESXi550-201502001 ESXi 5.5 Express Patch 6 2015-02-05 2456374
ESXi550-201501001 ESXi 5.5 Patch 4 2015-01-27 2403361
ESXi550-201412001 ESXi 5.5 Express Patch 5 2014-12-02 2302651
ESXi550-201410001 ESXi 5.5 Patch 3 2014-10-15 2143827
VMware ESXi 5.5 Update 2 ESXi 5.5 Update 2 2014-09-09 2068190
ESXi550-201407001 ESXi 5.5 Patch 2 2014-07-01 1892794
ESXi550-201406001 ESXi 5.5 Express Patch 4 2014-06-10 1881737
ESXi550-201404020 ESXi 5.5 Express Patch 3 2014-04-19 1746974
ESXi550-201404001 ESXi 5.5 Update 1a 2014-04-19 1746018
VMware ESXi 5.5.1 Driver Rollup 2014-03-11 1636597
VMware ESXi 5.5 Update 1 ESXi 5.5 Update 1 2014-03-11 1623387
ESXi550-201312001 ESXi 5.5 Patch 1 2013-12-22 1474528
vSAN Beta Refresh 2013-11-25 1439689
VMware ESXi 5.5 ESXi 5.5 GA 2013-09-22 1331820

vSphere ESXi 5.1

Name Version Release Build
ESXi510-201510001 2015-10-01 3070626
ESXi510-201503001 5.1.0 Patch 7 2015-03-26 2583090
VMware ESXi 5.1 Update 3 5.1.0 U3 2014-12-04 2323236
ESXi510-201410001 5.1.0 Patch 6 2014-10-31 2191751
ESXi510-201407001 5.1.0 Patch 5 2014-07-31 2000251
ESXi510-201406001 5.1.0 Express Patch 5 2014-06-17 1900470
ESXi510-201404001 5.1.0 Patch 4 2014-04-29 1743533
ESXi510-201402001 5.1.0 Express Patch 4 2014-02-27 1612806
VMware ESXi 5.1 Update 2 5.1.0 U2 2014-01-16 1483097
ESXi510-201310001 5.1.0 Patch 3 2013-10-17 1312873
ESXi510-201307001 5.1.0 Patch 2 2013-07-25 1157734
ESXi510-201305001 5.1.0 Express Patch 3 2013-05-22 1117900
VMware ESXi 5.1 Update 1 5.1.0 U1 2013-04-25 1065491
ESXi510-201303001 5.1.0 Express Patch 2 2013-03-07 1021289
ESXi510-201212001 5.1.0 Patch 1 2012-12-20 914609
ESXi510-201210001 5.1.0a 2012-10-24 838463
KB2034796 5.1.0 Hot-Patch 837262
VMware ESXi 5.1 5.1.0 GA 2012-09-11 799733

vSphere ESXi 5.0

Name Version Release Build
ESXi500-201510001 2015-10-01 3086167
ESXi500-201502001 5.0.0 Patch 11 2015-02-26 2509828
ESXi500-201412001 5.0.0 Patch 10 2014-12-04 2312428
ESXi500-201408001 5.0.0 Patch 9 2014-08-28 2000308
ESXi500-201407001 5.0.0 Express Patch 6 2014-07-01 1918656
ESXi500-201405001 5.0.0 Patch 8 2014-05-29 1851670
ESXi500-201401001 5.0.0 Patch 7 2014-01-23 1489271
VMware ESXi 5.0 Update 3 5.0.0 U3 2013-10-17 1311175
ESXi500-201308001 5.0.0 Patch 6 2013-08-29 1254542
ESXi500-201305001 5.0.0 Express Patch 5 2013-05-15 1117897
ESXi500-201303001 5.0.0 Patch 5 2013-03-28 1024429
VMware ESXi 5.0 Update 2 5.0.0 U2 2012-12-20 914586
ESXi500-201209001 5.0.0 Patch 4 2012-09-27 821926
ESXi500-201207001 5.0.0 Patch 3 2012-07-12 768111
ESXi500-201206001 5.0.0 Express Patch 4 2012-06-14 721882
ESXi500-201205001 5.0.0 Express Patch 3 2012-05-03 702118
ESXi500-201204001 5.0.0 Express Patch 2 2012-04-12 653509
VMware ESXi 5.0 Update 1 5.0.0 U1 2012-03-15 623860
ESXi500-201112001 5.0.0 Patch 2 2011-12-15 515841
ESXi500-201111001 5.0.0 Express Patch 1 2011-11-03 504890
ESXi500-201109001 5.0.0 Patch 1 2011-09-13 474610
VMware ESXi 5.0 5.0.0 2011-08-24 469512

vSphere ESXi 4.1

Name Version Release Build
ESXi410-201404001 4.1.0 Patch 11 2014-04-10 1682698
ESXi410-201312001 4.1.0 Patch 10 2013-12-05 1363503
ESXi410-201307001 4.1.0 Patch 9 2013-07-31 1198252
ESXi410-201304001 4.1.0 Patch 8 2013-04-30 1050704
ESXi410-201301001 4.1.0 Patch 7 2013-01-31 988178
ESXi410-201211001 4.1.0 Patch 6 2012-11-15 874690
VMware ESXi 4.1 Update 3 4.1.0 U3 2012-08-30 800380
ESXi410-201206001 4.1.0 Express Patch 3 2012-06-14 721871
ESXi410-201205001 4.1.0 Express Patch 2 2012-05-03 702113
ESXi410-201204001 4.1.0 Patch 5 2012-04-26 659051
ESXi410-201201001 4.1.0 Patch 4 2012-01-30 582267
VMware ESXi 4.1 Update 2 4.1.0 U2 2011-10-27 502767
ESXi410-201107001 4.1.0 Patch 3 2011-07-28 433742
ESXi410-201104001 4.1.0 Patch 2 2011-04-28 381591
VMware ESXi 4.1 Update 1 4.1.0 U1 2011-02-10 348481
ESXi410-201011001 4.1.0 Express Patch 1 2010-11-29 320137
ESXi410-201010001 4.1.0 Patch 1 2010-11-15 320092
VMware ESXi 4.1 4.1.0 2010-07-13 260247

 

How to generate VMware ESXi logs and how to Upload via the FTP portal using a third party FTP client for a VMware Support Case

Posted on Updated on


How to generate VMware ESXi logs:

Identify the ESXi host on which the server is hosted, putty to the Host and run the following command. But before you run the command, you need to select a  desired datastore  to direct the support log bundle to a location using the same command (mentioning the destination path).

For example:

vm-support -s > /vmfs/volumes/datastorexxx/vm-support-Hostname.tgz

 Datastorexxx = will be datastore with free space

vm-support-Hostname.tgz = host name

  1. After the log bundle has been collected and downloaded from the datastore by browsing the particular datastore normally using the vSphere client, then upload the logs to the SFTP/FTP site.

How to Upload via the FTP portal using a Filezilla (FTP Client)
There are many third-party GUI-based FTP clients that run on multiple platforms. These clients are able to perform the operations in this article using an intuitive GUI interface. Feel free to use the FTP client of your choice, which supports passive mode.

FileZilla is a popular third party FTP client.

To upload files from Windows using FileZilla:

  1. Open the FileZilla client.
  2. Set the transfer mode to binary:

    Go to the Transfer menu > Transfer type > Binary

  3. Go to the File menu > Site Manager.
  4. Add the VMware FTP site to My Sites using the Site Manager. The credentials are:

    Address = ftpsite.vmware.com
    Logon Type = normal
    User = inbound
    Password = inbound

  5. Click Connect.
  6. Change to the correct destination directory for your Support Request:
    1. If this is the first time you are uploading files to the VMware FTP Server for this case, create a directory in the root of the VMware FTP. To do this, right click the root directory on the remote site in the right pane and choose Create directory.
    2. If this is not the first time you are uploading files for this case, proceed to step 7.
  7. Change to your SR directory using the Remote site field.

    For example:

    Remote site: /12345678901

    Notes:

    1. For security reasons, you do not see any files or directories on the VMware FTP server, including files you have uploaded.
    2. The destination directory should contain numbers only. Do not enter letters or other characters.
  1. Once you connect to the correct destination directory, browse to the location of the log files on your local system using the file browser in the left pane or enter the full path in the Local site field.
  2. Right click the file and select Upload to start the transfer.
  3. Monitor the transfer progress in the Queued files pane.

How to power off a Virtual Machine on an ESXi host via Putty

Posted on Updated on


Sometime a virtual machine may not responsive and cannot be stopped or killed, then this is a workaround to reboot the virtual machine via putty.

The esxcli command can be used locally or remotely to power off a virtual machine running on ESXi 5.x or later.

  1. Open a console session where the esxcli tool is available, either in the ESXi Shell, the vSphere Management Assistant (vMA), or the location where the vSphere Command-Line Interface (vCLI) is installed.
  2. Get a list of running virtual machines, identified by World ID, UUID, Display Name, and path to the.vmx configuration file, using this command:esxcli vm process list
  3. Power off one of the virtual machines from the list using this command:esxcli vm process kill –type=[soft,hard,force]–world-id=WorldNumber

    Notes:
    Three power-off methods are available. Soft is the most graceful, hard performs an immediate shutdown, and force should be used as a last resort.
    Alternate power off command syntax is: esxcli vm process kill -t [soft,hard,force] -w WorldNumber

  4. Repeat Step 2 and validate that the virtual machine is no longer running.

How to fix a RDP issue without reboot?

Posted on Updated on


The following steps can be used to resolve RDP issues without a restart:

 Note: The below condition will be applicable only if the server is available on NetworkJ.

  Troubleshooting Steps:

1. Check if the Windows Firewall Setting is Enabled on the server. If yes, have them Disabled.

 Note: This is primarily applicable for Virtual Servers (VM machines) and if it is accessible in VM console.

 

 2. The following registry location, which is responsible for Terminal Server to access the via RDP:

 HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Terminal Server

 Under the Terminal Server key, the REG_DWORD value named fDenyTSConnection should be 0 because the value data 1 denies connecting to Terminal Services (to access the server via RDP).

 Note: Even if the value is 0, change it from 0 to 1 and refresh the registry. Again the change the value back from 1 to 0 and refresh the registry.

 HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Terminal Server

 Under the Terminal Server key, the REG_DWORD value named fAllowToGetHelp should be 0 because the value data 1 denies the Remote Assistance on a server (to access the server via RDP).

Note: Even if the value is 0, change it from 0 to 1 and refresh the registry. Again the change the value back from 1 to 0 and refresh the registry.

3. The following registry location is used to enable Remote User Session on a server (Citrix)

 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\ICA-Tcp

 Under the ICA-Tcp key, the REG_DWORD value named fEnableWinStation should be 1 because the value data 0 denies remote user sessions (to access the server via RDP).

Note: Even if the value is 1, change it from 1 to 0 and refresh the registry. Again the change the value back from 0 to 1 and refresh the registry.

 4. The following registry location is used to enable Remote User Session on a server

 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp

 Under the ICA-Tcp key, the REG_DWORD value named fEnableWinStation should be 1 from 0 because the value data 0 denies remote user sessions (to access the server via RDP).

Note: Even if the value is 1, change it from 1 to 0 and refresh the registry. Again the change the value back from 0 to 1 and refresh the registry.

5. The following registry location, which is responsible for RDP port:

 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp

Under the RDP-Tcp key, the REG_DWORD value named PortNumber should be 3389 because by default, the Remote Desktop listens on port 3389 via TCP connection (to access the server via RDP).

 Note: Open command prompt and type the below command

 C:\telnet “SERVERNAME OR IP ADDRESS” 3389

 See if it is opened!!

 P.S: At times, this may require a restart after making these changes if it still doesn’t work.

 6. The following registry location is used to enable/disable logon to a Terminal Server

 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

 Under the Winlogon key, the REG_DWORD value named WinStationsDisabled should be 0 because the value data 1 denies logon to a Terminal Server via RDP.

Note: Even if the value is 0, change it from 0 to 1 and refresh the registry. Again the change the value back from 1 to 0 and refresh the registry.

What is a Queue Manager? What are the responsibilities of a Queue Manager?

Posted on Updated on


A Queue Manager or a Dispatcher is a resource who primary task is to assign the incident tickets to resources as per their skill set. Their primary role is to meet the SLA targets for an incident ticket. Below are the responsibilities of a Queue Manager:

  • Monitoring the queues and assign the incidents before missing Response time SLA
  • Tickets to be assigned with respective Support Engineer according to required skills sets
  • Follow up with engineer for closing the tickets those are going to be SLA breached
  • Assigned the tickets which are out of scope to Service Desk/Other Teams.
  • Publishing Weekly Change Calendar
  • Daily Report on Incidents/Change/Problem tickets and SLA status
  • Daily Change schedule reminder to respective change assignee
  • Shift Handover to Next Queue Manager
  • Summary report on all Major incidents happen on that day
  • For high number of repeated incidents, you need to relate the incidents with Parent incident and cancel the duplicate incident by marking the parent ticket info.
  • Need to discuss with TL/Shift lead for taking action against bouncing tickets

The below are the knowledge or skills which a Queue Manager should possess in order to deliver their job.

  • SLA Metric
  • Process knowledge (IM/CM/PM/SR)
  • Support Scope
  • Inter team SPOC contact
  • Escalation Matrix & Entire team contacts
  • Incident Categorization
  • Entire team Skill set Matrix
  • Current Shift Roster & Oncall Resource
  • Technology specific SME for Tech assistance
  • Inter Supplier Support Scope & Queue Name
  • Inter Supplier Support SPOC & Contact Details
  • Application Owners Contact & Queue Name
  • Generating the reports from Ticketing Tool

How to install a memory on a Cisco UCS B200 M3

Posted on Updated on


To install a DIMM into the blade server, follow these steps:

Procedure

Step 1: Open both DIMM connector latches.

Installing DIMMs in the Blade Server
Installing DIMMs in the Blade Server

Step 2: Press the DIMM into its slot evenly on both ends until it clicks into place.

DIMMs are keyed, if a gentle force is not sufficient, make sure the notch on the DIMM is correctly aligned.

Note: Be sure that the notch in the DIMM aligns with the slot. If the notch is misaligned you may damage the DIMM, the slot, or both.

Step 3: Press the DIMM connector latches inward slightly to seat them fully.

Supported DIMMs

The DIMMs supported in this blade server are constantly being updated. A list of currently supported and available drives is in the specification sheets at:

http:/​/​www.cisco.com/​en/​US/​products/​ps10280/​products_​data_​sheets_​list.html

Cisco does not support third-party memory DIMMs, and in some cases their use may irreparably damage the server and require an RMA and down time.

Memory Arrangement

The blade server contains 24 DIMM slots—12 for each CPU. Each set of 12 DIMM slots is arranged into four channels, where each channel has three DIMMs.

Memory Slots within the Blade Server
Memory Slots within the Blade Server
1 Channels A-D for CPU 1 2 Channels E-H for CPU 2

DIMMs and Channels

Each channel is identified by a letter—A, B, C, D for CPU1, and E, F, G, H for CPU 2. Each DIMM slot is numbered 0, 1, or 2. Note that each DIMM slot 0 is blue, each slot 1 is black, and each slot 2 is off-white or beige.

The figure below shows how DIMMs and channels are physically laid out on the blade server. The DIMM slots in the upper and lower right are associated with the second CPU (CPU shown on right in the diagram), while the DIMM slots in the upper and lower left are associated with the first CPU (CPU shown on left).

Physical representation of DIMMS and channels
Physical representation of DIMMS and channels

 

Courtesy: Cisco

Microsoft is Adding a Native SSH Client and Server to Windows

Posted on Updated on


As Microsoft has shifted towards a more customer-oriented culture, Microsoft engineers are using social networks, tech communities and direct customer feedback as an integral part on how we make decisions about future investments. A popular request the PowerShell team has received is to use Secure Shell protocol and Shell session (aka SSH) to interoperate between Windows and Linux – both Linux connecting to and managing Windows via SSH and, vice versa, Windows connecting to and managing Linux via SSH. Thus, the combination of PowerShell and SSH will deliver a robust and secure solution to automate and to remotely manage Linux and Windows systems.

SSH solutions are available today by a number of vendors and communities, especially in the Linux world. However, there are limited implementations customers can deploy in Windows production environments.  After reviewing these alternatives, the PowerShell team realized the best option will be for our team to adopt an industry proven solution while providing tight integration with Windows; a solution that Microsoft will deliver in Windows while working closely with subject matter experts across the planet to build it. Based on these goals, I’m pleased to announce that the PowerShell team will support and contribute to the OpenSSH community – Very excited to work with the OpenSSH community to deliver the PowerShell and Windows SSH solution!

A follow up question the reader might have is When and How will the SSH support be available? The team is in the early planning phase, and there’re not exact days yet. However the PowerShell team will provide details in the near future on availability dates.

Finally, I’d like to share some background on today’s announcement, because this is the 3rd time the PowerShell team has attempted to support SSH.  The first attempts were during PowerShell V1 and V2 and were rejected.  Given our changes in leadership and culture, we decided to give it another try and this time, because we are able to show the clear and compelling customer value, the company is very supportive.  So I want to take a minute and thank all of you in the community who have been clearly and articulately making the case for why and how we should support SSH!  Your voices matter and we do listen.

Thank you!

Angel Calvo
Group Software Engineering Manager
PowerShell Team

 

Additional Information

For more information on SSH please go to http://www.ietf.org/rfc/rfc4251.txt

For information on OpenSSH go to: http://www.openssh.com/index.html

ESXi 6.0 and vCenter Server 6.0 launched

Posted on Updated on


ESXi 6.0 and vCenter Server 6.0 has been launched on 12th May 2015.

What’s New in the VMware vSphere® 6.0 Platform – Please check http://www.vmware.com/files/pdf/vsphere/VMW-WP-vSPHR-Whats-New-6-0-PLTFRM.pdf

Want to upgrade to ESXi 6.0, check the Vmware compatibility guide. http://www.vmware.com/resources/compatibility/search.php

What is Vblock?

Posted on Updated on


Vblocks are bundled virtual machine, server and storage packages marketed by the Virtual Computing Environment (VCE) Coalition, which comprises VMware, Cisco and EMC. Vblock bundles come as Vblock 0 (300 to 800 VMs), Vblock 1 (800 to 3,000 VMs) and Vblock 2 (3,000 to 6,000-plus VMs) and are made up of Cisco UCS servers, Cisco Nexus and MDS fabric switches; and EMC Clariion or Symmetrix storage arrays.

Vblock Introduction

VCE’s Vblocks come in three configurations — Vblock 0 (for 300 to 800 VMs with EMC Celerra storage), Vblock 1 (for 800 to 3,000 VMs with Celerra or Clariion storage) and Vblock 2 (for 3,000 to 6,000-plus VMs with Symmetrix storage).

Vblocks 0, 1 and 2 each have completely different EMC storage subsystems that can’t talk to each other, are not interchangeable and you can’t scale through them.

For more details related to Vblock architecture, please see http://www.vce.com/asset/documents/infrastructure-platforms.pdf 

 

How to fix if you are unable to upgrade existing VMware Tools in a Windows 2003 virtual machine

Posted on Updated on


As per VMware, the cause of this issue is currently unknown and is under investigation.  In order to help identify the cause, report this issue to VMware Support and provide answers to the following questions:

  • What version of the tools are you upgrading from?
  • What version of the tools are you upgrading to?
  • What method is being used to upgrade the tools?

In order to determine the previous versions of the VMware Tools that were installed on your system, open the Microsoft Windows event viewer and search for Event Source of MsiInstaller and Event ID of 1034 for more information on viewing events, see the Filter Displayed Events Tech Net article from Microsoft.

Now, to fix this issue involves modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine.

  1. Start the virtual machine and log on as the Administrator.
  2. Take a full backup of the registry prior to editing it. Do not skip this step.
  3. Open the Windows Registry editor. Click Start > Run, type regedit, and press Enter.
  4. Delete these registry keys if they exist:
    • HKEY_CLASSES_ROOT\Installer\Features05014B32081E884E91FB41199E24004
    • HKEY_CLASSES_ROOT\Installer\Products05014B32081E884E91FB41199E24004
    • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features05014B32081E884E91FB41199E24004
    • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products05014B32081E884E91FB41199E24004
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\ComponentsB150AC107B12D11A9DD0006794C4E25
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3B410500-1802-488E-9EF1-4B11992E0440}
    • HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.
  5. Some services might need to be removed manually from the registry. Delete these as well if they exist:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMTools
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMUpgradeHelper
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMware Physical Disk Helper Service
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmvss
  6. Search the registry for vmware and delete all associated entries.Note: On virtual machines with any other VMware products installed (for example, vCenter Server), you might not want to delete all entries. If you do have another VMware product installed, then you can skip this step if you have already removed the entries in the previous procedures.
  7. Close the registry editor.
  8. Open Windows Explorer.
  9. Delete the %ProgramFiles%\VMware\VMware Tools folder.
  10. Restart the virtual machine.
  11. Install the new version of VMware Tools.

The request failed because the remote server took too long to respond. (The command has timed out as the remote server is taking too long to respond)

Posted on Updated on


You will notice this error  “The request failed because the remote server “Vcenter name / ip” took too long to respond. (The command has timed out as the remote server is taking too long to respond), ” while checking the storage view of a VM or DataCenter.

To solve this, Just type your credentials manually in the vsphere client and login as the “Use Windows Session Credentials” doesn’t work always with SSO.

Thereby be sure to follow http://kb.vmware.com/kb/2035510 when adding external domains. After that, add the trusted domains to the default domains and reorder the domains to suit your needs and save it.

 

 

 

How to monitor the Disk Command Aborts on an ESXi host

Posted on Updated on


When storage is severely overloaded, commands are aborted because the storage subsystem is taking too long to respond to the commands. The storage subsystem has not responded within an acceptable amount of time, as defined by the guest operating system. Aborted commands are a sign that the storage hardware is overloaded and unable to handle the requests in line with the host’s expectations.

The number of aborted commands can be monitored by using either vsphere client or esxtop.

  1.  from vsphere client, monitor disk commands aborts

this one can be generated from host and clusters->Performance-> Advanced -> Switch to disk -> chart options-> commands aborted-> ok.

  1. from esxtop, monitor ABRTS/s

Open putty, login to the ESXi host, run esxtop, for the disk type u, type f to change the settings and type L to select Error stats. Press W to save it.

Once this is we can see the ABRTS/s field there which tracks the SCSI aborts, Aborts generally occur because the array takes long time to respond to commands.

Now if you are planning to deploy a monitoring tool to monitor this parameter, the threshold for ABRTS/s should be 1. This signifies number of SCSI commands aborted during the collection interval i.e. in 1 second.

DISK       ABRTS/s               1              Aborts issued by guest(VM) because storage is not responding. For Windows VMs this happens after 60 seconds by default. Can be caused for instance when paths failed or array is not accepting any IO for whatever reason.

However having said that the in ideal case the output of ABRTS/s should be 0, which may sometime not been observer during peak hours i.e. Backup may be running on the servers hosted on the ESXi host resulting in disk intensive workouts. This ABRTS/s will fluctuate 0 to 0.xx in real case scenario as the storage is always overloaded during these peak hours.

How to install and configure Multipathing I/O on a computer running Windows Server 2008

Posted on Updated on


To install Multipath I/O

  1. Open Server Manager.To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. In the Features area, click Add Features.
  3. On the Select Features page of the Add Features Wizard, select Multipath I/O, and then click Next.
  4. On the Confirm Installation Selections page, click Install.
  5. When installation has completed, click Close.

To install Multipath I/O on a computer by using the Server Manager command line, complete the following steps.

To install Multipath I/O by using a command line

  1. Open a Command Prompt window with elevated privileges.Right-click the Command Prompt object on the Start menu, and then click Run as administrator.
  2. Type the following, and press ENTER. ServerManagerCmd.exe -install Multipath-IO
  3. When installation has completed, you can verify that Multipath I/O has installed by entering the following command and reviewing the query results in the command window. Multipath I/O should show in the list of installed packages. ServerManagerCmd.exe -query

IC347745[1]

Removing Multipath I/O

To remove Multipath I/O, complete the following steps.

To remove Multipath I/O

  1. Open Server Manager.To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. In the Features area, click Remove Features.
  3. On the Select Features page of the Add Features Wizard, select Multipath I/O, and then click Next.
  4. On the Confirm Installation Selections page, click Install.
  5. When installation has completed, click Close.

To remove Multipath I/O by using the Server Manager command line, complete the following steps.

To remove Multipath I/O by using a command line

  1. Open a Command Prompt window with elevated privileges.Right-click the Command Prompt object on the Start menu, and then click Run as administrator.
  2. Type the following, and press ENTER. ServerManagerCmd.exe -remove Multipath-IO
  3. When removal has completed, you can verify that Multipath I/O was removed by entering the following command and reviewing the query results in the command window. Multipath I/O should not be in the list of installed packages. ServerManagerCmd.exe -query
To claim an iSCSI-attached device for use with MPIO

Open the MPIO control panel, and then click the Discover Multi-Paths tab.
  1. Select the Add support for iSCSI devices check box, and then click Add. When prompted to restart the computer, click Yes.
  2. When the computer restarts, the MPIO Devices tab lists the additional hardware ID “MSFT2005iSCSIBusType_0x9.” When this hardware ID is listed, all iSCSI bus attached devices will be claimed by the Microsoft DSM.

The Performance Overview tab fails to display with the error: Navigation to the webpage was cancelled (1014454)

Posted on Updated on


There are several possible causes for this issue. Attempt each of the troubleshooting steps below in sequence, without skipping any.

  1. Confirm that the vCenter Web Management Service is running.

    To resolve this issue, connect to vCenter locally with a vSphere Client located on the vCenter Server and followStopping, starting, or restarting vCenter services (1003895).

  2. Ensure that the correct DNS settings and IP address are being used:
    1. On the vCenter Server, navigate toC:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vim.stats.report\.
    2. Openxml in a text editor.
    3. Edit the line<url>https://hostname:8443/statsreport/vicr.do</url> to use an IP address instead of an FQDN to rule out issues with DNS.
    4. Restart vCenter Web Management Service and the vCenter Server Service after making any changes to the.xml  For moreinformation, see Stopping, starting, or restarting vCenter services (1003895).
  3. Disable any third party web services that may be interfering with the vCenter Web Management Services.

    To confirm that a third party web service is the cause:

    1. Stop the vCenter Web Management Service. For more information, seeStopping, starting, or restarting vCenter services (1003895).
    2. Try to connect to port 8443 (the port on which the Web Management Service runs) by executing:

      telnet IP8443

    3. If the port responds when the vCenter Web Management Service is stopped, there might be another service that is using the port. In this case, if you want to continue running the conflicting third party service, you may have to change the port that Performance Overview uses. To change the port used by Performance Overview, seeThe Performance Overview tab within vCenter Server reports the HTTP Status 404 error (1016160).
  4. Check if vCenter Server is using custom SSL certificates as a result of a recent upgrade to vCenter Server 4.0 Update 1. For more information, seeVMware vCenter Server plugins fail after adding custom SSL certificates (1017577).

Note: Additionally, you can perform these steps:

  • Disable the proxy settings from the browser.

    To disable the settings:

  1. LaunchInternet
  2. Navigate toTools > Internet options.
  3. Click theConnections
  4. ClickLAN settings.
  5. Select theUse automatic configuration script
  • If you experience this issue on workstations external to the vCenter Server, try to connect to port 8443 (the port on which the Web Management Service runs) as per Step 3b. If you are unable to connect to the port, disable the Windows Firewall on the vCenter Server system. For more information, see the Microsoft TechNet article I Need to Disable Windows Firewall.

Help and support service not running in Windows 2003

Posted on Updated on


To fix this:

  • Open a Command Prompt
  • Run the following commands
  • %SystemDrive%
  • CD %windir%\PCHealth\HelpCtr\Binaries
  • start /w helpsvc /svchost netsvcs /regserver /install

The service should install and start automatically.

How to Clean up the WinSxS Directory on Windows Server 2008 R2

Posted on Updated on


Prior to this we need to install Disk Cleanup on Windows 2008. Disk Cleanup is not installed by default on Windows Server 2008 R2. It is instead a component installed with the Desktop Experience feature.

To install Disk Cleanup without reboot the server – How to install Disk Cleanup without reboot the server in Window 2008

Now download the appropriate package and install the on the system.

Operating system Update
All supported x86-based versions of Windows 7
All supported x64-based versions of Windows 7
All supported x64-based versions of Windows Server 2008 R2

Looking at my Windows 2008 R2 Server with SP1 installed, according to Windows Explorer, the size of my Windows/WinSxS directory is as follows:

pic1[1]

The size of the WinSxS directory will vary by server. Some of you will have smaller WinSxS directories, some larger.

Installing the update is just like installing any other update. Just download and double-click on the .msu file:

pic2[1]

 

Now we need to run the disk cleanup wizard. Disk Cleanup option can be found under Start –> All Programs –> Accessories –> System Tools: or go to run and type ‘cleanmgr’ to launch it.

pic8[1]

On launch, Disk Cleanup prompts for the drive you want to clean up, default drive will be C: drive

pic9[1]

After clicking Ok, a scan is performed:

pic10[1]

Several options are provided for cleanup, including a new option for Windows Update Cleanup:

pic11[1]

If you didn’t launch Disk Cleanup as Administrator, at this point, you’ll need to take a couple extra steps. You’ll need to click on the Clean up system files button.

3348.diskcleanup3[1]

The actual cleanup occurs during the next reboot. After the reboot, taking a look at the WinSxS directory, it has shrunk to the following:

pic12[1]

 

How to change default snapshot location in VMware ESXi 5

Posted on Updated on


Defaulty the snapshots which are taken for any virtual machine are stored with their parent in the same directory or storage. Sometimes you may run out of space and you might not be able to take anymore snapshots so in that case you can always use some other location for the storage of snapshots.

snapshot
These are the required steps to be taken to change the default locations of all the snapshots .

NOTE: Please ensure that the vm you are working on is powered OFF.

Right Click the vm and select Edit Settings
Click on Options from the top TAB, select General and open the Configuration parameters

Add a new row with the following details

snapshot.redoNotWithParent

Save this parameter with a value “true” as shown below

Now open the CLI of the host where the vm is located

Go to the vm’s parent directory where all the vm files are stored and open the main .vmx file

As in my case

# cd /vmfs/volumes/53652b45-90f342h4-v3r3-s5dw676h5674/Windows2003
# vi Windows2003.vmx

Now add this line anywhere in the .vmx file with the path location where you want your snapshots to be stored

workingDir = “/vmfs/volumes/54332bf4-gd3bf353-g45b-g2ft353b5545/snapshots”

Save the file and exit

Now you need to reload this vm to make the changes take affect.
# vim-cmd vmsvc/getallvms | grep Windows2003
13 Windows2003 [iSCSI-Datastore15] Windows2003/Windows2003 win2003 vmx-07
Here 13 is the vm id which you can find out using the above command
# vim-cmd vmsvc/reload 13
Now when you take snapshots the snapshot files and vm swap files will be created in a different location.

How to redirect vm’s swap file

In case you do not want vm swap file to be redirected to another location and you want it to the same parent directory.
Add an extra parameter in the Configuration Parameter option shown above
sched.swap.dir=”<path_to_vm_directory>”
For example
/vmfs/volumes/54332bf4-gd3bf353-g45b-g2ft353b5545/vmswap

Save the settings and exit. Now each time you take snapshot the snapshot files and vm swap files will be saved at specified different location.

 

To get a serial number remotely for any server/desktop/laptop

Posted on Updated on


Run this command:

wmic /node:[remote computer name] bios get serialnumber

Or, if you would like to output to a text file:

set myfile = [The full UNC path with filename e.g. \\server\share\filename.txt]

wmic /append:%myfile% /node:[remote computer name] bios get serialnumber

Just open the shell with Admin rights, and type:

Get-WmiObject -ComputerName [remote computer name] -Class Win32_BIOS

or the short version:

gwmi -comp [remote computer name] -cl win32_bios

wmic cpu get name,CurrentClockSpeed,MaxClockSpeed This command will tell you the system motherboard (that happen to be the name) and it’s UUID

wmic bios get name,serialnumber,version This will tells you the name if your BIOS, current version and it’s serial number if there is any.

wmic csproduct  Computer system product information from SMBIOS 

Installing ADSI edit in Windows Server 2003

Posted on Updated on


The ADSI (Active Directory ServiceInterfaces) editor is a management console that comes along with the Windows Server support tools. Using this you can edit each and every attribute of the objects present in your active directory database. The support tools for the Windows Server OS is present in the OS installation CD. It is located at [CDDRIVE]:\SUPPORT\TOOLS\SUPTOOLS.MSI
If you don’t have the OS CD you can download it from Microsoft
Download Windows Server 2003 Support Tools
After installation got to Start -> Run and type adsiedit.msc to get the ADSI edit console.
If you get an error message saying adsiedit.msc is not found you have to register the DLL file required for it manually.
To do this go to Start-> Run and type regsvr32 adsiedit.dll.

How to change the thick or thin provisioning of a virtual disk

Posted on Updated on


Caution: Before following these procedures, it is highly recommended that you have a valid backup of the virtual machine and enough space to convert the virtual machine’s disk(s) from thin to thick.

To change the provisioning of a virtual machine base disk from thin to thick from the Datastore Browser:

  1. Power off the virtual machine.
  2. In vSphere Client, right-click the virtual machine in the inventory.
  3. Click Edit Settings to display the Virtual Machine Properties dialog box.
  4. Click the Hardware tab and select the appropriate hard disk in the Hardware list.Note: The Disk Provisioning Type section on the right displays either Thin Provision or Thick Provision. If the disk provision type is Thick, disk provisioning has already taken place. In this case, the disk provisioning is Thin.
  5. Click Cancel to exit out of Virtual Machine Properties dialog box.
  6. Click the Summary tab of the virtual machine.
  7. Under Resources, right-click the datastore where the virtual machine resides and click Browse Datastore.
  8. Double-click the virtual machine folder to display the .vmdk file.
  9. Right-click the .vmdk file, and click Inflate. The Inflate option converts the disk to thick provisioned.
  10. Reload the .vmx file. For more information see Reloading a vmx file without removing the virtual machine from inventory (1026043).

Notes:

  • If the Inflate option is grayed out, this indicates that the virtual machine is not powered off or that it is not thin provisioned.
  • There should be no snapshots and the conversion is performed on the base disk.

To convert a virtual machine base disk from thick to thin provisioning by changing the datastore and using offline virtual machine migration:

Note: This process requires more than one datastore. If only a single datastore exists, you can clone the virtual machine to a destination machine with thin provisioned disks instead of migrating.

  1. Power off the virtual machine.
  2. Right-click the virtual machine, and click Migrate.
  3. Click Change datastore.
  4. Click Next, and select a datastore that is not the same as the current datastore.
  5. From the dropdown, select the Thin Provision virtual disk format.
  6. Click Next, then Finish. You can monitor the progress of the conversion in the Tasks and Events view in vCenter Server.

Follow the below steps to do Storage vMotion from vSphere Webclient for vSphere 5.5:

  1. Right-click the virtual machine and select Migrate.
    1. To locate a virtual machine, select a datacenter, folder, cluster, resource pool, host, or vApp.
    2. Click the Related Objects tab and click Virtual Machines.
  2. Select Change datastore and click Next.
  3. Select “Thin Provision” for the virtual machine’s disks and click Next
  4. Select a virtual machine storage policy from the VM Storage Policy drop-down menu, click Next
  5. Select the datastore location where you want to store the virtual machine files and click Next.
  6. Review the information on the Review Selections page and click Finish.

How to Enable Remote Logins in a Windows server

Posted on Updated on


Locate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\

fDenyTSConnections value is set to 1 by default to disable remote desktop; editing the value remotely to 0 will enable remote desktop

How to download Cleanwipe Utility

Posted on Updated on


To download the utility, open the following web page in a browser:
https://fileshare.symantec.com
Log in with the following information:

Login ID: cleanwipeutility
Password: CL3@nw!p3

Once you have downloaded the utility, please follow these instructions.

Note: The .zip file may be password protected.
Un-Zip Password: symantec

Keyboard or mouse do not work in a hosted virtual machine

Posted on Updated on


To troubleshoot a misbehaving mouse or keyboard:
  1. Confirm that the virtual machine guest window currently has focus by clicking into the virtual machine’s console window. Keyboard or mouse input is only directed to the virtual machine when it has focus or is in full-screen mode.
  2. If your mouse is slow to respond or if it is working erratically, change the optimization settings. For more information, see Mouse movement is not smooth in a hosted virtual machine (1033416).
  3. If you are using a wireless mouse or keyboard, ensure that you have not connected it to the virtual machine by removing and re-adding the USB Controller from the virtual machine. For more information, see the Workstation Help topic Add a USB Controller to a Virtual Machine.
  4. Restart your host computer.
  5. For Windows hosts, use the Windows System Configuration (msconfig) utility to eliminate software and processes as possible causes. For more information, see Using the Windows System Configuration utility (1004010).
  6. For Linux hosts, start Linux in a mode that disables start daemons (typically run level 2; if your host lacks this, you may need to start in single-user mode). For more information, see Changing Linux run levels (1004015) or your operating system documentation.
    Note: These next steps require a second mouse/keyboard. For more information, see Connecting a second mouse or keyboard directly to a hosted virtual machine (1033435).
  7. Look for non-Microsoft, non-VMware mouse/keyboard drivers or software installed in the virtual machine, and remove them.
  8. Re-install VMware Tools. For details, see Overview of VMware Tools (340).

Syslog Server storage logs size calculation

Posted on Updated on


Syslog Server storage calculation:
I want to modify the settings so that my logs size is upped from 2mb to 10mb and we rotate after 40 logs not 20.Here we need to do some planning to see if we have enough free space.

Count hosts: 100
Current size log max: 2
Current rotation count: 20
Total possible MB used: 100x2x20 = 4,000MB  (4gb)

Count hosts: 100
Desired size log max: 10
Desired  rotation count: 40
Total possible MB used: 100x10x40=40,000MB (40GB)

So the drive where your logs are stored would need 40gbfree in the above example to be able to service future demands.
How to modify the VMware Syslog Collector configuration after it is installed:

  1. Make a backup of the file:vCenter Server 5.5 and lower%PROGRAMDATA%\VMware\VMware Syslog Collector\vmconfig-syslog.xml
    vCenter Server 6.0: %PROGRAMDATA%\VMware\vCenterServer\cfg\vmsyslogcollector\config.xml
  2. Open the copied file using a text editor.
  3. Under <defaultValues>, change any of the options to the required values.For example, to increase the log file size to 10 MB and to decrease the number of files retained to 20, modify the attributes:<defaultValues>
<port>514</port>
<protocol>TCP,UDP</protocol>
<maxSize>10</maxSize>
<rotate>20</rotate>
<sslPort>1514</sslPort>

</defaultValues>Note: This configuration in vCenter Server overrides the ESXi host configuration file.

  1. Save and close the file.
  2. Stop the VMware Syslog Collector service.
  3. Remove the file:

    vCenter Server 5.5 and lower
    %PROGRAMDATA%\VMware\VMware Syslog Collector\vmconfig-syslog.xml
    vCenter Server 6.0%PROGRAMDATA%\VMware\vCenterServer\cfg\vmsyslogcollector\config.xml
  4. Rename the copy of the modified file to:vCenter Server 5.5 and lower%PROGRAMDATA%\VMware\VMware Syslog Collector\vmconfig-syslog.xml
    vCenter Server 6.0%PROGRAMDATA%\VMware\vCenterServer\cfg\vmsyslogcollector\config.xml
  5. Start the VMware Syslog Collector service. It may be required to restart the syslog service on the ESXi host if logs are no longer updating on the Syslog Server. To restart the syslog service, see VMware ESXi 5.x host stops sending syslogs to remote server (2003127).

 

The maximum supported number of hosts for use with each vSphere Syslog Collector instance is 30, however depending on the load generated by your environment, you may encounter issues below this number.

To work around this issue, you can deploy multiple instances of vSphere Syslog Collector on separate Windows machine which allows you to distribute the load.

If the customer wishes to continue using vSphere Syslog Collector with more than 30 hosts (current maximum for syslog collector). There are no plans to increase the supported number of hosts. The windows event log error does not apply to the appliance, in some instances we receive no error message but the service simply stops responding or collecting logs.
Alternatively, investigate a more scalable solution such a VMware vRealize Log Insight.

How to restart Management agents on ESXi host

Posted on Updated on


Restarting the Management agents on ESXi

To restart the management agents on ESXi:

From the Direct Console User Interface (DCUI):

  1. Connect to the console of your ESXi host.
  2. PressF2 to customize the system.
  3. Log in asroot.
  4. Use theUp/Down arrows to navigate to Restart Management Agents.

    Note: In ESXi 4.1 and ESXi 5.0, 5.1, 5.5 and 6.0 this option is available under Troubleshooting Options.

  5. PressEnter.
  6. PressF11 to restart the services.
  7. When the service has been restarted, pressEnter.
  8. PressEsc to log out of the system.

From the Local Console or SSH:

  1. Log in to SSH or Local console as root.
  2. Run these commands:

    /etc/init.d/hostd restart
    /etc/init.d/vpxa restart

    Note: In ESXi 4.x, run this command to restart thevpxa agent:

    service vmware-vpxa restart

    Alternatively:

  • To reset the management network on a specific VMkernel interface, by default vmk0, run the command:

    esxcli network ip interface set -e false -i vmk0; esxcli network ip interface set -e true -i vmk0

    Note: Using a semicolon (;) between the two commands ensures the VMkernel interface is disabled and then re-enabled in succession. If the management interface is not running on vmk0, change the above command according to the VMkernel interface used.

  • To restart all management agents on the host, run the command:

    services.sh restart

    Caution:

  • Check if LACP is enabled on DVS for version 5.x and above. For more information, see vSphere 5.0 Networking Guide

If LACP is not configured, the services.sh script can be safely executed.

How to get Serial number and System information of ESXi host remotely using putty

Posted on Updated on


Get hardware serial number using this command from putty

esxcfg-info | grep “Serial N”

Type the following command from the command line on the service console and you will get some Vendor details and serial number information.

/usr/sbin/dmidecode |grep -A4 “System Information”

Multipathing policies in ESXi 5.x and ESXi/ESX 4.x

Posted on Updated on


These are referred to as Path Selection Plug-ins (PSP), and are also called Path Selection Policies.

These pathing policies can be used with VMware ESXi 5.x and ESXi/ESX 4.x:

  • Most Recently Used (MRU): Selects the first working path, discovered at system boot time. If this path becomes unavailable, the ESXi/ESX host switches to an alternative path and continues to use the new path while it is available. This is the default policy for Logical Unit Numbers (LUNs) presented from an Active/Passive array. ESXi/ESX does not return to the previous path if, or when, it returns; it remains on the working path until it, for any reason, fails.

    Note: The preferred flag, while sometimes visible, is not applicable to the MRU pathing policy and can be disregarded.

  • Fixed (Fixed): Uses the designated preferred path flag, if it has been configured. Otherwise, it uses the first working path discovered at system boot time. If the ESXi/ESX host cannot use the preferred path or it becomes unavailable, the ESXi/ESX host selects an alternative available path. The host automatically returns to the previously defined preferred path as soon as it becomes available again. This is the default policy for LUNs presented from an Active/Active storage array.
  • Round Robin (RR): Uses an automatic path selection rotating through all available paths, enabling the distribution of load across the configured paths.
    • For Active/Passive storage arrays, only the paths to the active controller will be used in the Round Robin policy.
    • For Active/Active storage arrays, all paths will be used in the Round Robin policy.

    Note: For logical Units associated with Microsoft Cluster Service (MSCS) and Microsoft Failover Clustering virtual machines, the Round Robin pathing policy is supported only on ESXi 5.5 and later.

  • Fixed path with Array Preference: The VMW_PSP_FIXED_AP policy was introduced in ESXi/ESX 4.1. It works for both Active/Active and Active/Passive storage arrays that support Asymmetric Logical Unit Access (ALUA). This policy queries the storage array for the preferred path based on the array’s preference. If no preferred path is specified by the user, the storage array selects the preferred path based on specific criteria.

    Note: The VMW_PSP_FIXED_AP policy has been removed from ESXi 5.0. For ALUA arrays in ESXi 5.0, the MRU Path Selection Policy (PSP) is normally selected but some storage arrays need to use Fixed. To check which PSP is recommended for your storage array, see the Storage/SAN section in the VMware Compatibility Guide or contact your storage vendor.

Notes:

  • These pathing policies apply to VMware’s Native Multipathing (NMP) Path Selection Plug-ins (PSP). Third-party PSPs have their own restrictions.
  • Round Robin is not supported on all storage arrays. Please check with your array documentation or storage vendor to verify that Round Robin is supported and/or recommended for your array and configuration. Switching to a unsupported or undesirable pathing policy can result in connectivity issues to the LUNs (in a worst-case scenario, this can cause an outage).

Warning: VMware does not recommend changing the LUN policy from Fixed to MRU, as the automatic selection of the pathing policy is based on the array that has been detected by the NMP PSP.

Dell ExtPart Partion Utility Tool

Posted on Updated on


The ExtPart utility provides support for online volume expansion of NTFS formatted basic disks.

This is a self extracting file that will install the extpart.exe utility. No reboot is necessary.

File Format:Hard-Drive
File Name:ExtPart.exe
Download Type:HTTP
File Size:36KB
Format DescriptionThis file format consists of an archive of files that may be decompressed to a directory on the hard drive. The installation can then be done from that directory.

 

RVTools 3.7

Posted on Updated on


RVTools

RVTools is a windows .NET 2.0 application which uses the VI SDK to display information about your virtual machines and ESX hosts. Interacting with VirtualCenter 2.5, ESX Server 3.5, ESX Server 3i, VirtualCenter 4.x, ESX Server 4.x, VirtualCenter 5.0, VirtualCenter Appliance, ESX Server 5.0, VirtualCenter 5.1, ESX Server 5.1, VirtualCenter 5.5, ESX Server 5.5. RVTools is able to list information about VMs, CPU, Memory, Disks, Partitions, Network, Floppy drives, CD drives, Snapshots, VMware tools, Resource pools, Clusters, ESX hosts, HBAs, Nics, Switches, Ports, Distributed Switches, Distributed Ports, Service consoles, VM Kernels, Datastores, Multipath info and health checks. With RVTools you can disconnect the cd-rom or floppy drives from the virtual machines and RVTools is able to update the VMware Tools installed inside each virtual machine to the latest version.

Version 3.7 (March, 2015)

VI SDK reference changed from 5.0 to 5.5
Extended the timeout value from 10 to 20 minutes for really big environments
New field VM Folder on vCPU, vMemory, vDisk, vPartition, vNetwork, vFloppy, vCD, vSnapshot and vTools tabpages
On vDisk tabpage new Storage IO Allocation Information
On vHost tabpage new fields: service tag (serial #) and OEM specific string
On vNic tabpage new field: Name of (distributed) virtual switch
On vMultipath tabpage added multipath info for path 5, 6, 7 and 8
On vHealth tabpage new health check: Multipath operational state
On vHealth tabpage new health check: Virtual machine consolidation needed check
On vInfo tabpage new fields: boot options, firmware and Scheduled Hardware Upgrade Info
On statusbar last refresh date time stamp
On vhealth tabpage: Search datastore errors are now visible as health messages
You can now export the csv files separately from the command line interface (just like the xls export)
You can now set a auto refresh data interval in the preferences dialog box
All datetime columns are now formatted as yyyy/mm/dd hh:mm:ss
The export dir / filenames now have a formated datetime stamp yyyy-mm-dd_hh:mm:ss
Bug fix: on dvPort tabpage not all networks are displayed
Overall improved debug information
Download link: http://robware.net/index.php/register

Documentation: http://robware.net/download/RVTools.pdf

Installing Disk Cleanup In Windows 2008 Without Rebooting The Server

Posted on Updated on


The Disk Cleanup executable file cleanmgr.exe and the associated Disk Cleanup button are not present in Windows Server® 2008 or in Windows Server® 2008 R2 by default. This is by design, as the Disk Cleanup button is part of the Desktop Experience feature. In order to have Disk Cleanup button appear on a disk’s Properties dialog, you will need to install the Desktop Experience feature.

So in order to use cleanmgr.exe you’ll need to copy two files that are already present on the server, cleanmgr.exe and cleanmgr.exe.mui. Use the following table to locate the files for your operating system.

Windows Server 2008 R2 64 bit

C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe

Windows Server 2008 R2 64-bit

C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui

Windows Server 2008 64-bit

C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.0.6001.18000_en-us_b9f50b71510436f2\cleanmgr.exe.mui

Windows Server 2008 64-bit

C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_c962d1e515e94269\cleanmgr.exe.mui

Windows Server 2008 32-bit

C:\Windows\winsxs\x86_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.0.6001.18000_en-us_5dd66fed98a6c5bc\cleanmgr.exe.mui

Windows Server 2008 32-bit

C:\Windows\winsxs\x86_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_6d4436615d8bd133\cleanmgr.exe
Once you’ve located the files move them to the following locations:

1. Cleanmgr.exe should go in %systemroot%\System32

2. Cleanmgr.exe.mui should go in %systemroot%\System32\en-US

You can now launch the Disk cleanup tool by running Cleanmgr.exe from the command prompt or by clicking Start and typing Cleanmgr into the Search bar.

 

Restart the domain controller in Directory Services Restore Mode locally

Posted on Updated on


If you have physical access to a domain controller, you can restart the domain controller in Directory Services Restore Mode locally. Restarting in Directory Services Restore Mode takes the domain controller offline. In this mode, the server is not functioning as a domain controller.

When you start Windows Server 2003 in Directory Services Restore Mode, the local Administrator account is authenticated by the local Security Accounts Manager (SAM) database. Therefore, logging on requires that you use the local administrator password, not an Active Directory domain password. This password is set during Active Directory installation when you provide the password for Directory Services Restore Mode.

Administrative credentials

To perform this procedure, you must provide the Administrator password for Directory Services Restore Mode.

To restart the domain controller in Directory Services Restore Mode locally

  1. Restart the domain controller.
  2. When the screen for selecting an operating system appears, press F8.
  3. On the Windows Advanced Options menu, select Directory Services Restore Mode.
  4. When you are prompted, log on as the local administrator.

Change the static IP address of a domain controller

Posted on Updated on


Administrative Credentials

To perform this procedure, you must be a member of the Domain Admins group in the domain of the domain controller whose IP address you are changing.

To change the static IP address of a domain controller

  1. Log on locally (also known as interactively) to the system console of the domain controller whose IP address you want to change. If you are not able to log on to the domain controller by using the domain, you may have to start the domain controller in Directory Services Restore Mode (DSRM). For more information, see Restart the domain controller in Directory Services Restore Mode locally (https://lazyadminblog.wordpress.com/2015/04/11/restart-the-domain-controller-in-directory-services-restore-mode-locally/).

On the desktop, right-click My Network Places, and then click Properties.

  1. In theNetwork Connections dialog box, right-click Local Area Connection, and then click Properties.
  2. In theLocal Area Connection Properties dialog box, double-click Internet Protocol (TCP/IP).
  3. In theInternet Protocol (TCP/IP) Properties dialog box, in the IP address box, type the new address.
  4. In theSubnet mask box, type the subnet mask.
  5. In theDefault gateway box, type the default gateway.
  6. In thePreferred DNS server box, type the address of the DNS server that this computer contacts.
  7. In theAlternate DNS server box, type the address of the DNS server that this computer contacts if the preferred server is unavailable.
  8. If this domain controller uses WINS servers, clickAdvanced and then, in the Advanced TCP/IP Settings dialog box, click the WINS
  9. If an address in the list is no longer appropriate, click the address, and then clickEdit.
  10. In theTCP/IP WINS Server dialog box, type the new address, and then click OK.
  11. Repeat steps 11 and 12 for all addresses that need to be changed, and then clickOK twice to close the TCP/IP WINS Server dialog box and the Advanced TCP/IP Settings dialog box.
  12. ClickOK to close the Internet Protocol (TCP/IP) Properties dialog box.

After you change the IP address of a domain controller, you should run the ipconfig /registerdns command to register the host record and dcdiag /fix command to ensure that service records are appropriately registered with DNS. For more information, see Dcdiag Overview and subordinate topics for additional information about the Dcdiag tool (https://lazyadminblog.wordpress.com/2015/04/11/dcdiag-overview/).

Changing the IP settings of a server does not affect the share resources or shared permissions on that server, if the name resolution structure DNS and WINS settings are correctly configured. However, if network drives or passive connections (connections that are made manually from a command prompt or run line) are mapped using the IP address, an update is required. For example, if a client computer has G: drive mapped using the following command net use g: \\192.168.0.199\data and the IP address of the server that hosts the Data shared folder is changed from 192.168.0.199 to 192.168.1.200, the new G: drive mapping command should be changed to net use g: \\192.168.1.200\data. A better solution would be to ensure that DNS name resolution is working properly and to use the server name, as opposed to the IP address, in the command. For example, if the server name is DC1, the command to map a G: drive to the Data share on the server is net use g: \\dc1\data. It changes only if the server name changes; it is not affected if the IP address of the server changes.

Using esxtop to identify storage performance issues for ESX / ESXi (multiple versions) (1008205)

Posted on Updated on


The interactive esxtop utility can be used to provide I/O metrics over various devices attached to a VMware ESX host.

Configuring monitoring using esxtop

 To monitor storage performance per HBA:

  1. Start esxtop by typing esxtop at the command line.
  2. Press d to switch to disk view (HBA mode).
  3. To view the entire Device name, press SHIFT + L and enter 36 in Change the name field size.
  4. Press f to modify the fields that are displayed.
  5. Press b, c, d, e, h, and j to toggle the fields and press Enter.
  6. Press s and then to alter the update time to every 2 seconds and press Enter.
  7. See Analyzing esxtop columns for a description of relevant columns. For more information, see Interpreting esxtop Statistics.

Note: These options are available only in VMware ESX 3.5 and later.

To monitor storage performance on a per-LUN basis:

  1. Start esxtop by typing esxtop from the command line.
  2. Press u to switch to disk view (LUN mode).
  3. Press f to modify the fields that are displayed.
  4. Press b, c, f, and h to toggle the fields and press Enter.
  5. Press s and then 2 to alter the update time to every 2 seconds and press Enter.
  6. See Analyzing esxtop columns for a description of relevant columns. For more information, see Interpreting esxtop Statistics.

To increase the width of the device field in esxtop to show the complete naa id:

  1. Start esxtop by typing esxtop at the command line.
  2. Press u to switch to the disk device display.
  3. Press L to change the name field size.Note: Ensure to use uppercase L.
  4. Enter the value 36 to display the complete naa identifier.

To monitor storage performance on a per-virtual machine basis:

  1. Start esxtop by typing esxtop at the command line.
  2. Type v to switch to disk view (virtual machine mode).
  3. Press f to modify the fields that are displayed.
  4. Press b, d, e, h, and j to toggle the fields and press Enter.
  5. Press s and then 2 to alter the update time to every 2 seconds and press Enter.
  6. See Analyzing esxtop columns for a description of relevant columns. For more information, see Interpreting esxtop Statistics.

 

Analyzing esxtop columns

Refer to this table for relevant columns and descriptions of these values:

Column  Description
CMDS/s This is the total amount of commands per second and includes IOPS (Input/Output Operations Per Second) and other SCSI commands such as SCSI reservations, locks, vendor string requests, unit attention commands etc. being sent to or coming from the device or virtual machine being monitored.In most cases, CMDS/s = IOPS unless there are a lot of metadata operations (such as SCSI reservations)
DAVG/cmd This is the average response time in milliseconds per command being sent to the device.
KAVG/cmd This is the amount of time the command spends in the VMkernel.
GAVG/cmd This is the response time as it is perceived by the guest operating system. This number is calculated with the formula: DAVG + KAVG = GAVG

These columns are for both reads and writes, whereas xAVG/rd is for reads and xAVG/wr is for writes. The combined value of these columns is the best way to monitor performance, but high read or write response time it may indicate that the read or write cache is disabled on the array. All arrays perform differently, however, DAVG/cmd, KAVG/cmd, and GAVG/cmd should not exceed more than 10 milliseconds (ms) for sustained periods of time.

Note: VMware ESX 3.0.x does not include direct functionality to monitor individual LUNs or virtual machines using esxtop. Inactive LUNs lower the average for DAVG/cmd, KAVG/cmd, and GAVG/cmd. These values are also visible from the vCenter Server performance charts. For more information, see the Performance Charts section in the Basic System Administration Guide.

If you experience high latency times, investigate current performance metrics and running configuration for the switches and the SAN targets. Check for errors or logging that may suggest a delay in operations being sent to, received, and acknowledged. This includes the array’s ability to process I/O from a spindle count aspect, or the array’s ability to handle the load presented to it.

If the response time increases to over 5000 ms (or 5 seconds), VMware ESX will time out the command and abort the operation. These events are logged; abort messages and other SCSI errors can be reviewed in these logs:

  • ESX 3.5 and 4.x – /var/log/vmkernel
  • ESXi 3.5 and 4.x – /var/log/messages 
  • ESXi 5.x and later – /var/log/vmkernel.log

The type of storage logging you may see in these files depends on the configuration of the server. You can find the value of these options by navigating to Host > Configuration > Advanced Settings > SCSI > SCSI.Log* or SCSI.Print*.

Connecting to a virtual machine console fails with the error: The VMRC Console has Disconnected. Trying to reconnect (2050470)

Posted on Updated on


Error: The VMRC Console has Disconnected.. Trying to reconnect

If this happens, then the VM will not be reachble on the network and you cannot see black screen on the VM console.

To fix this, kill the vmware-vmrc.exe*32 service from Windows Task Manager and then open the console again.

EVC and CPU Compatibility FAQ

Posted on


What is EVC?

EVC is short for Enhanced vMotion Compatibility. EVC allows you to migrate virtual machines between different generations of CPUs.

What is the benefit of EVC?

Because EVC allows you to migrate virtual machines between different generations of CPUs, with EVC you can mix older and newer server generations in the same cluster and be able to migrate virtual machines with vMotion between these hosts. This makes adding new hardware into your existing infrastructure easier and helps extend the value of your existing hosts. With EVC, full cluster upgrades can be achieved with no virtual machine downtime whatsoever. As you add new hosts to the cluster, you can migrate your virtual machines to the new hosts and retire the older hosts.

How do I use EVC?

EVC is enabled for a cluster in the VirtualCenter or vCenter Server inventory. After it is enabled, EVC ensures that migration with vMotion is possible between any hosts in the cluster. Only hosts that preserve this property can be added to the cluster.

How does it work?

After EVC is enabled, all hosts in the cluster are configured to present the CPU features of a user-selected processor type to all virtual machines running in the cluster. This ensures CPU compatibility for vMotion even though the underlying hardware might be different from host to host. Identical CPU features are exposed to virtual machines regardless of which host they are running on, so that the virtual machines can migrate between any hosts in cluster.

Can migrations with vMotion still fail for virtual machines within an EVC cluster?

Yes. More factors than CPU compatibility are used to determine vMotion compatibility. For example, if the virtual machine does not reside on storage shared by the source and destination hosts, then migration with vMotion cannot occur between these hosts.

Does EVC allow AMD and Intel CPUs to be vMotion compatible?

No. An EVC-enabled cluster only allows CPUs from a single vendor in the cluster. VirtualCenter and vCenter Server do not allow you to add a host from a different CPU vendor into an EVC-enabled cluster.

What EVC modes are available?

ESXi/ESX 3.5 Update 2 and later supports two EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • Intel “Merom” Generation (Intel Xeon Core 2)

In the earlier ESXi/ESX 3.5 releases, these modes were labeled simply AMD and Intel. Later updates use the names listed above.

ESXi/ESX 4.0 supports these EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)

ESXi/ESX 4.0 Update 1 and later supports these EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)
  • Intel “Westmere” Generation (Intel Xeon 32nm Core i7)

ESXi/ESX 4.1 supports these EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • AMD Opteron Generation 3 (no 3DNow!) (Greyhound)
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)
  • Intel “Westmere” Generation (Intel Xeon 32nm Core i7)

ESXi 5.0 supports these EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • AMD Opteron Generation 3 (no 3Dnow!) (Greyhound)
  • AMD Opteron Generation 4 (Bulldozer)
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)
  • Intel “Westmere” Generation (Intel Xeon 32nm Core i7)
  • Intel “Sandy Bridge” Generation

ESXi 5.1 supports these EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • AMD Opteron Generation 3 (no 3Dnow!) (Greyhound)
  • AMD Opteron Generation 4 (Bulldozer)
  • AMD Opteron “Piledriver” Generation
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)
  • Intel “Westmere” Generation (Intel Xeon 32nm Core i7)
  • Intel “Sandy Bridge” Generation
  • Intel “Ivy Bridge” Generation
ESXi 5.5 supports these EVC modes:
  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • AMD Opteron Generation 3 (no 3Dnow!) (Greyhound)
  • AMD Opteron Generation 4 (Bulldozer)
  • AMD Opteron “Piledriver” Generation
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)
  • Intel “Westmere” Generation (Intel Xeon 32nm Core i7)
  • Intel “Sandy Bridge” Generation
  • Intel “Ivy Bridge” Generation

ESXi 6.0 supports these EVC modes:

  • AMD Opteron Generation 1 (Rev. E)
  • AMD Opteron Generation 2 (Rev. F)
  • AMD Opteron Generation 3 (Greyhound)
  • AMD Opteron Generation 3 (no 3Dnow!) (Greyhound)
  • AMD Opteron Generation 4 (Bulldozer)
  • AMD Opteron “Piledriver” Generation
  • Intel “Merom” Generation (Intel Xeon Core 2)
  • Intel “Penryn” Generation (Intel Xeon 45nm Core2)
  • Intel “Nehalem” Generation (Intel Xeon Core i7)
  • Intel “Westmere” Generation (Intel Xeon 32nm Core i7)
  • Intel “Sandy Bridge” Generation
  • Intel “Ivy Bridge” Generation
  • Intel “Haswell” Generation

Which CPUs are compatible with each EVC mode?

To determine the EVC modes compatible with your CPU, search the VMware Compatibility Guide. Search for the server model or CPU family, and click the entry in the CPU Series column to display the compatible EVC modes.

What are the differences between the modes?

Each mode corresponds very closely to the features available in processors with the same name. Newer processors and their corresponding modes include additional features such as new instructions. For example, the Intel Xeon Core i7 processor added the SSE4.2 instruction set. These instructions are not available in earlier processors or their corresponding EVC modes.

AMD EVC modes expose these features:

EVC Mode
Available Features
AMD Opteron Generation 1 All features of AMD Opteron Rev. E CPUs
AMD Opteron Generation 2 All features of AMD Opteron Generation and additional CPU features including CMPXCHG16B and RDTSCP
AMD Opteron Generation 3 All features of AMD Opteron Generation 2 and additional CPU features including SSE4A, MisAlignSSE, POPCOUNT, ABM (LZCNT)
AMD Opteron Generation 3 (no 3Dnow!) Applies baseline feature set of AMD Opteron Generation 3 (Greyhound) processors, with 3DNow! support removed, to all hosts in the cluster.

This mode allows you to prepare clusters containing AMD hosts to accept AMD processors without 3DNow! support.

AMD Opteron Generation 4 Applies baseline feature set of AMD Opteron Generation 4 (Bulldozer) processors to all hosts in the cluster.

This EVC mode exposes additional CPU features including SSSE3, SSE4.1, AES, PCLMULQDQ, XSAVE, AVX, XOP and FMA4.

AMD Opteron “Piledriver” Generation Applies baseline feature set of AMD Opteron “Piledriver” Generation processors to all hosts in the cluster.

This EVC mode exposes additional CPU features including FMA3 (three operand FMA, aka Intel’s FMA), BMI1 and TBM.

 

Intel EVC modes expose these features:

EVC Mode Available Features
Intel “Merom” Generation (Intel Xeon Core2) All features of Intel Core2 CPUs
Intel “Penryn” Generation (Intel Xeon 45nm Core2) All features of Intel Core2 CPUs and additional CPU features including SSE4.1
Intel “Nehalem” Generation (Intel Xeon Core i7) All features of Intel Core2 CPUs and additional CPU features including SSE4.2 and POPCOUNT
Intel “Westmere” Generation (Intel Xeon 32nm Core i7) Applies baseline feature set of Intel Xeon 32nm Corei7 (Westmere) processors to all hosts in the cluster. Compared to the Intel Xeon Corei7 mode, this EVC mode exposes additional CPU features including AES and PCLMULQDQ.

Note: Intel i3/i5 Xeon Clarkdale Series processors that do not support AESNI and PCLMULQDQ cannot be admitted to EVC modes higher than the Intel Xeon Corei7 mode.
Note: Intel® Atom™ C2300-C2700 processors support the Intel® “Westmere” Gen. EVC baseline although their architecture is different from the architecture of the Intel® “Westmere” Generation processors.

Intel “Sandy Bridge” Generation Applies baseline feature set of Intel “Sandy Bridge” Generation processors to all hosts in the cluster.

This EVC mode exposes additional CPU features including AVX, XSAVE and ULE.

Note: Some Sandy Bridge microarchitecture processors do not provide the full Sandy Bridge feature set. Such processors do not support EVC mode; they will only be admitted to the Intel Nehalem Generation mode or below.

Intel “Ivy Bridge” Generation Applies baseline feature set of Intel “Ivy Bridge” Generation processors to all hosts in the cluster.

This EVC mode exposes additional CPU features including ENFSTRING, F16C, FSGSBASE, SMEP and CPUID Faulting.

Intel “Haswell” Generation
Applies the baseline feature set of Intel “Haswell” Generation processors to all hosts in the cluster.

This EVC mode exposes additional CPU features including Advanced Vector Extensions 2, fused multiply-adds, Transactional Synchronization Extensions, and new bit manipulation instructions.

How can I find the EVC mode supported by a host?

In the vSphere Client connected to vCenter Server 4.0, the host Summary tab indicates whether EVC is enabled, and displays the current EVC mode for the host. Click the blue icon next to the EVC mode to display a list of all the supported EVC modes for the host.

VMware also provides a free CPU identification utility that displays compatible EVC modes, in addition to other CPU features. You can download this utility and boot the host from the ISO image.

If I have an EVC-enabled cluster set to a particular EVC mode, and I have a host outside the cluster that matches the EVC mode, can I migrate a virtual machine with vMotion between that host and the cluster?

Yes, in both directions.

How do I handle Intel Xeon E3 and E5 Processors or Intel Xeon X-series, E-series, L-series Processors that have different revision or series numbers (e.g. v2, v3, v4 or x5680, x5687, x5690)

When enabling EVC for a cluster with Intel processors of the Xeon E3 or Xeon E5 family that have different revision numbers (v2, v3, v4), an EVC baseline is required. This is due to new instruction sets being available in the different revisions.  Although the processors will be the same EVC baseline, this is required for the processors to all present the same instruction sets to the virtual machines.

As with Xeon process with different revisions, when enabling EVC for a cluster with Intel processors of the same Xeon family (e.g. E56xx, X56xx, L56xx), an EVC baseline is required. This is due to new instruction sets being available in the different revisions.  Although the processors will be the same EVC baseline, this is required for the processors to all present the same instruction sets to the virtual machines.

What is the difference between EVC and the old CPUID masking feature (accessed from the Virtual Machine Settings dialog box, Options tab, CPUID mask option)?

The older masking feature involved applying manual masks to individual virtual machines. EVC takes effect on a whole cluster and all virtual machines in the cluster. More accurately, EVC affects the hosts themselves, making all the hosts in the cluster appear to be the same type of CPU hardware, even if they are different.

Why is the . vmx config file for the virtual machine updated with CPUID bits?

The .vmx file contains information about the features that the virtual machine is using. VirtualCenter and vCenter Server need this information to provide accurate vMotion compatibility checks. These values are unrelated to the old CPUID mask values that also appear in the .vmx file.

What happens when a host is removed from an EVC-enabled cluster?

When a host leaves an EVC-enabled cluster, it reverts to its normal behavior. New virtual machines started on that host can access all the features of the CPU, and are not limited by the EVC mode that was in effect while the host was in the EVC cluster. Note that virtual machines that were once able to migrate to the host might no longer be permitted to do so.

If I raise the EVC mode, will virtual machines be able to access the new features available in that mode?

Not until you power off and then power on the virtual machines. A reboot of the guest operating system is not sufficient. A virtual machine determines which features are available to it at power on, and cannot access any new features that are added until it is powered off.

What is an ill-behaved application, and why does it affect EVC?

An ill-behaved application is one that does not use CPU-vendor-recommended methods of detecting features supported on a CPU. The recommended method is to run the CPUID instruction and look for the correct feature bits for the capabilities the application is expected to use. Unsupported methods used by ill-behaved applications include try-catch-fail or inferring the features present from the CPU version information. When unsupported methods are used, an application might detect features on a host in an EVC cluster that are being masked from the virtual machines. The CPUID-masking MSRs provided by CPU vendors do not disable the actual features. Therefore, an application can still use masked features. If a virtual machine running such an application is then migrated with vMotion to a host that does not physically support those features, the application might fail. VMware is not aware of any commercially-available ill-behaved applications. For more information, see Detecting and Using CPU Features in Applications (1005763).

Can I create an EVC-enabled cluster if some of the hosts I want to add do not have AMD-V Extended Migration or Intel VT FlexMigration?

Yes. EVC-enabled clusters can contain hosts that do not feature AMD-V Extended Migration or Intel VT FlexMigration technology. For example, Intel Xeon Core2 processors do not have Intel VT FlexMigration technology, but can be added to clusters configured with an Intel Xeon Core2 EVC mode.

Can I add an ESXi/ESX 3.5 Update 1 or earlier host to an EVC-enabled cluster?

No. EVC is supported only on ESXi/ESX 3.5 Update 2 and later. vCenter Server does not permit the addition of hosts that do not provide support for EVC into an EVC-enabled cluster.

If I add newer hardware into an EVC-enabled cluster with a lower EVC mode, do I lose performance?

All CPU features provided by your host hardware are available to the hypervisor. Optimizations for CPU virtualization such as AMD-V and Intel VT-x or facilities for MMU virtualization such as AMD RVI or Intel EPT support are still used by the hypervisor. Only those CPU instructions that are unique to the new CPU are hidden from virtual machines when the host joins the EVC-enabled cluster. Typically this includes new SIMD instructions, such as the latest SSE additions. It is possible, but unlikely, that an application running in a virtual machine would benefit from these features, and that the application performance would be lower as the result of using an EVC mode that does not include the features. Check with the application vendor to determine which CPU features are used by the application.

How do I know when I can raise the EVC mode for a cluster?

You can raise the EVC mode for an EVC-enabled cluster if all hosts in the EVC cluster support the higher mode. This may occur periodically over time as older hosts are retired from the cluster and newer hosts are added. Use the Change EVC Mode dialog box to determine the EVC modes currently available to your cluster.
Can I enable EVC on an existing non-EVC enabled cluster with powered-on virtual machine guests?
For information related to vCenter Server 5.0, see CPU Compatibility and EVC in the vCenter Server and Host Management Guide.
For information related to vCenter Server 4.1, see CPU Compatibility and EVC in the vSphere Datacenter Administration Guide.

What is the impact on vSphere Cluster Features when I disable the EVC mode?

When disabling EVC mode on a cluster, it affects vSphere Cluster Features in the following ways:
  • vSphere HA (High Availability): vSphere HA is not impacted due to the failover power-cycling the virtual machines when starting them on a a new host. This allows the virtual machine to pick up the new CPU ID and allows it to start without a problem
  • vSphere DRS (Distributed Resource Scheduler):
    • vMotion:
      • Prior to power cycling the virtual machines:
        • They will maintain CPU level until a power cycle occurs.
        • DRS and vMotion operations will be the same as prior to disabling EVC mode.
      • Once the virtual machine is power cycled:
        • They are only able to move to other ESX/ESXi hosts that are at the same CPU generation or newer.
        • They will take on the CPU settings from the ESXi host it is running on.  This can prevent DRS operations and vMotioning of the virtual machine to another host due to CPU incompatibility.
    • Storage vMotion: Virtual machines are able to be moved to Storage vMotion with EVC mode disabled within a cluster
  • Swapfile Location: This is not impacted.

VMware View 4.0 Installation and Configuration

Posted on Updated on


VMware View 4 allows you to consolidate virtual desktops on datacenter servers and manage operating systems with improved reliability, better managementOverview

Features

  • Print from a virtual desktop to any local or networked printer that is defined on the client device.
  • Use multiple monitors With VMware PCoIP multiple-monitor support.
  • Access USB devices and other peripherals that are connected to the local device that displays your virtual desktop.
  • Use Microsoft Active Directory to manage access to virtual desktops and to manage policies.
  • Use the Web-based administrative console to manage virtual desktops from any location.
  • Use a template, or master image, to quickly create and provision pools of desktops.
  • Send updates and patches to virtual desktops without affecting user settings, data, or preferences.

Components of VMware View Enterprise:

  • View Connection Server 4 (Install on dedicated server)
  • View Agent (Install on virtual desktop VM)
  • View Client (Install on client physical desktop

Components of VMware View Premier:

  • View Connection Server 4 (Install on dedicated server)
  • View Composer 2 (Install on vCenter server)
  • View Agent (Install on virtual desktop VM)
  • View Client (Install on client physical desktop)
  • View Client Offline Desktop (Install on client physical laptop)

Pre-requisites:

Components Requirements
View Connection Server 4.0 ·  32bit or 64bit server

·  Pentium IV 2.0GHz processor or higher

·  2GB RAM or higher

·  One or more 10/100Mbps network interface cards (NIC)

·  Windows Server 2003 Standard or Enterprise with Service Pack 2

·  Valid View 4.0 license keys

·  Administrator rights on the domain user account used to install View Connection Server 4.0

·  VMware Infrastructure 3.0.2, VMware Infrastructure 3.5 Updates 3 or 4 or vSphere 4 Update 1

·  RSA Authentication Manager

·  Windows 2000, 2003 or 2008 Active Directory

View Composer 2.0 ·  Windows Server 2003 Standard or Enterprise with Service Pack 1 or Windows XP Professional with Service Pack 2

·  A supported SQL database.

View Administrator ·  Internet Explorer 7, Internet Explorer 8, Firefox 3.0 or Firefox 3.5

Installation Overview

The complete setup of Vmware View 4.0 environment includes 3 steps:

  • Installing VMware View Connection Server 4
  • Installing VMware View Composer 2
  • Configuring VMware View Connection Server 4 with View Manager

Installing VMware View Connection Server 4

Note:

  • The View Connection Server must be installed on its own dedicated server. It cannot be installed on the vCenter server.
  • It acts as a broker for client connections by authenticating directing incoming remote desktop user requests to a virtual desktop, physical desktop, or terminal server.
  1. Double Click “VMware-viewconnectionserver-4.xxxxx.exe” to start the installer.
  2. The installation wizard is displayed. Click Next.
  3. Read and Accept the VMware license agreement, Click Next.
  4. Enter the destination folder to install VMware View Composer. Click Next.
  5. Select “Standard” for the server instance type (as this is the first server). Click Next.
  6. Read and Accept the Microsoft ADAM license agreement, Click Next.
  7. Click Install to start the installation of the View Connection Server.
  8. Once the installation has completed Click Finish.

Installing VMware View Composer 2

Note:

  • VMware View Composer 2 is a component of View 4 Premier Edition.
  • Composer must be installed on the vCenter Server.
  1. Double Click “VMware-viewcomposer-2.0.0-210930.exe” to start the installer.
  1. You may receive a message about updating Microsoft .NET depending on which version you have installed. Click Ok to update .NET.
  1. After updating .NET (if it was required) the installation wizard is displayed. Click Next.
  1. Read and Accept the license agreement, Click Next.
  1. Enter the destination folder to install VMware View Composer. Click Next.
  1. VMware View Composer requires a MS SQL database. Enter the required details and Click Next.
  1. Confirm the SOAP port to use and note the SSL certificate being created. Click Next.
  1. Click Install to start the installation of Composer.
  1. Once the installation has completed Click Finish.
  1. It is required to restart the server to complete the installation. Click Yes to Restart.

Configuring VMware View Connection Server 4 with View Manager

  • View Manager 4 is a core component of VMware View 4 that is installed on the View Connection Server.
  • View Manager is a single console used to manage and deploy virtual desktops

Follow the below steps to configure the Vmware View Connection Sevrer

  1. Login to View Manager Administrator
  1. License the server.
  • Navigate to the “Configuration” tab and the “Product Licensing and Usage” section.
  • Click “Edit License” and enter the license.
  1. Add the vCenter Server.
  • Navigate to the “Configuration” tab and the “Servers” section.
  • Click “Add” to add the vCenter server.
  1. Enter the vCenter server details:
  • Server Address (FQDN)
  • Username
  • Password
  1. Optionally (If Premier Edition) enter View Composer Server details:
  • Click “Add” to add a Quick Prep domain.
  • Click Ok to save all the settings.
  1. Confirm the vCenter Server details are added correctly.
  2. Confirm the View Connection Server is activated.
  • Navigate to the “Configuration” tab and the “Registered Desktop Sources” section.
  1. Configure Connection Server Settings.
  • Select a Connection Server and Click “Edit”.
  • By default these settings do not need to be changed for View to work. However here you will find settings for smart cards, 2-factor authenication and backup of the View Manager Configuration.
  1. Configure any additional Administrators of VMware View Manager.
  • Navigate to the “Configuration” tab and the “Administrators” section.
  • Click “Add” to add any additionally groups that require administrator permissions in View Manager.
  • By default this is only BUILTIN\Administrators group on the connection server.
  1. Configure any require global settings.
  • Navigate to the “Configuration” tab and the “Global Settings” section.
  • Under the global settings configure any additional settings for session timeouts, login messages and forced logoff messages.
  • Click Ok to save the settings.

Zerto vs vSphere Replication

Posted on Updated on


Zerto vs vSphere Replication (focusing around data replication)

Zerto Replication vSphere Replication
Generally recommended for: Any size vSphere infrastructure Small infrastructures, remote offices, and non-critical applications
Max number of VMs protected per appliance and vCenter Server: 500/5000 500/500
Linked clone and template support: Yes No
Physical RDM and Virtual RDM support: Yes, virtual and physical mode RDMs are supported No/Yes, Physical RDMs are not supported but virtual RDM are supported
RPO range: Seconds 15 minutes to 24 hours
Application consistent?: Supports Windows VMs using VSS and Linux with Application Quesicense Only with Windows VMs using VSS
How VMs are chosen: VMs can be organized into Virtual Protection Groups VMs can be selected individually or multi-select but virtual protection grouping is not available
Automated failback support: Yes No, VMware recommends SRM
Allows you to plan, test, and automate failover and failback: Yes No, VMware recommends SRM
Compression included: Yes No, and neither does SRM
RE-IP addressing of virtual machines: Yes No, VMware recommends SRM
Cloning of recovery sites: Yes No
Point in time recovery: Yes, up to 5 days with standard recovery, up to 1 year with extended recovery using the Offsite Backup feature Yes, up to 24 snapshots
Compatible with vApps: Yes No
vCloud Director integration: Yes No
Snapshot-based? No Yes/No, VMware says that vSR doesn’t use snapshots technology but does use a modified version of CBT, still many of the same snapshot-based limitations apply. For example, vSR uses VM snapshots at the recovery site when recovering to a different point-in-time.

Zerto vs VMware Site Recovery Manager (focusing around automation of disaster recovery planning, testing, and automation)

Zerto SRM (with vSphere Replication)
Provides planning, testing, and execution of disaster recovery for vSphere: Yes Yes
Designed for: Zerto was designed for hypervisor-based replication AND disaster recovery orchestration SRM was designed for disaster recovery orchestration only
Licensed: Per-VM Per-VM
Replication granularity: Per-VM and/or Per- Virtual Protection Group Per-VM or multi-select but virtual protection grouping is not available
Configure consistency groups (virtual protection groups): Yes No
Replication recovery points: Yes, up to 5 days with standard recovery, up to 1 year with extended recovery using the Offsite Backup feature Yes, up to 24 snapshots
Compatibility: Zerto works with ESX 4.0 U1 and above. Zerto can replicate between different versions of vCenter. vSR works with ESX 5.x and above. SRM requires the same version of vCenter and SRM be installed at both sites.
Managed with: vSphere Client Plugin and stand-alone browser UI vSphere Client Plugin
Replication is performed with: Zerto Hypervisor-based replication vSphere Replication

A QUICK REFERENCE OF VSPHERE IDS

Posted on Updated on


Here is a list of a number of the different IDs used in the virtual infrastructure and how they are used:

  1. VC Instance UUID(aka serverGuid): This is a GUID that identifies the vCenter server.  This is accessible from the AboutInfo property in the VIM API.  The property name is AboutInfo#instanceUuid.  It’s set at install time and is persisted so the value is durable for a given VC instance.

To access this via PowerCLI you can use the following:

1

2

3

 

PS C:\> $vcenter = Connect-viserver vcsa-01a.corp.local -User Administrator@vsphere.local -Password VMware1!

PS C:\> $vcenter.InstanceUuid

d322b019-58d4-4d6f-9f8b-d28695a716c0

 

  1. The ESX Host UUIDis read by the ESX host from the System Management BIOS (SMBIOS). This UUID is not generated by VMware, it is unique to the hardware and is set in the BIOS by the vendor.

To access this via PowerCLI you can use the following:

1 (Get-VMHost | Select -first 1).ExtensionData.hardware.systeminfo.uuid

 

  1. VC-VM Instance UUID: This is the vc.uuid property in the VM vmx configuration file and also the instanceUuid property on the VmConfigInfo for a VirtualMachine in the VIM API.  This UUID is used by vCenter to uniquely identify VMs that it is managed.  vCenter assigns this UUID to the VM after it is created.  There are different workflows where a VM may not have a UUID initially or may have a duplicate.  vCenter actively looks over the VM inventory and will automatically patch the VM instance UUID if it sees a duplicate.

The scope of this uniqueness scan is a vCenter instance.  If there are duplicate VC-VM Instance UUIDs, they will not be detected as duplicates unless the VMs are managed by the same vCenter instance.  This value can be changed through the API.

To access this via PowerCLI you can use the following:

1

2

3

PS C:\> (Get-VM | Select -first 1).extensiondata.config.InstanceUUID

502e363d-393c-b0a4-8ede-639db30a625e

 

  1. VM SMBIOS UUID: This is the uuid.bios property in the VM vmx configuration file.  In the VIM API, this is the uuid property on the VmConfigInfo for a VirtualMachine managed object.  This UUID is visible to the guest OS as the SMBIOS UUID.  VMware generally try to avoid changing this UUID since it is often used by applications that manage the guest OS instances.  When the VM is migrated this UUID is maintained.

vCenter does a best effort to try to make sure these UUIDs are unique in an environment.  For operations like clone and deploy that create a new VM, a new UUID is provided to the VM by clearing the uuid.bios from the VM’s vmx file.  If the VM is copied without vCenter’s knowledge, 3rd party tools are advised to do the same thing as vCenter.  A new uuid.bios is generated the next time the VM is powered on.  This UUID is generated by the ESXi server so vCenter does not have to be in the control flow for the uuid.bios to be generated.

To access this via PowerCLI you can use the following:

1

2

3

PS C:\> (Get-VM | Select -first 1).extensiondata.Config.UUID422ee9f4-6cfd-1fb7-1376-a8ecb8eb8568
  1. VM Location ID: This identifier is stored in the VM configuration file as the variable uuid.location.  In the VIM API, the name is locationId also on the VmConfigInfo of the VirtualMachine.  This is one other detail that might be relevant to a 3rd party solution that might be moving the VM without vCenter’s knowledge.  This property is used in conjunction with the VM SMBIOS UUID.  This property is a hash of the VM’s configuration file and some UUID of the ESXi. The purpose of this UUID is to detect out-of-band migrations and copies of the VM.  If vSphere (or Workstation/Fusion) detect that the locationId is no longer valid, it will pop up dialog/question/error asking the user why the locationId is no longer valid.  The user is prompted to answer whether the VM was moved or copied.  The purpose is so that vSphere can determine whether it should keep the existing the SMBIOS UUID or generate a new one.

Recall, I mentioned that vCenter is doing a best effort to ensure the SMBIOS UUID is unique.  But when it detects a potential conflict, vCenter will not automatically patch the UUID since this could break 3rd party and VMware products that rely on the guest visible UUID to correlate the VM with other management entities in the environment.

The way 3rd party solutions can best interoperate with vCenter and it’s attempt to preserve a unique SMBIOS UUID is to be aware of these semantics.  If a 3rd party solution or program is moving the VM, it should clear out the uuid.location (ie. ConfigInfo.locationId) property.  On next power on, a new uuid.location will be generated, binding the VM to ESXi host and the file path where it is running.

Despite this however, there is a theoretical and real possibility that there could be duplicate SMBIOS UUIDs.  Because vCenter is deferring to what the user of the system what the the SMBIOS UUID should be, it will not change the UUID automatically if it detects conflicts.  If there SMBIOS UUIDs that are duplicated, it will not fix them.

To access this via PowerCLI you can use the following:

1

2

3

PS C:\> (Get-VM | Select -first 1).extensiondata.config.LocationId

 

564d043c-5dab-5413-c4a7-fb0837d354d9

  1. VM MoRef: The VM MoRef is a short key used by a vCenter instance to identify the VM.  This is the primary identifier used by the VIM API to refer to the VM.  The other identifiers can generally be used to find the VM, but the VM MoRef is the one that must ultimately be used to get data and issue operations to modify the VM.

In general, the MoRef is the important identifier because that’s what is used in the VC database to associate a VM to its stats, events, and configuration.

In environments where multiple vCenters are used, the MoRef will not necessarily be unique.  As a result, another identifier needs to paired with the VM MoRef or used instead.  In general, vSphere uses a combination of the vCenter instance UUID (ie. the serverGuid) with the MoRef to identify the VM for cross-vCenter scenarios like Linked Mode.

To access this via PowerCLI you can use the following:

1

2

PS C:\> (Get-VM | Select -first 1).ExtensionData.Moref.Value

vm-43

 

Recommended antivirus exclusions for Hyper-V hosts

Posted on


If antivirus software is installed and running on a Hyper-V host, there are several exclusions and options that you should configure for optimal operation of Hyper-V and the running virtual machines.

Configure the real-time scanning component within your antivirus software to exclude the following directories, files, and processes:

  • All directories that contain VHD, VHDX, AVHD, AVHDX, VSV, and ISO files
  • The following default virtual machine configuration directory, if it’s used, and any of its subdirectories:
    C:\ProgramData\Microsoft\Windows\Hyper-V
  • The following default virtual machine virtual hard disk files directory, if it’s used, and any of its subdirectories:
    C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
  • The following default snapshot files directory, if it’s used, and any of its subdirectories:
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots
  • The following default Cluster Shared Volumes path, if you’re using Cluster Shared Volumes, and any of its subdirectories:
    C:\ClusterStorage
  • Any custom virtual machine configuration directories, if applicable
  • Any custom virtual hard disk drive directories, if applicable
  • Any custom replication data directories, if you’re using Hyper-V Replica
  • If antivirus software is running on your file servers, any Server Message Block protocol 3.0 (SMB 3.0) file shares on which you store virtual machine files
  • Vmms.exe

    Note This file may have to be configured as a process exclusion within the antivirus software.

  • Vmwp.exe

    Note This file may have to be configured as a process exclusion within the antivirus software.