Kaseya Community

What does the Changed date mean for Patches

  • Hoping someone can answer this for me...

    If I go to Patch Mgmt->Approval by Policy screen, and then click on any of the Classifications or one of the number counts for Pending Approval, a Patch Approval Policy Details page is displayed - one row for each patch.

    On the righthand side, there is an Admin column and a Changed column (which shows a date/time).

    What exactly does the date/time in the Changed Column mean?

    My ultimate problem/question is... periodically, Microsoft releases new patches. Those patches shpw as Pending Approval. I will either Approve or Deny them. So the number of Pending Approval patches will be zero.

    But then a few days, or a week or so later, there will again be more Pending Approval patches. When I look at those patches, the Admin column will say "*System*"and a Changed column will be a very recent date.

    Right now, I have more than 70 Patches that are pending Approval. Last week or so, I probably had 10. When I look at those patches,, the Admin column says "*System*"and a Changed column will is "2:29:15 pm 6-Mar-09" for dozens of them, and "24-Feb-09" for many others, and then some other (recent) random dates.

    For many of these patches, the Published Date is 2003, 2004, 2005, 2006, etc - nothing recent.

    So why do previously approved patches once again show as Pending Approval? I would understand if Microsoft was updating a patch EXE, but that doesn't seem to be possible for all of these.

    Lloyd

    Lloyd

    Legacy Forum Name: What does the Changed date mean for Patches,
    Legacy Posted By Username: lwolf
  • We are experiencing this EXACT behaviour. I have a support ticket (ticket number 173180) open with Kaseya regarding this. Unfortunately we haven't made much progress, but glad to hear that I'm not the only one experiencing this.

    Also, are you seeing KB000000 return often? It's a slovenian interface for WMP, or updates to several Slovak files.

    Cheers,
    -LWX

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: LANWorx
  • Did you make any headway on this Lloyd?

    I still have my ticket open awaiting response.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: LANWorx
  • LANWorx,

    Actually, I did get an email message today with some more background info on patches. Here is a copy & paste

    Lloyd


    ===========================
    When a patch is detected for the first time on any machine, it is added to all of your policies with the default approval status for the policy.

    A patch may later be removed from the policies if it is no longer detected on any machines. This may happen if: -
    1) all machines which the patch applies to are removed from the system
    2) the patch scan no longer detects the patch due to a change in Microsoft's data

    If this patch is then detected again on any machine, it will be added to the policies as if it were new, and get the default approval status again.

    Something that can complicate this to some degree is that when a new machine is first scanned, the "Legacy Patch Scan" is run and it will report older patches as missing if the machine was not previously kept up-to-date. The legacy scan will detect patches prior to October 2007, when Microsoft replaced their previous scan engine with the Windows Update Agent (WUA). The legacy scan then determines if the machine meets the requirements to use the "WUA Patch Scan". If it can, the machine is rescanned using the new scan engine. When its scan results are processed, the results from the "Legacy Patch Scan" are deleted and replaced with the scan results from the "WUA Patch Scan". This can also cause patches to temporarily appear in the policies and then be deleted again.
    ===========================

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: lwolf
  • cheap Ultram next day shipping buy soma watson Valium no prescription needed buy Valium overnight cod Order Tramadol no script next day Viagra no prescription USA FedEx Soft tab generic Viagra Cialis next day delivery Buy Doxycycline no prescription Prednisone same day shipping buy Prednisone online Tramadol overnight Nolvadex cheap no prescription buy non perscription Ativan overnight delivery Soma no prescription Ambien cod delivery next day Ultram no prescription needed Xanax next day delivery buy Xanax no prescription cod Trazodone without a prescription Trazodone online Tramadol overnight no prescription


    [edited by: Anonymous at 6:33 PM (GMT -7) on 5-7-2011] cheap Ultram next day shipping buy soma watson Valium no prescription needed buy Valium overnight cod Order Tramadol no script next day Viagra no prescription USA FedEx Soft tab generic Viagra Cialis next day delivery Buy Doxycycline no prescription Prednisone same day shipping buy Prednisone online Tramadol overnight Nolvadex cheap no prescription buy non perscription Ativan overnight delivery Soma no prescription Ambien cod delivery next day Ultram no prescription needed Xanax next day delivery buy Xanax no prescription cod Trazodone without a prescription Trazodone online Tramadol overnight no prescription
  • LANWorx ,

    Yes, Dominic is working on my ticket. Thanks for sharing your reply message. If its mot too much trouble, could you let us know his response?

    Lloyd

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: lwolf
  • Hi Lloyd,

    I received the following reply this morning;

    [Ticket Notes ~ticId='173180']
    Ticket ID: 173180
    ---------------------------------------------------------
    Author: dominic.walsh
    Date: 17:59:00 18-Mar-09
    Hi

    Regarding your build process, yes if the machines are unpatched when you run the initial update then old patches may get detected by the legacy scan and later removed again. You are probably correct in saying this would be avoided if you manually install the latest patches before scanning with Kaseya, as this would prevent anything being detected by the legacy scan.

    I am going to submit an enhancement request based on this scenario for the system to remember deactivated patches if they get detected again at a later date.

    Dominic


    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: LANWorx
  • LANWorx,

    Thanks for sharing. I suppose some of the patch behavior that I have seen/experienced is beginning to make a little more sense now.

    Lloyd

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: lwolf
  • Yikes, this is mind-numbing Sad I thought Kaseya was supposed to make things easier?

    Maybe I'll reread this after my glass of wine has worn off. Or, maybe I should have another Smile

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: ReedMikel