locked
Win 2012R2 - Cannot set update Schedule RRS feed

  • Question

  • hi,

    I have the following issue - I cannot set the day and time for Windows updates to be applied on my 2012R2 Servers.

    The Servers are not in a domain - we use a script to set the Registry (successfully on all versions up  to 2012)

    We are using a Windows 2008R2 WSUS Server

    I found a patch which should fix this issue in 2012 pre R2 (KB2883201) but this will not install on my 2012R2 servers

    Is there a fix for 2012R2 comparable to the above KB ?

    Any help Appreciated - If my issue is not clear please let me know.

    Regards,

    Alan


    Regards, Alan

    Thursday, October 2, 2014 4:39 PM

Answers

  • I found a patch which should fix this issue in 2012 pre R2 (KB2883201) but this will not install on my 2012R2 servers

    Is there a fix for 2012R2 comparable to the above KB ?

    As per this blog article, the changed functionality deployed by KB2883201/KB2885694 is already included in Win8.1/WS012R2:

    http://blogs.technet.com/b/wsus/archive/2013/10/08/enabling-a-more-predictable-windows-update-experience-for-windows-8-and-windows-server-2012-kb-2885694.aspx

    Are you setting AUOptions=4 ?
    https://thwack.solarwinds.com/community/application-and-server_tht/patchzone/blog/2013/03/14/configuring-the-windows-update-agent--general-settings-part-1


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Thursday, October 2, 2014 9:13 PM
  • My Script does set the various options but the GUI in Control panel  remains the same - except for

    ...

    to ensure that the scripted setup is installing updates as expected

    1. If a client is configured to be a WSUS client, then some of the options (such as when the installation event occurs) in the Control Panel will be inaccessible to the user. This has been the case since the creation of SUS, and is not unique to any OS.

    2. Why are you using a *script* to configure the client? Does the script configure the client, or does the script install the updates? You cannot do BOTH in the same script.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Steven_Lee0510 Tuesday, November 11, 2014 3:16 AM
    Monday, October 6, 2014 1:10 PM

All replies

  • I found a patch which should fix this issue in 2012 pre R2 (KB2883201) but this will not install on my 2012R2 servers

    Is there a fix for 2012R2 comparable to the above KB ?

    As per this blog article, the changed functionality deployed by KB2883201/KB2885694 is already included in Win8.1/WS012R2:

    http://blogs.technet.com/b/wsus/archive/2013/10/08/enabling-a-more-predictable-windows-update-experience-for-windows-8-and-windows-server-2012-kb-2885694.aspx

    Are you setting AUOptions=4 ?
    https://thwack.solarwinds.com/community/application-and-server_tht/patchzone/blog/2013/03/14/configuring-the-windows-update-agent--general-settings-part-1


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Thursday, October 2, 2014 9:13 PM
  • Hi Don,

    Thanks for your reply. - yes I can see that sentence regarding the fix being included now.

    My Script does set the various options but the GUI in Control panel  remains the same - except for a comment about settings being managed by the system administrator. This is annoying as you cannot see at a glance what settings are in place and we use a few different settings on our servers depending on the function the server performs. Also you cannot adjust the settings in the CP GUI as before but now have to resort to the local policy editor or the registry.

    I guess that I will have to do a lot more testing to ensure that the scripted setup is installing updates as expected - seems a shame and somewhat unnecessary.

    Thanks again Don


    Regards, Alan

    Friday, October 3, 2014 8:52 AM
  • My Script does set the various options but the GUI in Control panel  remains the same - except for

    ...

    to ensure that the scripted setup is installing updates as expected

    1. If a client is configured to be a WSUS client, then some of the options (such as when the installation event occurs) in the Control Panel will be inaccessible to the user. This has been the case since the creation of SUS, and is not unique to any OS.

    2. Why are you using a *script* to configure the client? Does the script configure the client, or does the script install the updates? You cannot do BOTH in the same script.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Steven_Lee0510 Tuesday, November 11, 2014 3:16 AM
    Monday, October 6, 2014 1:10 PM
  • Hi Lawrence,

    Thanks for your input - much appreciated

    Regarding 1 - That may be true if you use a GPO to set the WSUS properties but my experience is that when the policy is manually set in the registry using a script then the GUI can still be used to adjust it - perhaps it is also a setting - but I don't have time to check at the moment

    Regarding 2 - We use a VBScript to configure the client to use our WSUS server and set the install day of the week and time - we do this because we do not use a domain and also because of the intricacies of our network environment - Each server (WSUS client) on it's own VLAN and very restricted access to the WSUS server - but it works.

    BTW - I added a couple of extra settings to the script and tested it and is does work with server 2012 - although the GUI of course is still of no value.

    Regards,

    Alan


    Regards, Alan

    Tuesday, October 7, 2014 2:05 PM
  • Regarding 1 - That may be true if you use a GPO to set the WSUS properties but my experience is that when the policy is manually set in the registry using a script then the GUI can still be used to adjust it

    Your presumption is incorrect. If the client is configured to use WSUS, then certain UI options are NOT accessible to the UI. Period. The UI and WUA have no idea, nor no care, how the WUA got configured... whether Group Policy, Local Policy, or Registry Hack. The only thing the WUA knows is that a registry value is set, or it isn't. If a registry value is set that makes the WUA a WSUS client, then the UI gets blocked.

    Regarding 2 - We use a VBScript to configure the client to use our WSUS server and set the install day of the week and time - we do this because we do not use a domain and also because of the intricacies of our network environment - Each server (WSUS client) on it's own VLAN and very restricted access to the WSUS server - but it works.

    Maybe not. You're posting here. :-)

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, October 8, 2014 2:01 AM