<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VCF Automation on iThinkVirtual™</title><link>https://ithinkvirtual.com/tags/vcf-automation/</link><description>Recent content in VCF Automation on iThinkVirtual™</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 14:00:00 -0400</lastBuildDate><atom:link href="https://ithinkvirtual.com/tags/vcf-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>VMware Cloud Foundation 9.1 Upgrade - Part 3: VCF Automation and Operations for Logs</title><link>https://ithinkvirtual.com/posts/vcf-9-1-upgrade-part-3-automation-logs/</link><pubDate>Tue, 06 Oct 2026 14:00:00 -0400</pubDate><guid>https://ithinkvirtual.com/posts/vcf-9-1-upgrade-part-3-automation-logs/</guid><description>&lt;p&gt;With SDDC Manager and the new VCF Management Services runtime in place after &lt;a href="https://ithinkvirtual.com/posts/vcf-9-1-upgrade-part-2-sddc-manager-management-services/"&gt;Part 2&lt;/a&gt;, Part 3 tackles two more components: &lt;strong&gt;VCF Automation&lt;/strong&gt; and &lt;strong&gt;VCF Operations for Logs&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;These two matter for a reason beyond just version numbers. As the &lt;a href="https://ithinkvirtual.com/posts/vcf-9-1-upgrade-series-overview/"&gt;series overview&lt;/a&gt; explains, the cert and password freeze window kicked in the moment I upgraded VCF Operations back in &lt;a href="https://ithinkvirtual.com/posts/vcf-9-1-upgrade-part-1-vcf-operations/"&gt;Part 1&lt;/a&gt;. VCF Automation and Logs are two of the four components stuck behind that freeze (the Identity Broker and VCF Operations for Networks are the others), so getting them to 9.1 lifts it for them.&lt;/p&gt;</description></item></channel></rss>