<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VMware on Support Tools</title><link>https://support.tools/categories/vmware/</link><description>Recent content in VMware on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 17 Jun 2025 10:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/vmware/index.xml" rel="self" type="application/rss+xml"/><item><title>Enterprise ESXi Custom Installer Automation: Comprehensive Guide to Production VMware Deployment and Advanced Driver Integration</title><link>https://support.tools/enterprise-esxi-custom-installer-automation-comprehensive-deployment-guide/</link><pubDate>Tue, 17 Jun 2025 10:00:00 -0500</pubDate><guid>https://support.tools/enterprise-esxi-custom-installer-automation-comprehensive-deployment-guide/</guid><description>&lt;p&gt;Enterprise ESXi deployment requires sophisticated installer customization, automated driver integration, and robust deployment frameworks to ensure consistent infrastructure provisioning across diverse hardware platforms. This guide covers comprehensive ESXi image building automation, enterprise deployment strategies, advanced driver management, and production-grade installation frameworks for large-scale VMware environments.&lt;/p&gt;</description></item><item><title>VMware Default Passwords and Credentials: Complete Security Reference Guide</title><link>https://support.tools/vmware-default-passwords-security-guide/</link><pubDate>Tue, 04 Feb 2025 10:00:00 -0500</pubDate><guid>https://support.tools/vmware-default-passwords-security-guide/</guid><description>&lt;p&gt;Understanding VMware&amp;rsquo;s default credentials is crucial for initial deployment and security hardening. This comprehensive guide covers default usernames, passwords, and security best practices across VMware&amp;rsquo;s virtualization infrastructure components, including critical security warnings and modern authentication recommendations.&lt;/p&gt;</description></item><item><title>Removing vCenter from died Active Directory</title><link>https://support.tools/post/vcenter-failing-to-leave-domain/</link><pubDate>Tue, 15 Feb 2022 22:21:00 +0000</pubDate><guid>https://support.tools/post/vcenter-failing-to-leave-domain/</guid><description>&lt;p&gt;I lost both of my domain controllers earlier this week, even after I restored one from a VM backup. There was too much corruption. As a result, I rebuilt my domain with new domain controllers, joined all my Windows virtual machines to the new domain, recreated my user accounts, etc. One of the challenges I ran into was getting my vCenter to leave the old domain so it could join the new domain. The old domain was no longer available, so I could not leave it.&lt;/p&gt;&#10;&lt;p&gt;When trying to “Leave Active Directory Domain” in the GUI, I got the following error:&lt;/p&gt;&#10;&lt;div class="code-block" data-copy-label="Copy code, block 1"&gt;&#10; &lt;div class="code-block-header" data-pagefind-ignore&gt;&lt;/div&gt;&#10; &lt;pre tabindex="0"&gt;&lt;code&gt;ldm client exception: Error trying to leave AD, error code [1332], user [mmattox@ad.support.tools]&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;</description></item><item><title>ESXi boot stuck at iscsi_vmk load successfully</title><link>https://support.tools/post/esxi-boot-stuck-at-iscsivmk/</link><pubDate>Sun, 24 Oct 2021 01:50:00 +0000</pubDate><guid>https://support.tools/post/esxi-boot-stuck-at-iscsivmk/</guid><description>&lt;p&gt;Problem: ESXi boot slow/stalled/stuck at “iscsi_vmk loaded successfully”&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="https://cdn.support.tools/posts/esxi-boot-stuck-at-iscsivmk/esxi07_stuck_at_iscsi.jpg" alt=""&gt;&lt;/p&gt;</description></item><item><title>Unlock Root Account on ESXi</title><link>https://support.tools/post/unlock-root-account-on-esxi/</link><pubDate>Wed, 08 Sep 2021 04:53:00 +0000</pubDate><guid>https://support.tools/post/unlock-root-account-on-esxi/</guid><description>&lt;p&gt;If the root account gets locked out, you won&amp;rsquo;t be able to access ESXi using SSH or the vSphere Web Client. Follow the steps below to unlock the account.&lt;/p&gt;&#10;&lt;h3 id="common-symptoms"&gt;Common Symptoms&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;You receive an &amp;ldquo;incorrect username/password&amp;rdquo; error even though the credentials are correct.&lt;/li&gt;&#10;&lt;li&gt;By default, ESXi 6.x has the following lockout behavior:&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Maximum Attempts&lt;/strong&gt;: After 10 failed login attempts, the account is locked.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Lockout Applies To&lt;/strong&gt;: SSH and the vSphere Web Services SDK.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Lockout Does Not Apply To&lt;/strong&gt;: Direct Console User Interface (DCUI) and the ESXi Shell.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>vSphere 7 – Certificates with VMCA as Subordinate</title><link>https://support.tools/post/vsphere-7-certificates-with-vmca-as-subordinate/</link><pubDate>Tue, 07 Sep 2021 07:46:00 +0000</pubDate><guid>https://support.tools/post/vsphere-7-certificates-with-vmca-as-subordinate/</guid><description>&lt;p&gt;For enterprises that need fully trusted SSL certificates for the vSphere 7.0 environment, you have two basic options:&lt;/p&gt;&#10;&lt;p&gt;Full Custom Mode: Manually replace all certificates for vCenter and the ESXi hosts with your trusted certificates.&#10;Subordinate CA Mode: Use the built-in VMCA service as an official subordinate CA of your existing PKI infrastructure. After the initial configuration, automates the issuing of SSL certs for your vSphere environment. This is the method covered in this blog post.&#10;VMware offers two other certificate options: Fully Managed and hybrid mode, for a total of four certificate options. You can find out more about all of them in this VMware blog post.&lt;/p&gt;&#10;&lt;p&gt;In a high-security environment, it is very likely the security team will NOT let you configure the vCenter VMCA as a subordinate CA. So, you will be left with the full custom mode if you want 100% of the certificates trusted. However, if you are in a situation where you can configure the VMCA as a subordinate CA, this post is for you!&lt;/p&gt;&#10;&lt;p&gt;Note: Before you do this replacement in production, I strongly urge you to set up a test vCenter instance and run this entire procedure. Botched certificate replacements can lead to bad days. And another tip for a lab test is to snapshot the vCenter VM before you try the process. That way, you can easily roll back should things go south.&lt;/p&gt;</description></item><item><title>How to Fix 'Migrate greyed out in vCenter for a single VM'</title><link>https://support.tools/post/vmware-mirgate-greyed-out/</link><pubDate>Tue, 22 Dec 2020 10:56:00 +0000</pubDate><guid>https://support.tools/post/vmware-mirgate-greyed-out/</guid><description>&lt;p&gt;While migrating some VMs to a new storage array, I ran into an issue while moving the last VM, which, of course, was my vCenter appliance. When I right-clicked the VM in vCenter, then went to migrate. The migration option was greyed out, which blocked the migration.&lt;/p&gt;&#10;&lt;p&gt;TL;DR&#10;Follow VMware&amp;rsquo;s KB &lt;a href="https://kb.vmware.com/s/article/1029926"&gt;1029926&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>