About jevans

jevans · ‎Aug 05, 2022

To find vCenter device names, the FlexNet Beacon's remote VMware inventory process locates all licenses associated with a vCenter server. It then populates the names of any linked devices from the licenses found as vCenter device names. The names retrieved from the licenses may not match the device hostnames. People commonly enter default names like "vcenterserver" into the license information – this name is then reflected in FlexNet Manager Suite or Flexera One IT Asset Management. To find vCenter device names In vCenter's vSphere web UI, you can find vCenter device names in: vCenter Web Console > Menu/Home > Administration > Licenses > Asset. In the Asset list, you’ll find the vCenter device name that matches what’s reported in FlexNet Manager Suite or Flexera One IT Asset Management. To manually go through the steps the FlexNet inventory beacon would take to query the API: 1. In a browser on your beacon, navigate to https://VCenterIPAddress/mob and enter your VMware or Service Account credentials. 2. In the Properties section, click on the content link. 3. Select the LicenseManager link located next to ManagedObjectReference:LicenseManager. 4. Select the LicenseManager link located next to ManagedObjectReference:LicenseAssignmentManager. 5. Select the QueryAssignedLicenses link located next to LicenseAssignmentManagerLicenseAssignment[]. 6. Click on the Invoke Method link. The vCenter name listed here matches the value in FlexNet Manager Suite or Flexera One IT Asset Management. Note: For more details on the VMware API in use by our beacon process, see VMware's API documentation.

jevans · ‎Jul 25, 2022

FlexNet inventory agent's full NDI file reports Oracle Universal Installer (OUI) evidence, including the Oracle product edition, though the edition isn't reported in the comps.xml file corresponding to the installation. Instead, the FlexNet inventory agent creates mapping in the Windows registry between Oracle home and Oracle Database editions to identify and report the product edition. Example The below extract from a FlexNet inventory agent NDI file shows the reported OUI data for an Oracle Database installation, with the edition populated. <Package Name="Oracle Database 19c Standard" Evidence="OUI" Version="19.0.0.0.0" InstallDate="YYYYMMDDTHHMMSS"> <Property Name="InstallLocation" Value="C:\oracle\product\19c\db_home\oracle.server"/> <Property Name="Publisher" Value="Oracle Corporation"/> </Package> Information about the edition is gathered from the Windows registry. In the Windows registry, there are several keys labeled key__ in the below paths: HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ORACLE Each key has an ORACLE_HOME value and an ORACLE_BUNDLE_NAME. The FlexNet inventory agent uses the link between Oracle home (ORACLE_HOME) and product editions (ORACLE_BUNDLE_NAME) to identify which Oracle Database edition the OUI data is linked to. When the Oracle home OUI evidence matches an ORACLE_HOME value in the registry paths above, the FlexNet inventory agent populates the product edition.

jevans · ‎May 24, 2022

Good afternoon Markward, I hope your week's going well? I'd advise raising this with Support to confirm. I've taken a look through the code for the SCCM Reader, and I can see this change was made during the Obsolete Inventory changes in 2019R2.2 / 2020R1 (On-Premises). It's not explicitly commented as an intentional change, so to be sure we can query this with our Product Engineering team. I agree with your reasoning behind what should be happening here - if there's a record present in Known (AKA already present in the FNMS/ITAM DB), but not Computer_System_Data, I would assume this should be flagged as Deleted. The ELSE condition here is also checking whether its' obsolete or not on the SCCM DB. Kind regards and thanks, Jack Flexera Support

jevans · ‎May 23, 2022

