Thanks Jon,

I've got it working now. 

I also think I made a silly error in the group_vars in regard to the 
configured SSH_USER. Changing that has now got this working.

Thanks

Marc

On Tuesday, February 2, 2016 at 2:48:16 PM UTC, J Hawkesworth wrote:
>
> Yeah this stuff is frustrating...
>
> You can disable UAC just for Administrators ...
>
>
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
> "ConsentPromptBehaviorAdmin"=dword:00000000
>
> then re-enable it once you have completed tasks that need it.
>
> Windows Registry Editor Version 5.00
>
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
> "ConsentPromptBehaviorAdmin"=dword:00000002
>
> Regular, non admin users will still get UAC prompts.
>
> Hope this helps
>
> Jon
>
>
>
> On Tuesday, 2 February 2016 13:58:33 UTC, Marc Farrow wrote:
>>
>> Hi All,
>>
>> This is a basic question as I'm just getting started with Ansible. I've 
>> got this working perfectly on our Linux distributions but not on Windows.
>>
>> Our environment dictates we need UAC enabled and we cannot use the built 
>> in administrator account for day to day activities. With ansible some of 
>> the modules work perfectly. However I'm having an issue with the modules 
>> such as win_msi that effectively need elevated permissions within UAC to 
>> "runas" administrator. If I run win_msi as the actual administrator (edit 
>> the ssh_user as the actual local administrator) then it works fine. But 
>> switching to either a domain user or a local user that's added to the local 
>> administrators group fails with access denied. Running the same command on 
>> the server requires me to either run the command in an elevated window or 
>> accept the prompts to install as administrator. WinRM is working as 
>> expected as I can perform tasks that don't require elevated permissions 
>> perfectly with the domain or local user.
>>
>> Does ansible have any way around this? I see from the notes that at some 
>> point "runas" is going to be enabled for windows, I guess this might be 
>> when powershell starts to support SSH?
>>
>> But if anyone has any advice then this would be greatly appreciated.
>>
>> Thanks
>>
>> Marc
>>
>

-- 
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/596c3248-74d3-4a07-918b-e101ef6761dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to