Yes you are right. I tried running ConfigureRemotingForAnsible.ps1 but it
failed. I'm sorry I don't have the error message.
I have little experience of Powershell, but I managed to work through the
script and run the individuals settings manually. Of course I could have
missed something, but it seemed to work fine with Ansible once I was part
of the administrators group on the Windows host.
Luckily I have access to another Windows servers (server B), and for this
the script ConfigureRemotingForAnsible.ps1 works. Also I hadn't placed the
user in the WinRMRemoteWMIUsers__ group.
Unfortunately I'm receiving the same errorr, and like with Server A, as
soon as I add my user to the administrators group, all works fine.
I've compared the WinRM settings across the two servers. Server A was
configured manually, and Server B via ConfigureRemotingForAnsible.ps1.
They are both the same:
Config
MaxEnvelopeSizekb = 500
MaxTimeoutms = 60000
MaxBatchItems = 32000
MaxProviderRequests = 4294967295
Client
NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = false
Auth
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
CredSSP = false
DefaultPorts
HTTP = 5985
HTTPS = 5986
TrustedHosts
Service
RootSDDL =
O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPerUser = 1500
EnumerationTimeoutms = 240000
MaxConnections = 300
MaxPacketRetrievalTimeSeconds = 120
AllowUnencrypted = false
Auth
Basic = true
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
AllowRemoteAccess = true
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 7200000
MaxConcurrentUsers = 10
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 25
MaxMemoryPerShellMB = 1024
MaxShellsPerUser = 30
Do we know if anyone that has got this working with a user that is *not*
part of the administrators group?
On Saturday, 27 February 2016 17:55:10 UTC, J Hawkesworth wrote:
>
> Thanks for this.
>
> Since ansible and pywinrm are behaving the same, it occurs to me that the
> winrm configuration might not suit pywinrm.
>
> From the above it appears you have created specific configuration for
> winrm, rather than using the settings that are applied if you run the
> ConfigureRemotingForAnsible.ps1.
>
> I suggest you run the ConfigureRemotingForAnsible.ps1 script on a windows
> host and then compare the winrm configuration with your test machine.
>
> You can see the winrm config by running
>
> Winrm get winrm/config
>
> From memory, pywinrm can not use credssp authorisation,
>
> Is your test user a member of the WinRMRemoteWMIUsers__ group? I wouldn't
> expect anything to work if not but just trying to understand what you have
> in place.
>
> Hope this helps,
>
> Jon
>
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/3e554e7c-289b-4032-8999-cd43e7c23ba2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
