Adam I would say yes, but if the customer is not using any remote targeting they can just ignore the message.  ... View more

Thanks Chris I will take a crack at it. We are using CMD as admin. I will keep this thread updated. ... View more

Very rough scripts to inventory our testbed computers in a segmented netwrok that has a file server as gateway, but works if you are changing server locations, search for "SERVERNAME" and set to a fileserver. and change f: to the local path on that file server where the inventory files will be uploaded. Create_inventory.ps1 Needs to be scheduled to run at start-up using GPO or other methods. Will execute ndtrack.exe from a fileserver and upload inventory results to a fileshare Upload_gateway.ps1 Executes on the file server where the inventory files are uploaded, requires also the full agent to be installed on this file server.     ... View more

HI @pchristian  Again it is the inventory device linked to the asset that has changed from being active but "Out-of-Date" to dummy as it is gone.  The difference is that "Out-of-Date" inventory will still consume your licenses. ... View more

Only approach I can think of would be to configure report(s) to expose the inventory data you want to extract and use the GetCustomView API as discussed here: Access or Update FNMS Cloud Data using PowerShell However, do consider: Inventory data tends to be large in terms of volume, so depending on your scale you may find this doesn't work. If you are looking for raw/low level inventory data (as opposed to normalized hardware or software inventory details), you may find that the data you want isn't exposed through the reporting options. ... View more

Here is a screenshot of how the option to add a service account should look: If you don't see this then maybe you don't have appropriate rights, or possibly you need to reach out to your Flexera Account Manager to get a FlexNet Manager Suite license that supports API access. ... View more

Here are some notes to clarify points which were made earlier in this discussion thread which I think may not be quite correct: @jjensen's initial pointer to set the networkname setting in the C:\Program Files (x86)\Flexera Software\Inventory Beacon\DotNet\conf\BeaconEngine.config file as per https://helpnet.flexerasoftware.com/fnms/EN/WebHelp/index.html#reference/FIB-WebConfigFile.html is the correct place to start here. Set networkname to the DNS name that you want agents to use when communicating with the beacon. This information will be subsequently uploaded to the application server. I'm not sure of the schedule of this upload, but I've observed it can take some time. Maybe allow a day or so. Restarting the Beacon Engine service may help to speed this step along, although I'm not sure about that - it won't hurt to try. Once the information is uploaded to the application, it gets stored in the Beacon table in the compliance database that @erwinlindemann has mentioned. You should not seek to directly make changes to the contents of this table yourself; if you do make changes they are likely to be overwritten by the system at some point based on the information in the BeaconEngine.config file. When each beacon in your environment updates its beacon policy, the latest beacon name information stored in the Beacon table will be downloaded as part of the policy and stored in the C:\ProgramData\Flexera Software\Beacon\BeaconPolicy.xml file mentioned earlier. When each agent in your environment updates its agent policy, it will download beacon failover settings details to be stored in the registry. The beacon generates a Default Failover Settings.ndc file based on what is stored by the beacon in its BeaconPolicy.xml file. The agent downloads the .ndc file. Of course, the agent can only download this file if it is currently in a state where it can successfully communicate with a beacon. If the agent configuration has been messed up such that it cannot communicate with a beacon (e.g. because it has lost track of the beacon's DNS name), it will be orphaned until you manually do something about it. ... View more

Firstly, thanks for these insights. The beacon server am using is based out of Australia(APAC). ... View more

The key information in the logging here is the following line: [3/9/2020 9:17:13 AM (G, 0)] {7704} WARNING: Configuration properties for the Oracle home "D:\psft\db\oracle-server\12.1.0.2" could not be discovered and instances in this home will not be inventoried. This log message indicates that there was a failure in any one of several steps that are encoded in the InventorySettings.xml file (this file contains details the agent uses to drive the Oracle Database inventory gathering process). However in the case of a failure like this, the logging is somewhat limited and it does not give insight into what the specific problematic step is attempting to do. Turning on some tracing by editing the etcp.trace file as @steven_donovan1 has suggested may give some further insight here beyond what the logging you have says. But if that doesn't help it is likely you will need to raise a case with Flexera Support to get some assistance and specific guidance on how to dig deeper. ... View more

Update on this discussion: We are validating the customer license to ensure it has the required Content Pack enabled. This will be worked upon a support case further. ... 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

If you look at the logs it connects to every server admin shares hense why you need the elevated permissions for NTFS permissions. ... View more

Hi Steven I have created a setup which i tested and works. See below, around the netselector you would need to see where to add it, hope this helps: ---------------------------------------------------------------------------------------------------------- #!/bin/sh # ------------------------------------------------------------------------------------------------- # FlexNet Inventory Agent installation # ------------------------------------------------------------------------------------------------- # Create variables used throughout this installation script BASEDIR=/var/tmp BEACON=beaconname # Create custom config.ini cat << EOF > $BASEDIR/tempconfig.ini [ManageSoft\Common\UploadSettings\Bootstrap Server 1] Priority=10 Host=beaconname [ManageSoft\Common\DownloadSettings\Bootstrap Server 1] Priority=10 Host=beaconname EOF # Install FlexNet Inventory Agent - Mac,Linux,AIX etc echo "Installing FlexNet Inventory Agent" rpm -i managesoft-13.1.1-1.x86_64.rpm # Apply custom configuration from $BASEDIR/config.ini echo "Applying custom configuration into config.ini" /opt/managesoft/bin/mgsconfig -i $BASEDIR/tempconfig.ini # Remove tempconfig file rm -rf $BASEDIR/tempconfig.ini # Re-run the mgspolicy /opt/managesoft/bin/mgspolicy -t machine ... View more