VDT 2 is now available!
VDT 2 has been rewritten from the ground up to evolve from a simple collection of python scripts to a python based health reporting framework. This new version provides libraries that standardize the output and format of each check. This means that compatibility for additional products is coming soon!
Release compatibility:
# cd /root/
# unzip vdt-version_number.zip
cd vdt-<version_number>
python vdt.py
Prompts for the password for [email protected]. Many checks will still run even if credentials are not supplied.
The tool will then proceed to run review the output by scrolling up and down in the window. Each test should be self-explanatory in its meaning, findings, and directions. If any check isn't clear in its direction, or a false positive is suspected, please report the issue to our team at [email protected] and we will address it.
VDT 2.x
vi ./vcenter/vc_cfg/vc_vdt.ini
[category:vc_iwa_checks]
name = "IWA/AD Checks"
;[category:vc_iwa_checks]
;name = "IWA/AD Checks"
:wq!
VDT 1.x
If a test hangs for an unreasonable amount of time, use ctrl-c out of the script, then move the test it was running out of the 'scripts' directory. For example:
mv scripts/vc_ad_check.py /tmp/
vSphere Diagnostic Tool does not make any changes to the environment (other than adding it's output to log bundles), and is a read-only set of scripts. There are no passwords recorded in the logs, and all code is non-compiled for easy review.
The hashes listed are only valid for the current files.
The current versions are as follows:
Version |
Compatibility |
MD5SUM |
SHA256SUM |
vdt-v1.1.4.zip | vCenter Server 6.5, 6.7, and 7.0 | 341c8a9cafde3a4ff334f1b26d412c5f | 992f380b2ad0bdb5acda0e60a3b3830c806c6b2b8369427fc6a8199cf99a433f |
vdt-2.2.5_09-05-2025.zip | vCenter Server 7.x, 8.x, and 9.x | fed6ac93307fb5bcb0f3155056a892e2 | 93a113cd683e5e3e72ae966cfd9dce37e6bc62456364f6d7a4acd9b887de2879 |