My suggestion, add a step when de-provisioning that deletes the object from sccm.
You can do this with a web front-end. http://eskonr.com/2012/04/vb-script-delete-computer-from-sccm-database/ (script) http://mdtcustomizations.codeplex.com/discussions/247915 (web service + script) Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Thursday, August 15, 2013 2:40 PM To: '[email protected]' Subject: [mssms] SCCM 12 client on reused hardware Like every other company, we tend to use a naming convention that includes an asset tag. SCCM will install the client and all that jazz, but let's say that person leaves the company after a month. So the help desk guys take the machine, do their thing, then reimage it. Our current imaging solution is not using SCCM and the client is not installed on it. So in SCCM it shows the machine name, and says it has a client but that it is inactive. Makes sense since it no longer can find that machine with the agent. So how do I get it to check if the agent is there, and if not to install it? It does that for a brand new machine, but because the machine name is reused it does nothing. If I click on Deploy agent, then everything is fine.... But I would like to make it a bit more automated as I have a bunch of inactive machines that I know have been deployed. *note, we are currently using MDT 2010 U1 for our image deployment, and will be making the trip to SCCM12 in the next few months.* Thanks, Kevin Johnston
<<inline: image001.jpg>>
