Hi I am wondering if clients that are deleted will somehow reflect this status in the SCCM console or in the database. We have a VMWare environment that we deploy our servers in and servers are often deleted and replaced. If a server is just deleted and not removed from SCCM is there someway to tell that this machine does no longer exist? I am asking because we are doing license counting and we have a problem with old machines still being shown as active=yes and obsolete=no. Thanks

Not directly no. ConfigMgr does not actively try to communicate with any managed systems so has no way of tracking clients. You can however use Client Status Reporting (CSR) -- part of R2 to track the status of clients by the last time they communicated with ConfigMgr. CSR will also mark clients as inactive based on thresholds you set up. Inacactive clients can then be culled using the Delete Inactive Client maintenance task.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Sorry for the follow up question, but here it is. Machine objects in the SCCM console, under properties -> general, there is a property called agent time [x]. As I understand this value it is a list of the last times the client signed in. When we count licenses we use a custom CMDB that we import data from SCCM into. Is it fair to say that clients that have not updated their agen time property in a month is inactive? If so we could write a SQL query that excludes all machines that have not updated their agent time in a month. That way we could exclude the machines(only servers that are online 24/7) that have not reported in. Is this a good way to weed out outdated servers that do not exists any more?

[x] refers to the agent that discovered the resource (heartbeat, AD system discovery etc). A (no longer existing) resource could also be updated by AD system discovery (if a DNS record is still available). You could have a look at R2's client status reporting tool; it helps to identify inactive clients.Torsten Meringer | http://www.mssccmfaq.de

Hmm well if we only use the heartbeat discovery date then we should be able to weed out old machines. As the heartbeat is only refreshed by the agent. Which one of the agent time [x] is heartbeat? I have looked into the client status reporting tool but as I understand it you have to install and make changes to the infrastructure. We are soon moving over to 2012 and I do not really want to make any larger changes now. I see the proposal above as a quick solution until we get over on 2012.