Lansweeper published this great report template that checks your Windows assets for Windows 11 compatibility.
Windows 11 Requirements Audit - Lansweeper IT Asset Management
However, there is a flaw in this report in that it is marking an asset as failing the "Disk Space > 64 GB" if it detects that there is less than 64 GB of available free space. The actual Windows 11 requirement is that the disk be 64 GB or larger, and the amount of free space you need is highly dependent on several factors.
Whoever built this report decided to check for free space instead, so that means we have several workstations that are marked as failing the compatibility check when they would otherwise update to Windows 11 just fine. For example, a workstation with a 256 GB drive with 60 GB available free space. Obviously available disk space can be a worry in certain situations, but marking machines that have 30,40,50, or 60 GB of free space as incompatible doesn't seem to be the way to go.
Is there a version of this report that looks at the disk size instead? Or can anyone provide an edited version that does so?
Solved! Go to Solution.
Thanks, but I'm only seeing a "Disk Space > 64GB" column, which appears to be looking at free space and not actual disk capacity. The "fail" on this is a system that has a 256gb SSD, although only 8.7gb free which I think is why it's failing. I was expecting to see a "pass" there because the disk does meet requirements.
Would it be possible to amend the report to mark systems like that in yellow to indicate that it is capable but needs intervention?
Hmm, well this is the subquery used for the disk space. You can use that to verify what the bigger report is using as raw data, any asset listed here should pass the test.
Select Top 1000000 tblAssets.AssetID, tblAssets.AssetName, Cast(Cast(tblDiskdrives.Freespace As bigint) / 1024 / 1024 / 1024 As numeric) As free, Cast(tblDiskdrives.Size / 1024 / 1024 / 1024 As numeric) As TotalSize, tblComputersystem.SystemType From tblAssets Inner Join tblDiskdrives On tblAssets.AssetID = tblDiskdrives.AssetID Inner Join tblComputersystem On tblAssets.AssetID = tblComputersystem.AssetID Where Cast(tblDiskdrives.Size / 1024 / 1024 / 1024 As numeric) > 64
Just in case someone needs an updateded version of the compatibility list including some of the newer supported CPUs: here you go. I formated the list on the Microsoft Site for AMD and Intel with Excel and created a very long list of cpus.
This fixed my problem with some new notebooks which were marked as incompatible. Unfortunately the list exceeds the 40.000 characters allowed in this comment section. But you can simply download it from my gdrive: https://drive.google.com/file/d/1YiN6Xe1l2AtNOUQyoP47R70zfYROGJND/view?usp=sharing
The URL should open a text preview for you where copy/paste the content whithout downloading the sql-file.
Hope this helps
Thanks, it is certainly useful. My organisation wants to do an in-place upgrade and then "free space" is of utmost importance. I had gotten that info from the report "Windows: disk space with color" (web50repwindiskcolor) which I then joinced in Excel.
Hi Esben, I am a long-time LanSweeper user/enthusiast, and I'm using it almost daily. Our database has been in place since version 1 and therefore has seen many migrations/updates. My problem: For some reason I cannot import the Win11 readiness audit report code. When I import in the online query-editor and try to save or save-and-run I get the deadly donut. When I import it using the editor in MS-SQL-server I get all kinds of binding errors (like "The multipart identifier 'tblProcessor.Name' could not be bound", and similar errors for other fields). I've edited the SQL code to insert "dbo." in front of the fieldnames in the error report (so that it now reads 'dbo.tblProcessor.Name'), and then the volume of errors decreases but never reaches zero. So, I cannot save the report code. Any idea what's wrong? I definitely want to use this very valuable report...
Found the cause of the problem I reported! This query is too complex for the SQL Designer I always use. It is a bug in the designer that causes the binding errors upon validation of the SQL code. When I use pure SQL to create the view "script view as -> create to --> new query editor window" then creation of the view runs without a hitch....
Also, there is a scan for the registry setting in "%SYSTEM\ControlSet001\Control\SecureBoot\State\UEFISecureBootEnabled" which was not scanned by default in our implementation, which caused 95% of all PCs to be not Win11 compatible. Now that the reg-key has been added to the scanning scheme I can see the volume of compatible PCs growing. Maybe this is also the case with others? Check your scanning setup guys!