Hi - I've not seen what you're experiencing, but I've only used this against Windows 2012r2 servers. Perhaps PSWindowsUpdate behaves differently there?
Alternatively, it may be that the surface area for my windows update exposure is smaller than yours - each month I trigger a build of an AWS AMI based on the new one that AWS release. They apply the updates that are current when they release the new AMI, so at any given point I only have a small increment to apply. Sorry that that's not a solution! On Friday, 4 September 2015 15:56:04 UTC+1, Dimitri Yioulos wrote: > > Many thanks. I'll set up the logPath parameter, and post my findings > early next week. I'm hopeful about the module's use. I, like many others, > work in a heterogeneous (Win/Linux) environment, so having Ansible work > well with both OSs would be a great thing. > > Dimitri > > On Wednesday, September 2, 2015 at 12:57:51 PM UTC-4, Dimitri Yioulos > wrote: > >> I'm trying to use the extras module win_updates to update my Windows >> servers. The play runs without failure, but no updates are applied. >> >> Ideally, I want the install all available updates (e.g. critical, >> important, optional, etc.). I've created a play to look like this: >> >> --- >> >> - hosts: windows >> gather_facts: true >> >> tasks: >> - name: win update >> win_updates: >> category: security >> >> What do I need to do to make this install the updates, and how to I >> install all available updates? >> >> Thanks. >> >> Dimitri >> > -- 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/909df529-d295-45eb-8b60-f7ba39e1a4df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
