All I want to do is stop CI install status from updating hardware asset state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello all,
I would be eternally grateful for any help I can get. I am new to ServiceNow (Australia release - most recent update) and have noticed when our SCCM/Discovery/CMDB updates a laptop as Retired, it changes the asset state to Retired and this should NOT be happening. The laptops we have identified as being automatically marked as "retired" are still in active use and deployed to a user. It is also changing some other states, but if I can get this one figured out, then I can do the rest.
There has to be an easy way to stop this from happening, right? When I test in our lower instances, if I change the install status to retired on the computer CI record, it changes the Hardware status (and it changes the Hardware Asset to retired.
I've read so many articles from the community, but none that are more recent than 2023 and do not really answer my question and to be honest I'm in over my head when scripting.
Could someone help me craft something or provide me guided instruction on how to stop this from happening? Again, I do NOT want the CI class = Computer, install status of Retired to change my hardware asset states and substates - we need to manually control the asset states for now.
Thanks!
Jen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
That was my first question as well. If the CI in question is in use, why is it marked as retired?
