I have a smart label created that is pulling in security related patches of any severity for all versions of SQL server that have been downloaded in the last 100 days. When my scheduled detect and deploy ran last month there were 3 updates in the label; SQL Server 2012 Service Pack 4 , SQL Server 2014 Service Pack 2 Cumulative Update (CU) 8, and SQL Server 2016 Service Pack 1 Cumulative Update (CU) 6.

Of those three patches the only one of them to install or display compliance percentages was the Service pack. I looked back and found that only service packs for SQL and not updates in between are being installed even though they are in the smart label when the schedule runs against it.

Why aren't these running during detect and deploys when I run them?
4 Comments   [ - ] Hide Comments


  • What's the status of those patches? if they are inactive or disabled they won't deploy. Same thing if they have been superseded.
  • They are active and they have not been superseded.
  • I am noticing the same issue. Does anyone have a resolution to this?
  • Anyone?
Please log in to comment

There are no answers at this time
Answer this question or Comment on this question for clarity


Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.