- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2024 10:49 AM
We're trying to setup a retirement policy for the vCenter Instance class.
We've created the following CMDB Retirement Custom Definition (Rule):
And we've created the following policy:
When the scheduled job "CMDB Data Manager Retire Policy Processor" is executed the task is created and processed in the cmdb_data_management_task table but the ci's found don't appear to have been retired. What are we missing here?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2024 01:22 PM
The Retirement Definition you set is using a "is not" operator, so this means that when Data Manager attempts to set a CI's Install Status field it will use any value except "Retired".
The purpose of Retirement Definitions is to specify the field and value for a CI class that equates to retirement. In the case above the Retirement Definition should be Install Status is Retired.
Note that Retirement Definitions can only specify a single value for a field included in the definition - multiple values for a single field are not supported.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2024 01:22 PM
The Retirement Definition you set is using a "is not" operator, so this means that when Data Manager attempts to set a CI's Install Status field it will use any value except "Retired".
The purpose of Retirement Definitions is to specify the field and value for a CI class that equates to retirement. In the case above the Retirement Definition should be Install Status is Retired.
Note that Retirement Definitions can only specify a single value for a field included in the definition - multiple values for a single field are not supported.