Pour les professionnels de l’informatique >
Forums - Accueil
>
Configuration Manager General
>
Identify Uninstalled Clients
Identify Uninstalled Clients
- Hi,
I have deployed SCCM to many clients in remote sites.
The clients were discovered by AD system discovery and then had the client installed by other deployment tools.
SCCM OSD is not yet in place and when computers are replaced they receive a build image and get the same name as the PC being replaced. I have not yet managed to update the build with the SCCM client.
A third party company does PC replacements and they are not reliable in alerting when a PC is replaced.
I thought that AD discovery would discover a duplicate client object as the new computer object in AD would have a different SID although the name is the same however this does not happen.
Is there a way in SCCM to quickly learn about a replaced computer without having to do some sort of scan outside of SCCM. I need to discover replacements ASAP in order to install the client and apply critical updates
Any suggestions would be appreciated
Thanks,
Jim- Type modifiéYvette OMeallyMSFT, Propriétairelundi 6 juillet 2009 20:54
Réponses
- It's not ASAP, but you could enable the Clear Install Flag task to something low like 7 days (or less); you must also decrease your Heartbeat discovery interval to make this work effectively. The Clear Install Flag, clears the flag on a resource that tells ConfigMgr the resource has the agent installed; it does this if it hasn't received a heartbeat from the resource in the number of days defined. Clearing the install flag allows ConfigMgr to automatically push the client again if you have client pushed enabled. The only danger with lowering the heartbeat interval is if you have systems that aren't turned on or away from the office for more than the interval, they may end up having their install flag reset; i.e., plan this carefully.
You could also enable the Delete Inactive discovery data task and lower it something like 7 days. This task simply deletes the resource from ConfigMgr if the client hasn't sent a heartbeat in the number of days specified. Once deleted, the AD discovery will pick up the system again but will create a new resource that you can manually push the agent to.
Another option is a few third party discovery tools including the Enhanced System Discovery 2007 from System Center Tools.
Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys- Marqué comme réponseYvette OMeallyMSFT, Propriétairelundi 6 juillet 2009 20:54
Toutes les réponses
- It's not ASAP, but you could enable the Clear Install Flag task to something low like 7 days (or less); you must also decrease your Heartbeat discovery interval to make this work effectively. The Clear Install Flag, clears the flag on a resource that tells ConfigMgr the resource has the agent installed; it does this if it hasn't received a heartbeat from the resource in the number of days defined. Clearing the install flag allows ConfigMgr to automatically push the client again if you have client pushed enabled. The only danger with lowering the heartbeat interval is if you have systems that aren't turned on or away from the office for more than the interval, they may end up having their install flag reset; i.e., plan this carefully.
You could also enable the Delete Inactive discovery data task and lower it something like 7 days. This task simply deletes the resource from ConfigMgr if the client hasn't sent a heartbeat in the number of days specified. Once deleted, the AD discovery will pick up the system again but will create a new resource that you can manually push the agent to.
Another option is a few third party discovery tools including the Enhanced System Discovery 2007 from System Center Tools.
Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys- Marqué comme réponseYvette OMeallyMSFT, Propriétairelundi 6 juillet 2009 20:54
