Woody Leonhard's no-bull news, tips and help for Windows and Office
Home icon Home icon Home icon Email icon RSS icon
  • Win10, Server 2016 KMS servers start rejecting Win7 client activation

    Posted on January 9th, 2017 at 06:31 woody 9 comments

    From ch100:

    It appears that Windows 2016 and Windows 10 when configured as KMS hosts, after a while reject the activation of Windows 7 KMS clients, considering them non-genuine. I don’t know the cause, but it appears to affect machines which were offline for about 2 weeks or longer, which should not happen. This became obvious after the Christmas & New Year’s break when many people took extended leave. Maybe it happens within Microsoft too, although I am expecting that their employees are not allowed to use Windows 7 any longer. 😉

    There is a manual fix for the affected machines by rearming the system (KMS activation does not have a limited number of rearming operations, as the counter is reset each time one such activation takes place). But there is no guarantee that it will not happen again.

    The solution proposed by Microsoft is to use older OS as KMS hosts until there will be a fix available. This may be related to the known crashes of the Windows 2016 Server role Volume Activation Services.


    And Microsoft’s workaround (from the same thread):


    “The recommendation at this point is to leave your existing KMS system alone. Whether it is running on Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, continue to service the machine via security and quality updates. Allow your KMS system to activate down-level operating systems and Office installs (Windows 7, Windows Server 2008/2008 R2, and Office 2010). Utilize Active Directory Based Activation (ADBA) for all new clients (Windows 8, 8.1, Windows Server 2012, 2012 R2, 2016, Windows 10, Office 2013, and Office 2016).”


    If that helped, take a second to support AskWoody on Patreon

    9 Responses to “Win10, Server 2016 KMS servers start rejecting Win7 client activation”

    1. James Bond 007 says:

      Haha, so Windows Server 2016/Windows 10 KMS hosts cannot activate older OS such as Windows 7 now? Microsoft, what have you done again? What is your intention? Wanting to force those Windows 7 users to Windows 10 again? I am sure Windows 10 clients won’t have such a problem, haha.

      In the comments of that thread:

      “Microsoft, it really HURTS to manage your flagship products.”

      “As if this whole activation process wasn’t a burden on your users already, Microsoft. It’s just increasingly hostile being a Microsoft customer.”

      “Really Microsoft, really!?!?! Why even have the option to install a kms host for legacy clients on 2016 server then?”

      So true.

      • ch100 says:

        “Haha, so Windows Server 2016/Windows 10 KMS hosts cannot activate older OS such as Windows 7 now?”

        They do… for a while.
        Time for a new beta, “Creators Edition” or whatever will be called when released.
        And another one, and another one…

        • Nd60 says:

          SO????? the gods has spoken (or whisper for now)…

          the writings on the wall….
          for A.L.L.U.S.E.R.S….

          as foretold…
          activation is the key
          the key is the bottle neck….
          the bottle neck is K.O.N.T.R.O.L.

          in their fair use policy…
          users pay to be used… no?
          same as all the gov-coporate laws and policy
          they exist ‘for your safety and awesome wholesome future’
          illusion of freedom – best thing since slice bread

          go back finshing for better dreams

    2. abbodi86 says:

      Let the conspiracies start 😀

    3. ch100 says:

      Unfortunately Windows 2016 looks as non-finalised as is Windows 10 1607 (they share the same build). Or you can name them extremely and annoyingly buggy instead of non-finalised.
      Based on Windows 10 build 1607 being made CBB, one would expect that the build with patches to date is already Enterprise-ready, or at least Small Business ready (which should be the same thing), but it can hardly be named so. The server should have been Enterprise ready because it made it into LTSB from the launch.

      Windows 8.1/2012R2 needed 2 major patches to be ready and one more for fine tuning:

      KB2884846 – October 2013 Update Rollup (I think this one was built in the Server 2012 R2, like 1607 is built in Server 2016)

      KB2919355 – April 2014 Update 1 for Windows 8.1/2012R2 (the true Service Pack 1)

      KB3000850 – November 2014 Rollup – current reference build, ISO v4 for Server 2012 R2

      As it stands today, Windows 8.1 and 2012 R2 are completely stable and reliable and this was the case since April 2014 and more so since November 2014. Some people may not like the GUI, but this is cosmetic and subject for a different discussion. I don’t particularly like it either, but it passes, just.

      How many more “Feature Upgrades” Windows 10 needs to be on par with Windows 8.1?
      This is even more important for the Server 2016 equivalent, which is supposed to take over from Windows 2012 R2, but while I use it today, it is mostly for what I consider non-critical functionality and Windows 2012 R2 is always on stand-by to take over if required.

      There have been already 18 months since Windows 10 was originally released. How much longer does it take to get reasonably stable?
      In reality, 1511 was almost there, there were excellent reviews for Windows Server 2016 Technical Preview 5 based on 1511, only to end with this yet another beta build (1607) officially supported replacing the previous stable one on its way out at the desktop level and not supported at the server level.

    4. ch100 says:

      The issue, although apparently known for more than 1 year, is now mentioned on patchmanagement.org email list.

    5. Anonymous says:

      You guys are misreading the issue.

      This is only for machines that are KMS clients that have been offline more than 2 weeks.

      So typically we see this when imaging a PC with an “old” image.

      Inconvenient for the help desk, yes.

      But this won’t affect machines on your network that are active.

    6. RobertD says:

      Well, yes it does. Our Server 2016 KMS host has just started developing this issue after we took it in production a few months ago. More and more windows 7 machines are reporting not genuine. slmgr.vbs /rearm – restart – slmgr.vbs /ato resolves it temporarily for them.
      Windows 10 machines and Office are activating just fine.
      We want a fix asap also!

    Leave a Reply