Follow

Why can’t I see a patch in my VSA that I know has been released by Microsoft?

KB#:  KKB000676
 
QUESTION
Why can’t I see a patch in my VSA that I know has been released by Microsoft?
 
ANSWER
Microsoft releases a tremendous number of patches for their vast array of products.  Not all environments requireevery patch that Microsoft releases.  Rather than inundating your system with patches you don’t need, Kaseya Patch Management presents the administrator with only the patches that could potentially be used in the environment. 
Kaseya Patch Management requires patches be available through the Microsoft Update Catalog (MUC).  Microsoft will often release patches but not add them to the MUC for a few days or more.  As described above, Kaseya will not display ALL Microsoft patches, only those that are needed in your environment.  To determine if a patch is required, a Patch Scan must occur.  Any patches that are needed in your environment that are available in the MUC will appear in Kaseya Patch Management.  Therefore, if a patch that’s been added to the MUC is needed by at least one endpoint in your environment that has been scanned since the patch was added to the MUC, you will see the patch listed in Kaseya Patch Management.
 
Scenario:
  • Microsoft Releases an Office 2010 patch on “Patch Tuesday” (the second Tuesday of each month).  Microsoft does not add the patch to the MUC the same day.
  • You scan an endpoint running Office 2010.  The patch will not appear in Kaseya Patch Management because the patch has not been added to the MUC.
  • Microsoft adds the Office 2010 patch to the MUC on Thursday.
  • The patch does not appear in Kaseya Patch Management because you have not scanned an endpoint that might need the patch.
  • You scan an endpoint that does not have Office installed.  The patch does not appear in Kaseya Patch Management because the machine scanned cannot make use of the patch and therefore is not needed in the environment.
  • You scan an endpoint running Office 2010.  Kaseya recognizes that the newly-released patch is needed by an endpoint in your environment.  The patch is added to your view in Kaseya Patch Management.
  • Unless you have the default action set for this type of patch, the patch will appear as Approval Pending and will not be deployed.  You must Approve or Deny the patch in Patch Policy.
 
MORE INFORMATION

Microsoft Update Catalog (requires Internet Explorer 6.0 or later): http://catalog.update.microsoft.com/v7/site/Home.aspx

Note:  Kaseya Patch Management does not support the following patch classifications:  

  • Drivers
  • Definition Updates
 
APPLIES TO
Patch Management
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.