hi jordan,
thanks for your reply can you please tell us how this can be achieved
through other programming or automation.
On Monday, December 2, 2019 at 2:22:54 AM UTC+5:30, Jordan Borean wrote:
>
> Running a command through Ansible is not designed to run interactive
> programs. Everything is
thank you for answer ,
is it possible to use `changed_when: false` on ad-hoc command mode ?
On Thursday, 28 November 2019 19:41:10 UTC, Felix Fontein wrote:
>
> Hi,
>
> > Running simple shell commands now produces CHANGED instead of SUCCESS.
>
> "now" has been for quite a while now. And as
Running a command through Ansible is not designed to run interactive
programs. Everything is run in the background with no interactive Window
and will wait until the process has exited. Because running mstsc is a GUI
application, it will stay open forever which results in
win_shell/win_command
Sounds like you might have a GPO policy that sets the timezone and on a
reboot that is being applied. The win_timezone module is just changing the
timezone when running but if something else is changing it back then
there's nothing Ansible can really do.
--
You received this message because
Having a invalid credentials error means WinRM returns a 401 HTTP code with
means the request was unauthorized. In WinRM terms this can mean a few
different things;
- The request is not encrypted
- Using https is always encrypted
- Using http is only encrypted if using NTLM,
