Yes, I use the Administrator as I read that domain users do not work.
Using the packer the following powershell script is given to the Instances user_data:
<powershell>
write-output "Running User Data Script"
write-host "(host) Running User Data Script"
Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force -ErrorAction Ignore
net user Administrator {{ user `administrator_password` }}
$ErrorActionPreference = "stop"
Remove-Item -Path WSMan:\\Localhost
listener
listener* -Recurse
$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:
LocalMachine
My -DnsName "packer"
New-Item -Path WSMan:\\LocalHost
Listener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint -Force
write-output "Setting up WinRM"
write-host "(host) setting up WinRM"
cmd.exe /c winrm quickconfig -q
cmd.exe /c winrm set "winrm/config" '@{MaxTimeoutms="1800000"}'
cmd.exe /c winrm set "winrm/config/winrs" '@{MaxMemoryPerShellMB="1024"}'
cmd.exe /c winrm set "winrm/config/service" '@{AllowUnencrypted="true"}'
cmd.exe /c winrm set "winrm/config/client" '@{AllowUnencrypted="true"}'
cmd.exe /c winrm set "winrm/config/service/auth" '@{Basic="true"}'
cmd.exe /c winrm set "winrm/config/client/auth" '@{Basic="true"}'
cmd.exe /c winrm set "winrm/config/service/auth" '@{CredSSP="true"}'
cmd.exe /c winrm set "winrm/config/listener?Address=*+Transport=HTTPS" "@{Port=`"5986`";Hostname=`"packer`";CertificateThumbprint=`"$($Cert.Thumbprint)`"}"
cmd.exe /c netsh advfirewall firewall set rule group="remote administration" new enable=yes
cmd.exe /c netsh firewall add portopening TCP 5986 "Port 5986"
cmd.exe /c net stop winrm
cmd.exe /c sc config winrm start= auto
cmd.exe /c net start winrm
</powershell>
If you are using the generated admin password from AWS, it is supported only from the 1.45, pay attention that you have to update the IAM role. If the password is pre define in the ami, I need to debug