VMware Visio Stencils: Download, Install and Use Them for VCF 9

VMware Visio stencils in 2026: the VVD icon set on GitHub, files included, install in Visio and draw.io, and what is missing for VCF 9.

Short answer: download the VMware Visio stencils from github.com/h0bbel/vmware-stencils (Code → Download ZIP). It is the VMware Validated Design (VVD) icon set: vmw_Icons.vssx, vmw_colors.vssx, the vmw_template.vstm template and 111 SVG icons, and it still opens in current Visio and draw.io. Broadcom has not published a newer set for VCF 9, so this page also shows which icon to use for each VCF 9 component.

Download the VMware Visio stencils (VVD icon set)

Old links point to VMTN community documents and to github.com/tenthirtyam/vmware-stencils. Both are dead; the GitHub repository returns 404. These are the working options, checked in October 2026:

SourceWhat you getAccessStatus
h0bbel/vmware-stencils on GitHubVisio .vssx stencils and .vstm template, OmniGraffle stencils, PPTX, 111 SVG iconsPublic, no login: Code → Download ZIPContent last changed 2020-11-30, no license file
draw.io (diagrams.net) built-in library“VMware” shape library (More Shapes → Networking), same VVD icon familyFree, web or desktop appMaintained as part of draw.io
Broadcom TechDocsOfficial architecture diagrams inside the VCF documentationPublicReference only, not a stencil pack

The GitHub fork chain is Ryan Johnson (tenthirtyam, deleted) → foozy74/vmware-stencils → h0bbel/vmware-stencils (Christian Mohn). Direct ZIP: https://github.com/h0bbel/vmware-stencils/archive/refs/heads/main.zip.

What is in the VMware stencils package

FolderFilesUse
visio/vmw_Icons.vssx, vmw_colors.vssx, vmw_template.vstmIcons, “Colors and Boxes” stencil, Visio template
omnigraffle/vmw_icons.gstencil, vmw_color.gstencil, vmw.clrOmniGraffle on macOS plus the color palette
pptx/vmw_icons.pptx (about 19 MB)Icons for slide decks
svg/111 individual SVG iconsdraw.io, web pages, any vector editor

The icon stencil is named vmw_Icons.vssx with a capital I, while the README writes vmw_icons.vssx. On Windows this does not matter; in scripts on Linux or macOS it does. The CHANGELOG has four releases: 2018-08-14 (initial), 2019-05-31 (large icon update and example diagrams), 2019-10-03 (fixed SDDC stencil and template) and 2020-11-20 (Visio update, plus OmniGraffle, PowerPoint and SVG). Nothing has been added since.

How to install VMware stencils in Visio

  1. Download the ZIP and extract it.
  2. Copy vmw_template.vstm, vmw_Icons.vssx and vmw_colors.vssx to C:\Users\<username>\Documents\My Shapes. Visio uses this folder as the default location for custom stencils.
  3. Open vmw_template.vstm to start a drawing with the intended page setup.
  4. In the Shapes pane, choose More Shapes → Open Stencil, select both .vssx files and click Open. Stencils saved in My Shapes are also listed under More Shapes → My Shapes.
  5. Save the drawing. Stencils open in the Shapes window stay attached to that drawing the next time you open it.

The README also lists the house style from VMware documentation: Metropolis font, no text smaller than 11 pt, do not scale icons and shapes, and keep the template’s paper format.

VMware stencils for draw.io (diagrams.net) and OmniGraffle

  • draw.io built-in library: open More Shapes, go to Networking and enable VMware. It is the VMware Validated Design (VVD) icon family; the shapes are tagged “vmware validated design”, so the shape search finds them too. No download needed.
  • draw.io with the GitHub files: drag vmw_Icons.vssx and vmw_colors.vssx into the web or desktop app (the README documents this), or drag individual SVGs from the svg/ folder onto the canvas.
  • OmniGraffle (macOS): create a VMware folder in ~/Library/Containers/com.omnigroup.OmniGraffle7/Data/Library/Application Support/The Omni Group/OmniGraffle/Stencils, copy both .gstencil files there, and copy vmw.clr to ~/Library/Colors.

Other VMware stencil sets compared

Search results for VMware stencils mix this set with older and vendor-specific packs. This is what each one is good for:

