Hi Duco,
The check across 9.0.1 and 9.0.2 remains the same. You need min. 24 CPU for deploying VCFA on OSA and 32 CPU for deploying VCFA on ESA for it to work in the nested setup based on our testing.
There are ways to hack around it, however if VCFA does not work or the deployment fails, then there is nothing we can do. If VCFA was working on your same infrastructure with 9.0.1, here is how you can skip this check for 9.0.2:
After running the New-HoloDeckInstance and letting it fail at the precheck, with the config loaded in the session, run the command:
vi $config.state
This will open up the state file. Look for the JSON object "Test-TargetHostCpu" and change its status from "InProgress" to "Success" and save the file. Then re-run the New-HoloDeckInstance command and it should continue further
-------------------------------------------
Original Message:
Sent: Mar 06, 2026 03:49 AM
From: Duco
Subject: Not able to deploy Automation in 9.0.2.0
In 9.0.1.0 I was able to deploy Automation. With 9.0.2.0 the recheck complains about not having 24 cores .... Has this behavior changed?
I do know my resources are limited. A am deploying to a physical cluster with 4 nodes and 20 cores (40 threads) per node.
Why did this work in 9.0.1.0 and not in 9.0.2.0? Can I skip the check?
Duco
-------------------------------------------