SCCM Client uninstall
Hi All, My Scenario is as follows: I have SCCM Central server, connected with SCCM Secondary sites. SCCM client is installed on the machines at Central & secondary sites. I had a reconcillation issue between the discovered count in SCCM and present AD system count. So I enabled a task, Delete Obsolete client discovert data for all days. After this, on one day all my discovered SCCM count seen to be goes down from 5000 to 2000 discovered items. This also decreased my installed sccm client count. I rediscovered all system again & then discovery starts to increases again and after 4 days it reaches to earlier count. In this my installed count had decreased and it also starts to increase with slow speed. why my discovered count decreases? why installed sccm client showed as uninstalled & again starts to installed. after checked on client machines, we came to know that, SCCM client is still installed on machines, only its status is not updated on SCCM console & so its showing as No for SCCM client.
January 27th, 2011 6:19am

That's most likely because a malfunctioning management point. Please use MP Troubleshooter from ConfigMgr Toolkit V2 and mplist / mpcert: http://technet.microsoft.com/en-us/library/bb932118.aspx
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 6:28am

Hello - Which are the discovery methods enabled in your environment ? Under the discovery options only add the necessary or specific OU details of the clients which you wanted to manage. Are you using Client Push Installation to install the client? or some other method? Also, if a machine is network and SCCM client is installed then the heartbeat discovery will find out the clients and it will show up in the console (if at all you deleted it from console). Go through the following article http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx You can get more details about the status details of the client from the following article http://technet.microsoft.com/en-us/library/bb633138.aspx Anoop C Nair
January 27th, 2011 6:33am

Hi Anoop, only AD system discovery is enabled and on each Secondary server a specific OU is specified for the discovery. Yes, the client push installation is enabled on all secondary sites. gone through the link, but that are if faced issues while installing client or if client status not reach to server while installing client. In my case, SCCM client was installed & it was showing in console as a Yes for Client install. Later on when my discovered count decrease it also moves down the SCCM client install count. after check on machines, sccm client is on system, but status not reach the server
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 7:31am

Have you checked your site maintenance tasks? is the heart beat discovery enabled? http://technet.microsoft.com/en-us/library/bb632595.aspxRegards, Madan
January 27th, 2011 7:47am

Hello - Did you check the points mentioned by Torsten? What is the StatusAgent.log file says ? Is it able to send the stat msg upto MP? Anoop C Nair
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 7:56am

yes, Heart beat discovery under Discovery methods is enabled for Central & all Secondary sites. It is scheduled for 1 week.
January 27th, 2011 8:00am

You said, after the client are discovered, they are again slowly becoming installed clients and in the console it is showing as Yes for SCCM client after few days? True? If no, then it could be a management point issues and please check the management point as suggested by Torsten and Anoop. If yes, could you check the "Clear Install Flag" maintenance task? If it is enabled, then it should be set more than the client heartbeat discovery interval. http://technet.microsoft.com/en-us/library/bb694040.aspx Regards, Madan
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 8:23am

Then from my experience there could two possibilities. 1. Overlapping boundaries. 2. Duplicate GUID (Check the std SCCM report for duplicate GUID machines) Also, you can check the decommission status of the clients from console?Anoop C Nair
January 27th, 2011 1:49pm

yes that was seen earlier, but later on after observation & check on machines we came to know that SCCM client does not get uninstall only the status in SCCM console become NO as discovery varies. Clear Install flag is not enable......... Check MPTEST with mplist & mpcert commands & it works fine
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 2:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics