Windows OS Version and Build Number in LogMeIn Central

Thank you AshC. ... and thank you PolarWizzle for bringing this up years ago! ;o)

I've heard the developer review  approach a year or two ago ... I second Polar Wizzle thought on discussion of the topic ... only common sense decision is needed ;o)

This is not a "I want" feature, this is a "I need / must have" feature.

---

PolarWizzle wrote:

Hi AshC,

Would you happen to have any further update?

 

Can we get a update on this question?  We are trying to find out how many computers we have on 1909 and it isnt reasonable to click each computer to find out the info.

---

Maybe the issues with LogMeIn Antivirus on Win 10 2004 will clarify to LogMeIn Cnetral team that clearly identifying Win 10 version is important and that Win 10 versions matter as a new way of identifying Windows OS upgrades ;o) Curious about Ash follow up ...

Hi, need this information as well. Cannot go and check hundreds of computers  in their individual dashboard to know the build number - need a report on this!

Can it really be that this is so hard to do that three years later, this issue still hasn't been resolved?

Hi abbeyinscal, I appreciate the info and tips!

I do NOT have any servers, my environments are Cloud only ... so server-based approach will not work ;o) ... and I  recommend that SMBs (most of my customers) get rid of servers ... to avoid VPN and Solarwind like issues.

LogMeIn agent already collects version info (per device), but the info is NOT available in Central, in aggregated format - for all devices - to facilitate proper management, security and compliance... 

 I cannot use share/free ware, and I do NOT want multiple management agents on devices - which create security risks ... I understand there are options (that provide that basic info) and that I will have to consider... e.g. Microsoft Endpoint Manager, Team Viewer or Continuum (which seems to be using LogMeIn as a back end platform ;o)

Yeah ... but I'm not paid by the hour ;o) ... and I do not have admin access to all devices ... the less access I have the better I sleep at night ;o)

Managing by policy is the idea, not by hands on access to each device.

You know what's especially funny.... someone took the time to make a function in the inventory that tells you how OLD the OS is. I'm guessing that age is calculated based on the date that the machine's particular build number was released. Maybe? But since it just says "Age of OS" with no explanation of how that calculation is derived, it's pretty useless to me.

Just, PLEASE, give us the build number. This cannot be a hard thing to do, and it would be an amazingly useful thing.

It's been a top request for two years and three months. I don't think "top request" means what they think it means....

AshC 

Following up as well ... OS version as displayed currently: Win 10 Pro is not enough for appropriate WIn 10 management - it does not tell us if the OS is recent. What we are looking for is something like: Win 10  1909, Win 10 1903 ... this OS identification seems to be available in Continuum tool (which seems to be a using LogMeIn ...)

Thanks for the feedback everyone, I have taken the use cases to Central Development for consideration. 

I'm not feeling overly encourged as this thread has been open since March 2019. Honestly it seems as if it should be a pretty easy fix.

Like you and other users I know, the Windows 10 version and variant is important to them, but given that Windows 10 was released 5 years ago there has not been any development from LogMeIn to suggest this is even being considered, let alone incorporated into LogMeIn Central...

Fingers crossed that it will be given some consideration soon! 🤞🏻

I second third fourth etc this - seriously? I either have to figure out a powershell script which doesn't really help with remote users OR go into EACH machine to get a build? Seriously....fix this! 

I'm not a PS expert but what about something alond the lines of an if statement to check the version and generate an error if it matches the one you are looking for or if it doesn't match the one your looking for - depending what you're trying to find.

Like I say, no expert but I guess it would go something like this (anyone welcome to change it to actually work and correct my mistakes).

$WinVerCheck = $null;
$WinVerCheck = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").ReleaseId

If ($WinVerCheck -eq 1909)
{
<some command that will not generate an error>
}
Else
{
<some command to generate an error>
}

some simple ideas for a command to make an error and not - a simple "dir" should give no error and maybe trying to delete a fake file would generate an error. e.g. Remove-Item –path c:\nosuchfolder

After this is done, you could check the results for an overview of which failed and succeeded - which ones matched the if statement or not.

I have definitely look into some PS scripts but I guess my point is that this can't be that hard for LMI to add lol! My gosh - it's a field for goodness sake that they do have just not in a report friendly way. 

For sure, it's something that should  be so simple to add. My suggestion is more a workaround than a solution. It would be good to have more response from someone at LMI.

Is there any progress in this report option. This is something we should have it by now. Appreciate the logme in feedback or any timeline.

Agreed, such an obvious thing that MSPs require and yet after over 5 years of Win10 being around, it still doesn't exist.  

The CMD has been broken for months now with no resolution in site

We call Australia customer help line 1800 658 079, stay on hold for hours.

Our license expires this Friday 28/09/20 and we cannot even get in touch to renew it

What the hell has happened to LMI.  Are you going bankrupt

We need someone to get in touch with us.  ASAP.

ezki  I apologize for the support delays.  If you click my Community name you may send over your direct contact info for a support follow up.