Author: Ashish Kumar Singh
Script: Finding RDM LUN UUIDs in a vSphere Cluster
If you’re managing a large virtual environment, keeping track of Raw Device Mappings (RDMs) can be a nightmare. Unlike standard virtual disks (VMDKs) that live neatly inside a datastore, RDMs are directly mapped to a LUN on your SAN.
When your storage team asks, “Which VM is using LUN ID 55?”, you don’t want to check every VM manually. This PowerCLI script will scan your entire cluster and export a list of all RDMs along with their Canonical Name (NAA ID) and Device Name.
The PowerCLI One-Liner
This command connects to your cluster, filters for disks that are either RawPhysical (Pass-through) or RawVirtual, and spits out the details to a text file for easy searching.
Run this in your PowerCLI window:
PowerShell
Get-Cluster 'YourClusterName' | Get-VM | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select-Object @{N="VM";E={$_.Parent.Name}},Name,DiskType,ScsiCanonicalName,DeviceName | Format-List | Out-File –FilePath C:\temp\RDM-list.txtBreaking Down the Output
Once you open C:\temp\RDM-list.txt, here is what you are looking at:
- Parent: The name of the Virtual Machine.
- Name: The label of the hard disk (e.g., “Hard disk 2”).
- DiskType: Confirms if it’s Physical (direct SCSI commands) or Virtual mode.
- ScsiCanonicalName: The NAA ID (e.g.,
naa.600601...). This is the “Universal ID” your storage array uses. - DeviceName: The internal vSphere path to the device.
Why do you need this?
- Storage Migrations: If you are decommissioning a storage array, you must identify every RDM to ensure you don’t leave a “Ghost LUN” behind.
- Troubleshooting Performance: If a specific LUN is showing high latency on the SAN side, this script tells you exactly which VM is the “noisy neighbor.”
- Audit & Compliance: Great for keeping a monthly record of physical hardware mappings.
Lazy Admin Note: This script specifically uses VMware PowerCLI cmdlets (
Get-HardDisk). If you are looking for similar info on a Hyper-V host, you would typically useGet-VMHardDiskDriveand look for theDiskNumberproperty to correlate with physical disks inDisk Management.
ZCP Study Guide: Zerto Certified Professional Exam Q&A
Ready to become a Master of Disaster? If you are preparing for the Zerto Certified Professional (ZCP) exam, you know that understanding the nuances of Continuous Data Protection (CDP) is key.
Below is a quick-reference study guide based on the core competencies of the Zerto 4.5+ curriculum. We’ve highlighted the correct answers to help you review.
ZCP Practice Exam Questions
1) After performing a failover operation (Test, Live, Move) Zerto allows you to generate a report detailing the steps performed during the operation.
- True
- False
2) VPGs can only protect virtual machines running Mac OS X or Windows XP and newer.
- True
- False (Note: Zerto is generally OS-agnostic as it operates at the hypervisor replication level.)
3) To recover a single VPG after a corrupted database, which of these operations would be most effective?
- Journal file-level restore
- Offsite clone
- Live failover
- Backup restore
4) ZVR’s Journal is stored where?
- Production/source site
- Recovery/target site
- Both
- Neither
5) During a VPG sync, which of the following operations can be performed? (Select all that apply)
- Add a VM to the group
- Remove a VM from the group
- Change length of Journal history for the group
- Change hard limit of Journal size for the group
6) Offsite Backups for a VPG should be scheduled to run at least every four hours, but no more than every 12 hours.
- True
- False
7) How much memory can be allocated to a Virtual Replication Appliance (VRA)?
- 1 GB
- 3 GB
- Between 1-16 GB
- Between 2-8 GB
8) If both sites (target/recovery and source/production) are up, healthy, and accessible, which VPG-level operation is most appropriate?
- Live Failover
- Move/migration
- Offsite Clone
- JFLR
9) What basic method does ZVR use to protect data and applications?
- VM-level continuous replication
- Scheduled and on-demand snapshots
- Daily delta syncs
- Guest/agent-based replication
10) ZVR cannot function across different hypervisors, storage configurations, or host OS versions.
- True
- False (Note: Cross-replication between VMware and Hyper-V is a core Zerto strength.)
11) What must be true for a Move operation to be effective? (Select all that apply)
- Both source (or production) and target (recovery) sites are up and accessible
- Each VM in the VPG has an up-to-date Journal
- The very latest copy of the data is required
- One of the site’s hosts has either a new VRA installed or an upgraded VRA
12) A fully configured ZVM on each paired site—e.g. production and recovery—requires which of the following? (Select all that apply)
- Adding a site-specific license under Site Settings
- Creating matching VPGs on each site
- Installing VRAs on that site’s host(s)
13) Enabling auto-commit will always provide 30 minutes to validate the results of a failover before committing the changes.
- True
- False (Note: The timeout is configurable.)
14) ZVR has built-in support for scheduled bandwidth throttling that can work with or without other hardware/software also managing this.
- True
- False
15) What characterizes the kinds of VMs you should group together in the same VPG?
- Each are using the same datastore or volume for storage
- They need to maintain consistency with each other and all be failed over or recovered together
- All are running both the same OS and same hypervisor
- The journal is sized the same on each VM
16) Adding a VM to an existing VPG means… (Select all that apply)
- The entire VPG will be re-synchronized to ensure group consistency
- The VPG protection will need to be paused before adding the additional VM
- A checkpoint will be automatically inserted in the Journal prior to adding the VM
- A Live Failover cannot be executed until the updated VPG is fully synchronized
17) What is the Journal?
- Audit trail to track which operations were performed and when
- Series of checkpoints tracking block-level changes within VMs
- Detailed list of every snapshot, whether automatic or manually generated snapshots
- Compliance record of each VPG’s replication status at any given checkpoint
18) The ZVR installer includes which of the following components? (Select all that apply)
- Local copies of the ZVR documentation specific to your hypervisor
- One license key for each site you’ll use with Zerto
- Microsoft .NET Framework in case the machine does not already have it installed
- VRA template for a custom-designed Zerto VM
- A Virtual Backup Appliance (VBA) for managing backups
19) If you needed to test the failover of an entire virtualized datacenter, what best practices should be followed? (Select all that apply)
- Perform the test during off hours or on the weekend
- Clone the VPGs you want to test prior to starting the failover test
- Use an isolated/fenced network for testing
- Always stop the test from within ZVM and not your hypervisor’s management console(s)
- Provision a sandbox where ZVR can deploy the test VMs
20) What is a Virtual Replication Appliance (VRA)?
- Lightweight agent installed on each VM in a protection group
- Snapshot engine that powers the ZVR Journal
- Custom Linux VM performing continuous replication
- A hypervisor plugin/add-on to manage cross-hypervisor replication
21) ZVR 4.5 allows for Journal Compression to increase storage capacity for journal history.
- True
- False
22) If the hypervisor service/admin account provided during installation is incorrect, ZVR will still proceed with the installation and ask for re-validation after installation is complete.
- True
- False
23) When configuring a Failover Test network, what is Zerto’s recommended best practice?
- Test and production network should be the same to ensure consistency
- Test network should be isolated/fenced
- The ZVM should be on a test network
- Pause replication on production network when using a test network during a test
24) What operating system is running on the VRA virtual machine?
- Ubuntu
- Debian
- Red Hat Enterprise Linux
- Windows Server 2012
25) What VPG configuration option would give you the ability to stagger when and how your protected VMs start?
- Bandwidth Throttling
- Re-IP
- Pre/Post Operation Scripting
- Boot Order Groups
Level Up: Becoming a Zerto Certified Professional (ZCP)
In the world of Disaster Recovery, there are two types of admins: those who panic during an outage, and those who have “Master of Disaster” status.
If you’re looking to join the elite ranks of the latter, it’s time to talk about Zerto Certified Professional (ZCP) training. While the original ZVR 4.5 training was a game-changer for its time, Zerto’s training ecosystem has evolved significantly since then to keep pace with modern cloud and ransomware threats.
What is ZCP Training?
Zerto Certified Professional (ZCP) is the official technical certification program designed for customers and partners. It moves you beyond the basics of “click and replicate” into the deep engineering of Continuous Data Protection (CDP).
The current curriculum has shifted from just “Basic” to a more modular, role-based approach available through the myZerto University platform.
Key Learning Pillars:
- Architecture & Installation: Setting up the Zerto Virtual Manager (ZVM) and Virtual Replication Appliances (VRAs).
- VPG Management: Creating Virtual Protection Groups (VPGs) to keep multi-VM applications consistent.
- The “Time Machine” (Journal): Master file-level restores and point-in-time recovery to defeat ransomware.
- The Big Red Button: Coordinating Test Failovers, Live Failovers, and Move operations without breaking a sweat.
Is it still “Basic”?
Zerto has streamlined its certifications into several paths to match your specific environment:
| Certification | Level | Focus Area |
| ZCP Enterprise | Foundation | Core vSphere/Hyper-V to On-Prem replication. |
| ZCP Azure/AWS | Intermediate | Hybrid Cloud DR and migration to public clouds. |
| ZCP Advanced | Expert | Complex troubleshooting, multi-site, and API automation. |
| ZCP Managed Services | Partner | Specifically for DRaaS (Disaster Recovery as a Service) providers. |
Why Bother Getting Certified?
- Confidence: Knowing exactly how the journal works means you can recover data from seconds before a crash.
- Professional Status: It officially recognizes you as a “Master of Disaster” within the community.
- Efficiency: You’ll learn the “Lazy Admin” way to automate IP re-addressing and boot ordering, so you don’t have to do it manually during a crisis.
How to Get Started
- Access: Head over to the myZerto Portal. (Note: You still need to be a customer or partner to access full technical training).
- Time Investment: Most foundational courses take between 90 minutes and 3 hours of self-paced e-learning.
- The Exam: You’ll typically need a 75% or higher to pass. The exams are online, unproctored, and refreshingly focused on real-world scenarios rather than trivia.
Lazy Admin Tip: Don’t just watch the videos. If you have a lab environment, try to break a VPG and see how the ZVM alerts you. Real learning happens when the lights go red!
Recovery Guide: Fixing Corrupt Image Profiles on ESXi
We’ve all been there—a patch remediation task in vSphere Update Manager (VUM) or vSphere Lifecycle Manager (vLCM) gets interrupted (shoutout to that one colleague!), and suddenly your ESXi host is in a “zombie” state.
If you see the dreaded “Unknown – no profile defined” error, your host has lost its identity. It no longer knows which VIBs (VMware Installation Bundles) should be installed. This is usually caused by a corrupt imgdb.tgz file.
We’ve all been there—a patch remediation task in vSphere Update Manager (VUM) or vSphere Lifecycle Manager (vLCM) gets interrupted (shoutout to that one colleague!), and suddenly your ESXi host is in a “zombie” state.
If you see the dreaded “Unknown – no profile defined” error, your host has lost its identity. It no longer knows which VIBs (VMware Installation Bundles) should be installed. This is usually caused by a corrupt imgdb.tgz file.
The Symptom: Missing Image Profile
When an image profile is empty or corrupt, you cannot install patches, remove drivers, or perform upgrades. ESXi relies on the image database to maintain consistency.
How to Diagnose a Corrupt imgdb.tgz
Before you resort to a full host rebuild, verify the file size of the database. A healthy imgdb.tgz is typically around 26 KB. If yours is only a few bytes, it’s corrupted.
SSH into the host.
Locate the files:
cd /vmfs/volumesfind * | grep imgdb.tgz
Note: You will usually see two results (one for each bootbank).
Check the size:
ls -l <path_to_result>/imgdb.tgzIf the size is tiny (e.g., 0-100 bytes), the database is toast.
The Fix: Borrowing a “Known Good” Profile
Instead of a time-consuming reinstall, you can manually restore the database from a healthy host running the exact same version and patch level.
Step 1: Export from a Healthy Host
On a working ESXi host, copy the healthy database to a shared datastore:
cp /bootbank/imgdb.tgz /vmfs/volumes//Step 2: Restore on the Corrupt Host
On the host with the issue, move the good file to /tmp and extract it to access the internal VIB and Profile metadata:
cp /vmfs/volumes//imgdb.tgz /tmpcd /tmptar -xzf imgdb.tgzStep 3: Rebuild the Database Directories
Now, manually place the healthy metadata into the system directories:
Copy Profiles:
cp /tmp/var/db/esximg/profiles/* /var/db/esximg/profiles/Copy VIBs:
cp /tmp/var/db/esximg/vibs/* /var/db/esximg/vibs/Replace Bootbank File:
rm /bootbank/imgdb.tgzcp /tmp/imgdb.tgz /bootbank/
Step 4: Finalize and Persist
To ensure these changes survive a reboot, run the backup script:
/sbin/auto-backup.shSummary Table: Resolution Options
| Option | Effort | Risk | When to use |
| Rebuild Host | High | Low | If you don’t have a matching “known good” host. |
| Manual File Copy | Low | Medium | When you need a fast fix and have a twin host available. |
How to fix Lost connectivity to the device backing the boot filesystem on an ESXi host?
Error: Lost connectivity to the device naa.60xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx backing the boot filesystem /vmfs/devices/disks/naa.60xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. As a result, host configuration changes will not be saved to persistent storage.
If we lose connectivity to the NIC that runs the boot LUN (switch reboot, cable disconnect, etc.), we will see the above error. This error is being displayed because connectivity is lost and the iSCSI boot does not support Multi pathing, which means that if connectivity is lost between the Storage Processor (SP) on the VNXe and the NIC on the host, the host can no longer access its boot lun and cannot write logs etc.
There is no impact as whole ESXi OS is loaded into memory so there is no outage for the VMs. Once the connectivity is restored the host can access the storage again. The error was for the fact that the error does not clear automatically.
The simplest solution is to put the host into maintenance mode, reboot it and the problem is solved Or restart the Management Agents on the ESXi host.
Check How to restart Management agents on ESXi host
How to rename the local administrator with Group Policy
To improve security in your Active Directory domain, you should rename the administrator account because this lowers the risk of brute force attacks. Renaming the administrator account and resetting its password on all computers in your AD domain can be easily done via Group Policy.
Open the Active Directory Group Policy Management console, create a new GPO, and link it to your desired OU. Of course, you can also work with an existing GPO.
Linking a GPO to an OU
Right-click the new GPO or an existing GPO and select Edit. This will launch the Group Policy editor. Now, browse to the following Group Policy setting: Computer Configuration > Preferences > Control Panel Settings > Local Users and Groups.
Renaming the administrator account
As you can see in the screenshot above, right-click Local Users and Groups and then navigate toNew > Local User.
On the next screen, you select the user name you would like to use for the administrator account:
Selecting the user name
Select the following:
Action – Select Update.
User name – Select Administrator (built-in).
Rename to – Enter the new user name.
Full name – Enter your desired name.
Description – Add a description (optional).
Password – Set a new password (optional).
Check boxes – Verify that the check boxes comply with your company policies.
The GPO is now configured and can be deployed in your network. The refresh interval for computer settings is 90 minutes. If you want to apply the GPO immediately on a client computer, open a command prompt and type gpupdate /force at the command line.
Alternatively, you can reboot the computer. If you are finding that a computer isn’t applying the policy, simply run gpresult /r at a command line to see whether your new GPO is listed:
Checking if the GPO has been applied
If it’s not listed or if you see a permission error message, go back to Active Directory Users and Computers and check the OU to which you have the policy applied. Also check whether the computer contains that OU. Perhaps the computer is in a different OU and therefore doesn’t pick up the policy.
Also check the GPO settings. In the Security Filtering section, ensure that the GPO is applied to Authenticated Users; in the Links section, verify that the correct OU is linked to the GPO :
GPO security filtering
If the policy is still not applied to some of your computers and you have checked all the above, then your domain controllers might not replicate the GPO properly.
How to reset ESXi 5.x root password using Host Profiles
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
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:
- 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.
- Click the Devices view (under Configuration > Storage):
- 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.
- 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.
- 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:
- 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 - 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
Standard Windows Monitoring Threshold Parameters
Confused with setting up Threshold Parameters on the Tools Server for Performance Monitoring?
Here are the typical parameters and the threshold limit with Warning, High, Alert levels with polling intervals. This will depend upon the SoW signed with the client.
RoD is nothing but Remedy on Demand.
VMware vCenter Release and Build Number History
| 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 |
- ← Previous
- 1
- 2
- 3
- …
- 10
- Next →
Lazy Admin Blog 