ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Making Windows Server 2016 Update Automatically

    Scheduled Pinned Locked Moved IT Discussion
    windowswindows server 2016windows serverpowershellregeditregistry
    17 Posts 6 Posters 1.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403 @scottalanmiller
      last edited by

      @scottalanmiller Why would you want your server automatically installing updates? Besides the obvious "because I never want to have to sit through windows updates".

      This seems like a bigger risk, in that an update could break your server.

      scottalanmillerS 2 Replies Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @DustinB3403
        last edited by

        @DustinB3403 said in Making Windows Server 2016 Update Automatically:

        @scottalanmiller Why would you want your server automatically installing updates?

        Whenever security is a top priority. Because having humans in the process is the biggest security risk.

        1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender
          last edited by

          Can it set it to reboot only between say 10 PM and 4 AM?

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @DustinB3403
            last edited by

            @DustinB3403 said in Making Windows Server 2016 Update Automatically:

            This seems like a bigger risk, in that an update could break your server.

            That's a "headline news" risk. In the real world, this is a risk, but a tiny one. In two ways. First, it is very unlikely to happen - when it does happen people make a big stink about it and it makes the news. So it sounds way more common than it is (like shark attacks.)

            The second is impact. The impact of a bad patch is traditionally trivial. Just application compatibility normally. That has typically a tiny financial impact on a company.

            The counter risk is ransomware or malware. These items are both far more likely to happen (if you aren't patching quickly) and the impact is dramatically more - data stolen, prolonged outages, data loss, etc.

            So it is a double whammy... bigger damage, more often. The rule is... patch fast, patch often, don't let a human get in the way of security unless you really, really need to.

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @Dashrender
              last edited by

              @Dashrender said in Making Windows Server 2016 Update Automatically:

              Can it set it to reboot only between say 10 PM and 4 AM?

              Yes, you control that.

              dafyreD 1 Reply Last reply Reply Quote 0
              • dafyreD
                dafyre @scottalanmiller
                last edited by

                @scottalanmiller said in Making Windows Server 2016 Update Automatically:

                @Dashrender said in Making Windows Server 2016 Update Automatically:

                Can it set it to reboot only between say 10 PM and 4 AM?

                Yes, you control that.

                And Snapshot at 9:50 PM (assuming this is a VM).

                jmooreJ 1 Reply Last reply Reply Quote 0
                • jmooreJ
                  jmoore @dafyre
                  last edited by

                  @dafyre Yes the Windows 1803 patch broke our database and caused EdExpress to go wonky for quite a while until I disabled updates. As soon as Windows went to 1809 it all started working again. So just an fyi for you @dafyre if you had any troubles with this too.

                  dafyreD DashrenderD scottalanmillerS 3 Replies Last reply Reply Quote 0
                  • dafyreD
                    dafyre @jmoore
                    last edited by

                    @jmoore said in Making Windows Server 2016 Update Automatically:

                    @dafyre Yes the Windows 1803 patch broke our database and caused EdExpress to go wonky for quite a while until I disabled updates. As soon as Windows went to 1809 it all started working again. So just an fyi for you @dafyre if you had any troubles with this too.

                    EdExpress is one of two pieces of software I'm glad I don't have to deal with anymore... (EdConnect is the other, lol).

                    jmooreJ 1 Reply Last reply Reply Quote 0
                    • jmooreJ
                      jmoore @dafyre
                      last edited by

                      @dafyre Ugghh lol and of course they are used in tandom. I support these and I hate it lol

                      dafyreD 1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender @jmoore
                        last edited by

                        @jmoore said in Making Windows Server 2016 Update Automatically:

                        @dafyre Yes the Windows 1803 patch broke our database and caused EdExpress to go wonky for quite a while until I disabled updates. As soon as Windows went to 1809 it all started working again. So just an fyi for you @dafyre if you had any troubles with this too.

                        did you roll back to 1709? then roll up to 1809 when it came out?

                        jmooreJ 1 Reply Last reply Reply Quote 0
                        • dafyreD
                          dafyre @jmoore
                          last edited by

                          @jmoore said in Making Windows Server 2016 Update Automatically:

                          @dafyre Ugghh lol and of course they are used in tandom. I support these and I hate it lol

                          I no longer have to do anything but snicker anytime somebody mentions them now, ha ha... so.... *snicker, snicker.

                          jmooreJ 1 Reply Last reply Reply Quote 0
                          • jmooreJ
                            jmoore @Dashrender
                            last edited by

                            @Dashrender Yes. I may have the version wrong but I did have to do that and then I disabled updates until 1809 tested well at my workstation.

                            1 Reply Last reply Reply Quote 0
                            • jmooreJ
                              jmoore @dafyre
                              last edited by

                              @dafyre lol and I can't wait for that same day 🙂

                              1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @jmoore
                                last edited by

                                @jmoore said in Making Windows Server 2016 Update Automatically:

                                @dafyre Yes the Windows 1803 patch broke our database and caused EdExpress to go wonky for quite a while until I disabled updates. As soon as Windows went to 1809 it all started working again. So just an fyi for you @dafyre if you had any troubles with this too.

                                1803 is not a patch. That's a new OS version. While it is handled through Windows Updates, it's not the same as a patch.

                                1 Reply Last reply Reply Quote 0
                                • black3dynamiteB
                                  black3dynamite
                                  last edited by

                                  Has anyone tried this with 2019?

                                  1 Reply Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller
                                    last edited by

                                    Not yet.

                                    1 Reply Last reply Reply Quote 0
                                    • 1 / 1
                                    • First post
                                      Last post