Identify software that causes a device to be 'Archived'

Title

In FlexNet Manager Suite, you might notice that some devices move to Archived status when their linked asset is set to Retired or Disposed. This can be confusing, especially if the device has never actively consumed an IBM PVU or VPC license.

This behavior occurs because FlexNet Manager Suite tracks certain software installations historically. This article explains why a device becomes archived and shows you how to identify the software that triggered this status.

Instructions

Why a device becomes archived

A device does not need to currently consume an IBM PVU or VPC license to be archived. It only needs to have software installed that can be licensed under PVU or VPC metrics.

If FlexNet Manager Suite detects that:

The linked asset is Retired or Disposed, and
The device has (or historically had) software that could be covered by PVU or VPC licenses

The device is moved to Archived instead of Ignored to preserve historical license compliance data.

For background information, see Why a device becomes archived in the product documentation.

Identify the software that triggered the archived status (on-premises only)

If you manage an on-premises FlexNet Manager Suite environment, you can use the database to identify which software titles caused the device to be archived.

Run the following SQL query against the FlexNet Manager Suite compliance database. It checks the temporal (slowly changing dimension) tables to find software that was installed on the device during historical reporting periods.

/* Find software titles on an archived device that trigger historical tracking */
SELECT 
    cc.ComputerName, 
    st.FullName AS [Software_Title], 
    st.SoftwareTitleID,
    temp.ComplianceComputerID
FROM TemporalInstalledSoftwareSCD temp
JOIN ComplianceComputer cc ON cc.ComplianceComputerID = temp.ComplianceComputerID
JOIN SoftwareTitle st ON st.SoftwareTitleID = temp.SoftwareTitleID
WHERE cc.ComputerName = 'Your_Archived_Computer_Name'
ORDER BY st.FullName ASC

Replace Archived_computer_name with the name of the archived device you want to investigate.

After running the query, you can see which software titles were installed on the device and are eligible for PVU or VPC licensing. This helps explain why FlexNet Manager Suite preserved the device in Archived status instead of ignoring it.

Was this helpful?

Support Hub

Product

FlexNet Manager Suite

Related Products

FlexNet Manager Suite

Deployment type

On-premises

Visibility

Guest

URL Name

Identify-Software-Causing-a-Device-to-be-Archived

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Why a device becomes archived

Related Articles

Please wait...

Case id: 00001065