SetCoversLast updatedFormatUse it for
VVD icons (h0bbel/vmware-stencils)vCenter, ESXi, VM, vSAN, NSX (Manager, gateway, DLR, CSM), HCX, Site Recovery, Kubernetes, vRealize products, generic infrastructure2020-11.vssx, .vstm, .gstencil, .pptx, .svgVMware design documents (HLD/LLD), VCF diagrams with relabeled boxes
draw.io “VMware” libraryThe same VVD icon familyMaintained with draw.ioBuilt in (More Shapes → Networking)Wikis, labs, shared editing without distributing files
vmtoday.com stencilsvSphere icons, Horizon View (184 shapes), vCenter Orchestrator (118 shapes)Drawn 2012–2014.vssx, .vssHorizon and Orchestrator diagrams; not VCF
Veeam stencils250+ shapes: generic hosts, storage, VMs and Veeam components. The old veeam.com stencil URL now opens Veeam’s brand resource center; draw.io also has a built-in “Veeam” library under Networking.Maintained by VeeamVisio, draw.io built-inBackup and data-protection designs
VeloCloud stencils (Broadcom KB 376248)VMware VeloCloud SD-WAN onlyOfficial Broadcom attachmentVisio ZIPSD-WAN topologies

The VeloCloud pack is the only official Broadcom stencil download I could find. For vSphere, vSAN, NSX and VCF, the VVD set is still the most complete VMware-specific option.

Which package for which diagram

DiagramBest fitWhy
Customer design document (HLD/LLD) in Visiovmw_template.vstm + both .vssxSame icons and box colors as the old VVD documentation
Lab or wiki diagram, shared editingdraw.io built-in VMware libraryFree, no files to distribute
Slide deckvmw_icons.pptxIcons already sized for PowerPoint
Web page, Markdown docs, Excalidraw-style toolssvg/ folderPlain vector files, easy to recolor
Mac usersOmniGraffle stencilsNative format and palette

Mapping VVD icons to VCF 9 components

The icon set is from the vSphere 7 and vRealize era, so several VCF 9 components have no icon of their own and the management products still carry vRealize names. The practical approach: use the closest VVD icon and put the current VCF 9 name in the label. File names below are from the svg/ folder; the Visio stencil uses the same icons.

VCF 9 componentVVD icon to useNote
vCentervcenter-server.svgExact match
ESX hostrack-server.svg, or vm-server.svg for a host with VMsLabel as ESX 9.x
Virtual machinevm.svgExact match
vSAN (OSA or ESA)vmware-vsan.svgPut “ESA” in the label; there is no separate ESA icon
vSphere Distributed Switchvirtual-switch.svgPhysical uplinks: physical-nic.svg, ToR: switch.svg
NSX Managernsx-manager.svgExact match
NSX Edge, Tier-0 / Tier-1 gatewaynsx-gateway.svgUse router.svg for the physical BGP peers
NSX VPCnoneUse a box from vmw_colors.vssx labeled “VPC”
VCF Operationsvrops.svgRelabel; the icon still says vRealize Operations
VCF Operations for logsvmware-vrealize-log-insight.svgRelabel
VCF Operations for networksvmware-vrealize-network-insight.svgRelabel
VCF Automationvmware-vrealize-automation.svgRelabel
SDDC Manager / VCF Operations fleet managementvmware-cloud-foundation.svgNo dedicated icon. Separate components in 9.0; Broadcom’s 9.1 feature comparison lists fleet management as “formerly SDDC Manager”
VCF Operations orchestratorvmware-vrealize-orchestrator.svgRelabel
VCF Installervirtual-appliance.svgNo dedicated icon
vSphere Supervisor / vSphere Kubernetes Servicekubernetes.svgpks.svg is the old Enterprise PKS icon; avoid it
VCF Operations HCXvmware-hcx.svgSame icon, new name
Site Recovery, vSphere Replicationvmware-site-recovery.svg, vmware-vsphere-replication.svgLabel with the current product name
VCF Identity Broker, external IdPidentity.svgGeneric
Certificate authoritycertificate-server.svgGeneric
Avi Load Balancerload-balancer.svgGeneric

For a VCF 9 design, start from the component list in VCF 9.0 minimum requirements for a lab to decide which boxes belong on the page, and check component names against Broadcom KB 401497 (the VCF 9.0 component list). Official reference diagrams are in the VCF documentation on TechDocs. A worked example is my VCF 9 lab network diagram.

Is there a VMware Visio stencils 2025 or 2026 update?

