Open diegopozzi1 opened 2 years ago
Deployment-Microsoft.Template-20220615151527.zip
Here it is the final results of the current branch
Deployment-Microsoft.Template-20220615170504.zip
Here it is the final results of the tech preview branch
There is the same issue happening on other templates currently. The workaround for the AD deployment template is to swap out image versions. Issue: https://github.com/Azure/azure-quickstart-templates/issues/12538
imageReference: { publisher: 'MicrosoftWindowsServer' offer: 'WindowsServer' sku: '2019-Datacenter' version: '17763.3131.220505' }
I got tech preview to work with some alternate vm settings (along with an alternate win10).
"DC": {
"name": "DC01",
"disktype": "Premium_LRS",
"size": "[parameters('vmSize')]",
"imageReference": {
"publisher": "MicrosoftWindowsServer",
"offer": "WindowsServer",
"sku": "2022-Datacenter",
"version": "20348.707.220505"
}
},
"DPMP": {
"name": "DPMP01",
"disktype": "Premium_LRS",
"size": "[parameters('vmSize')]",
"imageReference": {
"publisher": "MicrosoftWindowsServer",
"offer": "WindowsServer",
"sku": "2019-Datacenter",
"version": "17763.3130.220404"
}
}
},
"vmrole": "[createarray('DC','DPMP')]",
"vmInfo": "[variables('vmInfoNoClient')]",
"copy": [
{
"name": "ClientName",
"count": "[parameters('ClientsCount')]",
"input": "[concat(parameters('prefix'),'Cl0',copyIndex('ClientName',1))]"
},
{
"name": "clientRole",
"count": "[parameters('ClientsCount')]",
"input": "[concat('Client',copyIndex('clientRole',1))]"
},
{
"name": "clientInfo",
"count": "[parameters('ClientsCount')]",
"input": "[json(concat('{\"Client',copyIndex('clientInfo',1),'\":{\"name\": \"Cl0',copyIndex('clientInfo',1),'\",\"disktype\": \"Premium_LRS\",\"size\": \"',parameters('vmSize'),'\",\"imageReference\": {\"publisher\": \"MicrosoftWindowsDesktop\",\"offer\": \"Windows-10\",\"sku\": \"21h1-ent\",\"version\": \"19043.1706.220505\"}}}'))]"
}`
@routebyintuition thanks for your kind support, I'm really a newbie, I've got conflict errors again, I've corrected the template before the deployment but maybe I've did it in the wrong way.
here the deployment errors and the template I've used.
@diegopozzi1 I have attached my working template. I had to swap out the win 10 images as well and the link location default value has been updated. This launched for me. sccm-curr-branch.json.zip
@routebyintuition thanks a lot! deployment completed without errors! thanks for your help. I will search the difference between the one I used and your one, in order to understand my customization mistake. It could be a good idea propose a modification of the original template?
I would personally avoid making any specific changes to these templates at this point given the potential root cause. See https://github.com/Azure/azure-quickstart-templates/issues/12538 for a discussion around this and a temporary workaround.
Looks like the culprit was found: Related Issue Regarding the bandaid in the template I attached, this can't be pushed to the repo as it is hard coded version numbers but hopefully this gets resolved soon. If this is still an issue I may just update DSC to disable the KB security features that are suspected of breaking the deployment: KB Issue
sccm-currentbranch
Issue Details
I've deployed the template once last monday evening then deleted the resource group few days later. Need to deploy it again but since this second attempt all the deployments fails due xx-dc01/WorkFlow conflict
here the error related to the flow
{ "status": "Failed", "error": { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'WorkFlow'. Error message: \"DSC Configuration 'Configuration' completed with error(s). Following are the first few: Failed to create an object of PowerShell class SetupDomain. The SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot " } }
I've created several different resource groups with different names, also, deleted all the resource groups and try again, just the subscription is the same in all the attemps due the visual studio credit is here. Each attempts fails with the same conflict.
What I'm doing wrong?
the Vms are created but not configured, there is no domain on the DC or configuration manager installed