DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get post/how-to-vsan-witness-9-0 -o yaml$ soultec get post/how-to-vsan-witness-9-0 -o json$ soultec get post/how-to-vsan-witness-9-0 -o toml$ soultec get post/how-to-vsan-witness-9-0 -o xml$ python3 how-to-vsan-witness-9-0.pyPS> ./how-to-vsan-witness-9-0.ps1$ go run how-to-vsan-witness-9-0.go$ node how-to-vsan-witness-9-0.js

apiVersion: soultec.ch/v1kind: Postmetadata: name: how-to-vsan-witness-9-0 locale: en labels: author: daniel-stadelmann series: how-to capability/storage: 2.36 capability/cloud: 1.92 capability/virtualization: 1.42 vendor/vmware: 0.98 annotations: source: blog-content/posts/en/how-to-vsan-witness-9-0.md route: /en/insights/how-to-vsan-witness-9-0/ schema: /nerd/schema/posts.json markdown: /en/insights/how-to-vsan-witness-9-0.mdspec: title: vSAN Witness Appliance 9.0 date: 2025-09-15 author: daniel-stadelmann locale: en summary: >- You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence. capabilities: [storage, cloud, virtualization] vendors: [vmware] series: how-to hero: /blog-assets/how-to-vsan-witness-9-0/hero.webp migrated: 2026-08-24 translationReviewed: false draft: false sections: - body: | You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`). ![](/blog-assets/how-to-vsan-witness-9-0/01.webp) The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well. A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround. ### The workaround It sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter. You will also find that the configuration parameters in the OVA are applied correctly. 1. Install the Witness 2. Add the Witness to vCenter 3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager ![](/blog-assets/how-to-vsan-witness-9-0/02.webp) Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/).status: corpus: 315 alsoLike: - {ref: posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation/vmware-vsan, score: 0.76} - {ref: solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity, score: 0.76} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "how-to-vsan-witness-9-0", "locale": "en", "labels": { "author": "daniel-stadelmann", "series": "how-to", "capability/storage": 2.36, "capability/cloud": 1.92, "capability/virtualization": 1.42, "vendor/vmware": 0.98 }, "annotations": { "source": "blog-content/posts/en/how-to-vsan-witness-9-0.md", "route": "/en/insights/how-to-vsan-witness-9-0/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/how-to-vsan-witness-9-0.md" } }, "spec": { "title": "vSAN Witness Appliance 9.0", "date": "2025-09-15", "author": "daniel-stadelmann", "locale": "en", "summary": "You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.", "capabilities": [ "storage", "cloud", "virtualization" ], "vendors": [ "vmware" ], "series": "how-to", "hero": "/blog-assets/how-to-vsan-witness-9-0/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false, "sections": [ { "body": "You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).\n\n![](/blog-assets/how-to-vsan-witness-9-0/01.webp)\n\nThe vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.\n\nA short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.\n\n### The workaround\n\nIt sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.\n\nYou will also find that the configuration parameters in the OVA are applied correctly.\n\n1. Install the Witness\n2. Add the Witness to vCenter\n3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager\n\n![](/blog-assets/how-to-vsan-witness-9-0/02.webp)\n\nRunning into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/)." } ] }, "status": { "corpus": 315, "alsoLike": [ { "ref": "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vmware-vsan", "score": "0.76" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity", "score": "0.76" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "how-to-vsan-witness-9-0"locale = "en"[metadata.labels]author = "daniel-stadelmann"series = "how-to""capability/storage" = 2.36"capability/cloud" = 1.92"capability/virtualization" = 1.42"vendor/vmware" = 0.98[metadata.annotations]source = "blog-content/posts/en/how-to-vsan-witness-9-0.md"route = "/en/insights/how-to-vsan-witness-9-0/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/how-to-vsan-witness-9-0.md"[spec]title = "vSAN Witness Appliance 9.0"date = 2025-09-15author = "daniel-stadelmann"locale = "en"summary = "You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence."capabilities = ["storage", "cloud", "virtualization"]vendors = ["vmware"]series = "how-to"hero = "/blog-assets/how-to-vsan-witness-9-0/hero.webp"migrated = 2026-08-24translationReviewed = falsedraft = false[[spec.sections]]body = '''You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).![](/blog-assets/how-to-vsan-witness-9-0/01.webp)The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.### The workaroundIt sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.You will also find that the configuration parameters in the OVA are applied correctly.1. Install the Witness2. Add the Witness to vCenter3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager![](/blog-assets/how-to-vsan-witness-9-0/02.webp)Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/).'''[status]corpus = 315search = "/en/search.json"[[status.alsoLike]]ref = "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades"score = "1.00"[[status.alsoLike]]ref = "solutions/vmware/vmware-cloud-foundation/vmware-vsan"score = "0.76"[[status.alsoLike]]ref = "solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity"score = "0.76"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>how-to-vsan-witness-9-0</name> <locale>en</locale> <labels> <author>daniel-stadelmann</author> <series>how-to</series> <entry key="capability/storage">2.36</entry> <entry key="capability/cloud">1.92</entry> <entry key="capability/virtualization">1.42</entry> <entry key="vendor/vmware">0.98</entry> </labels> <annotations> <source>blog-content/posts/en/how-to-vsan-witness-9-0.md</source> <route>/en/insights/how-to-vsan-witness-9-0/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/how-to-vsan-witness-9-0.md</markdown> </annotations> </metadata> <spec> <title>vSAN Witness Appliance 9.0</title> <date>2025-09-15</date> <author>daniel-stadelmann</author> <locale>en</locale> <summary>You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.</summary> <capabilities> <item>storage</item> <item>cloud</item> <item>virtualization</item> </capabilities> <vendors> <item>vmware</item> </vendors> <series>how-to</series> <hero>/blog-assets/how-to-vsan-witness-9-0/hero.webp</hero> <migrated>2026-08-24</migrated> <translationReviewed>false</translationReviewed> <draft>false</draft> <sections> <section> <body>You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).![](/blog-assets/how-to-vsan-witness-9-0/01.webp)The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.### The workaroundIt sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.You will also find that the configuration parameters in the OVA are applied correctly.1. Install the Witness2. Add the Witness to vCenter3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager![](/blog-assets/how-to-vsan-witness-9-0/02.webp)Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/). </body> </section> </sections> </spec> <status> <corpus>315</corpus> <alsoLike> <item> <ref>posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vmware-vsan</ref> <score>0.76</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity</ref> <score>0.76</score> </item> </alsoLike> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "how-to-vsan-witness-9-0", "locale": "en", "labels": { "author": "daniel-stadelmann", "series": "how-to", "capability/storage": 2.36, "capability/cloud": 1.92, "capability/virtualization": 1.42, "vendor/vmware": 0.98, }, "annotations": { "source": "blog-content/posts/en/how-to-vsan-witness-9-0.md", "route": "/en/insights/how-to-vsan-witness-9-0/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/how-to-vsan-witness-9-0.md", }, }, "spec": { "title": "vSAN Witness Appliance 9.0", "date": "2025-09-15", "author": "daniel-stadelmann", "locale": "en", "summary": "You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.", "capabilities": ["storage", "cloud", "virtualization"], "vendors": ["vmware"], "series": "how-to", "hero": "/blog-assets/how-to-vsan-witness-9-0/hero.webp", "migrated": "2026-08-24", "translationReviewed": False, "draft": False, "sections": [ { "body": ( "You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).\n" "\n" "![](/blog-assets/how-to-vsan-witness-9-0/01.webp)\n" "\n" "The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.\n" "\n" "A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.\n" "\n" "### The workaround\n" "\n" "It sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.\n" "\n" "You will also find that the configuration parameters in the OVA are applied correctly.\n" "\n" "1. Install the Witness\n" "2. Add the Witness to vCenter\n" "3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager\n" "\n" "![](/blog-assets/how-to-vsan-witness-9-0/02.webp)\n" "\n" "Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/)." ), }, ], }, "status": { "corpus": 315, "alsoLike": [ { "ref": "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades", "score": "1.00", }, { "ref": "solutions/vmware/vmware-cloud-foundation/vmware-vsan", "score": "0.76", }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity", "score": "0.76", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Post' metadata = [ordered]@{ name = 'how-to-vsan-witness-9-0' locale = 'en' labels = [ordered]@{ author = 'daniel-stadelmann' series = 'how-to' 'capability/storage' = 2.36 'capability/cloud' = 1.92 'capability/virtualization' = 1.42 'vendor/vmware' = 0.98 } annotations = [ordered]@{ source = 'blog-content/posts/en/how-to-vsan-witness-9-0.md' route = '/en/insights/how-to-vsan-witness-9-0/' schema = '/nerd/schema/posts.json' markdown = '/en/insights/how-to-vsan-witness-9-0.md' } } spec = [ordered]@{ title = 'vSAN Witness Appliance 9.0' date = '2025-09-15' author = 'daniel-stadelmann' locale = 'en' summary = 'You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.' capabilities = @('storage', 'cloud', 'virtualization') vendors = @('vmware') series = 'how-to' hero = '/blog-assets/how-to-vsan-witness-9-0/hero.webp' migrated = '2026-08-24' translationReviewed = $false draft = $false sections = @( [ordered]@{ body = @'You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).![](/blog-assets/how-to-vsan-witness-9-0/01.webp)The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.### The workaroundIt sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.You will also find that the configuration parameters in the OVA are applied correctly.1. Install the Witness2. Add the Witness to vCenter3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager![](/blog-assets/how-to-vsan-witness-9-0/02.webp)Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/).'@ } ) } status = [ordered]@{ corpus = 315 alsoLike = @( [ordered]@{ ref = 'posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades' score = '1.00' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/vmware-vsan' score = '0.76' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity' score = '0.76' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": map[string]any{ "name": "how-to-vsan-witness-9-0", "locale": "en", "labels": map[string]any{ "author": "daniel-stadelmann", "series": "how-to", "capability/storage": 2.36, "capability/cloud": 1.92, "capability/virtualization": 1.42, "vendor/vmware": 0.98, }, "annotations": map[string]any{ "source": "blog-content/posts/en/how-to-vsan-witness-9-0.md", "route": "/en/insights/how-to-vsan-witness-9-0/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/how-to-vsan-witness-9-0.md", }, }, "spec": map[string]any{ "title": "vSAN Witness Appliance 9.0", "date": "2025-09-15", "author": "daniel-stadelmann", "locale": "en", "summary": "You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.", "capabilities": []any{"storage", "cloud", "virtualization"}, "vendors": []any{"vmware"}, "series": "how-to", "hero": "/blog-assets/how-to-vsan-witness-9-0/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false, "sections": []any{ map[string]any{ "body": "You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).\n" + "\n" + "![](/blog-assets/how-to-vsan-witness-9-0/01.webp)\n" + "\n" + "The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.\n" + "\n" + "A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.\n" + "\n" + "### The workaround\n" + "\n" + "It sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.\n" + "\n" + "You will also find that the configuration parameters in the OVA are applied correctly.\n" + "\n" + "1. Install the Witness\n" + "2. Add the Witness to vCenter\n" + "3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager\n" + "\n" + "![](/blog-assets/how-to-vsan-witness-9-0/02.webp)\n" + "\n" + "Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/).", }, }, }, "status": map[string]any{ "corpus": 315, "alsoLike": []any{ map[string]any{ "ref": "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades", "score": "1.00", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/vmware-vsan", "score": "0.76", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity", "score": "0.76", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Post", metadata: { name: "how-to-vsan-witness-9-0", locale: "en", labels: { author: "daniel-stadelmann", series: "how-to", "capability/storage": 2.36, "capability/cloud": 1.92, "capability/virtualization": 1.42, "vendor/vmware": 0.98, }, annotations: { source: "blog-content/posts/en/how-to-vsan-witness-9-0.md", route: "/en/insights/how-to-vsan-witness-9-0/", schema: "/nerd/schema/posts.json", markdown: "/en/insights/how-to-vsan-witness-9-0.md", }, }, spec: { title: "vSAN Witness Appliance 9.0", date: "2025-09-15", author: "daniel-stadelmann", locale: "en", summary: "You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.", capabilities: ["storage", "cloud", "virtualization"], vendors: ["vmware"], series: "how-to", hero: "/blog-assets/how-to-vsan-witness-9-0/hero.webp", migrated: "2026-08-24", translationReviewed: false, draft: false, sections: [ { body: "You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (`Your license for ESXi has expired.`).\n" + "\n" + "![](/blog-assets/how-to-vsan-witness-9-0/01.webp)\n" + "\n" + "The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.\n" + "\n" + "A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.\n" + "\n" + "### The workaround\n" + "\n" + "It sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.\n" + "\n" + "You will also find that the configuration parameters in the OVA are applied correctly.\n" + "\n" + "1. Install the Witness\n" + "2. Add the Witness to vCenter\n" + "3. Upgrade the Witness to 9.0 with vSphere Lifecycle Manager\n" + "\n" + "![](/blog-assets/how-to-vsan-witness-9-0/02.webp)\n" + "\n" + "Running into trouble, or have a question? [Get in touch](https://soultec.ch/contact-us/).", }, ], }, status: { corpus: 315, alsoLike: [ { ref: "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades", score: "1.00", }, { ref: "solutions/vmware/vmware-cloud-foundation/vmware-vsan", score: "0.76", }, { ref: "solutions/vmware/vmware-cloud-foundation/addon/vsan-additional-capacity", score: "0.76", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 62 lines · YAML · validated at build# 65 lines · JSON · validated at build# 75 lines · TOML · validated at build# 87 lines · XML · validated at build# 87 lines · Python · read back at build, equals the JSON record# 84 lines · PowerShell · read back at build, equals the JSON record# 97 lines · Go · read back at build, equals the JSON record# 82 lines · JavaScript · read back at build, equals the JSON record · served at /en/insights/how-to-vsan-witness-9-0.md

How-To · 2025-09-15

vSAN Witness Appliance 9.0

You have probably run into the same problem I did: a freshly deployed 9.0 Witness Appliance that ignores its configuration and reports an expired licence.

2025-09-15Date

Daniel StadelmannAuthor

1Min read

Topics Storage 2.36 Cloud 1.92 Virtualization 1.42

Vendors VMware 0.98

You have probably run into the same problem I did. You downloaded the VMware vSAN ESA Witness Appliance for 9.0 (VMware-vSAN-ESA-Witness-9.0.0.0.24755427.ova) and deployed it on your Witness Host. Then you found two things: the configuration parameters were not applied, and, worse, the Witness Appliance reports an expired licence (Your license for ESXi has expired.).

The vSAN Witness does ship with a built-in OEM licence, but it is not picked up here. With VCF 9.0 there are no licence keys any more either, so the old workaround with a temporary key is gone as well.

A short support session with Broadcom Support settled it: this is a bug. There is no fix yet, but there is a workaround.

The workaround

It sounds silly and it works. Take the vSAN ESA Witness 8.0.3 OVA (VMware-vSAN-ESA-Witness-8.0U3e-24674464.ova) and upgrade it to 9.0 through vCenter.

You will also find that the configuration parameters in the OVA are applied correctly.