I had several issues with DSC Configuration failures , conflicts, client cannot connect to the destination specified etc. Was occurring with the Microsoft catalog and my own images. The last bit was after my firewall guys were certain it was not them.
"VM has reported a failure when processing extension 'dscextension'. Error message: \\\"DSC Configuration 'AddSessionHost' completed with error(s). Following are the first few: The client cannot connect to the destination specified in the request."
This is the workaround for me. Waiting on Microsoft support to weigh in see if it a bug etc. Test this in your lower environments! :)
- Create a new VM from your disk template. I suggest you create a separate RG for workspaces.
- Disable IPv6 on nontunnel interfaces (except the loopback) and on IPv6 tunnel interface https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advance... use the fix it.
- Sysprep , genralize, OBE, shutdown.
- Convert the VHD to an Image (your mojo)
$disk = Get-AzDisk -ResourceGroupName 'your-rg' -DiskName 'your-disk'
$location = 'South Central US'
$imageName = 'golden-image-name-ipv6-disabled'
$rgName = 'your-rg'
$imageConfig = New-AzImageConfig `
-Location $location
$imageConfig = Set-AzImageOsDisk `
-Image $imageConfig `
-OsState Generalized `
-OsType Windows `
-ManagedDiskId $disk.Id
$image = New-AzImage `
-ImageName $imageName `
-ResourceGroupName $rgName `
-Image $imageConfig
- Deploy new Host pool and Session hosts with the new image
