Hi Rajesh, Can you try this, please? When using the default template for importing POs as well as when using a business importer (MGSBI) If you are importing from an Excel (.xlsx) file, make sure all data in the "PO Number" column are formatted as "Text" (data display left aligned in Excel) If you are importing data from a CSV file, use a "schema.ini" file to specify that the "PO Number" column needs to be treated as "Text". ... View more

Hi Steve, Oracle Enterprise Manager (OEM) is not really an Inventory tool. However, you can use the "OEM Adapter" to extract a TNSNAMES.ORA file that can be used for scanning Oracle databases remotely from a Beacon. For additional details, please review the FNMSSystemReference.pdf file available for download from the FNMS online help. There is a chapter "Oracle Discovery and Inventory > Interaction with Oracle Enterprise Manager" providing additional information. Generally, collecting the Oracle inventory by installing a FNMS Agent on the Oracle server is easier to implement and easier to maintain than scanning Oracle databases remotely.   ... View more

Remember that computers must respond to a PING (ICMP) request to be discovered sucessfully. Typically, the required steps would be: Add the IP adresses as a new site to the "Discovery & Inventory > Network > Subnets" page. In case you want to target specific IP adresses, you can assign multiple "One IP network" with a /32 network mask to your site, like 172.31.0.15/32. Make sure that all subnets are assigned to a Beacon.  Use the "Discovery & Inventory > Network > Unassigned Subnets" page for assigning multiple subnets to the same Beacon in a single step. Under "Discovery & Inventory > Discovery > Discovery and Inventory Rules" locate the rule that is being used for discovering servers. Open the rule to find which targets are used for this rule.   Again under "Discovery & Inventory > Discovery > Discovery and Inventory Rules", locate the target that you identified in the previous step and open it for editing. In the list "Define machines to target", make sure that the new/updated subnet is included. Save your target after updating it. Make sure the updated rule information (with the updated target) is downloaded to the Beacon assigned to the IP subnet (see step #2). You can enforce immediate updating by using the "Update Rules" button in the "Rules" section in the Beacon UI.  On the Beacon, you can trigger the immediate execution of the rule by selecting it in the "Rules" section and clickin on the the "Run" button. Discovery results will be visible in the FNMS Web UI immediately (without Compliance Import). In case the servers are not being discovered immediately, check the LOG files on the Beacon (inventorybeacon.log, beaconEngine.log) for further information. You can also enforce additional logging by editing the \Program Files (x86)\Flexera Software\Inventory Beacon\etdp.trace file. Hope this helps :-). ... View more