- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2020 08:26 AM
Hi Experts,
Latest discovered CI's status is not getting change from absent to installed. How to debug this issue ?
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2020 12:09 PM
Hi,
As far as i know the status is not changed by the discovery when the ci is discovered. When it is created then it updates the status as operational by default but if you mark it as retired for example then it will not update the status back to Operational.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2020 08:34 AM
Please provide more details. What kind of CI it is ? Do you mean last scan date is not getting updated ? What kind of credentials you have for this CI ?
And what kind of reconciliation and identification rules you have setup ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2020 11:11 AM
Hi,
It is happening for the Windows Server CIs. Windows Server Cis are getting discover and attributes are getting updated fine, however state of the CI is not getting change from "Absent" to "Installed".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2020 12:02 PM
okay. Can you please check if the discovery is getting completed ? Are you scanning this as a part of IP range or a specific IP ?
You might want to check in discovery logs or ECC queue if there is an error.
I would consider running a quick discovery on this IP and checking logs if there are error etc.
Do you have any identification and reconciliation rules built ?
Thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2020 10:23 AM
Hi,
Are you able to find which Discovery Schedule it is being used. If so, you can observe the Discovery Logs/ You can use "Show Discovery Events" on CI to find the events upon that CI.
Also, check whether you have any Reconciliation Rules that are blocking
Finally, you might need to update the Probe in case if everything doesn't work.
Thanks,
Narsing