Symptom 1: During Delivery Group creation the warning "There are no AppDisks compatible with the selected machines" appears on the 'AppDisks' page.


Symptom 2: The AppDisks page is not present during Delivery Group creation when specific machine catalogs are selected.
 

Symptom 3: Attempts to add AppDisks to an existing Delivery Group return the error "There are no suitable AppDisks for this Delivery Group".

Step 1: Ensure that the Machine Catalog selected during Delivery Group creation is compatible with AppDisk

• Open PowerShell and issue 'Get-BrokerCatalog | select Name, ProvisioningType, AllocationType, PersistUserChanges | fl'
• Ensure the following configurations:
  • ProvisioningType is set to either 'PVS' or 'MCS'
  • AllocationType is 'Random'
  • PersistUserChanges is set to 'Discard'
  • Ex. Filtered output from 'Get-BrokerCatalog' cmdlet that displays both compatible and incompatible Machine Catalogs, '2012 AppDisk Creator' and '2012 Test Catalog' respectively​
• If the properties of the Machine Catalog do not match expected values a new Machine Catalog must be created with a compatible AppDisk configuration. 

Step 2: Ensure that machines within the Delivery Group are compatible with AppDisk

1. Open Powershell and issue 'Get-AppLibAppDisk | select AppDiskName, HypervisorConnectionName, HypervisorConnectionUid | fl', and note the 'HypervisorConnectionUid' of the desired AppDisk
2. Issue 'Get-BrokerHypervisorConnection | where{$_.HypHypervisorConnectionUid -eq "[HypervisorConnectionUid of the AppDisk]"}', and note the 'Uid' of the HypervisorConnection object  
3. Issue 'Get-BrokerMachine [MachineName] | select MachineName, HypervisorConnectionName, HypervisorConnectionUid' and compare the 'HypervisorConnectionUid' of the machine that you want to deploy into the Delivery Group against the 'Uid' value obtained from the 'Get-BrokerHypervisorConnection' cmdlet                                                                                                                                                                                                                                                                     
4.  The 'HypervisorConnectionUid' of the machine should match the 'Uid' of the HypervisorConnection. If the HypervisorConnection used by the AppDisk is different from the one set on the machine then set the HypervisorConnectionUid of the machine to match that used by the AppDisk:
   • MCS - Create a new Machine Catalog and select the desired Host Connection. The HypervisorConnectionUid of MCS created machines cannot be manually modified.
   • PVS - 'Get-BrokerMachine [MachineName] | Set-BrokerMachine -HypervisorConnectionUid [Uid of HypervisorConnection utilized by AppDisk]                           

---

Problem Cause

Citrix Studio utilizes the properties of the Machine Catalog and the machines within the Delivery Group to determine AppDisk compatibility. The behavior in 'Symptom 3' referenced above is seen if either the Machine Catalog or the selected machines are not compatible with AppDisk.

More specifically 'Symptom 2' indicates that the selected Machine Catalog is incompatible, in which case the properties of the Catalog must be corrected. The catalog properties must be adjusted even in cases where machines are PVS created but have been imported as existing machines - this is because Citrix Studio queries both the Machine Catalog and the individual machines to determine eligibility for AppDisk use. This is to verify that only MCS/PVS created Machine Catalogs which are of the Pooled Random type are found eligible. Pooled Random MCS/PVS created machines are the only types that are supported for use with AppDisk.

​'Symptom 1' indicates that the Machine Catalog is compatible with AppDisk but that the selected machines are not compatible, in this case we must ensure that the HypervisorConnectionUid of the AppDisks and the Machines both match.