Hi Bleepie, I hope your week's going well? Thanks for reaching out on the forum here! Particularly for the scenarios you mention - where a customer's querying what data should be populated, or the logic behind FNMS behaviour - I found the Online Help invaluable when starting out as a Support Engineer. This is contextual, so you can hit the Help icon wherever you are in the FNMS Web UI to open a related Help page. We also have it as its' own separate link on the docs.flexera.com page - here's the 2022R1 version: https://docs.flexera.com/FlexNetManagerSuite2022R1/EN/WebHelp/index.html Of particular use is pages like All Licenses, where it shows all possible fields and potential values, along with a descriptor of what these fields show: https://docs.flexera.com/FlexNetManagerSuite2022R1/EN/WebHelp/index.html#topics/AllLicences.html Or if one of your customers asks for the logic behind FNMS License Consumption, there's a Glossary page for each License Type with insight on how these values are calculated: https://docs.flexera.com/FlexNetManagerSuite2022R1/EN/WebHelp/index.html#glossaries/licType_NamedUser.html I hope that helps! Kind regards and thanks Jack Flexera Support

jevans · ‎May 23, 2022

Good afternoon ATD, I hope you're well? From a little research, I don't think we've specifically assigned this port. "The range 49152–65535 (215 + 214 to 216 − 1) contains dynamic or private ports that cannot be registered with IANA" (https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers) While this doesn't rule out the FNMEA Agent reporting through that port or not, it does imply these likely wouldn't be documented. I'll ask a colleague of mine more familiar with the FNMEA product to provide some confirmation here. Kind regards and thanks, Jack Flexera Support

jevans · ‎Apr 29, 2022

Good afternoon Piyush, I hope you're doing well? Thanks for reaching out on the forums here! If you have incoming Cyberreason evidences already gathered, you can follow the ARL process here and reach out to Support via the Support portal to get that added to the Application Recognition Library. https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-Suggest-Changes-to-the-ARL-SKU-Library-or-PURL/ta-p/2087 Following this data being validated by our Content team, your Cyberreason applications should be recognised as with any other application in the ARL. The Online Help also breaks down how to add a new Application here: https://docs.flexera.com/fnms/EN/WebHelp/index.html#tasks/App-AddingAnApplication.html You can then add your Cyberreason evidences to each new Application from that Application's Evidence tab. This would create a Local Application, which is recognizable and discoverable as with any other application, but exclusive to your environment. I hope that helps, but let me know if you have any other questions or concerns. Best regards, Jack

jevans · ‎Apr 29, 2022

Hi PM6, I'd agree with Tim here. The Inventory from the Agent is identified by a unique identifier - an AgentID - in the inventory file, which is dependent on several underlying hardware values. If the hostname changes, I wouldn't expect this unique value to. Any incoming inventory should therefore be merged with older Inventory data. I hope that helps! Best regards, Jack

jevans · ‎Apr 29, 2022

Hi Anjan, I hope you're well? I thought I'd add some reasoning about why the Agent might be connecting to the wrong Beacon here. When you first connect an Agent, you provide it an initial download URL to download Agent Policy from - as Chris has outlined in his earlier reply. Agent Policy contains configuration for Agent inventory and scheduling, but also details on every other Beacon in the environment (by default). When an Agent tries to upload up to FNMS, it makes a decision on which Beacon its best to upload to. This is outlined here in the Agent's documentation: https://docs.flexera.com/fnms/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/SelectIBs-ChapterOverview.html By default, an Agent will choose the highest priority Beacon of: A Matching AD sitename The fastest ping response A random number - for load balancing between similar Beacons from the previous two algorithms This may be modified in the Agent policy, there's some other alternatives outlined in the earlier linked document. If you would prefer particular Agents communicate with particular Beacons, this is also possible through the Inventory Group Settings. In the Web UI, you can specify a target set of Agents, as with configuring a Discovery & Inventory Rule, and force those Agents to only communicate with a subset of your environment's Beacons. This is outlined in our documentation, here: https://docs.flexera.com/FlexNetManagerSuite2022R1/EN/WebHelp/index.html#tasks/InvSet-InventoryGroupSettings.html I hope that is insightful for you! Best regards, Jack

jevans · ‎Apr 26, 2022

Good afternoon Dave, I certainly can't complain, thanks for asking! That's certainly possible in the mgssetup.ini. This is outlined in Step 7, here: https://docs.flexera.com/fnms/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/tasks/FA3-CustomSetupIni.html Changing the Registry path, setting name and values as relevant. I believe you'd be looking for something like: ; Registry settings to be created under: ; HKLM\Software\ManageSoft Corp\ManageSoft\VDI Endpoint Agent [VDI Endpoint Agent] desc0 = EnableVirtAppUsageTracking val0 = False I hope that helps! Best regards, Jack

