This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Community FAQ
Register | Log In
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- General Discussions
- Re: Win10 Anniversary Update recognition
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Register to ask a question, start a topic or share an idea
Join the Community
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2016 10:04 PM
Pretty trivial and no doubt an easy fix, but I just thought that I'd give a heads-up that Win10 1607 is unrecognized by certain widgets, such as "Windows OS/SP Overview." Perhaps they trigger off the build number, which of course changed (10586 to 14393). A surer way might have been to look at the ProductName in the Registry, which is unchanged.
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-03-2016 07:43 PM
I assume development chose the build number because the OS name might not be uniform across language-specific OS releases. I've created a ticket for development to get the new build number implemented, but I'm not sure when a new Lansweeper update will be available.
You can manually resolve the issue by executing the script below in the Configuration\Database Scripts section of the web console. The script adds an entry to tsysOS. Copy and paste the code and hit the Execute SQL Code button. To be safe, back up your database prior to running any scripts. Backup instructions can be found here.
You can manually resolve the issue by executing the script below in the Configuration\Database Scripts section of the web console. The script adds an entry to tsysOS. Copy and paste the code and hit the Execute SQL Code button. To be safe, back up your database prior to running any scripts. Backup instructions can be found here.
INSERT INTO tsysOS(OScode, OSname, Image, Sortorder) VALUES('10.0.14393', 'Win 10', 'ten10.png', 18)
GO
12 REPLIES 12
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2018 05:18 PM
It took a couple years somehow, but:
6.0.230.45:
Added: #591287 A Windows 10 computer's full version and build number are now scanned and displayed in several locations in the web console, e.g. in the Summary tab of the asset page
6.0.230.45:
Added: #591287 A Windows 10 computer's full version and build number are now scanned and displayed in several locations in the web console, e.g. in the Summary tab of the asset page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2016 02:11 AM
Does anyone have any thoughts on the last post?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2016 05:36 PM
Hi. I didn't mean for Insider builds but patch revisions for Win10:
https://support.microsoft.com/en-us/help/12387/windows-10-update-history
That turns up in various places, like winver and the CurrentVersion key in the Registry.
https://support.microsoft.com/en-us/help/12387/windows-10-update-history
That turns up in various places, like winver and the CurrentVersion key in the Registry.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2016 01:18 PM
Windows does not use a segment after that.
You could check the following website for the actual slow/fast/release builds:
http://changewindows.org/overview/desktop
Every 'green' build should be a version included in Lansweeper.
You could check the following website for the actual slow/fast/release builds:
http://changewindows.org/overview/desktop
Every 'green' build should be a version included in Lansweeper.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2016 04:36 PM
Reminded of this now, I wonder if there's a way to get greedy and report the next decimal segment. So, instead of just 10.0.14393, 10.0.14393.105 or whatever.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2016 07:50 AM
Thanks Susan.A for the fix.
I was a bit worried for a while there then the number of klients went down then we started upgrading.
Hope the developers find a solution to automatic add new buildnummer to the database, or something else to fix it.
I was a bit worried for a while there then the number of klients went down then we started upgrading.
Hope the developers find a solution to automatic add new buildnummer to the database, or something else to fix it.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-05-2016 12:45 AM
Thanks. I found this though, which works:
http://www.lansweeper.com/Forum/yaf_postsm44801_Different-versions-of-Windows-10.aspx
http://www.lansweeper.com/Forum/yaf_postsm44801_Different-versions-of-Windows-10.aspx
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2016 11:23 PM
We had a similar requirement in our environment. We ended up scanning this key (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion) and values (BuildLabEx and ReleaseID). We wrote up a custom report to split the reported strings to give us the values we wanted.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2016 08:00 AM
Thanks, that works great.
BTW, do you happen to know if the Windows build number is surfaced anywhere? I'm looking for a way to differentiate the Win10's (14393 vs 10586 etc) in order to see what's been upgraded, but I haven't found it so far.
BTW, do you happen to know if the Windows build number is surfaced anywhere? I'm looking for a way to differentiate the Win10's (14393 vs 10586 etc) in order to see what's been upgraded, but I haven't found it so far.
General Discussions
Find answers to technical questions about Lansweeper.
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now