@SenthilNathan , The upgrade would have completed and at the end of the migration, a schema check is performed which failed. However, as ARL version 2624 which has the fix will be available by Monday (16th August), I would recommend that you import this ARL and run the migration scripts again. It should go through without any errors. You can then continue with point 2 in your note above. ... View more

Hi Detria, Based on the screenshots you've shared, the device should have shown up in the TargetedDevices screen. Can you please raise a support ticket and provide these details there? We can investigate further and may request more details which is best managed via support. ... View more

There are no known bugs related to this functionality in 2019 R1. Condition Evaluation.png shows the view that gives us the details on include/exclude conditions or views that are set (global/campaign level). This is available for each campaign, each device. Go to Targeted Devices for that campaign and click on – “Is eligible for alert?” Column for the devices which are part of exclude view and are still getting processed. Another check is the Global precedence settings found in Settings -> Website -> Catalog Behavior -> Ignore Include enforcements if any… should be “enabled” for Exclusion to take precedence. Screenshot - Settings.png Logs in MyApps folder CampaignConditions.log and MyApps_ConditionEvaluation.log also provide more information on the same. There is another log file gets generated under MyApps folder for any given machine during the process and it will be in DEVICE.log format, this will also capture the details of condition evaluation, where DEVICE would be the name of the actual device.     ... View more

Hi, There was an issue detected that caused the upgrade of FlexNet Manager Suite from an older version to 2020 R2 to fail, when the SQL Server version in use is 2017 or later. 'Database Migration for FlexNet Manager Suite 2020 R2.zip' was updated on Dec 17th to address this issue. If the FNMS 2020 R2 system was already setup, there is no changed needed. ... View more

This will be in an upcoming release of the FlexNet Manager. We're currently aiming to address this in the next on-prem release that is tentatively scheduled for December this year. ... View more

The “Creating a Flexera SQL Edition view within Tanium Asset” section in the document refers to a view that needs to be manually created in Tanium Asset, to get SQL Server evidence and not just the edition details. Without this SQL Server recognition itself wouldn’t work correctly. Currently, the edition information received from this Tanium view is not in a format that FlexNet Manager can directly consume to recognize the SQL Server edition. We are planning to make a change in an upcoming release to handle this. ... View more

Hi, TLS is not required for the connection to work. It looks like TLS is enabled on the Tanium end. Could you try disabling it and checking if test connection works? I see this Tanium web page has points mentioned to enable/disable TLS: https://docs.tanium.com/platform_deployment_reference/platform_deployment_reference/tls.html Also, which is the version of Tanium Server being used - 7.3 or 7.4? ... View more

Rob, Steps 8 and 11 related to scheduling and Execute Now are only applicable when the beacon is not co-located. These are not applicable for co-located beacons. This is standard behavior in the beacon for inventory sources including Tanium. I agree that the documentation can highlight these differences, when dealing with steps to follow while working with free-standing versus co-located beacons. I’ve made a note of this. ... View more