<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>VMware Cloud Foundation on DimensionQuest - Burke's Blog!</title><link>https://dimensionquest.net/tags/vmware-cloud-foundation/</link><description>Recent content in VMware Cloud Foundation on DimensionQuest - Burke's Blog!</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 1999-2026 Burke Azbill. All Rights Reserved.</copyright><lastBuildDate>Tue, 25 Mar 2025 13:34:00 -0400</lastBuildDate><atom:link href="https://dimensionquest.net/tags/vmware-cloud-foundation/index.xml" rel="self" type="application/rss+xml"/><item><title>VCF SDDC Manager: Identity Internal Server Error</title><link>https://dimensionquest.net/2025/03/vcf-sddc-manager-identity-internal-server-error/</link><pubDate>Tue, 25 Mar 2025 13:34:00 -0400</pubDate><guid>https://dimensionquest.net/2025/03/vcf-sddc-manager-identity-internal-server-error/</guid><description><![CDATA[<p><img loading="lazy" class="img-fluid" src="images/vcf-internal-error.png"  alt="Identity Internal Server Error"   /></p>
<p>I was recently working on our lab environment at work that runs VCF 5.2.1. This &ldquo;lab&rdquo; is the one used in the VMware Livefire classes so it is quite similar to those used in the VMware Explore Hands On Labs. In any case, I had attempted to use Lifecycle Manager to start one of the VMs in the environment and it immediatel failed due to a bad password on vCenter. I did a RETRY on the Request and manually specified the password to use. That immediately went through to success. Since LCM was deployed via VCF&rsquo;s SDDC Manager, I decided to power that up and attempt to login to it. NOTE: Since this is a lab, we don&rsquo;t always power on SDDC Manager.</p>]]></description><enclosure url="https://dimensionquest.net/2025/03/vcf-sddc-manager-identity-internal-server-error/images/vcf-internal-error.png" length="61633" type="image/png"/></item><item><title>Home Server Build for VMware ESXi and Holodeck</title><link>https://dimensionquest.net/2024/11/home-server-build-for-vmware-esxi-and-holodeck/</link><pubDate>Sat, 30 Nov 2024 17:33:34 +0000</pubDate><guid>https://dimensionquest.net/2024/11/home-server-build-for-vmware-esxi-and-holodeck/</guid><description><![CDATA[<p>When working with a Holodeck environment, a pretty beefy system is required. While you can get vSAN Ready nodes from vendors like SuperMicro, Dell, HP, etc&hellip; I chose to DIY because I really enjoy building systems and wanted something more home-friendly (Read: Less power hungry and quieter.) I&rsquo;ll do a more in-depth post soon, but for now I&rsquo;ve had a number of request for my Bill Of Materials (BOM) for my new server.</p>]]></description><enclosure url="https://dimensionquest.net/2024/11/home-server-build-for-vmware-esxi-and-holodeck/images/holodeck-diagram.png" length="169496" type="image/png"/></item><item><title>How to update upstream DNS servers in Holodeck Cloud Builder</title><link>https://dimensionquest.net/2024/10/holodeck-upstream-dns/</link><pubDate>Thu, 03 Oct 2024 17:33:34 +0000</pubDate><guid>https://dimensionquest.net/2024/10/holodeck-upstream-dns/</guid><description>&lt;p>When working with a Holodeck environment, the Cloud Builder VM acts as DNS for the lab environment. This handles all dns resolution within the lab itself and forwards all non-lab related DNS queries to upstream DNS servers. These servers are defined VMware Cloud Foundation Lab Constructor (VLC) during the intiial deployment of the lab environment. I needed to do this recently in a lab environment that I moved from one cloud to another, where the originally specified upstream DNS Servers no longer existed. Having invalid upstream DNS Server specified results in extended time to resolution and/or failed requests to resources that reside outside of the Holodeck lab environment.&lt;/p></description><enclosure url="https://dimensionquest.net/2024/10/holodeck-upstream-dns/images/holodeck-diagram.png" length="169496" type="image/png"/></item><item><title>SDDC Manager Precheck Fails NSX-T Password Expired</title><link>https://dimensionquest.net/2021/04/sddc-manager-precheck-fails-nsxt-password-expired/</link><pubDate>Tue, 06 Apr 2021 06:49:39 -0400</pubDate><guid>https://dimensionquest.net/2021/04/sddc-manager-precheck-fails-nsxt-password-expired/</guid><description><![CDATA[<p><img loading="lazy" class="img-fluid" src="featured-image-preview"  alt="NSX-T Password Validity Check Failed in SDDC Manager"   /></p>
<p>I have gotten into the habit of disabling password expiration on linux systems in my lab environments because often times, when dealing with VMware products, these are set to a year or less. Of course forgetting about an expired password can lead to other issues and time troubleshooting. My Validity Check failed due to Password has expired error&hellip;</p>]]></description><enclosure url="https://dimensionquest.net/2021/04/sddc-manager-precheck-fails-nsxt-password-expired/images/nsx-t-password-validity-check-failed.png" length="87143" type="image/png"/></item><item><title>VCF SDDC Manager Not Showing ESXi Bundle</title><link>https://dimensionquest.net/2021/04/vcf-sddc-manager-not-showing-esxi-bundle/</link><pubDate>Sun, 04 Apr 2021 13:34:00 -0400</pubDate><guid>https://dimensionquest.net/2021/04/vcf-sddc-manager-not-showing-esxi-bundle/</guid><description><![CDATA[<p><img loading="lazy" class="img-fluid" src="featured-image-preview"  alt="VCF Bundle Management"   /></p>
<p>During a recent upgrade of VCF 4.1 to 4.1.0.1 and then on to 4.2, I found myself in a bit of an unsupported situation due to the use of a build that was not part of the VCF 4.2 Bill Of Materials (BOM).</p>
<p>Symptom: SDDC Manager 4.2.0 will not apply the 4.2 update to the ESXi hosts even though the Update 4.2.0.0 bundle for VMware ESXi 7.0 Update 1d has already been downloaded.</p>]]></description><enclosure url="https://dimensionquest.net/2021/04/vcf-sddc-manager-not-showing-esxi-bundle/images/vcf-bundle-management.png" length="301481" type="image/png"/></item></channel></rss>