Azure / Azure/azure-quickstart-templates

WINRM issue

Open
#12,830 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

I receive an WINRM issue when running the deployment (it has worked with the same code 2 month ago).

New-AzResourceGroupDeployment : 23:29:03 - The deployment 'azuredeploy' failed with error(s). Showing 1 out of 1
error(s).
Status Message: At least one resource deployment operation failed. Please list deployment operations for details.
Please see https://aka.ms/DeployOperations for usage details. (Code: DeploymentFailed)
- {
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'CreateADForest1'. Error message: \"DSC
Configuration 'CreateADRootDC1' completed with error(s). Following are the first few: WinRM cannot process the
request. The following error with errorcode 0x80090350 occurred while using Negotiate authentication: An unknown
security error occurred. \r\n Possible causes are:\r\n -The user name or password specified are invalid.\r\n
-Kerberos is used when no authentication method and no user name are specified.\r\n -Kerberos accepts domain user
names, but not local user names.\r\n -The Service Principal Name (SPN) for the remote computer name and port does not
exist.\r\n -The client and remote computers are in different domains and there is no trust between the two
domains.\r\n After checking for the above issues, try the following:\r\n -Check the Event Viewer for events related
to authentication.\r\n -Change the authentication method; add the destination computer to the WinRM TrustedHosts
configuration setting or use HTTPS transport.\r\n Note that computers in the TrustedHosts list might not be
authenticated.\r\n -For more information about WinRM configuration, run the following command: winrm help
config.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "
}

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue

We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

[Template Name goes here](Template link goes here)

### Issue Details

### Repro steps (*if necessary, delete otherwise*)
1.
2.
3.
4.
5.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the reported New-AzResourceGroupDeployment output and the VM extension errors for CreateADForest1 and CreateADRootDC1. Review the deployment operations and the linked VM Extension DSC troubleshooting guidance; done means identifying a reproducible cause and documenting or correcting the affected deployment, though no template name or complete repro steps are provided.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.