Devoted to Virtualization Technologies

Site to share knowledge about VMware and related Technologies

Metric Description in vCOPS

vCOPS documentation is not really good and information is scattered all over the place. It would be really nice, if VMware does justice to this product and puts in more resources for documentation.

It is very hard to understand all the metrics that are in “All Metrics” tab under “Operations” tab, when you click on a VM. After some research, I found few nice links – which explains few of those counters. I will keep on adding them as I find.

  1. -Metrics

Hope this helps, when we are trying to decipher those cryptic counters.

Blue Icons in vCOPS

When ever we delete/de-commission a VM/Resource from the vCenter Server, we need to remove those resource from vCOPS otherwise, there will be a blue icon with a question mark. I wish, it could have updated automatically. But as of vCOPS 5.3 we don’t have that option. If anyone knows  a better way, please let me know about it.

To remove the resource, we need to go to

1. Custom UI i.e https://ip_address_of_vcOPS/Custom

2. Click on the Environment Tab

3. Click on “Recently Added Resources”

4. Select the resources by number of Days – I prefer to go with last 30 days

5. Sort via “Health” column

6. Select all the resources, which have blue icon

7. And click on Delete Resources.

Click to enlarge

vCOPS Metrics

To understand vCOPS and its metrics one needs to understand the below mentioned metrics. I thought to add this on my blog site to help me. Hope this helps you too.


Amount of a resource that the user configures.The provisioned metric might apply to the amount of physical memory for a host or the number of vCPUs for a virtual machine.


Actual amount of a resource that the object can use. The usable amount is less than or equal to the provisioned amount. The difference between the provisioned amount and usable amount stems from factors such as hardware capacity and virtualization overhead. This overhead might include the memory that an ESX host uses to run the host, to support reservations for virtual machines, and to add a buffer for high availability. The usable metric does not apply to virtual machines.


Amount of a resource that an object consumes. The usage amount is less than or equal to the usable amount.


Amount of a physical resource that the object might consume without any existing constraints. An object becomes constrained because of under provisioning or contention with other consumers of the

A virtual machine might need 10GB of memory but can only get 5GB because the virtual machine must share resources with other virtual machines on the host.When the demand amount is less than the usage amount, the environment might have wasted resources. When the demand amount is greater than the usage amount, the environment might incur latency and exhibit decreased performance.


Effect of the difference between the amount of the resource that the object requires and the amount of the resource that the object gets.
This metric measures the effect of conflict for a resource between consumers. Contention measures latency or the amount of time it takes to gain access to a resource. This measurement accounts for dropped packets for networking.


Maximum amount that an object can get from a resource. The limit sets the upper bound for CPU, memory, or disk I/O resources that you allocate and configure in vCenter Server.
The usage amount is less than or equal to the limit amount. The demand amount can be greater than the limit amount. The limit amount is less than or equal to the provisioned amount.

The default limit amount is unlimited.
Rules: Usage <= Limit
Demand can be greater than Limit .


Guaranteed amount of resources for an object. The object does not start without this reserved amount. The default amount is 0.


Amount of a resource that a virtual machine can use based on the relative priority of that consumer set by the virtualization configuration. This metric is a function of provisioned resources, limit, reservation, shares, and demand. Shares involve proportional weighting that indicates the importance of a virtual machine.
The entitlement amount is less than or equal to the limit amount. The only case in which entitlement is less than provisioned is when the total provisioned amount is greater than total capacity.

The entitlement metric applies only to virtual machines.
Rules: Entitlement <= Limit <= Provisioned
Entitlement >= Reservations

Source vCenter Operations Advance Getting started Guide.

Network connectivity requirements for VMware View Manager 4.5 and later

Nice KB from VMware about the Firewall ports that’s needed to configure VMware View. This is only for VMware View 4.5 and above.

Important files in ThinApp Directory

A colleague of mine, shared few important definitions/files for ThinApp.I thought, it will be useful to the community.

  1. AppSync.exe – The Application Sync utility is an automatic update facility. This file allows the desktop administrator to manually run the Application Sync utility.
  2. dll_dump.exe – It shows all applications captured with ThinApp that are running on the machine.
  3.  log_monitor.exe – A troubleshooting utility to generate a readable log file from a captured application as it runs.
  4. relink.exe – It updates older ThinApp 4.x versions of packages to the current version. A package update is necessary if, such as, a ThinApp 4.0.4 application package is to run on Windows 7.
  5.  sbmerge.exe – Updates applications after they are captured, by merging run time changes from the sandbox back into the existing project.
  6. Setup Capture.exe – The wizard for capturing an application with ThinApp.
  7. snapshot.exe – The tool that Setup Capture uses to look at the file system and Registry of the computer. This utility is for the pre-installation scan and post-installation scan. snapshot.exe also compares the two scans.
  8. snapshot.ini – Created when you install ThinApp. Contains configuration information for Setup Capture. This Configuration Settings file contains a list of system locations to exclude from the capture (such as the %TEMP% directory). ThinApp installs a default snapshot.ini file in the ThinApp folder that is used in the ThinApp scanning process. This file is involved whether you do your capture with Setup Capture or at the command prompt.
  9.  ThinAppConverter.exe – Implements the ThinApp Converter process.
  10.  ThinDirect.adm – Group Policy object (GPO) for administrator-controlled URLs for ThinDirect.
  11.  ThinDirect.msi – The installation file for the ThinDirect plug-in.
  12.  thinreg.exe – Creates the Start menu and desktop shortcuts, sets up file type associations, and adds uninstall information that can be executed from the system Control Panel.
  13.  tlink.exe – The ThinApp linker. Links the ThinApp run time into the ThinApp package during the build.
  14. vftool.exe – The virtual file system compiler. Used during the build.
  15.  vmw.lic – The file that contains the encrypted ThinApp license key.
  16.  vregtool.exe – ThinApp virtual registry compiler and exporter. Used during the build.
  17. Captures folder – When you start doing captures, a Captures folder appears at the highest level. The ThinApp projects go there, by default, under a folder for each application.
  • Modified logo
  • Recent Post

  • Tag Coud

  • Archives