Windows 11 VDA machines stuck at Initializing for Azure AD or Hybrid Azure AD

Windows 11 VDA machines stuck at Initializing for Azure AD or Hybrid Azure AD

book

Article ID: CTX475187

calendar_today

Updated On:

Description

For Citrix MCS provisioned Azure AD or Hybrid Azure AD joined machine catalogs that use Windows 11 22H2 or 23H2 as master VMs’ OS, the VDA machines might be stuck at “Initializing” status after startup. And when you login to the VDA machines and execute the “dsregcmd /status” command, “Provider: MISSING” message will be shown as below. 


image.png
 

Environment

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.

Resolution

To resolve this issue, you can upgrade your VDA to version 2303 or later for CVAD current release or to version 2203 CU5 or later for CVAD LTSR release.  Alternatively, you can configure your master VM as below:

  • For Azure AD joined machine catalogs, create a scheduled task in the master VM that executes the following command at system startup using SYSTEM account.

reg ADD HKLM\Software\AzureAD\VirtualDesktop /v Provider /t REG_SZ /d Citrix /f

 

  • For Hybrid Azure AD joined machine catalogs, create a scheduled task in the master VM that executes the following commands at system startup using SYSTEM account.

$VirtualDesktopKeyPath = 'HKLM:\Software\AzureAD\VirtualDesktop'
$WorkplaceJoinKeyPath = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin'
$MaxCount = 60

for ($count = 1; $count -le $MaxCount; $count++)
{
    if ((Test-Path -Path $VirtualDesktopKeyPath) -eq $true)
    {
        $provider = (Get-Item -Path $VirtualDesktopKeyPath).GetValue("Provider", $null)
        if ($provider -eq 'Citrix')
        {
            break;
        }

        if ($provider -eq 1)
        {
            Set-ItemProperty -Path $VirtualDesktopKeyPath -Name "Provider" -Value "Citrix" -Force
            Set-ItemProperty -Path $WorkplaceJoinKeyPath -Name "autoWorkplaceJoin" -Value 1 -Force
            Start-Sleep 5
            dsregcmd /join
            break
        }
    }

    Start-Sleep 1
}




 


Problem Cause

Dsreg utility fails to recognize the virtual desktop provider settings in the VDA machines and blocks the Azure AD or Hybrid Azure AD join of the machines. Citrix is working with Microsoft to deliver a permanent fix in new releases.

Additional Information

Use Machine identities | Citrix DaaS articles to plan, deploy and troubleshoot Citrix MCS provisioned Azure AD or Hybrid Azure AD joined machine catalogs.

Reference to schedule a task: https://learn.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/use-at-command-to-schedule-tasks