powershell - Issues configuring WinRM while deploying a Windows VM on Azure via API -
When a VM is deployed with the Windows2008-SQL-Server template through the REST API on Ezers, To enable WinRM with a PowerShell script, to enable basic proof, we use the Azure extensions 'CustomScript extension' which loads a script from our blobstoreos and runs it
- In the script's output There are errors and PowerShell ports do not respond to 5985.
- We use SQL-Server-2008R2-SP2-10.50.4319.0-standard-ENU -Win2008R2 template.
- In the deployment we set up a listener who uses the protocol as 'HTP'
- We open the port 5985 and at the end of the VM provision we will open the socket on it Are capable.
code:
winrm quickconfig -q winrm set winrm / config / winrs' @ {MaxMemoryPerShellMB = "300"} 'winrm set winrm / config' @ {Maxtimeimouts = "1800000"} 'winrm set winrm / config / service' @ {AllowUnencrypted = "true"} 'winrm set winrm / config / service / auth' @ {basic = "true"} '< / Pre>We have the following error for each script command:
Message = Access is inhibited \\ n \\ nError Number: -2147024891 0x80070005 \\ nAccess is denied.Once the provision of VM is made, we can log in using Remote Desktop and if we launch a parcel the script, it works perfectly .
After some research we have come to know that a possible solution is proposed, but the problem is that it exposes the security problem, because the script needs the admin password password.
We are looking for other advice or solutions. We are working with a full automated workflow, so sadly that "hand-made solutions" are not an option for us. Thanks in advance for any help.
I have a blue Windows VM in my case at Chef Client Bootstrap, in addition to whatever you have done , I had to open 5985 on the Windows Firewall and enable the 5985 Endpoint on the cloud service. It was a potty, but she got a job but she got a job.
Comments
Post a Comment