Online Help | Desktop App

Marking Configuration Items as retired

If a computer, hardware device, document, or configuration is retired from use in your operational environment, you can mark its record as retired. Typically, you mark configuration items as retired using these workflow actions:

  • Retire Computer

  • Retire Hardware

  • Retire Document

  • Retire Configuration

INFO: For details on retiring software, see Marking Tracked Software and Software Licenses as retired.

Typically, if retired CIs are associated with Asset records, those Assets become retired, too. If retired Computers or Hardware had been auto-added from Alloy Discovery, their original records are deleted from Alloy Discovery.

Retired CI records cannot be edited, you can only view them.

The information about retired Computers and Hardware device is not considered when Alloy Navigator checks license compliance, i.e.:

  • Discovered installations on retired Computers are not counted when Alloy Navigator calculates discovered installations of the Software Product.

  • The allocations of Software Licenses to retired Computers or Hardware items are not counted when Alloy Navigator calculates the number of allocations for these licenses.

The information about retired CIs are hidden on the following locations:

  • Retired CI records disappear from the corresponding Select [Object] windows.

  • The discovered installations on retired Computers are not listed on the Discovered Installations tabs of corresponding Tracked Software and Software Product records.

  • The Discovered Installations grid omits discovered installations on retired Computers.

  • The allocations of Software Licenses to retired Computers or Hardware items are neither listed on the Allocated Licenses tab of the Tracked Software window and the Allocation tab of the Software License window.

NOTE: If you mark a Configuration Item as retired, the "On Condition" Triggers (if any have been configured by your Alloy Navigator administrator) do not fire on these records. For details, see Configuring Triggers.