How is the install_status on network adapter set to absent

[dthenderson]

I am working with a client trying to understand how CI's like network adapters and IP addresses get set to a status of "Absent" if they are not being scanned any longer.   We used a windows server in the lab as our test subject.   We discovered it. Looked up the IP and NetAdapter.   We then shut the server down and rediscovered.   We expected after 5 subsequent discoveries of this device that it would set the IP address and NetAdapter status to "Absent".  

Can anyone help me understand how this concept is supposed to work?   Is there a counter table somewhere that only sets the status after so many scans?   Is there a number of days that must pass before these should be set to absent?

Thanks in advance,

-Terry

[Dave Ainsworth]

Hi Terry,

It sounds like from above, you are shutting down the Windows server so that it is not discoverable? In this case, the install status of the adapters will not change because the Windows server is not discoverable. There could be a number of reasons for a Windows server not being discoverable such as being shut down temporarily for maintenance or credentials failing to work but the network adapter is still there and so because discovery can't check the status of the network adapter, it does not change it.

If you were to disable a network adapter or remove it so that the discovery results no longer contained the adapter, the install status will change to absent after a successful discovery.

Regards,

Dave

[dthenderson]

We were testing in an attempt to see what we could do upon decommissioning of a server.   Is our only recourse to run a business rule that checks the 'Most recent discovery' date and then set to an inactive state for server components like IP and Network Adapter?   We were hoping that if the server becomes inactive, the CI's attached would be set to inactive so that they can be investigated and deleted if necessary?

Thanks,

-Terry