Operational Status of "rediscovered" CIs via ACC-V?

[Tone1]

Hello,

how do you guys handle the rediscovery of already "retired" CIs via ACC-V?

Is there a possibility to automatically set the lifecycle to operational when ACC-V  notifies the CMDB of a already retired CI?

Thanks in Advance.

[Tone1]

It Updats the old (retired) one without changing the status back to operatinal, for "normal" discovery i'm used to this as well.

[AJ-TechTrek]

Hi @Tone1 ,

Refer the below articles, which may help you.

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/conc...

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/refe...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Tone1]

Sorry but i cant find anyhting to my issue in those two links, i want to change the status from an already retired computer ci back to operational when its rediscovered via ACC.

[scottl]

Outside of the spam comments, did you find out how to set the CI back to operational, and where it was done? As I can see if you bring a CI out of retirement it sets the operational status to "non-operational", instead of it being "operational" in the case that it's "installed"

[Tone1]

Hi,

i created a Business Rule to reset the Op-Status/Lifecycle:

  

This will get in conflict with stuff you do via Integrationhub ETL.

Have a look at this post if you use this:
https://www.servicenow.com/community/cmdb-forum/last-discovered-data-manager-tasks-and-integhub/td-p...