The mobility service installation failed with error code 95422. UEFI Secure Boot is not supported.

Question

Hi,

I'm a MSP/CSP, and in many years i've been converting and migrating workloads to Azure from various environments.

Sometimes customers want 1:1 migration of servers, Hosted in some private cloud, with no access to the Hypervisor, and some very poor communication from the customers old provider.

I've done this before, but the mobility client has changed a bit over the years.

Scenario.
As stated above, I don't have access to the Hypervisor. That means, I need to migrate the servers as physical machines.

I've deployed an Azure Site recovery server, registrered it all including the servers.

I'm getting the error in mention.

"In the old days"(tm) - I was able to make a workaround on the servers I need to protect, by changing a file in C:\ProgramData\Microsoft Azure Site Recovery\Mobility Service\WMISSH\ - as i remember it, it was "V2A-MOBILITYSERVICE-REQUIREMENTS.json". It was a workaround provided to me from Microsoft support.

The file layout has changed a bit (or i got old and forgetful :) ), and I cant seem to find the line to change.

Any know how to make this workaround - or has there been any other hacks to go around this?

/Take care

Answer 1

Old Workaround:

 

Need to change installer to install on Physical Machine.

 

Go inside folder:

Need to change installer to install on Physical Machine.

 

Go inside folder

C:\ProgramData\Microsoft Azure Site Recovery\Mobility Service

 

Search file V2A-MOBILITYSERVICE-REQUIREMENTS.Json file recursively inside this folder.

 

Open this file. It should contain following attribute,

"OperationName" : "PreCheckBootUEFIValidation",

 

Inside this operation remove attribute

 "Hypervisor" : "vmware"

 

Please make sure to remove comma before this line for json format compatibility.

 

After update BootUefi check should look like,

{

        "CheckName": "BootUEFICheck",

        "OperationName" : "PreCheckBootUEFIValidation",

        "Params": {

            "MinOSMajorVersion": "6",

            "MinOSMinorVersion": "1",

            "MaxNumPartitions": "4",

            "BytesPerSector": "512"

        }

    }

 

 

This folder should contain ASR installer. Now install from the installer in this folder.

 

 

Considering that the product has undergone several changes over time, the workaround might also require some adjustments. One of the changes I identified is the path:

 

 

Need to change installer to install on Physical Machine.

 

Go inside folder:

Need to change installer to install on Physical Machine.

 

Go inside folder

C:\Program Files (x86)\Microsoft Azure Site Recovery

 

Search file V2A-MOBILITYSERVICE-REQUIREMENTS.Json file recursively inside this folder.

 

Open this file. It should contain following attribute,

"OperationName" : "PreCheckBootUEFIValidation",

 

Inside this operation remove attribute

 "Hypervisor" : "vmware"

 

Please make sure to remove comma before this line for json format compatibility.

 

After update BootUefi check should look like,

{

        "CheckName": "BootUEFICheck",

        "OperationName" : "PreCheckBootUEFIValidation",

        "Params": {

            "MinOSMajorVersion": "6",

            "MinOSMinorVersion": "1",

            "MaxNumPartitions": "4",

            "BytesPerSector": "512"

 ----

This solved it.