I'd suggest a logon script that searches for the client and then installs it if it isn't there.
On Thu, Aug 15, 2013 at 1:39 PM, Kevin Johnston < [email protected]> wrote: > 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**** > > ** ** > >
