When the following metadata exists on the affected zone: CatalogServiceType: CustomerManaged
Web Studio may display: You don't have permission to access the zone for this resource, the catalog will be put in the default zone.
In this scenario, the environment was previously configured as Quick Deploy (QD) and was later switched to Premium, but the "CatalogServiceType: CustomerManaged" metadata remained on the zone.
The CatalogServiceType: CustomerManaged metadata entry remains on the zone after the environment is migrated from Quick Deploy to Premium.
Because this metadata is still present, Web Studio identifies the zone as externally managed or restricted and consequently displays the permission warning.
The metadata is no longer appropriate for the current Premium configuration and should be removed.
Remove the CatalogServiceType metadata entry from the affected zone.
Before making the change, back up all existing zone metadata so that it can be restored if necessary.
Replace <ZoneName> with the actual zone name. The backup path can also be customized. For example: C:\temp\<ZoneName>_metadata_backup.clixml
[Remove the Metadata]
Step 1: Authenticate and Get the zone data
Run the commands from a machine with the Remote PowerShell SDK installed.
# Load Citrix SDK snap-ins
Add-PSSnapin Citrix.*
# Authenticate to the DaaS tenant
Get-XDAuthentication
# Settings
$zoneName = '<ZoneName>'
$targetKey = 'CatalogServiceType'
$backupFile = 'C:\temp\<ZoneName>_metadata_backup.clixml'
# Ensure the backup folder exists
New-Item -ItemType Directory -Path (Split-Path $backupFile) -Force | Out-Null
# Get the zone
$zone = Get-ConfigZone -Name $zoneName
Step 2: Back up the existing zone metadata
$map = @{}
$zone.MetadataMap.GetEnumerator() | ForEach-Object {
$map[$_.Key] = $_.Value
}
$map | Export-Clixml -Path $backupFile
Write-Host "Backed up $($map.Count) metadata entries to $backupFile" -ForegroundColor Green
# Display the backed-up metadata
$map
Step 3: Remove the CatalogServiceType metadata
if ($map.ContainsKey($targetKey)) {
$zone | Remove-ConfigZoneMetadata -Name $targetKey
Write-Host "Removed metadata key: $targetKey" -ForegroundColor Yellow
}
else {
Write-Host "Key '$targetKey' not found on the zone - nothing removed." -ForegroundColor Red
}
Step 4: Verify the change
(Get-ConfigZone -Name $zoneName).MetadataMap
Confirm that the following entry is no longer present:
CatalogServiceType CustomerManaged
After the metadata is removed, check Web Studio again and confirm that the zone permission warning is no longer displayed.
[Rollback]
If the original metadata needs to be restored, import the previously created backup and restore each metadata entry.
$zone = Get-ConfigZone -Name '<ZoneName>'
$restore = Import-Clixml -Path 'C:\temp\<ZoneName>_metadata_backup.clixml'
foreach ($k in $restore.Keys) {
$zone | Set-ConfigZoneMetadata -Name $k -Value $restore[$k]
}
Write-Host "Restored $($restore.Count) metadata entries" -ForegroundColor Green
# Verify
(Get-ConfigZone -Name '<ZoneName>').MetadataMap
After an environment is migrated from Quick Deploy (QD) to Premium, Web Studio may display the following warning when creating or managing a machine catalog:
You don't have permission to access the zone for this resource, the catalog will be put in the default zone.
The warning may occur when the zone still contains the following metadata from the previous Quick Deploy configuration: "CatalogServiceType: CustomerManaged".
The stale metadata causes Web Studio to treat the zone as an externally managed or restricted resource and display the permission warning.
This warning does not block MCS catalog creation.
Feedback submitted!