Kaseya Community

XP SP3- Installed automatically? -

  • We have had alot of our clients upgraded to XP sp3 last night- ??

    1. All "windows automatic update" is disabled on all of our managed clients.

    Not sure how this got threw, They were ALL installed according to the
    time schedule we have setup in our "automatic update" schedule.

    The patch has not even been updated in kaseya yet.

    Look in your logs for the following
    2:57:42 am 8-May-08 System NtServicePack None 4371 SYSTEM
    Windows XP Service Pack 3 was installed (Service Pack 2 was previously installed).

    Search for event id 4371 - system log.

    Did anyone else have this happen?


    Kaseya- How are patches getting past our patch approvel process?

    Eek

    Legacy Forum Name: XP SP3- Installed automatically? -,
    Legacy Posted By Username: jim@bitvision.com
  • The patch has not even been updated in kaseya yet.


    Actually sir, that's... not... entirely accurate.

    XP SP3 showed up in Patch Approval early Tuesday, so if you don't have Machine Collections defined and the accompanying Approvals/Denials in place... it would've gone out with the automatic update schedule you have defined.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: GreyDuck
  • XP SP3 showed up in Patch Approval early Tuesday, so if you don't have Machine Collections defined and the accompanying Approvals/Denials in place... it would've gone out with the automatic update schedule you have defined.


    All collections, Default approvel policy by machine collections are setup, The patch does NOT repeat Does not show up.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: jim@bitvision.com
  • About 100 of ours got SP3 as well. Sure enough it was auto approved on the 6th. Going to have to change that to manual approval. Fortunately the phone did not ring once with an SP3 related issue. Someone was watching out for me...

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: jamie177
  • If you are in a hurry to block this servicepack...

    here is the # KB936929

    Just do a KB override under the patch tab, and you will be covered.
    If your users have auto update on, they are going to get it anyway, as pointed out earlier in this post.

    Turn off auto updates for the time being by going to patch tab, then under "windows Auto Update" select all your users necessary and turn that sucka OFF.
    It may require a reboot for it to take effect so plan accordingly.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: gamer-x
  • The problem with using Kaseya to turn off Automatic Updates in Windows itself is that the setting change doesn't seem to "stick" very well. It's not a recurring state check, it's a one-off toggle. If something (manual intervention, group policy, what-have-you) switches it back... too bad, so sad.

    So. After being frustrated by this situation one too many times, I devised the following:

    Script Name: NoAutoUpdate (MS) - kk
    Script Description: Sets registry entries used by GPO objects to disable Windows' Auto Updates for all users, preventing user intervention. Stops and starts WUAU service before and after to make sure settings take. Also stops & disables Security Center service.

    IF True
    THEN
    Execute Shell Command
    Parameter 1 : psservice stop wuauserv
    Parameter 2 : 1
    OS Type : 1
    Set Registry Value
    Parameter 1 : HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\NoAutoUpdate
    Parameter 2 : 1
    Parameter 3 : REG_DWORD
    OS Type : 1
    Set Registry Value
    Parameter 1 : HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\AUOptions
    Parameter 2 : 1
    Parameter 3 : REG_DWORD
    OS Type : 1
    Execute Shell Command
    Parameter 1 : psservice start wuauserv
    Parameter 2 : 1
    OS Type : 1
    Execute Shell Command
    Parameter 1 : psservice stop wscsvc
    Parameter 2 : 1
    OS Type : 1
    Execute Shell Command
    Parameter 1 : sc.exe config wscsvc start= disabled
    Parameter 2 : 1
    OS Type : 1
    ELSE


    YMMV, adjust to taste, etc.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: GreyDuck
  • For some reason, Kaseya pushed out 3 different versions of SP3. Each a day apart. All with the same ID.

    Anyone know why?

    We blocked 2 by were done in by the 3rd.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: rvines@axcelltech.com
  • SP3 auto update went through smoothly with all of our client machines (say about 200 or so). There weren't any major significant notices than say, from sp1 to sp2. no need to sweat it.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: ccarter@eresources.com
  • has anyone done any research into what xp sp3 actually does?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: james@williswhite.co.nz
  • james@williswhite.co.nz
    has anyone done any research into what xp sp3 actually does?


    you mean like read the release notes?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: RCS-Michael
  • rvines@axcelltech.com
    For some reason, Kaseya pushed out 3 different versions of SP3. Each a day apart. All with the same ID.

    Anyone know why?

    We blocked 2 by were done in by the 3rd.

    We noticed the same thing today. 3 instances of SP3, each with the same KB#. We numerous machines that got the SP we think due to this.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: jonall
  • In our case,

    The KB948496 for XP sp3 had been updated in our kaseya server for deployment, However it could not be scene.

    The problem we had (had to have Kaeya tech support look at out system) was the KB did NOT show up in our system for approval/Disapproval anywhere, but it was there behind the scenes.

    The Kaseya tech had to "reapplly schema" to get it to show up, It would even ignore our "kb override" until we did so,

    I still do not have total faith that patches will not "autoapprove,autodeploy"
    even with All patch management policies set to "Pending approval"

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: jim@bitvision.com
  • When you see multiple versions of a particular MS KB# this meant that Microsoft has released different flavors of patches related to the OS version. Any time one of those patches change from 'Approved'/'Denied' to 'Denied (Pending approval)' this is a indication that Microsoft has changed that patch in either the actual installer, binary, descriptor, or a repackage or the installer.

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