About dennis_reinhardt

dennis_reinhardt · ‎Jun 14, 2021

Hello all, we have a small challenge with a client and I would like to hear your opinion on this issue. The O365 portal is connected to FNMS via the OOB adapter and provides reliable data. The customer's O365 process currently states that no users will be deleted from the O365 portal, even if they have already left the company and their status in AD or other user sources is Inactive. The background to this is that the data must be retained for a certain period of time due to internal rules, and if a user is reactivated, their O365 files should still be available. O365 Business deletes all files after removing a user after 30 more days (https://docs.microsoft.com/en-us/microsoft-365/business-video/delete-user?view=o365-worldwide). We cannot change these internal processes and they must be taken as a given. Of course, we also import the corresponding user status from the appropriate user sources (AD, IAM, ...) and map this to the Compliance User object in FNMS (Active, Retired, Inactive, ...). The setting of the user status naturally has a direct influence on the license calculation for certain license types, since inactive users are no longer considered for user licenses, for example. Based on the above conditions, we receive from the portal about 157,000 users assigned to corresponding licenses (products) in the O365 portal. The view under "All Licenses" now shows us the following 157,000 users allocated, but only 153,000 users under Consumed. If we look at the table "SoftwareLicenseAllocation", we will find all 157,000 imported users from the portal for the specific license container. If you also compare the user status in the ComplianceUser table, you get about 4000 users with the status inactive, which are no longer taken into account in the compliance calculation for O365. (see tip box: https://docs.flexera.com/FlexNetManagerSuite2020R2/EN/WebHelp/index.html#topics/Allocated-LicProp.html) As we all know, a user assigned in the O365 portal first consumes a license regardless of its status in, for example, Azure AD. The rule is: Assigned = license consumption. Now my question to the community, do you have this challenge in your companies or clients as well, if so - how do you deal with it? Otherwise, I would appreciate any advice on how to properly map O365 compliance in FNMS in connection with inactive FNMS users but assigned O365 portal users. And no, we can't just reactivate the O365 users in FNMS! 🙂 Best, Dennis

dennis_reinhardt · ‎Jun 07, 2021

System information: FNMS 2020 R2 incl. Analytics (On-Premise) 4 tier architecture (Web, Processing, DB, Analytics Server) FNMS uses SAML for authentication via customer's own IDP ------------ We are looking for colleagues who already have experience with the connection of SAML to Analytics for authentication, since we are unfortunately not successful with the documents from the documentation. For SAML and FNMS the documentation is very good and the configuration is comprehensible. For the setup of SAML in connection with Cognos Analytics, there is unfortunately only a hint that you select the SAML Authenticaton in the "Flexera Report Designer Package Import Utility" and update the configuration. Unfortunately we lack transparency what is happening in the background now? When setting up FNMS and SAML, an XML had to be exchanged with the IDP and the corresponding configuration had to be done in webui.config (kento.auth) - all this does not seem to be necessary with Analytics - but how should Cognos then communicate with the SAML IDP? Thanks for your support and greetings, Dennis

dennis_reinhardt · ‎Jan 20, 2021

Hi @rwiltshire I would recommend a tiered approach to beacons. If possible, then operate a central beacon within the GCP and all agents report their data to it. The central GCP beacon is then connected to your DMZ or intranet beacon via only one necessary firewall rule. A normal configuration. When it comes to agent deployment, I think it depends on how dynamic your environment is. If VMs are only active for a short time and then deleted again, then the results of the inventory may be wrong and have an impact on your balance. Here I would recommend a solution like the AWS/Azure Connector. On the one hand, the inventories are determined by the agent (agent in the template incl. first start after deployment) and, on the other hand, the infrastructure data (status of the VMs, similar to the vCenter Adapter) is determined. Based on this information, inventories that are no longer in the structure are cleaned up. You can find more information about the procedure in the documentation. https://docs.flexera.com/FlexNetManagerSuite2020R2/EN/InvAdapConn/index.html#adapters/Azure/topics/Azure-AgentInventoryExInst.html Terminated instances are a special case. 1.Before termination, the running instance may have had an inventory device record (provided that it was reporting inventory). 2. When you terminate the instance, Microsoft Azure keeps the terminated instance visible through the API for about an hour, and if you have implemented your Azure PowerShell connector on an inventory beacon with the default 30 minute schedule, the termination is imported through the connector, and the record in the CloudServiceInstance table is updated with the terminated status. (This record, with its terminated status, is visible in the Cloud Service Provider Inventory page, if you set the filters on that page appropriately.) 3. At the next full inventory import (by default, overnight, immediately before the license compliance calculations), any inventory device record linked to a terminated instance is deleted, because you do not want terminated instances consuming from your licenses. 4. Of course, the terminated instance no longer reports inventory; but its previously-recorded inventory is still in the inventory database (and in normal processes is not cleaned up for a while). Although the next full import (typically the next night) normally imports records from the inventory database, for terminated instances this is prevented by the terminated flag in the CloudServiceInstance table. This prevents the deleted inventory device record from reappearing. Best, Dennis

dennis_reinhardt · ‎Nov 09, 2020

