Kaseya Community

Automatic Update not initialized on machine.

  • Does anyone have a script to fix this status? This status shows up in Patch Mgmt -> Configure -> Windows Auto Update -> under the category "Windows automatic update configuration".

    Thanks

    Legacy Forum Name: Automatic Update not initialized on machine.,
    Legacy Posted By Username: jbechard
  • I too have seen this on a few of our agents, and have not been abel to figrue out. Hoping someone else may have the answer.

    Lloyd

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: lwolf
  • You need to click on the Windows Automatic Updates icon in the system tray to run the Windows Automatic Updates Setup wizard to fix this. I don't know if there's any way of launching it other than using the icon, or whether it can run silently.

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: dwalsh
  • I'm reopening this post as I'm having a similar problem.

    I have several servers that are now showing "Automatic Update Not Initialized", however I know it is. When I go into My Computer -> Properties -> Automatic Update I see all options are grayed out and "Turn off Automatic Updates" is selected. This is correct as I used Kaseya to disable Automatic Updates.

    But why is Kaseya now reporting that AU is not initialized and how can I fix this?

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: CCDave
  • Here is a script to fix the Automatic Update not Initialized error you see. This will set it to a value, "initializing it," so that it can THEN be disabled from the Windows Auto Update section under Patch Management.


    Script Name: Enable Windows Auto Update
    Script Description: This script will reset the WUA schedule to Automatic (Every Day at 4am). This will fix the Automatic Update Not Initialized error you see within Patch Management.

    IF True
    THEN
    Use Credential
    OS Type : 0
    Set Registry Value - (Continue on Fail)
    Parameter 1 : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\ScheduledInstallDate
    Parameter 2 : 0
    Parameter 3 : REG_DWORD
    OS Type : 0
    Set Registry Value - (Continue on Fail)
    Parameter 1 : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\ScheduledInstallTime
    Parameter 2 : 4
    Parameter 3 : REG_DWORD
    OS Type : 0
    Set Registry Value
    Parameter 1 : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\AUOptions
    Parameter 2 : 4
    Parameter 3 : REG_DWORD
    OS Type : 0
    Set Registry Value
    Parameter 1 : HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\NoAutoUpdate
    Parameter 2 : 0
    Parameter 3 : REG_DWORD
    OS Type : 0
    ELSE



    Although, I will mention that this is not really necessary, the machines can sit at Not Initialized and still be successfully patched by Kaseya. Its more or less a cosmetic issue.

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: Marshall
  • Thanks for the script. I know it's not necessary, but it helps and I have alerts setup so I know if something changes.

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: CCDave
  • getting an error

    C:\auscript.vbs(1, 29) Microsoft VBScript compilation error: Expected end of sta

    tement