ContributionsMost RecentMost LikesSolutionsRe: Change user password as Administrator 9 years later. NINE! And they still haven't been able to put in a function to let an admin reset a user password. Literally one of the most basic functions of any user admin system, and in nine years LMI could not be bothered to amend this issue. I would say I was surprised, but with LMI, no shortcoming of the software surprises me. Re: Windows OS Version and Build Number in LogMeIn Central It really is. I don't want to scale down. I don't want to switch products. We all know what a pain in the backside that is. Starting all over, getting a new vendor, and then hoping they weren't selling you a lot of false promises. I would much rather they just fix this. I bet a lot of us are programmers here, and we're not so easily fooled about how long something takes. A good programming team could pump out a corrected inventory system in a week, a couple of weeks tops if we're doing a paranoid level of bug checking. Which, let's face it, this is LMI, so no bug checking is going to happen. So, yeah, a week or so. Re: Windows OS Version and Build Number in LogMeIn Central You would be wise for not holding your breath. LogMeIn has managed to keep some bugs going since I started using the product at 2016. At this point, you'd actually have to put work into maintaining some of these bugs that long. They have your money, what do they are about improvements. Until someone comes along who's a legit competitor to them, you're not going to get squat. TeamViewer, while simpler (and better), in some ways, is twice as much money, with a lot less functionality. Frankly. I would take less functionality for more improvements in what we already have that can only be considered "working" by only the most charitable of evaluations. Re: Updates I have this exact same issue, STILL. And it looks like variations of this go back to at least 2014. It makes trusting LogMeIn for update information useless. All the warnings are useless since I can't trust them to be accurate or not. I get messages about updates that cannot be applied, do not need to be applied, or that have already been applied, days, weeks, or months ago. Almost every single machine in my organization is listed as needing updates that Windows itself says it doesn't need. Re: Windows OS Version and Build Number in LogMeIn Central It's been a top request for two years and three months. I don't think "top request" means what they think it means.... Re: Windows OS Version and Build Number in LogMeIn Central 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. Re: Windows OS Version and Build Number in LogMeIn Central I'll certainly agree to that. Central has a lot of great features, but it's very frustrating that this one little thing, they haven't managed to add in, what putting a lot of features I'll never use. Re: Windows OS Version and Build Number in LogMeIn Central Can it really be that this is so hard to do that three years later, this issue still hasn't been resolved?