Retiring an asset without using licenses

[Russell5]

We are currently using discovery to populate the CMDB. In our company we have a fairly high rate of system life-cycling. Doing some basic testing with trying to set flags to a retired status, I have not been able to get the production instance to flag a system as retired so that it can stay in the CMDB for historical purposes without the platform continuing to consume a license.

My questions are simply, is it possible to have server resources exist in a retired state in the CMDB without it continuing to pull a license and if so, what needs to be done?

If there is a document that I missed when I was digging through that details this that would be awesome.

Thank you in advance to anyone that can assist.

[doug_schulze]

Russell,

Definitely, a question for your account team to answer officially. But it's my understanding that a device that has been discovered in the past 90? days regardless of its state is still a counted license. Discover it on Monday, retire it on Wednesday well it's 88 days before it no longer counts as a licensed CI..But again, talk to your account team for absolutes..

[Russell5]

Thank you for this input. We are reaching out to our account team to validate this response and will respond back here with what they indicate.

[Russell5 · Accepted solution]

Bringing this to a close for anyone that does view it:

According to our account team it depends on the specific license you are on. What was mentioned by Doug above is the case for one license model. Apparently there is another license model (or so I am told) that does a daily role-up so add an asset one day and it would count against your license during that day/nights license script run and then retire it the next day and it would no longer count against you. 

Best bet, check with your account rep but Doug's explanation, base on what we are seeing in our instance appears to be what we have in place.