Hey Jonathan, appreciate the advice, I think I may start doing just that. Will keep you guys updated.
I only have executed the script up to this point, and I am almost more intrigued in why the differences between local execution and remote (via winrm) execution. Have a feeling I should ease my stubborn engineering mind and throw this in the bucket of strange Windows behaviors. On Sunday, January 25, 2015 at 9:09:29 AM UTC-6, Jonathan Davila wrote: > > Personally, I've had greater success converting a normal PS script into a > proper module. It really isn't too difficult to do and is probably a better > way to go in the long term anyways. Have you tried doing that? Or just > exclusively executing via the script module? > > On Saturday, January 24, 2015 at 1:22:35 PM UTC-5, John-Paul Herold wrote: >> >> My case is rather specific, understandably. But if anyone has had issues >> with powershell scripts running over winrm and successfully debugged them, >> any tips/references (either Ansible or winrm related) would be greatly >> appreciated. I'm reading through technet articles and other resources >> learning how to troubleshoot winrm and just about the service as a whole. >> >> >> 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/d18d7122-7cc0-4d4f-bd00-29750209d6e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
