Newly Created VMs via MCS are invisible on Azure portal whilist visible in Citrix Studio
Article ID: CTX477228
Updated On:
Description
Updated dedicate MCS catalog on Azure with PowerShell:
Publish-ProvMasterVmImage -ProvisioningSchemeName "%provisioningSchemeName%" -MasterImageVM "%templatePSPath%"
After that we add a machine to the original catalog, no machine is created on Azure so it's invisible.
Meanwhile, the process in Studio seems to be completed with no errors.
Same behavior when we create a new catalog with the updated template.
On the Azure management portal, we can see that the identity disk has been created but OS disk has not.
Resolution
""State"": ""StoppedDeallocated""
By further checking, we are able to see the new VM in Studio although it's invisible in Azure.
We add the VM to a delivery group, and power it on.
Finally, this new VM appears in the Azure portal.
Problem Cause
This is a behavior decided by “Azure on-demand provisioning” feature initially rollout in CVAD Cloud, and was later integrated into on-prem CVAD L1912 LTSR since CU3:
https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/1912-ltsr/install-configure/install-prepare/azure-resource-manager.html#azure-on-demand-provisioning
With the feature, the provisioned VM is only created in Azure (p.s. “create” herein means composing the VM entity by the related components like disk, network etc.) when DDC initiates a power-on action to the VM.
Instead, once the provisioned VM is stopped/deallocated, the VM entity turns invisible in Azure portal.
In Citrix Studio, the VM should be always visible, regardless it is running or not.
