locked
Server 2016 - installing updates RRS feed

  • Question

  • Hi there

    Currently we have a number of Server 2008 R2 boxes that are due to be replaced with new hardware and Server 2016 when it is released - we have preview 5 running on one new box..

    With 2008 R2 we schedule updates for the Saturday after patch Tuesday and notify our customers that there will be planned maintenance for 15 minutes or so on that day. In addition if MS release an out of band patch we can de-select that and install other items that will not require a reboot until the next scheduled downtime...

    Not sure if it's just a preview thing, but there are two items that are concerning with 2016...

    1. I can't seem to find a way to install, say definition updates, and leave the others

    2. Security updates are arriving on a different date to 2008 R2 (one just landed overnight). This is OK for the preview version but we don't want two different monthly downtime dates when they go live

    Is this something that will be addressed in the release version?

    Thanks :-)


    Qui me amat, amet et canem meum

    Thursday, August 25, 2016 2:00 PM

Answers

  • Once Windows Server 2016 is officially released, it will be on the same patch schedule as other Microsoft products, so if your existing method works for you, it should continue to work when applied to 2016.

    It is better to use a tool such as WSUS or SCCM or one of many third party tools for scheduling patching/updating instead of relying simply on the capabilities within Windows itself.  These utilities provide you much more flexibility in selecting/de-selecting patches.  They also allow you to easily test the patches on a sub-group (lab) of computers to see whether or not the patches would affect anything you are currently running.  They also allow a central point of management for all patches instead of managing every box individually.  Many other benefits accrue from centralized patch management.


    . : | : . : | : . tim

    • Marked as answer by gchq_fox Thursday, August 25, 2016 3:00 PM
    Thursday, August 25, 2016 2:25 PM

All replies

  • Once Windows Server 2016 is officially released, it will be on the same patch schedule as other Microsoft products, so if your existing method works for you, it should continue to work when applied to 2016.

    It is better to use a tool such as WSUS or SCCM or one of many third party tools for scheduling patching/updating instead of relying simply on the capabilities within Windows itself.  These utilities provide you much more flexibility in selecting/de-selecting patches.  They also allow you to easily test the patches on a sub-group (lab) of computers to see whether or not the patches would affect anything you are currently running.  They also allow a central point of management for all patches instead of managing every box individually.  Many other benefits accrue from centralized patch management.


    . : | : . : | : . tim

    • Marked as answer by gchq_fox Thursday, August 25, 2016 3:00 PM
    Thursday, August 25, 2016 2:25 PM
  • Thanks Tim

    Never even heard of WSUS or SCCM and I've been installing networks (albeit fairly small ones) since Netware 3.x :-(

    Just goes to show you can always learn something new.

    Thank you


    Qui me amat, amet et canem meum

    Thursday, August 25, 2016 3:02 PM
  • WSUS - Windows Server Update Service - been around for at least 10 years.

    SCCM - System Center Configuration Manager - been around for at least 20 years.


    . : | : . : | : . tim

    Thursday, August 25, 2016 10:03 PM