Unmanaged Devices

FlexNet Manager Suite 2019 R1 (On-Premises Edition)

The Discovery & Inventory > Unmanaged Devices page (in the Discovery group) lists the devices discovered out of the defined subnets. By default, this page displays all unmanaged discovered devices, but you can apply filters to restrict the number of records. This page mainly enables you to perform the following actions on the discovered device records:

• Search for an unmanaged discovered device: You can search for a particular unmanaged discovered device by applying filters. For more information about using lists, filters, and other UI options, see the topics under Using Lists in FlexNet Manager Suite.
• Create a discovered device: See Create a Discovered Device
• View or change the properties of an unmanaged discovered device: You can click a device name to view its properties. See Discovered Device Properties
• View the discovery and inventory rules applicable to an unmanaged discovered device: Select any discovered device and click Applicable rules to view the discovery and inventory rules applicable to that device. For more information on discovery and inventory rules, see Discovery and Inventory Rules.
• Delete a discovered device: See Deleting a Discovered Device.
• Create a management view: The Save view as feature of FlexNet Manager Suite enables you to create customized management views of a page by saving the applied user interface settings. For more information, see Creating Management Views.

Device Properties

FlexNet Manager Suite groups the device properties into the following two categories. The category name appears on the top of the column heading when you drag a property from the Column Chooser. Properties that belong to the same category appear under single category title.

• Discovered device properties: This category contains the properties that describe one or more attributes of a discovered device.
• Rule results: This category contains the properties that describe the status information for one or more actions performed on a device as a part of the discovery and inventory rule.

This page displays the following columns (listed alphabetically). Some columns are displayed by default and others can be displayed through the column chooser. To manage columns and other UI options, see the topics under Managing Columns in a Table.

Table 1. Device properties on the Unmanaged Devices page

