HI, not sure when the beta enhancement page will be available to all again. This way going back to the old way of communicate. We have the problem that we installed the Daemon to perform scheduled reports. That is a great option. But we want to export the data e. g. weekly or monthly and keep the previous version. The export option does not support any wildcards in the file name e. g. DD-MM-YYYY or anything which would have a fixed value and a dynamic value. This way we can run the same export scheduled without override on our export source. We end up now to have a scheduled task to move data away which is annoying. Regards Lukas ... View more

We have a security requirement to monitor EOL products more closely. As in general EOL or discontinued could be classified as unsecure from that point as vendors don't patch anything anymore. We would like to be able to build Product Smart groups based on when they become the status of EOL or discontinued. EOL - over 14 days high or above EOL- within 14 days high or above EOL- within 14 days medium or Lower EOL - over 14 days Medium or lower I've use SAID creation date as trigger. Support confirmed this does not work as Secunia do not post SAID or Criticality ratings for EOL or discontinued. This way we have no way to use the data we have and easy monitor changes in the out of the box "End-of-Life-Products" product smart group. This is really annoying as we can't meet our security team requirements and then end up again to compile this manual vs vendors pages constantly. ... View more

Our WSUS is bypassed and management is only in SCCM. Are you planning any changes in this area as well ?   cheers Lukas ... View more

Dear Support, I will try to explain an issue. If you have devices random failing on completed scans with various errors. The completed scan shows you an high level error. There is zero details behind this message like Partial, Failed Communication etc.   The technical Problem is if you want to debug the only way is to enable the logging with -v or -v -v or -v -v -v depending on the needs. The issue is that if you set it: 1. service need to restart to pick it up 2. it stay forever or you have to roll it back per device or device group 3. it contain too much info potentially which is required only for debug troubleshooting when you know what a high level issue might be.   It would really help if there would be in settings or on per device level where you can turn on logging temporary only or for a timeframe of xy days.   On top of that instead of showing only an error in completed scans. It would be much better if there was a reason code (which is happening anyway on each device when issue appears) been written to the error as an own column or to an additional SQL table. For example the communication could mean a lot. But if we could have this data captured with a reason code we could export, pivot and troubleshoot on the most common problem.   Today, you have to do it all manual with client logging enable which is on high scale of devices like impossible. Specially when an issue is random and can't be reproduced this option isn't ideal as you would need to turn on logging on all devices and then grap manual from each device the log file and then clean it afterwards.   I hope it make sense but this would make our life much easier. Lukas ... View more

Dear Support, we would like to be able to monitor devices for their integration with scans. There is today technically no way to generate a host smart group which can filter by "Scan status" from "Completed Scans" section. The only way is to export and filter in Excel or PowerBI.   We would like pro-active to have smart groups where we can combine devices which does not have a "succes: OK" state of our configuration and been able to report/export those data for monitoring reasons. E. g. one off issues, dedicated sites, offices or devices issues to send data back.   Technically filter by "Scan Status: "Success: OK" "Failed:  Communication Error" "Failed: Resolving Host" "partial: Windows Update failed"   and on top to above then "Results Exist" or not to narrow down further on those devices which have issues.   Regards Lukas     ... View more

Dear Team, the SVM solution is today only reactive view of data sets scanned of the devices. We end up quite often that a software become secure/unsecure and switch to EOL or product discontinued. This way technically the company become unsecure as no patches anymore without a pre-warning. It would be nice to have an different column or header or an smart group which warns us using SVM when a product reach end of life. This information is known and published by most vendors. Like this happens with Windows 7. I assume all should know the last security patches next year. But for some it might be a surprise in Jan 2020 🙂 The same apply to all other vendors or products. It would help to make your product better and allow customers pro active to do work vs reacting all the time only. Lukas ... View more

