Client issues how accurate is 'client installed = yes'

[TechGuy83]

There is 1 machine that stated it had the client installed I went to the machine and it had no client, I went back to the SCCM console did an update collection and refresh it still insisted that the client was installed however when trying to remote control this proved that it wasn't. Looks like the machine had a custom rebuild without going through OSD on the server and for some reason the client push didn't install the client.

 

How sure can you be when it says client installed that it is telling the truth is there a way of checking client health. I did notice the clear install flag task but reluctant to set that up as I am not sure of the knock on effects are, and also the machine was still on and working so not sure this would work anyway.

 

I am not sure if I trust collections that say the client is installed anymore.

 

Any advice on double checking client is installed and healthly on your workstations/servers?

 

Server details:

SCCM 2007 R2 SP2

2003 Standard SP2 R2

[Eswar Koneti]

can you check if the client is installed successfully(able to locate its MP and site by looking at locationservices.log and clientlocation.log) and then check if all the client agents are avalable in configuration manager applet before you troubleshoot.

http://eskonr.com/2010/11/sccm-client-installation-troubleshooting-steps-check-list/

 

to install the SCCM client using client ,you have to configure client push installation account (this account have local admin rights on the target computers) i suppose you could have done this. Please check ccm.log from your site server for client push installation staus.

[TechGuy83]

Thanks for your reply and the link to your blog both most helpful.

 

The client push is working with no issues, however I may not have explained what I was asking properly.

 

The machine in question used to have the client installed and for some reason a tech reimaged the machine by hand (using windows disk), the client push then didn't reinstall. I was unaware that this had happened until I went to deploy software to the machine and remote control it. All new machines that are joined outside of a OSD get the push install fine.

 

Is there any way to be confident that when in a collection it says the client is installed, is 100% correct or do we take with a pinch of salt. In this case it was reporting it was installed when it wasn't.

 

We have many remote working staff and the clear install flag task worries me as sometimes they may not come back to network for couple of months. If the install flag task sets it to no, when they come back on the network will the push set it back to yes?

[mars147]

The client push didnt work thats because your SCCM DB is still knowing the client as installed, meaning your client = 1 in your site DB. When you enable clear install flag, if the client does not send heartbeat to your site server, this task will set that Client = 0 in site DB. Meaning that system is no more sccm client, and your client push will work on the system. Just make sure when the install flag is enabled, you enable Heartbeat discovery with period shorter than the client discovery period (in clear install flag properties).

[TechGuy83]

Ok thanks I have set the clear install flag task. I have set it to 40. My worry is that if a user does not come back to network over 40 days (very possible in our enviroment) and the install flag sets to no, what will happen to the healthly client installed on their device? Will push simply set it back to yes or is it the heartbeat that will set it back to yes?