Property name	Details
Discovered Device Properties: This category contains the basic properties of a discovered device.
Agent installed	Indicates whether the discovered computer has the FlexNet inventory agent installed on it. Value is set to Yes: Automatically when the device has been adopted within the last 30 days (an initial grace period before inventory uploads start) Automatically each time that FlexNet inventory is received from the device in cycles of less than 30 days, and the FlexNet inventory agent is recognized within that inventory Manually, if you are creating a discovered device record.If the 30-day cycle is exceeded, the value is set to No. Selectable in the Advanced tab of the discovery device properties.
Discovered	A Yes indicates that the device was first identified in a discovery process (either remotely from an inventory beacon, or locally when the installed FlexNet inventory agent found Oracle on the device). A No indicates that the discovery record was 'back-generated' after the device was found in collected inventory. The discovery and inventory processes generate the value of this field.
Discovered by	Identifies the beacon that discovered this device. The discovery and inventory process generates the value of this field.
DNS full name	The fully qualified name of the discovered computing asset in the Domain Name System. Editable in the General tab in the discovery device properties.
Domain name	The name of the domain to which the computing device belongs. Editable in the General tab of the discovery device properties.
First discovered	Specifies the date and time when the discovery process discovered this device. The discovery and inventory process generates the value of this field.
Inventoried	Indicates that the inventory information has been collected for this device, and the device appears in the All Inventory list. FlexNet Manager Suite may have collected this information through an agent or through discovery and inventory rules. The discovery and inventory process generates the value of this field.
IP address	The IPv4 address of the discovered device. For discovered devices with multiple IP addresses (for example, those with multiple network cards), only the first validly-formed IP address is displayed. The IP address may be blank for reasons like these: The first (or only) IP address returned was in the IPv6 address family (and these addresses are not included) The device was discovered by NetBIOS queries, or through a TNSNames.ora file, that provided only a device name, and the DNS look-up did not return an IPv4 address for this device. Editable in the General tab of the discovered device properties.
Last discovered	Specifies the date and time when this device was last discovered by the discovery process. A blank value for this field indicates that the device has been discovered by a third-party inventory collection tool, and not by discovery and inventory rules or FlexNet inventory agent. The discovery and inventory process generates the value of this field.
Last inventory date	The date when the last inventory information was collected by the Last inventory source for this inventory device. The inventory process generates the value of this field.
MAC address	The Media Access Control (MAC) address of the inventory device. If a device has multiple network interface cards, this field displays a comma-separated list of MAC addresses. Editable in the General tab of the discovery device properties.
Name	The name of the computing device. Editable in the General tab in the discovery device properties. This field is not editable in the Raw Software Usage page. Note: It is best practice to leave names unchanged for records created automatically from discovery or inventory. As the name is used to identify the device, changing the name effectively creates a separate device record, and the old one is recreated at the next import.
Operating system	The operating system running on this device. Tip: This value may be blank because: The device is recently discovered – the operating system can only occasionally be populated during first discovery, and is often backfilled once inventory is returned for this device. The device is a VM host that is a hardware frame that may not be running its own operating system. In this case, the computer Name field is set to a serial number associated with the hardware (because, without an operating system, there is no host name). In fact, no inventory of any kind is possible without an operating system, so FlexNet Manager Suite synthesizes the VM host record from common data reported by its guest VMs. The virtual machines in these cases may typically be partitions like: LPARs running on IBM PowerPC servers Solaris zones on either x86 or SPARC architectures nPar or vPar partitions running on HP Integrity servers. The discovery and inventory process generates the value of this field.
Oracle DB listeners	Lists the names of the Oracle listeners installed on this device. The discovery and inventory process generates the value of this field.
Oracle DB services	Lists the names of the Oracle services installed on this device. The discovery and inventory process generates the value of this field.
Site	Specifies the name of the site or subnet to which this device has been allocated, based on its reported IP address. If the reported IP address does not place the computer in any defined site, the site is reported as Unrecognized. The discovery and inventory process generates the value of this field.
SQL Server	Indicates whether the computer is running SQL Server database. Editable in the Databases tab of the discovery device properties.
VDI	Indicates whether the device is a virtual machine hosted in VDI. The discovery and inventory process generates the value of this field.
VDI broker	Indicates whether the device is running a Citrix Broker service. The discovery and inventory process generates the value of this field.
VDI template	Identifies the VDI template (Catalog in Citrix terminology) from which the virtual desktop instance accessed remotely from this inventory device, was spawned. The value of this field appears only when this device has been used as an end-point to access a remote desktop. The discovery and inventory process generates the value of this field.
Virtual parent	Specifies whether the device is a virtual parent. The discovery and inventory process generates the value of this field.
Virtualization host	Specifies the name of the site or subnet to which this device has been allocated, based on its reported IP address. If the reported IP address does not place the computer in any defined site, the site is reported as Unrecognized. The value of this field is automatically generated by the discovery process.
Virtualization port	Specifies the virtualization port number. Editable in the Advanced tab of the discovery device properties.
Rule results: This category lists the status of discovery and inventory rule execution on a device.
Adoption	Displays the status of adoption for this device. This field indicates the details of success or failure while adopting the discovered device. This field can have any of the following values: Agent already installed — The discovery and inventory process performed no adoption because FlexNet inventory agent has been already installed on this device Completed — The adoption completed successfully Failed — The adoption failed Exempted — Not relevant for adoption, which occurs when the inventory device is identified within any target (whether used in a rule or not) that is marked for adoption to occur Not configured — The discovery and inventory process performed no adoption because the discovery and inventory rule is not configured to gather inventory Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Not targeted — No inventory gathering was performed as the device was specifically excluded in the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
Adoption date	Displays the date and time when FlexNet Manager Suite adopted this device. The discovery and inventory process generates the value of this field.
Citrix XenDesktop discovery	Specifies whether the discovery and inventory process has discovered Citrix XenDesktop on this device, through remote execution. This field may have any of the following values: Discovered successfully — Citrix XenDesktop is discovered Discovery completed with errors — The discovery process completed with some errors. You can check the Rules page for troubleshooting information. Exempted — No attempt was made to identify Citrix XenDesktop on this device because it was discovered through a TNSNames.ora file and is therefore assumed to be an Oracle Database server Not configured — The discovery and inventory rule is not configured to discover Citrix XenDesktop Not discovered — Citrix XenDesktop is not discovered The discovery and inventory process generates the value of this field.
Citrix XenDesktop discovery date	Specifies the date and time when FlexNet Manager Suite discovered Citrix XenDesktop on this device. Not editable for existing devices.
Citrix XenDesktop inventory	Specifies whether the discovery and inventory process has collected Citrix XenDesktop inventory for this device, through remote execution. This field may have any of the following values: Completed — Citrix XenDesktop inventory collected successfully Discovery not enabled — Citrix XenDesktop discovery disabled in the rule Exempted — No attempt was made to collect Citrix XenDesktop inventory, because the device discovered through a TNSNames.ora file and is therefore assumed to be an Oracle Database server Failed — Citrix XenDesktop inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for Citrix XenDesktop Not discovered — Citrix XenDesktop is not discovered on this device Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
Citrix XenDesktop inventory date	Specifies the date and time when FlexNet Manager Suite collected Citrix XenDesktop inventory for this device. The value of this field is automatically generated by the discovery and inventory process.
MS Hyper-V discovery	Specifies whether the discovery and inventory process has discovered Microsoft Hyper-V on this device, through remote execution. This field may have any of the following values: Discovered successfully — Microsoft Hyper-V is discovered. Discovery completed with errors — The discovery process completed with some errors. You can check the Rules page for troubleshooting information. Exempted — No attempt was made to discover Microsoft Hyper-V on this device because it was discovered through a TNSNames.ora file, and is therefore assumed to be an Oracle Database server. Not configured — The discovery and inventory rule is not configured to discover Microsoft Hyper-V. Not discovered — Microsoft Hyper-V is not discovered. The discovery and inventory process generates the value of this field.
MS Hyper-V discovery date	Specifies the date and time when FlexNet Manager Suite discovered MS Hyper-V on this device. The value of this field is automatically generated by the discovery and inventory process.
MS Hyper-V inventory	Specifies whether the discovery and inventory process has collected Microsoft Hyper-V inventory for this device, through remote execution. This field may have any of the following values: Completed — Microsoft Hyper-V inventory collected successfully Discovery not enabled — Microsoft Hyper-V discovery disabled in the rule Exempted — No attempt was made to collect Hyper-V inventory from this device because it was discovered through a TNSNames.ora file, and is therefore assumed to be an Oracle Database server Failed — Microsoft Hyper-V inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for Microsoft Hyper-V Not discovered — Microsoft Hyper-V is not discovered on this device Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
MS Hyper-V inventory date	Specifies the date and time when FlexNet Manager Suite collected MS Hyper-V inventory for this device. The discovery and inventory process generates the value of this field.
MS SQL discovery	Specifies whether the discovery and inventory process has discovered MS SQL on this device, through remote execution. This field may have any of the following values: Discovered successfully — MS SQL is discovered. Discovery completed with errors — The discovery process completed with some errors. You can check the Rules page for troubleshooting information. Exempted — No attempt was made to discover MS SQL on this device because it was discovered through a TNSNames.ora file, and is therefore assumed to be an Oracle Database server. Not configured — The discovery and inventory rule is not configured to discover MS SQL. Not discovered — MS SQL is not discovered. The discovery and inventory process generates the value of this field.
MS SQL discovery date	Specifies the date and time when FlexNet Manager Suite discovered MS SQL on this device. The discovery and inventory process generates the value of this field.
MS SQL inventory	Specifies whether the discovery and inventory process has collected MS SQL inventory for this device, through remote execution. This field may have any of the following values: Completed — MS SQL inventory collected successfully Discovery not enabled — MS SQL discovery disabled in the rule Exempted — No MS SQL inventory was attempted on this device because it was discovered through a TNSNames.ora file and is therefore assumed to be an Oracle Database server Failed — MS SQL inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for MS SQL Not discovered — MS SQL is not discovered on this device Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
MS SQL inventory date	Specifies the date and time when FlexNet Manager Suite collected MS SQL inventory for this device. Not editable for existing devices.
Oracle DB discovery	Specifies whether the discovery process has discovered Oracle Database on this device, through remote execution. This field may have any of the following values: Discovered successfully — Oracle Database is discovered. Discovery completed with errors — The discovery process completed with some errors. You can check the Rules page for troubleshooting information. Exempted — The discovery process did not attempt to identify Oracle Database, because the device was identified through a TNSNames.ora file, and is therefore assumed to be an active Oracle Database server with further discovery not required. Not configured — The discovery and inventory rule is not configured to discover Oracle DB. Not discovered — Oracle DB is not discovered. The discovery and inventory process generates the value of this field.
Oracle DB discovery date	Specifies the date and time when FlexNet Manager Suite discovered Oracle database on this device. The discovery and inventory process generates the value of this field.
Oracle DB inventory	Specifies whether the inventory beacon has collected Oracle Database inventory for this device, through remote execution. This field may have any of the following values: Completed — Oracle Database inventory was collected successfully Discovery not enabled — Oracle Database discovery is disabled in the rule Exempted — This value does not apply to Oracle Database inventory Failed — Oracle Database inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for Oracle Database Not discovered — Oracle Database was not discovered on this device Not in beacon's subnet — No inventory gathering was performed because the device is outside the inventory beacon's subnet Not specified in rule's target — No inventory gathering was performed as the device is outside the target specified in the underlying discovery and inventory rule Unknown IP address — No inventory gathering was performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
Oracle DB inventory date	Specifies the date and time when FlexNet Manager Suite collected Oracle database inventory for this device. The discovery and inventory process generates the value of this field.
Oracle VM discovery	Specifies whether the discovery and inventory process has discovered Oracle VM on this device, through remote execution. This field may have any of the following values: Discovered successfully — Oracle VM is discovered. Discovery completed with errors — The discovery process completed with some errors. You can check the Rules page for troubleshooting information. Exempted — The discovery process did not try to identify Oracle VMs, because the device was identified through a TNSnames.ora file and is assumed to be an Oracle Database server. Not configured — The discovery and inventory rule is not configured to discover Oracle VM. Not discovered — Oracle VM is not discovered. The discovery and inventory process generates the value of this field.
Oracle VM discovery date	Specifies the date and time when FlexNet Manager Suite discovered Oracle VM on this device. The discovery and inventory process generates the value of this field.
Oracle VM inventory	Specifies whether the discovery and inventory process has collected Oracle VM inventory for this device, through remote execution. This field may have any of the following values: Completed — Oracle VM inventory collected successfully Discovery not enabled — Oracle VM discovery disabled in the rule Exempted — The device was exempted from inventory collection for Oracle VMs because it was identified in a TNSNames.ora file, and is assumed to be an Oracle Database server Failed — Oracle VM inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for Oracle VM Not discovered — Oracle VM is not discovered on this device Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
Oracle VM inventory date	Specifies the date and time when FlexNet Manager Suite collected Oracle VM inventory for this device. The discovery and inventory process generates the value of this field.
Remote inventory	Indicates that the inventory information has been collected for this device through discovery and inventory rules. This field may have any of the following values: Completed — Remote inventory collected successfully Discovery not enabled — Remote discovery disabled in the rule Exempted — The device was exempted from general remote inventory gathering because it was identified through a TNSNames.ora file, and is therefore assumed to be an Oracle server Failed — Remote inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for remote devices Not discovered — Remote inventory is not discovered on this device Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
Remote inventory date	Specifies the date and time when FlexNet Manager Suite collected inventory information for this device through discovery and inventory rules. The discovery and inventory process generates the value of this field.
VMware discovery	Specifies whether the discovery and inventory process has discovered VMware on this device, through remote execution. This field may have any of the following values: Discovered successfully — VMware is discovered. Discovery completed with errors — The discovery process completed with some errors. You can check the Rules page for troubleshooting information. Exempted — The discovery process did not look for VMware software because the device was identified in a TNSNames.ora file, and is therefore assumed to be an Oracle server. Not configured — The discovery and inventory rule is not configured to discover VMware. Not discovered — VMware is not discovered. The discovery and inventory process generates the value of this field.
VMware discovery date	Specifies the date and time when FlexNet Manager Suite discovered VMware on this device. The discovery and inventory process generates the value of this field.
VMware inventory	Specifies whether the discovery and inventory process has collected VMware inventory for this device, through remote execution. This field may have any of the following values: Completed — VMware inventory collected successfully Discovery not enabled — VMware discovery disabled in the rule Exempted — No attempt was made to collect VMware inventory from this device because it was discovered through a TNSNames.ora file, and is therefore assumed to be an Oracle Database server Failed — VMware inventory collection failed Local agent — The locally-installed FlexNet inventory agent gathers inventory Not configured — The discovery and inventory rule is not configured to gather inventory for VMware Not discovered — VMware is not discovered on this device Not in beacon's subnet — No inventory gathering performed because the device is outside the beacon's subnet Not specified in rule's target — No inventory gathering performed as the device is outside the underlying discovery and inventory rule's target Unknown IP address — No inventory gathering performed as the IP address of the device is unknown. The discovery and inventory process generates the value of this field.
VMware inventory date	Specifies the date and time when FlexNet Manager Suite collected VMware inventory for this device. The discovery and inventory process generates the value of this field.