ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clients changing from managed to retired and unmanaged


Article ID: 173422


Updated On:


IT Management Suite


I notice an asset that has been actively reporting to the Notification Server disappears from my reports. I find that the asset has changed from managed to unmanaged (ItemResource.[IsManaged] goes from a 1 to a 0). Usually what I then see is that in about a day it goes back to managed, while all the while it has been actively reporting to the Notification Server.


There are two processes at work here.
  • The user is running an automatic merge script that merges duplicate computers that have the same name and domain. If one of these computers are retired, the resultant computer after the merge will also be "retired".
  • Inventory Solution 6.1 introduced a new scheduled task called NS.Clean-up Old Inventory Data. This runs at 12:00 midnight daily and sets the IsManaged bit from 1 to 0 and deletes all of the computer's inventory data. Its purpose is to free up licenses for computers that are no longer active.


The merge query was modified to include the following lines which will flag the computer to "active" after the merge has taken place:

Update ResourceAssociation set childresourceguid = '{0A0203A5-D2B6-49F1-A53B-5EC31A89437C}' where ParentResourceguid = @ToGuid and resourceassociationtypeguid like '302816%'

Applies To
Notification Server 6.0 SP3 R2