View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005492||SUMo||Bug||public||2019-05-21 03:04||2019-09-29 10:59|
|OS||Windows 10||OS Version||1809 64-bit|
|Target Version||Long term|
|Summary||0005492: SUMo cannot add folder for the Windows Admin Center plug-ins to its scanning folders|
|Description||Now its more than 13 months that Microsoft introduced (without announcement) the Windows Admin Center product with its plug-ins comparable to the management consoles introduced 21 years before. SUMo still doesn't seem detecting it even when Microsoft product detection and reporting is enabled in SUMo. Windows Admin Center is for the management of Windows 10, Windows Server 2012 and later, and some infrastructure.|
As long as SUMo doesn't look into all standard locations for such programs, these plug-ins cannot be found. A work-around would be the use of additional folders in SUMo settings as mentioned already in forum post https://www.kcsoftwares.com/forum/viewtopic.php?f=11&t=2927&start=10#p5213. But this is not possible as the additional folders editor of SUMo doesn't allow to specify the usual system folder for these plug-ins which is reported as:
C:\ProgramData\Server Management Experience\Extensions
|Steps To Reproduce||Enable Microsoft product detection and reporting in SUMo,|
open SUMo settings and activate additional folder popup,
activate adding and try finding the plugin folder reported above for adding.
|Additional Information||In default configuration of Windows explorer, system and hidden folders are not shown which can be reconfigured to display also those folders. This root entry for the Windows Admin Center plug-ins is such a folder. It seems that this additional folder editor of SUMo settings has difficulty with this property.|
Not supported because do not hold version info.
OK to close ?
That's not true. They hold version info. In a sample taken now to check your false claim, the same version info is found at several places. It's incorporated into the folder name and in manifest.json. Didn't check other constituent elements.
I made this probe with extension msft.sme.apps-and-features. The corresponding folder name is:
C:\ProgramData\Server Management Experience\Extensions\msft.sme.apps-and-features.1.32.0\
The file manifest.json has these the following strings names and values at its bottom:
So I repest myself how may I configure SUMo to detect and report these version infos with their associated component names?
So version info is present. How may I configure
Yes but the ".msc" hold no information is the same format as .exe, .dll... specific version extraction code is required.
Therefore, not possible to configure SUMo to load it in the current implementation.
This issue has nothing to do with .msc.
On a more abstract level there are similarities indeed requiring some code change. And as reported for .msc, also here version info should be determined not yet at file level but at product level as documented by Microsoft.
And that's normal that bug fixes will change implementation. Scheduling to fix these bugs is your choice and task. Which feedback are you still awaiting?
One aspect I like at Intel Driver and Support Assistant is its display of a web link documenting limitations of kind of drivers not addressed by this tool. Neither HP Support Assistant nor SUMo are so kind to document their current limitations.
|2019-05-21 03:04||wolf||New Issue|
|2019-05-21 03:04||wolf||Tag Attached: options|
|2019-05-21 03:04||wolf||Issue generated from: 0005491|
|2019-05-21 03:04||wolf||Relationship added||related to 0005491|
|2019-05-21 21:52||Kyle_Katarn||Assigned To||=> Kyle_Katarn|
|2019-05-21 21:52||Kyle_Katarn||Status||new => feedback|
|2019-05-21 21:52||Kyle_Katarn||Note Added: 0003360|
|2019-05-22 14:56||wolf||Note Added: 0003365|
|2019-05-22 19:10||Kyle_Katarn||Note Added: 0003370|
|2019-05-22 23:21||wolf||Note Added: 0003379|
|2019-09-29 10:59||Kyle_Katarn||Target Version||=> Long term|