Discovery of CIs marked as "Retired" or "Non-Operational"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2018 12:39 AM
We marked some of our CIs as retired for a test:
Status- Retired
Operational Status- Non-Operational
These CIs are still on network and we wanted to check the impact of discovery on these records.
Now, the these are being discovered but these are updating the same CI (that's fine). But the Status and Operational status are still the same which gives a wrong impression.
What should be done?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2018 11:45 PM
You may right a script if the updated time is less than a specified time, these field values should be modified? But this is going to take a lot of execution efficiency?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2018 03:06 AM
You can add operational status in your identifiers and a new CI would be created next time, when discovery is run.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2024 09:49 PM
I have implemented csdm life cycle mapping. Once life cycle stage status is end of life, update operational status is set to retire