SCCM agent not installed on re-imaged machines

[checksergio]

Some curious behavior I just noticed, our machines that have had the client pushed to them automatically upon discovery- do not install that client again once re-imaged. Manual push still works on tested machines so that ruled out admin account authentication, IP ranges etc. Someone suggested deleting the old entry from SCCM, and sure enough AD discovery brought the device back again the next day, but still no client.

 

I am 100% sure the solution lies in tuning Heartbeat discovery and the clear flag maintenance task. I have mine set up to run at weekly intervals and the CF task every Saturday, but yet here is Monday and the agent still hasn't deployed yet (but yet that "weekly" interval for Heartbeat discovery is vague so who knows what day it runs on- what log would this be by the way).

 

Any suggestions?

 

Thanks,

[Peter van der Woude]

If you're not using ConfigMgr for the OS deployment, then yes the solution is in tuning the combination of the Heartbeat Discovery and the Clear Install Flag. As long as the console still shows client YES, then the automatic client push will not be performed.

[checksergio]

If you're not using ConfigMgr for the OS deployment, then yes the solution is in tuning the combination of the Heartbeat Discovery and the Clear Install Flag. As long as the console still shows client YES, then the automatic client push will not be performed.

 

Would you happen to know how I can pinpoint the exact time the HB discovery is done? as in day, time ....There must be some kind of log somewhere. Without knowing the exact time, kind of hard to tune the two to work with each other

[Peter van der Woude]

You can look in the properties of the device and look at the Agent Time property. You need the Agent Time that's on the same position as Heartbeat Discovery with Agent Name.