A new Flexera Community experience is coming on November 25th. Click here for more information.
When you are using IT Asset Management, at this stage you may need to approach beacon (re-)configuration a bit differently.
2. If you only have credentials for IT Assets (app.flexera.com or app.flexera.eu), then for now you need to perform beacon configuration starting from Flexera One web UI (and not from the beacon application user interface):
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\BeaconUID
On the Beacon Server, go to the Windows Start menu. Find the Flexera Beacon application and launch it. Be patient while it loads. You will be on the Parent Connection page.
Browse to the location of the downloaded configuration file and select it. The beacon will import the configuration file and attempt to establish secure communication to Flexera One.
on Mar 01, 2021 01:29 AM - edited on Aug 26, 2021 02:44 PM by AustinG
Good day Flexera,
please confirm beacon connection requirements for current EU instance FNMS Cloud users.
Current beacon configuration is :
Beacon | beacon.flexnetmanager.eu | 18.156.184.224 3.123.233.63 3.121.138.111 |
Inventory | data.flexnetmanager.eu | 3.126.23.8 18.197.197.2 3.127.78.223 |
Presentation - Web UI | Dynamic |
Flexera One documentation only shows:
Flexera One web page access | https://app.flexera.com (standard port 443) |
FlexNet Beacon endpoint (for uploads) | |
Performance and reliability monitoring | |
Certificate revocation checks (standard port 80) |
what is the requirements here, are we now pointing to new endpoints? will the current EU links still work or do they change?
this impacts customers where upload links outside of the estate needs cloud and risk approval that takes a long time.
Hi @tertiusd,
There is currently no change to endpoints for FNMS (IT Assets) beacons.
The documentation you are referring to is only specifically related to IT Visibility beacons, not beacons that are used with FNMS (IT Assets). We will change documentation to highlight the difference.
The KB is related only to the fact that any customers that do configuration of beacons in IT Assets, may need to initiate the configuration from the web UI (and not the beacon) in case if they do not have credentials with agw/login. Other than that there is absolutely no impact on beacons and no change to current endpoints
Thank you,
Elvira Kan.
thank you Elvira,
and the Current FNMS API used for App Portal on-prem and admin studio? used to collect MGS ID's and do license availability checks?
does this stay the same or will we see any impact on the URL changes?
example current would be http://customer.flexnetmanager.eu/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx