Deploying Azure Local on unsupported hardware

Preface

Let start by saying, this is not a great idea and you probably shouldn’t be doing this. BUT, sometimes you just need to get Azure local stood up on some lab hardware for a quick test or one of the health checks may have a little bug in it. This is obviously not supported, and again you probably shouldn’t do this.

When you deploy Azure Local it runs many health checks, and that’s a good thing. Bypassing these health checks is not easy, nor should it be. Personally, I’ve had to do this for some logic issues in the Test-NetAdapter check, the Test-MemoryProperties test for some lab hardware without ECC, etc.

Bypass process

Navigate to the following paths on the nodes. Node1 is slightly different from the other nodes in the cluster.

First Node: c$\Program Files\WindowsPowerShell\Modules\AzStackHci.EnvironmentChecker

Other Nodes: c$\Program Files\WindowsPowerShell\Modules\AzStackHci.EnvironmentChecker\10.2602.0.2003 (Fill in current version)

Create a text file named “ExcludeTests.txt” and paste whichever test you need to skip into the file.

Available hardware tests:

‘Test-Processor’, ‘Test-NetAdapter’, ‘Test-MemoryCapacity’, ‘Test-MemoryProperties’, ‘Test-Gpu’, ‘Test-Baseboard’, ‘Test-Model’, ‘Test-VirtualizationBasedSecurity’, ‘Test-PhysicalDisk’, ‘Test-TpmVersion’, ‘Test-TpmProperties’, ‘Test-SecureBoot’, ‘Test-MinCoreCount’