Sorry to hear this, hope you can go back to a snapshot or similar?
Can't really think why it would be different.
I run the script like this:
- name: set auto logon
script: "setSecureAutoLogon.ps1 -Username {{ automation_user }} -Domain
{{ windows_domain_name }} -Password {{ automation_password }}"
Jon
On Wednesday, July 13, 2016 at 3:43:27 PM UTC+1, skinnedknuckles wrote:
>
> I tried this and it worked fine but now my ansible profile is all messed
> up and many other tasks in my playbook are failing. My USERPROFILE is
> supposed to be C:\\Users\\ansibleAdmin but now it shows up as
> C:\\Users\\ansibleAdmin.DOMAIN or sometimes C:\\Users\\Temp.
>
> On Wednesday, May 11, 2016 at 10:01:52 AM UTC-5, skinnedknuckles wrote:
>>
>> Management Node:
>> CentOs 7.1
>> Ansible 2.1
>> Remote Node:
>> Windows 7
>> Powershell 3.0
>>
>> How do I launch an executable on a remote node running Windows 7? As I
>> understand win_scheduled_task only works with Windows Server 2012 and
>> win_nssm is only for startup services. Is there any other way do do this?
>> If not, is there any way to access the Invoke-Command option of
>> Powershell? I suppose a module could be written to do that but I'm new to
>> python and doubt I could pull it off.
>>
>> Thanks,
>>
>> Jonathan
>>
>
--
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/533ce192-2ccc-495c-bf42-f77840b9326e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
