Free Readiness MEMCM / SCCM Windows 11 Report

Benoit LecoursSCCM15 Comments

Windows 11 has been officially announced on June 24th, 2021 and the first ISO was released last week. Windows 11 is coming and as an SCCM administrator, you must get ready to deploy this new OS. We released a complete post on everything you need to know about this major OS release. This blog post will focus on Windows 11 readiness. How can you ensure that your device will be ready to install Windows 11? The best solution as of today is to build an SCCM Windows 11 report to list which device is ready and which needs attention.

Windows 10 was specifically designed to run on older hardware, Windows 11 requires new hardware and you’ll not be able to install it on older PCs. Most PCs built-in 2019 or later will work with Windows 11, although there are some exceptions. Older hardware is less likely to pass Windows 11’s prerequisites checks. PCs purchased in 2016 or earlier are almost certain to be unsupported.

Windows 11 also requires a Trusted Platform Module (TPM), UEFI firmware (no legacy BIOS allowed) and Secure Boot. Virtually all PCs designed and built since 2015 include TPM 2.0 support, but you might have to go into the firmware settings to enable it.

Here are Microsoft official requirements needed for Windows 11

Processor:1 gigahertz (GHz) or faster with 2 or more cores on a compatible 64-bit processor or System on a Chip (SoC)
RAM:4 gigabyte (GB)
Storage:64 GB or larger storage device
System firmware:UEFI, Secure Boot capable
TPM:Trusted Platform Module (TPM) version 2.0
Graphics card:Compatible with DirectX 12 or later with WDDM 2.0 driver
Display:High definition (720p) display that is greater than 9” diagonally, 8 bits per colour channel

As you can see, there’s a couple of checks to install Windows 11. If you have SCCM installed on your devices, you can build a report to find your compliant devices. We have good news for you: We built it for you and it’s available for free!

Windows 11 Readiness Report

Updated 2022/02/17 :

We build this report to list which machines could or be couldn’t install Windows 11 based on Microsoft recommandation.

Here are the detailed specifications of the report :

  • List : Device Name, UserName, Client Status, Client Version, OS Edition, OS Version, OS Branch, CPU Speed, Supported Intel CPU, RAM, Free Space, Device Manufacturer, Device Model, Secure Boot Status, UEFI Bios status, TPM version and status
  • 6 comprehensives pie charts to list a count of compliant devices in each categories
  • Red hightlight if a component did not match Microsoft minimum requirement
SCCM Windows 11 Report
  • You can scope the report using a Collection or enter a device name to show its status. You can also choose to display only non-compliant devices.

Download the SCCM Windows 11 report

The report is available for free on our shop website. All you need to do is to download the report and install it on your reporting server. You can read our blog post on how to install a report if you need clarification.

SCCM Windows 11 Report

We hope this report is useful. Please share your comment if you have any ideas to improve it !

15 Comments on “Free Readiness MEMCM / SCCM Windows 11 Report”

  1. Pingback: Windows 11 Compatibility for Businesses –

  2. Pingback: DEPLOY, REFRESH AND UPGRADE WINDOWS 11 SCCM / MEMCM - Hidden Shard Blog


  4. I have modified the report to add the 8 GB RAM settings but am getting an error “Invalid length Parameter passed to LEFT or SUBSTRING function ” any help appreciated. thanks

  5. Thank you for the awesome report. Only issue I’m having with it is that the “CPU- More than 1Ghz” graphic for “Yes”, which is all of the clients in my environment, is represented in red instead of green. “Yes” for all the other graphics is in green, including “RAM – Moe than 4GB” which is also all of my clients.

  6. This report is awesome, except the “CPU – more than 1Ghz” graphic is displaying “yes” in red. It’s pretty obvious, but kind of throws a viewer off at first look.

  7. Thanks great report, I did make a few tweaks to it. I move the “TPM.SpecVersion0 != ‘Not Supported’” from the where statement to the join statement. I have some PCs that TPM is disabled in BIOS and were not showing on the report. Deleting it from the where and adding it to the join now all the PCs show up. I know most of the PCs with TPM disabled won’t run Win 11 but my boss will still want to see them on the report. The join looks like this now.
    LEFT JOIN v_GS_TPM as TPM on TPM.ResourceID = S.ResourceID AND TPM.SpecVersion0 != ‘Not Supported’

    For the CPU generation number I know you can’t really add this to the report but maybe this will help someone else. For mine I’ve created a separate DB with tables of different things I use in a lot of reports (Win 10 build numbers, Office build numbers, PC Types…) . I went thru our CPU list and created a table matching the CPUKey field with the generation number. So the table has the CPUKey field, then the name field (Kaby Lake, Comet Lake, Tiger Lake…) and then the Gen (7th Gen, 8th Gen, 9th Gen…) It took an afternoon of googling to get a good list but now I can easy join that remote DB table to my report to have the generation number in a column. I also added a graph to show 8th gen and higher as yes and the rest as no.

  8. Thank you for this report, it is going to be very helpful when we start our migration to Windows 11! The only problem I am having with the legacy version is that both the “SecureBoot Enabled” and “UEFI” Enabled are returning #Error as the value.

    Is there anything I need to change / enable to get these values returning a Yes or No? I had a look at the Query in the report builder and it seems fine to me, but I may be missing something.

  9. I echo the previous comment, this report is really helpful. What are the possibilities of getting data on the supported CPU generation? This report would be 100% comprehensive if it could report back on that. Right now I’m using device collection queries in ConfigMgr which is sloppy, at best.

  10. Actually, I just realized what is going on. For that chart, there are no systems that have a value of No. That means Yes is the only value, so yes gets assigned the first color in the color set, which is red. Somewhat confusing at first look.

  11. This is a great report! It does have one formatting problem: the SecureBoot Enabled pie chart shows Yes as red and No as green. All the other charts show Yes as green and No as red.

Leave a Reply