Michael from what I can see you're running a command "through" a (Windows) Ansible node targeting another node ($server)? Why don't you just run it against $server directly from ansible?
Instead of Ansible-->Managed Node-->$Server Just to Ansible-->$Server You could be running into the double-hop issue, or it could be that the user setup in your ansible_ssh_user variable is a local user and not a domain one (in which case you can't use it to invoke a command on a remote computer). The easiest way to tell what's going on is to check the security log on your $Server computer. On Thursday, October 2, 2014 10:09:41 PM UTC+2, J Hawkesworth wrote: > Not hit this particular problem myself and am not a powershell expert but >> I have a couple of suggestions. >> > > Last time I tried the raw module I came to the conclusion it was a running > something close to a DOS command environment, rather than a powershell > environment. So maybe worth trying to turn your 'raw' into a 'script'. > > Second (rather vague) suggestion is to make use of groups if possible and > perhaps that way you don't need full administrator permissions, just > logging in as a user who has sufficient group access to do whatever you > need to to IIS might be enough. > > Hope that's some help, please let us know how you get on, I know I have > IIS configuration tasks I want to automate in the future. > > 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/ee5a9be8-2b08-4453-ae71-9e6510bdb926%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
