Interesting. They're VMs, and I think just before they were shut down, they had been moved between hosts, so maybe that's what caused it? The heartbeat interval is at the default setting of 7 days, but is there a way to manually kick it off?

Initiate a "discovery data cycle" on the client or use one of the right click tools remotely.Torsten Meringer | http://www.mssccmfaq.de

Thanks Torsten. I've done that for the 3 clients, just waiting now to see if they update.

Is there a way of finding out when exactly the next heartbeat discovery is scheduled for? I have 3 clients that were offline for a period of time, and now they are marked as Obsolete. I would like to know when they'll be rediscovered, as they are back online, hopefully for keeps now. Also, how long does a client have to be offline to be marked Obsolete?

They will be added to the database again, You can see the heartbeat interval by opening the properties (by default every 7 days).Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Heartbeat discovery runs according to the schedule you have setup for it and is based on the agent's original startup time (http://technet.microsoft.com/en-us/library/bb693896.aspx). Clients are not marked as obsolete for being offline though; they are marked as obsolete because the client record was superseded by a newer one for the same client which is determined by the hardware ID: http://technet.microsoft.com/en-us/library/bb632879.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys