This one is probably going to be hard to explain.  It was certainly hard to understand why and what happened.   

If I understand correctly, libraries for no-longer-owned products were deleted so as to delete the modules for the products.
Then it was discovered that the libraries contained other modules that were still needed and so they were restored.
That brought back the modules for the unowned products and a subsequent TADz discovery triggers a bill for running products that aren't owned.

I know that the correct resolution for this is to only delete the modules and not the libraries.  However, there is a requirement for a technical solution of some sort.  Not sure what can be done - a restored module is unlikely to have a "I used to be deleted" flag.   But if there's anything within IZSAM that could help here, I'd be pleased to hear it.
Many thanks
Matt

This one is probably going to be hard to explain.  It was certainly hard to understand why and what happened.   

If I understand correctly, libraries for no-longer-owned products were deleted so as to delete the modules for the products.
Then it was discovered that the libraries contained other modules that were still needed and so they were restored.
That brought back the modules for the unowned products and a subsequent TADz discovery triggers a bill for running products that aren't owned.

I know that the correct resolution for this is to only delete the modules and not the libraries.  However, there is a requirement for a technical solution of some sort.  Not sure what can be done - a restored module is unlikely to have a "I used to be deleted" flag.   But if there's anything within IZSAM that could help here, I'd be pleased to hear it.
Many thanks
Matt

This one is probably going to be hard to explain.  It was certainly hard to understand why and what happened.   

If I understand correctly, libraries for no-longer-owned products were deleted so as to delete the modules for the products.
Then it was discovered that the libraries contained other modules that were still needed and so they were restored.
That brought back the modules for the unowned products and a subsequent TADz discovery triggers a bill for running products that aren't owned.

I know that the correct resolution for this is to only delete the modules and not the libraries.  However, there is a requirement for a technical solution of some sort.  Not sure what can be done - a restored module is unlikely to have a "I used to be deleted" flag.   But if there's anything within IZSAM that could help here, I'd be pleased to hear it.
Many thanks
Matt