Thank you ... View more

I completely agree that the best approach would be to do a migration of the OS instead of an in-place upgrade, and doing a clean install of FNMS on the new server. Doing this would also allow you to keep FNMS up and running, and could remain running if any issues were faced in the migration.  ... View more

As documented by Google, Chrome can use two alternative ways for registering an extension: Using the Windows registry (for Windows only) Using a preferences JSON file (for Mac OS X and Linux only) For Windows, you can use the "IncludeRegistryKey" option for the Flexera Agent for collecting the additional evidence from the HKLM\Software\Wow6432Node\Google\Chrome\Extensions branch in Registry. For non-Windows computers, make sure that the paths where the JSON files are stored (/usr/share/google-chrome/extensions/, /opt/google/chrome/extensions/) are included in the list of folders to be scanned by the Flexera agent. You can use the "IncludeExtension" option for the Flexera agent to make sure that .json is added to the default list of file name extensions to be reported. As Google Chrome extensions are not contained in the Flexera ARL (yet), you will have to create these extensions as local applications in FNMS and link these applications to the additional file evidence collected by the Flexera agent. ... View more

It calculated the users. Thanks! ... View more

Thank you for the details. Will see what we have to do to make it working. I can see in FNMS the information of employee ID and cost center under all users.  The correct product name is :  FlexNet Manager Suite Cloud Production ... View more

 Hi @JohnSorensenDK , Appreciate your inputs, already raised a service request and its been 40days.   Regards, winvarma ... View more

Thank you for all of your help. ... View more

SSO is what they should be using but it's sort of an odd situation where SSO likely won't help here. But I'll pass along the suggestion of the local account on the App server, citing the fact it will circumvent corporate security policies, and see if it works for them (they'd allow the exception).   Appreciate the suggestions @erwinlindemann @mfranz . ... View more

Hi @kyle_wolff  In the URL https://helpnet.flexerasoftware.com/fnms/EN/WebHelp/index.html#topics/FIB-PortsAndURLs.html in Ref #2 and Ref #5 it does list the digicert URLs we use for the CRLs. Are you able to confirm what other URLs are needed going forward and I can pass that on to our documentation team. Thanks in advance. ... View more

Hi Abhilash, The reason why you are getting more users from the MGSBI Active Directory adapter compared to  the standard Active Director (AD) interface most likely is the 'User Blacklist' used for filtering users in the standard AD interface. You can see the list of black-listed user names in the FNMS Web UI under "(cogs) > System Settings > Users". This list contains account names available on any Windows computer, like 'Administrator' and 'Guest'. The list also contains generic accounts using the percent sign ('%') as a wildcard. You don't want these standard accounts to be counted as real users. In case you want to check the list of  AD users imported by your Business Adapter for Windows accounts to be filtered, you can run the following SQL statement on the staging table where you store users:  SELECT     [ComplianceUserID]    ,[UserName]    ,[SAMAccountName] FROM [ComplianceUser] cu LEFT JOIN [ComplianceDomain] cd ON cd.ComplianceDomainID = cu.ComplianceDomainID WHERE EXISTS (    SELECT 'x'    FROM [UserNameBlacklist] unb    WHERE cu.SAMAccountName LIKE unb.UserName      OR (cd.FlatName IS NOT NULL              AND (cd.FlatName + '\' + cu.SAMAccountName LIKE unb.UserName)) ) This statement assumes that you did import the users into tables named [ComplianceUser] and [ComplianceDomain] built like the original tables in the [FNMSCompliance] database, and that you have the black-listed users stored in a column [UserName] in a table named [UserNameBlacklist]. A quick word of warning: Be careful when replacing the FNMS standard Active Director (AD) interface by a Business Importer. The import process (compliance reader) relies on the standard [FNMSInventory].[ADUser] table being populated by the Active Director (AD) interface. Any users not found in the standard user table will be deleted from the users visible in the FNMS Web UI (stored in the [FNMSCompliance].[ComplianceUser] table) when running a compliance import. Customizing the SQL code used in the compliance import (READERs and WRITERs) might be an option when working in an FNMS on-premises environment. You don't have that option when working in the Cloud. The best practice approach for populating user data in FNMS would be: Use the standard Active Director (AD) interface for importing users from AD. This interface will import the "Full name"", Account name" and "Domain name" user properties only. Use a Business Adapter for augmenting the user information imported from AD with additional user properties, like "First Name", "Last Name" and "Email". ... View more

I think that attempting to create a Custom Field and maintaining it with a list of every UserID is not something that can realistically be maintained and would not be scalable. I think that at present, the best you can do is to create a custom 'Audit Report' that lists all of the current values entered into this Custom Field and then compare this to the list of active Users.  For FNMS On-Premises, this would be possible in SQL, and for FNMS Cloud would be a bit more of a manual process. ... View more

Hi Steve, Adding "%!%" in the [UserNameBlacklist] table should prevent users having an exclamation mark in their user name from being imported into FNMS. Here are the boring technical details: All Active Directory users stored in the the [FNMSInventory].[ADUser] table will be imported by the READER into the [FNMSCompliance].[ImportedUser] table. However, the [FNMSCompliance].[ImportedUser] will be filtered using the [UserNameBlacklist] by the WRITER when data are copied into [FNMSCompliance].[ComplianceUser]. Please note that users that have been imported into the [ComplianceUser] table already will not be removed after the [UserNameBlacklist] table has been updated. You must manually delete these users from [FNMSCompliance].[ComplianceUser], make sure that the [UserNameBlacklist] is updated to prevent further imports of the users having an exclamation mark in their name and then and run a new ComplianceImport. ... View more

Hi David, Under "Reports > License Compliance > Applications", there is a standard report named "Device Installation Details" that allows listing all applications installed on a single Inventory only. You can create a custom report from the FNMS Web UI that allows listing applications installed on multiple Inventories. In the "Report Builder", combine the "Inventory Device" object with the "Installations" object. For the "Installations" object, I remove the "Inventory Device Name" property (as this would be listed twice). From the "Application" object, feel free to add additional properties like "Edition" or "Classification". In the subsequent "Preview and Filter" dialog, you can re-arrange the columns as needed (see attached screen shots). After giving your report a name and saving it, you can use the "global search" feature in the report, or use an advanced filter for filtering on multiple device names in the "Inventory device name" column.   ... View more