Apr 08 2020 04:54 PM - edited Apr 10 2020 08:25 AM
Hello,
I am using two different tenants and up until today both were failing in South Central US.
However my Lab was working in East US just fine. My lab succeed at 2:07 PM for some reason. However prod still has an issue. My Prod environment is having DOM Join issues so I am not sure about East US working as of yet. I think it is peering so I can't prove that it works in East US yet in Prod.
Info: Windows Multi User Edition with Office from ARM Catalog
I am using a SPN in both environments. I have a couple working host pools from using the exact steps previously. Seems strange.
Any suggestions?
],
"error": {
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'dscextension'. Error message: \\\"DSC Configuration 'CreateHostPoolAndRegisterSessionHost' completed with error(s). Following are the first few: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: \\\"winrm quickconfig\\\".\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot \"\r\n }\r\n ]\r\n }\r\n}"
}
]
},
"validationLevel": "Template"
}
}
Apr 17 2020 09:11 AM
@BryanHeath
Good morning Bryan, I have the same problem, could you solve it somehow?
Jun 23 2020 04:37 PM - edited Jun 23 2020 04:38 PM
I JUST figured out how to fix this in my prod environment.
I am not sure if this is specific to our setup or not. It is worth a shot if you are stuck.
https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advance... use the fix it.
$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
Good luck!!!
Jun 23 2020 04:39 PM - edited Jun 23 2020 04:46 PM
$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