jevans · ‎Apr 26, 2022

Good afternoon Ymhadjou, I hope you're well? Thank you for reaching out via our Community! If you manually run the inventory on your Beacon for the relevant Admin Module, what do we see in: ProgramData\Flexera Software\Compliance\Logging\SAPReader\ ProgramData\Flexera Software\Beacon\IntermediateData\ (You should see a .ZIP file with your Admin Module's clientID in the name) Do we see any mention of your System which isn't updating? Could you also confirm whether there's any issues with the connections to that System in the Admin Module's Connection Monitor? Best regards, Jack

jevans · ‎Apr 26, 2022

Good afternoon Dave, I hope you're well? My thanks for reaching out via the Community! The VDI Endpoint Agent is enabled by default. This error would be thrown when the Agent is running on a non-VDI machine. I believe for a Windows machine, this may be disabled by setting the below Registry option to 'False' : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\VDI Endpoint Agent\CurrentVersion\EnableVirtAppUsageTracking Best regards, Jack

jevans · ‎Apr 26, 2022

Good afternoon Reshma, I hope you're well? Thanks for reaching out on the Community! If you have both the FlexNet Inventory Agent and the SCCM endpoint agent installed, I'd anticipate we should get inventory from both sources. The 'Last Inventory Source' will just be the inventory source of the two which most recently reported inventory. If you take a look at ITAM's Inventory Device Matching view, do you still see Inventory records for both FNMS and SCCM for this machine? Is the 'Raw Inventory Date' up to date for both sources? Best regards, Jack

jevans · ‎Apr 26, 2022

Good morning Shelby, I hope your week's going well? Thanks for reaching out on the Community! I took a look through the SaaS Manager documentation regarding this, and noticed the following: 1. In SaaS Management, add the Power BI application. Refer to Adding an Application. 2. For License Type, select the appropriate option: • Free is for Power BI. • Paid is for Power BI Pro. Leave blank if both free and paid licenses are needed. https://docs.flexera.com/flexera/EN/SaaSManager/PowerBIIntegration.htm#:~:text=a%20Support%20Case.-,Integrating%20Power%20BI%20with%20SaaS%20Management,-To%20integrate%20Power Can you confirm what you've configured for your 'License Type' here? From your use case, it sounds like you should be leaving this blank. I'll also reach out to my colleagues on the SaaS Manager side for their perspective. Best regards, Jack

jevans · ‎Apr 13, 2022

