Thanks, Jordan. I've already tried that, and here's the return:
fatal: [kcrook10]: FAILED! => {"changed": true, "cmd": "powershell.exe
-ExecutionPolicy Bypass -File C:\\temp\\command_update.ps1 -ConsoleTitle
\"Dell Command | Update\"", "delta": "0:00:00.546000", "end": "2018-10-18
08:24:45.319793", "msg": "non-zero return code", "rc": 1, "start":
"2018-10-18 08:24:44.773793", "stderr": "At
C:\\temp\\command_update.ps1:232 char:8\r\n+ } else {\r\n+
~\r\nMissing closing '}' in statement block or type definition.\r\n +
CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordEx
\r\n ception\r\n + FullyQualifiedErrorId : MissingEndCurlyBrace\r\n
\r\n", "stderr_lines": ["At C:\\temp\\command_update.ps1:232 char:8", "+ }
else {", "+ ~", "Missing closing '}' in statement block or type
definition.", " + CategoryInfo : ParserError: (:) [],
ParentContainsErrorRecordEx ", " ception", " + FullyQualifiedErrorId :
MissingEndCurlyBrace", " "], "stdout": "", "stdout_lines": []}
Any other ideas?
On Thursday, October 18, 2018 at 9:42:41 AM UTC-4, Dimitri Yioulos wrote:
>
> Hi, all.
>
> I've created a playbook to run a PowerShell script. The script is already
> copied to the target system (but also exists on the Ansible server). It
> must be run with the following argument:
>
> -ConsoleTitle "Dell Command | Update"
>
> I've tried every module I can think of, with every way to add the argument
> that I can think of, but can't get the playbook to run successfully. Help
> would be greatly appreciated.
>
--
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/02b8fe8a-b546-479c-acf9-b6f8c0b22d82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
