UEFI Secure Boot is not supported IN AZURE Error Code 95422

 

  • Provider error code: 95422 
     Provider error message: The mobility service installation failed with error code 95422. 
    Provider error possible causes: UEFI Secure Boot is not supported. Provider error recommended action: Please refer to https://aka.ms/asr-installation-prerequisites-windows
  • Check the provider error for more details.
  • Resolve the issue as recommended in the provider error details.
  • 4/1/2021, 4:46:33 PM
     
    Solution
    power off the vm
     
     
    Right on the vm click on edit settings
     
     
     
     Select the VM Options and click on Boot options Select the Bios
     
     
    OR 
    Remove the secure boot  Option and Try

     
    Click  on OK ........

Comments

  1. Unknown13 August 2021 at 00:10

    hola, muchas gracias por la valiosa ayuda me ayudaron bastante con esta informacion ya que el fabricante no fue muy claro al momento de desmontar la interfaz del almacenamiento.

    ReplyDelete

Post a Comment

Popular posts from this blog

Zabbix Server is not working: the information dispaly may not be current

Image
  Details  Cannot display item queue. Connection to Zabbix server "localhost:10051" refused. Possible reasons: 1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. Connection refused Observation:- In Centos 9 [root@nmtool ~]# systemctl status zabbix-server.service ● zabbix-server.service - Zabbix Server      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: d>     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 10:36:52 IST;>    Process: 57289 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCC>    Process: 57295 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)    Main PID: 57291 (code=exited, status=0/
Read more

How to install VNX Launcher that has embedded java and Firefox

Image
  Alternative for Adobe Flash Player to access Unisphere. Symptoms VNXe Unisphere in older OE revisions is not accessible after December 31, 2020. The Adobe Flash Player plug-in is no longer supported in browsers. VNXe Unisphere used to require a browser with the Flash Player plug-in. Cause When VNXe is running an older OE revision, Adobe Flash Player is required by Unisphere. Refer: https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf?key=1588743011568 Adobe has expired Flash Player as of December 31, 2020.   Details: https://www.adobe.com/products/flashplayer/end-of-life.html Resolution Newer VNXe OE revisions support HTML5. Once the VNXe is upgraded, Unisphere will work. Since December 31, 2020 browsers do not support Adobe Flash Player. Most browsers support HTML5. VNXe Unisphere must also support HTML5 in order to use VNXe Unisphere. HTML5 support is delivered in these VNXe revisions:       VNXe3200: VNXe Operating Env
Read more

DHCP FAILED APIPA IS USED

Image
Hi to all, In a Cisco packet tracer while i am trying to connect the dhcp server to pc it will getting the error like dhcp failed. APIPA is being used. For this issues this is also one reason.dhcp is not configured correctly. If we create a  vlan's in the switch's and we configured dhcp server in the layer 3 switch or layer 2 switch or in router. VLAN 10 NAME SALES VLAN 20 NAME DATA We created two vlan's now creating dhcp server for that  Switch(config)#ip dhcp pool name sales (should be the vlan name. not any other name.) Switch(Dhcp-config)#network 192.168.10.0 255.255.255.0  Switch(dhcp-config)#default-router 192.168.10.1 Switch(dhcp-config)#exit Swithc(config)#ip dhcp pool name data Switch(dhcp-config)#network 192.168.20.0 255.255.255.0 Switch(dhcp-config)#default-router 192.168.20.1 Switch(dhcp-config)#exit
Read more