It would be great if the Product Smart group for OS e. g. Windows 10 would show per device more detailed information. At the moment post scan it only shows e. g. "Windows 10 Enterprise, WinNT, Terminal Server 16299 This data are kind useless for us. This number only indicate if this is e. g. 1709, 1809 etc OS version. @docs.microsoft.com/en-us/windows/release-information/ If a scan was run on the device and SVM shows as secure. I have no idea if this is valid or not. The only way to narrow this down would be to show 17763.864 instead as shown in MS table. This way we know 100% that your scan patch level is latest November MS CU patch level: KB 4523205 This information already exist as basic stuff on each Windows 10 device and are shown to the user under system. The SVM scan is able to show missing hotfixes but for "secure" device we have no chance to know the latest KB install which state it is secure. This way we have to go back to last scan data and then again go back to SCCM to check this. This way the view of this is for us not useful and can't be a valid source for dashboards. We have already to export all hosts from this smart group to generate a Pivot table. Just our security team don't accept this data set as it is not visible on the time of export creation what is the real patch level of the device (as scan could be 1 day, 2 weeks, 1 month etc last time done). Can this be added going forward to help us to properly audit security for the OS? REgards Lukas     ... View more

We are deploying apps via SCCM applications and SCCM AppV. There is at the moment not way to see in SVM product groups a split between both apps technologies. There is also no way to create an own product group to filter by them either deployment technology/product or/and based on a logic like path contains C:\ProgramData\AppV. The issue is that we see products with both deployments been always combined into one product. We have then always to run an export of the data and split between virtual packaged update required vs physical installs. This way to build deployment collections is also more hard and complicated. Could we add a way to display them differently or any kind of filtering option to be able to split them to avoid constantly export as csv and then back to Excel and Pivot? ... View more

We have similar issue then with Office. Microsoft offers different servicing channels with Window 10. Then inside of this channels like "Win10 Enterprise" they have versions like 1709, 1809 etc. The Product Smart group only shows Win10 and then inside a version numbering logic for each host. This data give you then secure/non secure/EOL. The problem is that as company you have different set of users on different channels to allow a pre-business view before it hits our users. To get  a proper view in SVM to see how many devices in each channel are secure/non secure I have every month to export your data, load to Excel, run painful Pivot with numbering mapping from MS page to get an overview in granular view: - Channel - version - secure/non secure / EOL docs.microsoft.com/en-us/windows/deployment/update/waas-overview docs.microsoft.com/en-us/windows/release-information/   This is all manual and end up to use SCCM to show this information instead of SVM for what we paid for to have this add-hoc view with detailed information. There must be a way to improve this 🙂 ... View more

We have the problem that this described Office 365 Changes are for our usage not helpful. https://community.flexera.com/t5/Software-Vulnerability-Manager/Handling-of-Office-365-quot-Click-2-Run-quot-versions-in-SVM/ta-p/4882 The issue is that SVM combine the whole suite or each product like Excel in one large set. This way. I end up to see for example Excel 2019 /Office 365 with secure/unsecure / EOL. That view is really miss leading. There a few factors which are missing here. 1. Microsoft have four channels Monthly, Semi-Annual, Semi-Annual Targeted, Inside Program. docs.microsoft.com/en-gb/officeupdates/update-history-office365-proplus-by-date That way I see one large view of Office 365. In our company we have sets of users on different channels. This way each channel is for us technically an own "product" as it delivers other functionality/updates in each.   2. Microsoft have inside of the channels Versions like in in Semi-Annual 1808 + 1902 are in support. We have early adaptors and then are on 1902 and majority e. g. on 1808. The issue is then again like above one large set together combined.   What I have todo today to get a real view of our estate. I have to export each product into Excel. Then go to MS page, filter by version number which product is which channel assigned. Then inside channel see which is secure/non secure. Post that create manual dashboards to make it visible to Management which channels/versions are secure or not globally in our environment. This is a lot of work. We have then to check in our SCCM/WSUS why xy device wasn't patched. But due of the different combinations been in one "pocket" combined the date are at the end not usefull for us today as we have heavy to manipulate them to get out of SVM what we want = - each channel and version of product secure/non secure/EOL Lukas ... View more