Notification

Icon
Error

Windows 1803, 1809 and 1909 end of life

Posted: Tuesday, May 11, 2021 2:59:29 PM(UTC)
Esben.D

Esben.D

Member Administration Original PosterPosts: 2,083
0
Like
It is that time again. Microsoft is leaving behind some of its older OS versions and ending support. To help you manage this, we've created a blog detailing the changes, and also a report that covers all of the currently known EOL dates for Windows.

Visit the blog post here.

UserPostedImage
brodiemac-too
#1brodiemac-too Member Posts: 48  
posted: 5/27/2021 9:36:54 PM(UTC)
When will Lansweeper properly report version numbers? Once we have updated beyond 2004, all of our devices will report as being 2009.
Esben.D
#2Esben.D Member Administration Original PosterPosts: 2,083  
posted: 5/28/2021 12:53:25 PM(UTC)
Originally Posted by: brodiemac-too Go to Quoted Post
When will Lansweeper properly report version numbers? Once we have updated beyond 2004, all of our devices will report as being 2009.


It's actually technically correct. Windows WMI still lists Windows version in the old style. While they display & market it as 20H2.

You can run the following powershell script to see it for yourself:
Code:
Get-ComputerInfo  | select windowsversion
brodiemac-too
#3brodiemac-too Member Posts: 48  
posted: 5/28/2021 1:02:00 PM(UTC)
That is true for 20H2 but 21H1 also reports as 2009
Esben.D
#4Esben.D Member Administration Original PosterPosts: 2,083  
posted: 6/1/2021 4:12:06 PM(UTC)
Originally Posted by: brodiemac-too Go to Quoted Post
That is true for 20H2 but 21H1 also reports as 2009


Did some digging. It's a Microsoft issue, multiple people are complaining about it:

https://techcommunity.mi...81/highlight/true#M2747
https://twitter.com/SMSa...394869259742896130?s=19

You are indeed correct, I spun up a VM:
UserPostedImage

Unfortunately, not much we can do about it until MS fixes their own mistake. One way to get around it is to use the build version to determine the OS version in your report (similar to what we do in the Patch Tuesday reports).
In case you are wondering, the patch Tuesday reports use that method because before LS 7, we didn't scan the version directly, so it's kinda legacy code Anxious
Esben.D
#5Esben.D Member Administration Original PosterPosts: 2,083  
posted: 6/4/2021 2:08:52 PM(UTC)
Quick update that we are looking at ways to resolve this ;)
Guest
#6systeembeheerders@westlandinfra.nl Guest Posts: 18  
posted: 6/8/2021 2:02:59 PM(UTC)
Hopefully it will be fixed at the June Patch Tuesday.

Active Discussions

Lansweeper Linux Agent - login user
by  Dinusha Chandrasinghe   Go to last post Go to first unread
Last post: Today at 11:03:07 AM(UTC)
Lansweeper device with multiple NICs
by  mzipperer  
Go to last post Go to first unread
Last post: Yesterday at 7:42:57 PM(UTC)
Lansweeper Internal Note
by  mdavis2503   Go to last post Go to first unread
Last post: Yesterday at 6:00:07 PM(UTC)
Lansweeper Problem with deploy software
by  Max90  
Go to last post Go to first unread
Last post: Yesterday at 12:09:40 PM(UTC)
Lansweeper Can lsagent be protected from deletion
by  RKCar   Go to last post Go to first unread
Last post: 11/29/2021 8:56:09 PM(UTC)
Lansweeper HTTPS not secure
by  Larry Rhea  
Go to last post Go to first unread
Last post: 11/29/2021 7:50:59 PM(UTC)
Lansweeper Warning about Built-in Admin
by  Larry Rhea   Go to last post Go to first unread
Last post: 11/29/2021 7:45:45 PM(UTC)