Windows Security Vulnerability
I am sure you guys are aware of this issue , MS to release patches today.
Do you know if it will be available in PDQ in the coming days?
-
@... 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 -
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:
-
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."
Please sign in to leave a comment.
Comments
8 comments