PVS Hybrid Azure AD joined catalog VDAs do not register after creation

book

Article ID: CTX697246

calendar_today

Updated On:

Description

VDA fails to register.

Cause

As part of the registration process the  DDC contacts the VDA but VDA returns Unavailable(AzureADJoinInitializing) since it cannot register with Azure AD  

13:53:22:49911,12764,2904,BrokerService.exe,0,BrokerDAL,,0,,,1,Information,"Ping2(S-1-5-21-24118604-1705323714-1318725885-86486): Unavailable(AzureADJoinInitializing)LogonEnabled, VdaSessionLimit=-1, MaxLogons=2, IdleTimes=False, NotAadJoined, OnboardedOntoAzureArc=False, LoadIndexes[<none>]","TraceId=a7beaed450b16c8be8d8c9226f3398bb, SpanId=f2738b928de62254, ParentId=3921cda58e7d5198, TransactionId=a7beaed4-50b1-6c8b-e8d8-xxxxxxxxxx"  

 

This is because the VDA hostname is incorrectly set to the master image hostname . 

The VDA event log shows that the VDA cannot join with Azure AD. 

 

The get join response operation callback failed with exit code: Unknown HResult Error code: 0x801c005b. 
Activity Id: 4c60d0f7-ff1c-4242-8577-xxxxxxxx 
The server returned HTTP status: 400 
Server response was: {"code":"invalid_request","subcode":"error_computer_signature_check_failure","message":"The verification of the signature failed for device 35cef507-xxxxx-xxxx-xxxx- in domain xxxxxxxxxxxxx-45bf-b2c1-xxxxxxxxxx","operation":"DeviceRenew","requestid":"xxxxxxxx-ff1c-xxxx-xxxx-xxxxxxxx"time":"08-18-2026 13:15:50Z"} 

 

/* Because of this error the VDA stays Soft-Registered  

13:53:22:50070,12764,2904,BrokerService.exe,0,BrokerDAL,,0,,,1,Information,"UpdateWorkerLoadData_TXW(S-1-5-21-24118604-1705323714-xxxxxxxxxxx): ignored: SoftRegistration","TraceId=a7beaed450b16c8be8d8c9226f3398bb, SpanId=f2738b928de62254, ParentId=3921cda58e7d5198, TransactionId=a7beaed4-50b1-6c8b-e8d8-xxxxxxxxxx"  

 

The root cause is the wrong name on the VDA.  

Azure AD rejects the join request since hostname is that of the master image which is already registered.

Resolution

Check this key on the master image.  

HKLM:\Software\Citrix\MetaInstall  

These are the possible values. 

0 = 'EndUser'; 1 = 'MasterImagePvs'; 2 = 'MasterImageMcs'; 3 = 'WebSocket 

If the value is 0, then this means the VDA as installed as a RemotePC VDA and so necessary services for PVS are missing. 

For instance, the service "Citrix Pvs for VMs agent" is missing . 

To resolve the issue, reinstall the VDA on the master image and this time choose  

"Create master image to be used for Citrix Provisioning (PVS) streaming" 

Then reseal the image and recreate the catalog.

 image.png

 

Issue/Introduction

Windows 10\11 VDAs that are Hybrid Joined to Azure AD.  

Customer is using   a PowerShell script to create a PVS catalog because XenServer isn’t supported in the Web Studio GUI for creating PVS catalogs. 

The script is based on that documented at  https://docs.citrix.com/en-us/provisioning/2507-1-ltsr/configure/create-hybrid-joined-catalogs.html  amended for XenServer . 

VDAs are created. However the hostname is the  the master image hostname and not the actual VDA hostname. 

The VDA is soft registered but never hard-registers.