Problem We're having issues installing the Az and Az.ResourceGraph Powershell modules for the FlexNet Beacon's Azure connector. We're unable to install these modules with the Powershell Install-Module command, or are having issues when trying to. We have already confirmed our .NET version is up to date, and our Beacon is upgraded to the required version, according to the pre-requisites section of the Azure connector document: (https://docs.flexera.com/fnms/EN/WebHelp/index.html#tasks/IB-ConnectAzure.html) Solution Installing the Az Module using MSI Installing Az is possible via an MSI installer, available on Microsoft's own github: https://github.com/Azure/azure-powershell/releases Ensure you download a compatible version of Az's Gallery Module - version 6.1.0 or later. Scroll down to the Assets section, and choose the MSI installer for your architecture (usually x64). This can then be copied onto your Beacon and installed. You may need to remove an installation of AzureRm if you've used an older Azure connector in the past. This is covered in step 1 of the Azure connector document above. Az and all of its' underlying modules should be visible in Powershell if you run: Get-InstalledModule Manually importing the Az.ResourceGraph Module On a device with internet access, download the Az.ResourceGraph Powershell module from PSGallery. The first supported version, 0.11.0, can be found here: https://www.powershellgallery.com/packages/Az.ResourceGraph/0.11.0 Under 'Installation Options' choose Manual Download. This will download a .nupkg file. Extract this using a file compression program like 7Zip. The contents should look similar to the following: Remove the NuGet-specific files from this folder: _rels, package, [Content_Types].xml and <name>.nuspec files These are not used when manually importing the Powershell module. Your extracted folder should look like this: Rename your folder. The extracted folder will be called az.resourcegraph.0.11.0. Rename this to Az.ResourceGraph Paste the entire folder into %ProgramFiles%\WindowsPowerShell\Modules This Powershell module will not appear in Get-InstalledModule. This will still be utilised by the Azure adapter successfully. The underlying DLLs and Powershell files can be blocked by Windows. "ERROR: System.Management.Automation.CmdletInvocationException: Could not load file or assembly 'file:///C:\Program Files\WindowsPowerShell\Modules\Az.ResourceGraph\Microsoft.Azure.Management.ResourceGraph.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) ---> System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Program Files\WindowsPowerShell\Modules\Az.ResourceGraph\Microsoft.Azure.Management.ResourceGraph.dll' or one of its dependencies." If running the connector fails with the above error, try right-clicking and Unblocking the files we've placed in %ProgramFiles%\WindowsPowershell\Modules\Az.ResourceGraph\ References "Install Azure PowerShell on Windows with MSI", Last Visited 15/02/2022 https://docs.microsoft.com/en-us/powershell/azure/install-az-ps-msi?view=azps-6.5.0 "Manual Package Download", Last Visited 15/02/2022 https://docs.microsoft.com/en-us/powershell/scripting/gallery/how-to/working-with-packages/manual-download?view=powershell-7.1#installing-powershell-modules-from-a-nuget-package

jevans · ‎Apr 13, 2022

Question What information is gathered from the Oracle Fusion Middleware (OracleFMW) inventory process? Answer OracleFMW gathers additional hardware information, along with files present and processes running on the target system. The list of files and processes the agent looks for is given to us by Oracle's Verification Program. This is confidential data that cannot be disclosed to customers. There are three ways this data is gathered, however: CPUQ Based on a component of the Oracle collection tool, we gather hardware information for machines running Oracle software FMW Copies of defined configuration and log files from the system & the output of the 'opmnctl' command, if available Logs A list of defined processes on the system, along with their parameters Not all devices would show all three types of OracleFMW data. We would expect to see CPUQ for all devices with OracleFMW evidence. Some devices would not have the listed processes or files - we'd therefore not see FMW or Logs data reflected. The lists of relevant FMW files or Logs processes are encrypted as part of the InventorySettings.xml configuration file for each Agent. The files or processes list may be updated by the weekly ARL update.

Online Status	Offline
Date Last Visited	‎Aug 18, 2022 07:42 AM

How does the FlexNet Beacon identify vCenter device names?

Where does the Oracle Database edition come from on Windows machines?

Re: SCCM Reader - GetDeletedComputerList

Re: Which FNMS learning paths or other tutorials are useful?

Re: FNMEA port 51219, 51220

Re: Publisher Cybereason is present in our Environment. However it is not visible in our Installed A...

Re: What effect does a hostname change have on the Flexera Inventory Agent

Re: Flexnet Questions

Re: Windows agent, vdi.log file growing

Re: One of dependent SAP System not updating

Re: Windows agent, vdi.log file growing

Re: Flexnet Agent and SCCM client

Re: Differentiate Associated Applications

Installing the Az & Az.ResourceGraph Powershell modules without a package repository

What is Oracle Fusion Middleware (OracleFMW) Evidence?

How does the FlexNet Beacon identify vCenter device names?

Where does the Oracle Database edition come from on Windows machines?

Re: SCCM Reader - GetDeletedComputerList

Re: Which FNMS learning paths or other tutorials are useful?

Re: FNMEA port 51219, 51220

Re: Publisher Cybereason is present in our Environment. However it is not visible in our Installed A...

Re: What effect does a hostname change have on the Flexera Inventory Agent

Re: Flexnet Questions

Re: Windows agent, vdi.log file growing

Re: One of dependent SAP System not updating