/build/static/layout/Breadcrumb_cap_w.png

KACE SMA - Windows End of Support Report



Klick here for the latest version: Klick 



========================================================================

Changelog:

11/18/2021:
  • Added support for the Windows 10 November 2021 Update (21H2)
  • Added support for the Windows 11 GA Version (21H2)
  • You can download a ready to use KACE package here.
07/02/2021:
  • Added support for the Windows 10 May 2021 Update (21H1)
01/04/2021:
  • **Happy new year and sorry for the delayed update
  • Added support for the Windows 10 October 2020 Update (20H2)
  • Removed the calculated MS EoS Date (instead only using the official listed EoS Date here: https://docs.microsoft.com/en-us/windows/release-information/ 
  • Added a last inventory field (just the date to find old devices) and added the last logged in user.
05/28/2020:
  • **Found an error in my support dates (fat fingers...) please make sure the downloaded file is called "Windows10 Support_2004._v2.zip".
  • Added support for the Windows 10 Mai 2020 Update (2004)
11/28/2019:
  • Added support for the Windows 10 November 2019 Update (1909).
  • Used the new OS_RELEASE field of SMA 10.0
05/29/2019:
  • Added support for the Windows 10 May 2019 Update (1903).
  • Updated the end of support date for the Windows 10 October 2018 Update (1809).
10/16/2018:
  • Added support for the Windows 10 October 2018 Update (1809).
  • Added a link to the output when there is a unknown build number which redirects you to this article.
09/17/2018:
  • Updated the report to comply with the latest changes in the Microsoft Windows 10 Modern Lifecycle Policy.
05/03/2018:
  • Added support for Windows 10 April 2018 Update (1803)
02/05/2018:
  • Updated to fit the new release policy published by Microsoft
    • All fields are now checking if its an Enterprise or Education release (+6 Month Support)
    • Added the newest End of Support Dates for 1709
  • Added a Common Name Field to Display the Name of the release.
10/18/2017: 
  • Modified Query to have to EOL sections:
    • Calculated EOL Date based on MS 18 month support policy in the Semi-Anual-Channel. 
    • Fixed MS EOL Date
  • Added Windows 10 1709 into the Query.

Note: This query will not work with the Long-Term Servicing Channel

Hi Guys, 

ever wanted to quickly get an overview on which managed Windows device still has support? 
Note: this is not of interest for companies who are running the LTSB/LTSC Version of Windows!
Based on these articles i wrote an easy to extend report for you: Windows 10 release information & Windows 11 release information

The query will find all machines in the inventory of the current org with operating system name starts with "Microsoft Windows 1". 



Cheers 
Timo

Comments

  • Great thing, Timo! Thx!
    By the way:is there a chance we will see some kind of automated Windows 10 build-upgrade tool in KACE some day...? - chrpetri 6 years ago
    • just copy the content of the "new" windows 10 ISO to a networkshare, connect that via script to the client and run: setup.exe with parameter “/auto upgrade". Works like a charm. - ChristianT 6 years ago
      • That's more or less how I've been handling it, but I've broken the process into several scripts.

        Script 1 Robocopies the ISO to a staging directory on the client.

        Script 2 Runs setup with "/auto upgrade /quiet /showoobe none /dynamicupdate enable /copylogs [staging log directory]

        Script 3 Removes the ISO

        I broke it down into three steps to accommodate our remote 1 and 2 cmoputer offices with slow network connections. - billcurnow 6 years ago
  • Does this report also include Windows 10 LTSB? - aquiles 5 years ago
    • Hi aquiles,
      no. LTSB (in comparison with WaaS) is not challenging you to stay up to date with your build versions. You can see in the following link that there are currently only two supported versions of LTSB available and they have extended support till 2025 / 2026.

      https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet - Timokirch 5 years ago
  • Thanks for adding 1803.

    I started to do this myself then came here to check if you updated it, so I didn't have to. Then I was confused that 1803 Enterprise or Education releases do not have +6 months support, ugh MS. - erush 5 years ago
    • No Problem.
      I also was confused (i think everyone was) that MS silently removed the +6 months. First i thought they may have forgotten to update the text below the chart but i double checked today and there is still no update. So it's a said fact that companies now have again the trouble to update within 18 Month. But with KACE no problem :)

      https://support.quest.com/kb/255380/windows-10-build-upgrade-deployment-walkthrough - Timokirch 5 years ago
  • Looks like this Report needs another update. All currently supported Enterprise/Education and all future September Enterprise/Education releases are a 30 month lifecycle. MS fact sheet web page was updated. - erush 5 years ago
    • Hi erush,
      yes MS has updates his policy. Unfortunatly i was OOO traveling. Will update the report asap.
      Regards
      Timo - Timokirch 5 years ago
  • Updated the report to comply with the latest changes in the Microsoft Windows 10 Modern Lifecycle Policy. - Timokirch 5 years ago
  • Updated to support 1809 - Timokirch 5 years ago
  • Updated to support 1903 - Timokirch 4 years ago
  • It works like a charm! Thks Timo - Steph386 4 years ago
  • Hi Timo,

    Can you ugrade Windows 10 1709 to 1809 in one step?
    Kind regards,

    Rachid - Rachid 4 years ago
    • Hi Rachid,
      you definitely can do this (did this today in a demo). If you want to check if one of your endpoints have any blocking configuration for an build update check this article: https://www.itninja.com/blog/view/kace-sma-windows-10-inplace-upgrade-precheck

      Kind Regards
      Timo - Timokirch 4 years ago
      • Hi Timo,

        Thanks for the information!

        Kind Regards,

        Rachid - Rachid 4 years ago
  • Is there an easy way to add username of the user to the report above? i have tried adding the following: USER.USER_NAME AS 'NAME',

    but keep getting an error :(!

    Thanks - samuel.campbell@gilbert-ash.co.uk 4 years ago
    • Hi Samuel,
      do you want to see the loginname or the displayname in the report?

      Kind Regards
      Timo - Timokirch 4 years ago
      • Hi Timo,

        Login name if possible, we then plan to use this report as are checksheet to see which users still require updating.

        Thanks
        Sammy - samuel.campbell@gilbert-ash.co.uk 4 years ago
      • Hi Samuel,
        please try to add the following line to your select statement:

        MACHINE.USER_LOGGED AS 'Username',

        This should bring the login name of the currently logged in (or last logged in) user at the time of the last inventory of the device.

        Kind Regards
        Timo - Timokirch 4 years ago
  • Thank you for making and publishing this. It's exactly what I need to maintain OS versions. I cant sadly download it at the moment, I don't seem to be a approved member... - daniel.lingxxxxx 4 years ago
    • Hi Daniel,
      did you try to submit your email address which you are using for our support site? You need to have active maintenance as well.
      Kind Regards
      Timo - Timokirch 4 years ago
      • I believe I became a approved member by simply posting but I don't have a proper support account. I need to sort that out. Thanks for the assistance, Timokirch! - daniel.lingxxxxx 4 years ago
  • I really appreciate this script, we use it all the time as we are updating our desktops. Are you going to add v1909 to this as well? - ahall@aisinauto.com 4 years ago
    • Update for 1909 done :) - Timokirch 4 years ago
  • I really like your script, but I Just tried to upload this new one on SMA 10.0 and it would not go through. Says it's not a valid .kbin file. - zbaatz 4 years ago
    • Hey Zbaatz,
      have you tried to redwonload the file and apply it again? The MD5 of my local file is:
      1CEC9770EE32F98123B02747FD1744B9 - Timokirch 4 years ago
      • I just tried the kpkg, get an md5 of a66715bb66ea6be73faf1ddd259a946f

        did you make a different link? the one in thread shows date of 08/12/2019 - rwt 4 years ago
      • Hi rwt, sorry for the delay. i have reuploaded the package. Could you please try again downloading it? - Timokirch 4 years ago
      • The hash is correct, but the SMA still says to use a valid .kbin file. The file I downloaded is a .kpkg file and not a .kbin. - zbaatz 4 years ago
      • It’s right that the file is a .kpkg. Please follow the instructions of this kb article and let me know if there are further problems.

        https://support.quest.com/kace-systems-management-appliance/kb/116949/how-to-import-and-export-resources - Timokirch 4 years ago
      • I must be losing it. I haven't used my file share in over a year and completely forgot about that. It worked. Thank you! :) - zbaatz 4 years ago
      • No worries, glad that it’s now working for you :) - Timokirch 4 years ago
      • Awesome it worked, thanks for reuploading it. Very useful. Appreciate the work that went into it and providing it publicly. - rwt 4 years ago
  • Timokirch Could you please provide me the sql query? Thank you! - Levio 4 years ago
    • Hi tlambert54,
      please excuse my delay. You can find the SQL query within the .zip which i have posted in the customer downloads.
      Kind Regards
      Timo - Timokirch 3 years ago
  • Timokirch...same here...any way to get the SQL query...thanks! - tlambert54 3 years ago
    • Hi tlambert54,
      please excuse my delay. You can find the SQL query within the .zip which i have posted in the customer downloads.
      Kind Regards
      Timo - Timokirch 3 years ago
  • Hi all,
    i have updated the report to include the 2004 build. Also i have added the plain SQL to the download file (is now a .zip).
    Kind Regards
    Timo - Timokirch 3 years ago
  • Updated to 20H2. - Timokirch 3 years ago
  • thanks alot for updating, brill work as always! - samuel.campbell@gilbert-ash.co.uk 2 years ago
  • Updated to 21H1 - Timokirch 2 years ago
  • Updated to 21H2 - Timokirch 2 years ago
  • Are you going to add Win 10 and Win 11 22H2? - timglass 1 year ago
    • Hi Tim, there is a new blog post with the updated report :)

      https://www.itninja.com/blog/view/kace-sma-windows-end-of-support-report - sven.hain 1 year ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