Applying CSP-102547 Patch to vIDM 3.3.7

vIDM 3.3.7 Patch CSP-102457 recently dropped, let's apply it! Download it here.

Like the KB says, once downloaded go ahead and upload it to /db/vidm-upgrade on the vIDM VM. I had to create this directory.

Once uploaded, unzip it:

unzip CSP-102547-Appliance-3.3.7-Patch.zip

Once unzipped, cd to the new directory and run the script like this.

cd CSP-102547-Appliance-3.3.7-Patch

./CSP-102547-patch-automation.sh -f CSP-102547-Appliance-3.3.7.zip -r

This will apply the patch and eventually reboot the VM, took about 5.

root@vidm-bpeterson [ /db/vidm-upgrade/CSP-102547-Appliance-3.3.7-Patch ]# ./CSP-102547-patch-automation.sh -f CSP-102547-Appliance-3.3.7.zip -r
2026-03-01 15:40:30 - Checking Patch ZIP location, should not be at /db/data...
2026-03-01 15:40:30 - Patch ZIP location check passed: /db/vidm-upgrade/CSP-102547-Appliance-3.3.7-Patch/CSP-102547-Appliance-3.3.7.zip
2026-03-01 15:40:30 - Disk space at /db/vidm-upgrade/CSP-102547-Appliance-3.3.7-Patch: 16.16GB free
2026-03-01 15:40:30 - Disk space at /boot: 78MB free
2026-03-01 15:40:30 - All checks passed for ZIP '/db/vidm-upgrade/CSP-102547-Appliance-3.3.7-Patch/CSP-102547-Appliance-3.3.7.zip'.
2026-03-01 15:40:30 - Running on node: vidm-bpeterson.vcfops.lab
2026-03-01 15:40:30 - Checking grub2 presence
2026-03-01 15:40:30 - grub2 detected: /boot/grub2/grub.cfg exists
2026-03-01 15:40:31 - NOTE : Cluster size is displayed 0 , if prepare-vidm-patch.sh is run in a cluster
2026-03-01 15:40:31 - Cluster size detected: 1
2026-03-01 15:40:31 - Extracting patch bundle
2026-03-01 15:40:58 - Patch directory ready: CSP-102547-Appliance-3.3.7
2026-03-01 15:40:58 - Running patch script: CSP-102547-applyPatch.sh
2026-03-01 15:40:58 - Tail the log file /opt/vmware/var/log/update/vidm-CSP-102547-update.log for live logs..
2026-03-01 15:40:58 - Running pre patch validations...
2026-03-01 15:40:59 - Sufficient disk space in /db/vidm-upgrade/CSP-102547-Appliance-3.3.7-Patch/CSP-102547-Appliance-3.3.7: 16GB
2026-03-01 15:40:59 - Pre-checks passed successfully.
2026-03-01 15:40:59 - Target version: 3.3.7.0 | Detected version: 3.3.7.0
2026-03-01 15:40:59 - Detected Build Number: 21173100
2026-03-01 15:40:59 - Applying current patch CSP-102547...
2026-03-01 15:48:00 - Created update.success marker file.
2026-03-01 15:48:12 - Patch CSP-102547 applied successfully.
2026-03-01 15:48:12 - Cleanup deprecated rpms on the system...
2026-03-01 15:48:27 - Cleanup deprecated rpms done.
2026-03-01 15:48:27 - Validating CSP-102547 patch status...
2026-03-01 15:48:27 - CSP-102547 Patch applied successfully and flag file /usr/local/horizon/conf/flags/CSP-102547-3.3.7.0-hotfix.applied is present.
2026-03-01 15:48:28 - CSP-102547-Appliance-3.3.7 directory cleanup complete
2026-03-01 15:48:28 - Rebooting system...
Connection to vidm-bpeterson.vcfops.lab closed by remote host.
Connection to vidm-bpeterson.vcfops.lab closed.

At this point the vIDM Web Console will look like this.

As indicated in the KB you must now SSH into the vIDM VM and run the following commands.

systemctl enable getty@tty1.service

systemctl start getty@tty1.service

You will then be presented with the standard screen via the Web Console.

And we're done, hope this was helpful! Next up will be applying the Aria Suite Lifecycle Manager 8.18.0 Patch 7.