I'm guessing that applying the LocalAccountTokenFilterPolicy kicks your ansible connection out before it can respond.
Since you are on 2.2 you should be able to use async, which might let you switch from from 0 - 1 There isn't a way to become another user yet on windows but it is slated for 2.3 - see https://github.com/ansible/ansible/blob/devel/docsite/rst/roadmap/ROADMAP_2_3.rst Hope this helps, Jon On Friday, November 11, 2016 at 4:14:22 PM UTC, [email protected] wrote: > > Our environment is under some pretty strict security requirements and it's > causing lots of issues. First, we don't have an active directory set up > (all local accounts, I know it's stupid but I'm just the idiot trying to > clean it up). Then, we have this LocalAccountTokenFilterPolicy registry > setting set to 1 so every time I try to run something I get permission > errors as it lowers permissions. > > I am allowed to temporarily disable the LocalAccountTokenFilterPolicy to > do what I need to do, but need a mechanism to do that. I'm able to use > win_command to do switch it from 1 to 0 but can't switch it from 0 - 1. > > Is there any way to get in with WinRM through ansible then run a command > as an elevated user? > > Thanks! > -- 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/5fa798ed-c837-4f8d-8744-930f71bf939b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