Hi, this function/feature was added in the June 2020 cloud release (https://docs.flexera.com/fnms/EN/features/index.html#FeatureList/2020R1/RN-chg-UseForMatchingReq.html) Check page 209 in the BAS manual so get detailed information about the "UsedForMatching" Checkbox (https://docs.flexera.com/fnms/EN/WebHelp/PDF%20Documents/Cloud/UsingFlexNetBusinessAdapters.pdf) You've to define one or more values to identifiy the object in the database to update object data. Best, Dennis

dennis_reinhardt · ‎Oct 07, 2020

Hi Community, by default a unix agent uses the following path "/var/opt/managesoft/etc/ssl/cert.pem" to check for SSL certificates. We would like to switch over from a dedicated file deployed via "mgsft_rollout_cert" to a certificate path where the Unix admin will maintain all certificated in a global way (based on the recommendations by Flexera, name of the file, ...). https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/PMD-SSLCACertificateFile.html Is it sufficient to specify the parameters for the SSLCACertificatePath via mgsconfig and the agent will look into the second location too? /opt/managesoft/bin/ mgsconfig -i /var/tmp/tempconfig.ini tempconfig.ini [ManageSoft\Common\CurrentVersion] SSLCACertificateFile=/opt/global_cert/cert-xxx.pem Thanks and Best, Dennis

dennis_reinhardt · ‎Oct 07, 2020

Hi @Vishal I would say yes, because the agent uses the ping only to prioritize the possible beacons (https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/NetSel-SuppliedAlgors.html). If the ping fails, the beacon will only get a lower priority, but will still be used. Decisive is only whether the agent can reach/resolve the URL "https://Server-FQDN/ManageSoftRL". Just try it and post the logs in case of problems (C:\Windows\Temp\ManageSoft) Best, Dennis

dennis_reinhardt · ‎Oct 07, 2020

Hi @bmaudlin could you please post some log file of a fresh installed agent running into this issue? C:\Windows\Temp\ManageSoft ... (Installation.log, upload.log) an your mgssetup.ini. Thanks and Best, Dennis

dennis_reinhardt · ‎Oct 07, 2020

Hi @rclark0 detailed information for Unix and Windows can be found here: https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/tasks/FA3-CustomUNIXSetup.html https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/tasks/FA3-CustomSetupIni.html If you miss any information, let us know and we'll answer your questions in this post. Best, Dennis

dennis_reinhardt · ‎Oct 07, 2020

Hi @JonStrong , as @kclausen said, there is only a new agent version with every release change. As an alternative you could check the following sources to see if a new version is available there. Personally, I think it is a bit "over the top", because normally in the context of an FNMS update you should establish a process which should look at the agent update process on the different sources. On each Beacon you can find the latest packages in this folder: "C:\ProgramDate\Flexera Software\Staging\Common\Packages\Flexera\Adoption" or check the database table "SELECT * FROM AvailablePackage" for the latest version. Best, Dennis

dennis_reinhardt · ‎Oct 05, 2020

based on the recommendation (for testing only) of @adrian_ritz1 , here are the necessary commands. ndtrack.exe -t machine -o Upload=True -o UploadLocation=https://server/ManageSoftRL -o CheckServerCertificate="False" -o CheckCertificateRevocation="False" Please also check that the complete certificate chain of the beacon server can be resolved by the agent and/or that the certificates are available in the store. Best, Dennis

dennis_reinhardt · ‎Oct 02, 2020

Hi, problem solved after running a normalization job. Unfortunately, the behavior is a bit confusing, because you expect the reports to be available immediately after the updat. Best, Dennis

dennis_reinhardt · ‎Oct 01, 2020

Hi Teamand & community we've updated to the latest release of DP AC/UC v5.5.33, but I'm missing the mentioned 9 new interactive reports. (http://docs.bdna.com/patchset/RN_5.5.33_UC.pdf, Change ID 32789). Have any of you already installed the update and can see these reports? For example, if you search for "Sprawl", only the "Technology Sprawl KPI Dashboard" report will appear. Thanks and Best, Dennis

dennis_reinhardt · ‎Sep 26, 2020

Hi, last week we've updated the customer system up to 2020 R1 On-Prem and the issue is now gone. Best, Dennis

dennis_reinhardt · ‎Aug 19, 2020

Hi @EHacking depending on your settings in "Inventory data". We've set "FlexNet Manager Suite" as primary (should be default) and fine with the results https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/WebHelp/index.html#topics/Sys-DataInputsInvTab.html The primary connection has priority for the import of hardware inventory. Any non-null value from the primary connection cannot be over-written by conflicting data from any secondary source, even if the secondary source was imported more recently. For values that are null (not reported) in the primary connection, secondary connections can provide data, with the most recent secondary import taking priority for this. (The primary connection setting has no effect on the import of software inventory.)

dennis_reinhardt · ‎Aug 16, 2020

Hi @gotqcorp , based on the structure of FNMS subnets, you should do the following steps 1. Create a new site nodes based on the required data for the SP "EXEC SitePutBatchByName" 2. Add IP subents to sites creates in step 1, using the SP "EXEC SiteSubnetPutBatchByIPSubnetIPSubnetBitsSiteID" 3. Assign IP subnets created in step 2 to beacon assignment, using the SP "EXEC BeaconSiteSubnetMappingPutBatchByBeaconIDSubnetID" Best, Dennis

Online Status	Online
Date Last Visited	‎Jun 16, 2021 03:05 AM

Management of O365 user license allocations when ComplianceUser is Inactive but assigned in O365 por...

(FNMS 2020 R2) How to setup/use Cognos Analytics with SAML authentication

Re: Google Cloud and FNMS

Re: Import failed. Error: UseForMatching, must be set for the following objects: [Asset].

Unix Agent (standard deployment) - how to use SSLCACertificatePath

Re: Sending inventory to beacon where ICMP is disabled

Re: Agent install not applying the configuration correctly

Re: mgssetup.ini setup

Re: Automating agent download for third-party install

Re: Zero footprint Inventory not uploading through HTTPS

Re: Missing new interactive reports under Report Management (UC 5.5.33)

Missing new interactive reports under Report Management (UC 5.5.33)

Re: Beacon - Discovery & Inventory Rule - "Calculating NMAP range strings" took 30 minutes in Discov...

Re: Which inventory is king? Flexera Agent or SCCM?

Re: Can subnet be registered through SQL Query directly?