No. The “2025” and “2026” posts you find in search results point to the same 2020 files on GitHub. In a Broadcom Community thread about Visio stencils for VCF, a reply states that no current official VCF-specific Visio stencil package from Broadcom is known and that the old VVD packages are outdated for VCF 9.x. The README’s own note says official diagrams live in the product documentation, which today means Broadcom TechDocs. If Broadcom publishes a new set, it will be announced there or on the VCF blog. Until then, treat the VVD set as a community-maintained copy without a stated license: fine for internal design work, but check it against your policy before using it in commercial material.

Sources

Related on vdan.cz

Virtually Speaking: Inventory and Calculator…

Virtually Speaking: Inventory and Calculator scripts for VMware Cloud Foundation VCF and vSphere Foundation VVF

Virtually Speaking: Inventory and Calculator…

On this episode of the Virtually Speaking Podcast Pete and John welcome William Lam to discuss the details of some new tools for VMware Cloud Foundation VCF and VMware vSphere Foundation VVF.


VMware Social Media Advocacy

Usage Meter Upgrade Path: From 4.8 (Broadcom Advantage) to VCF Usage Meter 9.0 and 9.1.1

Current VCF Usage Meter upgrade path: 4.4+ to 4.8, 4.7+ to 9.0.x, 9.0+ to 9.1.1. In-place ISO steps, the 9.0 access token, known issues and 4.8 history.

Short answer: The current release is VCF Usage Meter 9.1.1 (8 Sep 2026, build 25660887). Usage Meter 9.1 and 9.1.1 install as an in-place upgrade on top of 9.0 and later. Usage Meter 9.0.x installs in place on top of 4.7 and later. From 4.7 or 4.8, go to 9.0.x first and then to 9.1.1. From 4.4 to 4.6, upgrade to 4.8 first. Every step uses the upgrade ISO and upgrade-um.sh. The 9.0 step also needs an access token from the VCF Business Services console.

Usage Meter upgrade path at a glance

Target releaseReleased / buildIn-place upgrade supported from
VCF Usage Meter 9.1.18 Sep 2026 / 256608879.0 and later
VCF Usage Meter 9.112 May 2026 / 253865089.0 and later
VCF Usage Meter 9.0.1.1009 Sep 2025 / 249378954.7 and later
VCF Usage Meter 9.0.1.017 Jul 2025 / 247983874.7 and later
VCF Usage Meter 9.07 May 2025 / 246994914.7 and later
vCloud Usage Meter 4.87 Feb 2024 / 232229514.4 and later

Typical paths:

  • 4.7 / 4.8 → 9.0.1.100 → 9.1.1. 9.1.x only accepts 9.0 or later as its source.
  • 4.4–4.6 → 4.8 → 9.0.1.100 → 9.1.1. 9.0.x only accepts 4.7 or later.
  • Any 9.0.x → 9.1.1 directly.

For appliances older than 4.4, the release notes cited here don’t document a path. Check with Broadcom support before you plan a redeployment.

VCF Usage Meter 9.0 upgrade: what changes

The move from 4.x to 9.0 is more than a version bump. According to the 9.0 release notes:

  • Usage Meter management moves to the VCF Business Services console, and usage upload uses an OAuth app. Before you upgrade, generate an access token in that console. upgrade-um.sh asks for it and then asks you to confirm the tenant.
  • Registering and managing instances in offline mode is no longer supported. Usage Meter 4.8 had already dropped it. License categories and metering of Tanzu Kubernetes Grid management clusters are gone too.
  • The appliance OS moves from Photon OS 4 to Photon OS 5, and the FIPS libraries adopt FIPS 140-3.
  • New metering targets: VMware Cloud Foundation 9.0 and the vDefend add-ons.

Usage Meter 9.1 adds metering of VCF Automation, detection of the AVI Load Balancer through NSX Manager, a cert-management.sh utility and a .tar.gz usage-file format. 9.1.1 is a security and bug-fix release.

How to upgrade Usage Meter (in-place, ISO)

The procedure has barely changed since 4.8. The steps below follow the 9.1 TechDocs page. Download the upgrade ISO, for example VCF_Usage_Meter-9.1.0.0-<BUILD_NUMBER>_Upgrade.iso, plus the optional .mf, .crt and .sign files, from the Usage Meter product page on the Broadcom Support Portal. You need a Broadcom support account with access to the product.

  1. Take a snapshot of the Usage Meter appliance.
  2. (Optional) Verify the download with sha1sum -c against the .mf file, and check the signature with openssl as shown in the docs.
  3. Connect the VM’s CD-ROM drive to the upgrade ISO.
  4. Log in as root on the console. Alternatively, enable SSH in the VAMI (https://<um-host>:5480 → Access), log in as usagemeter and run su root. The upgrade turns SSH off again afterwards.
  5. Mount the ISO and start the upgrade (commands below).
  6. Confirm that the snapshot exists. When upgrading to 9.0, also paste the access token and confirm the tenant. Answer y to the reboot prompt.
  7. Check the services. They should report Online.
mkdir /root/upgrade
mount -o loop /dev/cdrom /root/upgrade
bash /root/upgrade/upgrade-um.sh
# after the reboot
bash /opt/vmware/cloudusagemetering/scripts/status.sh

If upgrade-um.sh warns about a wrong hostname, fix the hostname first and regenerate or re-import the certificate. The certificate CN must match the appliance hostname. Otherwise you can have trouble logging in to the web UI afterwards. After a successful upgrade, don’t revert to the pre-upgrade snapshot. Broadcom warns that this breaks the automatic aggregation and reporting of monthly consumption data.

Known upgrade issues

  • VM hangs, “The guest operating system has locked the CD-ROM door”. This is listed for 4.8 and 9.0.x. Workaround: VMware KB 2144053.
  • Second network adapter swaps with the first after upgrading to 9.0 or 9.1. See KB 399671.
  • SSH “REMOTE HOST IDENTIFICATION HAS CHANGED!” on the first SSH login after upgrading to 9.0 (listed in the 9.0 release notes). The appliance host ID changes, so remove the old entry from your known_hosts.
  • No account lockout after failed logins on 9.0 → 9.1 upgrades, because the PAM files keep their legacy content. 9.1 has a manual workaround, and 9.1.1 lists the issue as resolved.
  • Upgrades from 4.x to 4.8 required you to accept the certificates of all metered products again in the web UI.

History: Usage Meter 4.8 and the Broadcom Advantage program

This post was first written in February 2024. VMware’s Cloud Provider blog announced Usage Meter 4.8 as the required version for VCSPs under the Broadcom Advantage program from 1 April 2024. The reasons given were full support for independent clusters and core-based metering. The 4.8 release notes list Aria re-branding, Photon OS 4, TLS 1.3 and updated FIPS libraries as its changes. Offline-mode registration and Horizon metering were dropped. My 4.8 upgrade used exactly the ISO procedure above and ended with this prompt:

Usage Meter console after upgrade-um.sh: Appliance upgraded to version 4.8.0.0, log in /opt/vmware/var/log/um-upgrade.log, reboot prompt

The upgrade log is written to /opt/vmware/var/log/um-upgrade.log.

Sources

Related on vdan.cz

Quick Tip – Block or remove download URL for…

Quick Tip – Block or remove download URL for VMware Enhanced Authentication Plug-in (EAP)

Quick Tip – Block or remove download URL for…

There was a new VMware Security Advisory (VMSA-2024-0003) that was published this week that affects the deprecated VMware Enhanced Authentication Plug-in (EAP) and as part of the remediation, per VMware KB 96442, there are instructions on how to uninstall the EAP plugin from desktop systems […]


VMware Social Media Advocacy

Automate the deployment & initial configuration…

Automate the deployment & initial configuration…

I love writing automation, especially for deploying a consistent and repeatable environment for testing or learning purposes. I recently deployed the latest Aria Suite Lifecycle Manager 8.14 (formally vRealize Suite Lifecycle Manager or vRSLCM) manually using the graphical Easy Installer method [..]


VMware Social Media Advocacy

Automating vCenter certificate-manager CLI: Scripting Solution User Certificate Replacement (and When to Use vCert Instead)

certificate-manager in vCenter has no unattended mode. How to script the same steps with certool, vecs-cli and dir-cli, and when vCert is the better tool.

Short answer: /usr/lib/vmware-vmca/bin/certificate-manager on the vCenter Server Appliance is interactive only; there is no documented non-interactive or answer-file mode. To automate it you either script the underlying tools it wraps (certool, vecs-cli, dir-cli, service-control) following the documented manual CLI procedure, or you use Broadcom’s newer vCert utility, which Broadcom now recommends over certificate-manager for most certificate workflows. Always snapshot vCenter first.

What certificate-manager is and where it lives

The vSphere Certificate Manager is a menu-driven shell utility on the VCSA. According to Broadcom KB 318946 it must be run as root and offers eight options:

OptionAction
1Replace Machine SSL certificate with Custom CA certificate
2Replace VMCA root with Custom CA signing certificate and replace all certificates
3Replace Machine SSL certificate with VMCA-generated certificate
4Regenerate new default VMCA root and replace all certificates
5Replace Solution User certificates with Custom CA certificates
6Replace Solution User certificates with VMCA-generated certificates
7Revert last operation by re-publishing old certificates
8Reset all certificates

Useful paths for troubleshooting and automation:

  • Binary: /usr/lib/vmware-vmca/bin/certificate-manager
  • Log: /var/log/vmware/vmcad/certificate-manager.log
  • Certificate template used by certool: /usr/lib/vmware-vmca/share/config/certool.cfg

Why it cannot be automated directly

Every option prompts for the SSO administrator password, certificate attributes and confirmations. Wrapping it with expect works in a lab but is brittle: prompts change between builds, and a mismatched answer can leave vCenter half-updated. certificate-manager is essentially a front end for the VMCA and VECS command-line tools, and it records the commands it runs in certificate-manager.log. Running a workflow once interactively in a lab and reading that log is a good way to see exactly which calls you need to reproduce.

Scripting solution user certificate replacement with certool, vecs-cli and dir-cli

Broadcom documents the manual CLI equivalent of option 6 in Replace Solution User Certificates with New VMCA-Signed Certificates. The solution users are machine, vpxd, vpxd-extension, vsphere-webclient and wcp. Because the steps are identical per user, they loop cleanly:

#!/bin/bash
# Run as root on the VCSA after taking a snapshot.
# sol_usr.cfg = certool config with your Country/Org/Hostname values.
CERTOOL=/usr/lib/vmware-vmca/bin/certool
VECS=/usr/lib/vmware-vmafd/bin/vecs-cli
DIRCLI=/usr/lib/vmware-vmafd/bin/dir-cli

for SU in machine vpxd vpxd-extension vsphere-webclient wcp; do
  $CERTOOL --genkey --privkey=$SU-key.priv --pubkey=$SU-key.pub
  $CERTOOL --gencert --cert=new-$SU.crt --privkey=$SU-key.priv --Name=$SU --config sol_usr.cfg
  $VECS entry delete --store $SU --alias $SU
  $VECS entry create --store $SU --alias $SU --cert new-$SU.crt --key $SU-key.priv
done

# Map each solution user to its unique service ID in VMware Directory:
$DIRCLI service list
# then for each one, e.g.:
# $DIRCLI service update --name vpxd-<ID> --cert new-vpxd.crt

service-control --stop --all && service-control --start --all

Notes: vecs-cli entry delete asks for confirmation unless you answer it (-y); dir-cli prompts for SSO credentials unless you pass --login and --password. Keep the password out of shell history, for example by reading it from a protected file. Replacing solution user certificates is rarely required: VMware’s guidance has long been to leave them VMCA-signed and replace only the Machine SSL certificate.

certificate-manager vs vCert: which one to use

vCert (KB 385107) is a Python-based tool from Broadcom support for vCenter 7.0, 8.0 and 9.x. KB 313947 now presents vCert as the primary method for solution user replacement and lists certificate-manager as the deprecated method.

certificate-managervCert
Shipped with VCSAYesNo, downloaded from the KB
Status/expiry checksNoYes, across VECS stores, trust anchors, STS
Expired certificate recoveryLimitedDesigned for it
Command-line optionsNoneYes, see ./vCert.py --help
Logs/var/log/vmware/vmcad/certificate-manager.log/var/log/vmware/vCert/vCert.log

My rule of thumb: use vCert for checks, reports and recovery; use the raw certool/vecs-cli/dir-cli sequence only when you need a fully scripted, repeatable change in a pipeline. Installation and menu walkthrough are in Installing and using the vCert tool. If vCenter already shows “no healthy upstream” because the STS signing certificate expired, start with this STS certificate guide.

Before you run anything

  1. Take a snapshot of vCenter; for Enhanced Linked Mode, take powered-off snapshots of all linked vCenters at the same time (KB 318946).
  2. Confirm the hostname matches the FQDN in the certificate config, otherwise replacement does not complete correctly.
  3. Expect connected products (NSX, backup, SRM, VCF Operations) to need re-registration or trust updates.

Further reading

Preserving VM snapshot hierarchy across vCenter…

Preserving VM snapshot hierarchy across vCenter…

On occasion, you might find yourself needing to take multi-level VM snapshots for various testing or development purposes, not an uncommon task for IT administrators. In the past, if you needed to move the VM and preserve its snapshot hierarchy, it was usually difficult and involved manual tasks […]


VMware Social Media Advocacy