The suggestion was very much appreciated...in fact I'm already doing something like this (scheduled task to kick off the install) with SQL. Unfortunately I ran into the same issue when I attempted the install with specific app...the custom action in the installer kept resetting the flags I was passing to kill any reboot. It's a poorly-written (and documented) command line installer. What I eventually found when reading a verbose install log was that there's an undocumented option to suppress the installer (so the app installer is over-riding the default Windows installer options...yes, it's pure genius) over-ride of the reboot flags. I re-did my playbook with that option and now it's working the way I'd like.
Insanity. On Sunday, September 27, 2015 at 4:09:59 AM UTC-5, J Hawkesworth wrote: > > I don't have anything I have tested myself but I do have a couple of > ideas. > > Maybe the way to handle is to kick off a scheduled task to run the install > and then take a look at trond hindenes' win_reboot role in galaxy which I > believe can wait until a reboot has been achieved. > > There is a PR for a module to run a scheduled task been submitted > recently. > > Hopefully you can put the two things together to get what you need. > > Please let us know how you get on. > > Jon > > -- 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/d204ccea-d3f1-43e0-a84a-12ccad7bfc14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
