Comments

8 comments

  • Colby Bouma

    We usually have most Windows patches out by the end of the day, but we can't guarantee it.

    1
    Comment actions Permalink
  • Liam Mulrooney

    sweet, happy to get this out today

    1
    Comment actions Permalink
  • Liam Mulrooney

    Cheers Colby..

    0
    Comment actions Permalink
  • Michael Koo

    Just saw it pop up on my PDQ Deploy console.

    0
    Comment actions Permalink
  • Heyner Gomez

    Colby Bouma I have downloaded the Windows patch in PDQ Deploy, but when I deploy it the package fails and I get this output log:

    Registry Condition(s) not satisfied

    Summary : Exists Condition. . . . . . . . . . . . . . . . . . [Success]
    Key : HKEY_LOCAL_MACHINE\. . . . . . . . . . . . . . . . .[Success]
    Value Name : ProductName. . . . . . . . . . . . . . . . . . . . .[Success]
    Value : Contains 2015 LTSB. . . . . . . . . . . . . . . . . . .[Fail]
    Value = Windows 10 Pro
    : Condition failed because 2015 LTSB was not found.
    [*] means that the condition was not checked because of previous failures

     

     

    0
    Comment actions Permalink
  • Colby Bouma

    Heyner Gomez

    Each Windows 10 Cumulative Update package correlates to a specific build of Windows 10. You can see which build your computers are running by looking at the SP / Release column in Inventory:

    0
    Comment actions Permalink
  • Jeff Percival

    Awesome job getting the package ready to roll so quickly. 

    I had just convinced my boss to pull the trigger on the $500 to buy PDQ and THE NEXT DAY we were reading about the new MS vulnerability. After doing some digging on a potential huge manual deployment I was THRILLED to see that it was sitting there waiting for me in PDQ. Deployment was done on over 200 computers in less than an hour.

    My skeptical boss (after one day): "Money well spent."

    0
    Comment actions Permalink
  • Liam Mulrooney

    For some reason all of my Win 7 patches (20 machines) have failed with the following error - 

    MSI Error -2146885628: MSI failed with error code -2146885628

     

    Have you guys any info on what may be causing this?

     

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.