OS: Not latest Build of Windows XXX - error with version numbers

[Andreas_79]

Hello togehter,

we are using the Reports to show which clients and servers are up to date.

But it shows all server builds wrong. The Build numbers in lansweeper are always with a Letter S in it, like 10.0.17763S.6414 I think the S is wrong so the report wont work coreectly. What can we do that the report work correctly?

Regards
Bert

[Lennart]

I have the same kind of problem as you, but on Server 2016.

I added these fields to a copy of the report: MaxOsCodeNumeric, MaxBuildNumber, OsCodeNumeric, BuildNumber 

And in my report, It now shows MaxBuildNumber ="" or NULL, as you pointed out.

We need a condition in the SQL that handles this kind of situation, not all can lift all servers one sub-version on the day lansweeper adds the buildnumber to the table. I don´t know if this builds is even released yet, and in the meantime we can´t easy see how many server is behind the rest of our fleet.

[Josha]

Strange, I made a very detailed reply, but I guess it didn't save or got removed?

The reports ignore the S so that's not the problem.  It looks at the tsysOS table and shows any machines that match the server version (Win 2019) but aren't on the max OS Code.  In the case of Server 2019 (17763) my installation (11.4.1.4) shows the max OS Code is 10.0.19043S and since none of them are on that version, they are all showing up on the report.  I don't know where this table gets its data but maybe it's a bug?

OScode	OSname	Image	Sortorder	OSCodeNumeric
10.0.19043S	Win 2019	ten10.png	20	10019043

[Josha]

Which exact report are you running?  I'm pretty sure Lansweeper adds that S in there to identify it as a Server OS.  

For my servers, the OScode in the tblAssets table shows 10.0.14393S / 10.0.17763S.

However, the Version column in the tblOperatingSystem table shows 10.0.14393 / 10.0.17763.

I checked OS: Not latest Build of Windows 2016 & OS: Not latest Build of Windows 2019 on my server (version 11.4.1.4) and both have logic to ignore the S in the tblAssets table.  

(Select Case
	When IsNumeric(Replace(Replace(Replace(tblAssets.OScode, '.', ''),
	  'S', ''), 'R', '') + '.0') = 1 Then
	  Cast(Replace(Replace(Replace(tblAssets.OScode, '.', ''), 'S', ''),
	  'R', '') As BIGINT)
	Else 0
  End As Expr1) As OsCodeNumeric,

To further dive into this report, it looks like the code above converts 10.0.17763S to 10017763.  It then looks at the tsysOS table and gets the max version for the matching OS version.  In my case, Server 2019 shows a max version of 10.0.19043.  It looks at the numeric value (10019043) and if your servers are lower than that version they show up on the report.  It also looks at the max build number for the matching OS numeric value (10019043) and shows any servers that are on the same version but not on the newest build.  

It would be helpful to add a column to the report showing the expected version / build number so you know why the servers are appearing.  However, I'm not sure how the tsysOS table gets updated.  We don't have any Win 2019 servers on 10.0.19043 and that makes the max build number NULL since the report is looking for build numbers in your existing environment and not a database from MS.