Hi @winvarma  So I'm guessing that there is not two beacons in place? As my understanding is in terms of the Cloud solution at least it is recommended for at least two beacons to be in place: So one that connects to the Flexera cloud with the necessary TLS requirement in place, and a second beacon to which collects the inventory data from the agent which doesn't require TLS which sends its data to the beacon that connects to the FLexera cloud. Ben   ... View more

Hey, So to confirm that when the logs were verified the agent is trying to connect to the beacon, and the default configuration is not being used. If the default configuration is being used - it looks something like this: Thu Jul 11 13:08:35 2019 (N, 2)] {12120} Prioritizing download servers [Thu Jul 11 13:08:35 2019 (N, 2)] {12120} Starting to prioritize servers from "HKLM\Software\ManageSoft Corp\ManageSoft\Common\DownloadSettings" [Thu Jul 11 13:08:35 2019 (N, 2)] {12120} Applying prioritization algorithm "MgsRandom" with parameters "" [Thu Jul 11 13:08:35 2019 (N, 2)] {12120} Applying prioritization algorithm "MgsPing" with parameters "" [Thu Jul 11 13:08:35 2019 (N, 2)] {12120} Applying prioritization algorithm "MgsADSiteMatch" with parameters "" [Thu Jul 11 13:08:35 2019 (N, 2)] {12120} SelectorAlgorithm "MgsADSiteMatch" could not be loaded [Thu Jul 11 13:08:35 2019 (N, 2)] {12120} ERROR: Could not successfully prioritize servers [Thu Jul 11 13:08:36 2019 (G, 0)] {12120}   Can you also confirm which server os version you're running on the Flexera beacon, at a guess I'm guessing that Windows 7 by default has TLS switched off, and Windows Server 2012 or newer has TLS switched on by default. Please note: TLS is different to SSL and requiring the agent to communicate on port 443 rather than 80. With the manual policy download are you trying to run that via command prompt? As for this testing I would test either using Windows or cmd line but just using the following parameters - mgspolicy -t machine Ben ... View more

Hey, In the agent logs, on the installer.log file can you confirm the agent is trying to connect to the correct FQDN to download the FNMS policy? As if all other checks are working, it may be an issue with the configuration file. Ben     ... View more

In terms of workaround - there is a number of options - and depending what the environment stipulates is also a factor: Switch on TLS 1.1/.2 for 2008R2 Servers - however this will not solve the issue on 2003/2008. Switch TLS off on the inventory beacon for client connections - im guessing here there is at least two beacons (inventory and master) Enable a second beacon that does not have the requirement for TLS - however the agent configuration will have to differ for these versions  Decomm the older servers - remove the problem that way 🙂   ... View more

Hi Markward, Are you able to complete those tasks on a Cloud based environment, as my understanding was you couldn't. Ben ... View more

This is typically the behaviour experienced in either: Necessary firewalling hasn't been completed from Agent to Inventory server Or more likely as its Windows 2012 and lower TLS 1.1/.2 has not been enabled on the servers to be inventoried by the agent.  As on 2008R2 it is switched off by default, on lower so 2008 or 2003 it cannot be enabled.    ... View more

Hi Vinod, I'm currently on the EU Cloud environment and we have about 35k workstations and 5k servers reporting in - and rollout is still ongoing. (I'm not sure where you are in your Flexera journey.) We also do not just ingest the agent data, we also do connect into multiple data sources. On average, a reconcile takes about 3 hours, however I have noticed the following behaviours: *If a mass deployment of the agent goes out, reconciliation takes far longer. For example the end of last week we rolled out 5k agents overnight to one of our environments this reconciliation then took about 8 hours. * We use unique naming conventions for our packaged software, so we manually match the evidence to the application. Again when completing a high number of tasks, reconciliation normally takes longer. *Once the above is completed, reconciliation times return. In terms of performance I have not noticed any performance degradation to the end users when running the reconciliation. That said, I have certainly noticed a performance in FNMS on our corporate network (slow) to my own internet connection (super fast.) So that could be worth a try. Ben ... View more

Hello, We're also still awaiting an update on the root cause. Is this something you're able to provide @KPBussey ? Ben ... View more

Hello, Performance has returned, and there is less errors - so thank you. However, I am still facing an error when navigating to this page: https://aviva.flexnetmanager.eu/Suite/Locations/List And trying to add an additional location presents this error; An error has occurred while retrieving information; you may need to refresh the page. Error ID: d59d802a-d4c7-4555-9d00-b41f48225fdd   ... View more

Hello, Since the status update, that the platform is fixed, I am still experiencing the same issues and I have raised call 01887086 to track the problem. Ben ... View more

Also seeing errors such as this, when navigating to a number of pages: An error has occurred while retrieving information; you may need to refresh the page. Error ID: b5f3413a-8f54-4b9f-87eb-d52623253a53 ... View more

Hello, I am still having issues with page turn speed, and pages simply timing out. In terms of impact, the system has been intermittent since 8am ... View more