Horizon Provisioning Fails with VC_FAULT Error During vCenter Server Maintenance - VMware vSphere
search cancel

Horizon Provisioning Fails with VC_FAULT Error During vCenter Server Maintenance - VMware vSphere

book

Article ID: 454739

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Automated Horizon provisioning may enter a "disabled" state and report a VC_FAULT error immediately following a vCenter Server reboot or OS upgrade. This occurs because Horizon pre-check workflows fail when storage services are not yet ready.

Environment

VMware vCenter Server

Cause

 Following a vCenter reboot, the Storage Policy Based Management (SPBM) service requires approximately 30 to 45 minutes to fully initialize and register VASA providers. If Horizon attempts to provision machines during this initialization phase, the missing PBM/VASA connection triggers a critical fault.

Resolution

Review Horizon Provision and stop it when the vCenter is under maintenance. 

Preventative Steps (Before Upgrading or Restarting vCenter):

  1. Log in to the Horizon Console.

  2. Navigate to Desktops / Automated Desktop Pools.

  3. Temporarily Disable Provisioning for all active pools.

  4. Proceed with the vCenter Server upgrade or maintenance.

  5. Once vCenter Server is fully operational, Enable Provisioning in Horizon Console.

Powered by Wolken Software