SCCM Clients showing client status as NO in SCCM console

Hi Experts,
I have strange issue though SCCM Client is installed on computers unfortunately I see client status as NO on about 20% of the computers.I have done some googling on it and I found it could happen due to same GUIDS.May I know how can I repair this part for all computers at same time.

Many thanks..
ameenfusionAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
KezziConnect With a Mentor Commented:
Create a new collection that holds all machines listed as not having a client.  Then right click the collection and select to uninstall the client. then right click and select to reboot them when you know they are not in use and reinstall. (you could try do the reinstall after about 30mins of it being uninstalled to make sure all memory based components have cleared instead of rebooting?)
0
 
KezziCommented:
Try this first to see if it resolves it:

The client installation status is extracted when the Discovery Agent runs on the machine.  If you have SCCM console extensions installed (3rd party tools), you can right click a collection or machine and initiate the Discovery Client action.  Give it up to 10min to collect the data, then update and refresh your collection and see if its updated its client status.
0
 
ameenfusionAuthor Commented:
Thanks Kezzi,
Just now I have installed SCCM Client extension 1.6 but unable to find the option" initiate the Discovery Client action".However please find attached screenshot .Do you mean to try allocate new SMS GUID...?

Many thanks
Client-extension-option.jpg
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
KezziCommented:
use the menu option just above it called SCCM Client Actions.
0
 
ameenfusionAuthor Commented:
Please find attached screen shot, when I try to perform any sccm client action following error gets displayed.

Client-extension-option02.jpg
0
 
KezziCommented:
If you try initiate a client action and it fails to find the provider, then the WMI class is not present on the machine and/or it cannot access its registry.

uninstall the client from the machine, repair wmi, then reinstall the client.

http://trevorsullivan.net/2009/11/06/wmi-repository-corruption-sccm-client-fix/
0
 
ameenfusionAuthor Commented:
HI Kezzi,
I could have done that but the problem is I have about 100+ such clients I am looking for some thing to do this type of thing automatically at one go or group wise.Can we do this..?
0
 
KezziCommented:
ok first attempt client repairs then.  using the console extensions, initiate a repair of the client.  (maybe create a collection that lists machines with no clients so you can initiate it against the collection)

If after 30mins, the clients are still not showing as installed, then you could attempt a script to automate the wmi repair - which i could write for you if we get to that.
0
 
ameenfusionAuthor Commented:
Sorry Kezzi I tried to repair still same issue after 1 hr.

Please find  attached files.Please let me know if you need more.
CcmExec.log
CcmRepair.log
0
 
KezziCommented:
Can you post this log file please:
C:\WINDOWS\system32\CCM\logs\repair-msi-2609EDF1-34C4-4B03-B634-55F3B3BC4931.log
0
 
ameenfusionAuthor Commented:
HI Kezzi,
Please find attached file.
repair-msi-2609EDF1-34C4-4B03-B6.log
0
 
KezziCommented:
can you try using the tools to invoke an uninstall of the client, reboot the machine, then try the install again?
0
 
merowingerCommented:
How is your Heartbeat Discovery configured.
Also tell us how your Maintenance Tasks are configured
0
 
ameenfusionAuthor Commented:
Hi Mero,
Please find attached Heartbeat Discovery and Maintenace tasks.
Can you please tell me which maintenance task configs would you like me to send...?

Many thanks..
Heartbeat-discovery.jpg
Maintenance-task.jpg
0
 
merowingerCommented:
I can see that you Clear Install Flag Task is not enabled so the Clients are not set to "No" by this SCCM Task
0
 
KezziCommented:
ameen did you try the uninstall, reboot, reinstall of the client on one of the machines?
0
 
ameenfusionAuthor Commented:
Do you want me to turn on Clear Install Flag Task and If I do will that make a difference...?
0
 
ameenfusionAuthor Commented:
Hi Kezzi,
That desktop is one of the doctors desktop so I am afraid to say I cannot touch it either.

That is the reason I was asking some remote methods.
0
 
KezziCommented:
not in this case ameen.  the issue these machines have is related to wmi problems on the machines.  the clear install flag is just to make sure that your client push installations are successfull and report that the client is installed before the client push attempts to install the client.
0
 
KezziCommented:
you can use the tools you have installed for this.  there is a client uninstall tool in your 3rd party extension list.  you could try uninstalling and waiting some time before the reinstall.  If you have 50 clients reporting this issue, then dont you have another machine to test this on?
0
 
ameenfusionAuthor Commented:
Thanks KezzI yes I did find one computer that can be tested.Please let me know what should be the next step.

Many thanks
0
 
KezziCommented:
uninstall the client via the tools, then reboot the system, (you might have that tool depending on which ones you installed) and then initiate the install of the client again.
0
 
ameenfusionAuthor Commented:
Morning  Kezzi,

Now I can see this machine is showing after restart and re installation of SCCM client.

What do you think should be done if the same situation is there on 100+ clients...?
0
 
ameenfusionAuthor Commented:
Can we schedule a collection to get restarted at night time..?
0
 
MarkieSCommented:
Hi Guys and Gals,

I have a useful script that you can run.

It takes a text file of computer host names - ie a list you can extract that has your "Client = NO"

Using PSEXEC it runs a batch file to repair WMI on the faulty PCs.

In this way WMI is repaired on each of the faulty PCs and they all start communicating properly again...


REMOTE-WMI-FIX.vbs
0
 
MarkieSCommented:
Dont know what happened there!!!  Should have attached 2 files...  As below

Download the two files to a folder.
Create a file called computers.txt and populate it with the host names of the faulty machines
Place a copy of PSEXEC.EXE in the same folder.

(Note: PSEXEC.EXE is part of the Microsoft SysInternals suite) REMOTE-WMI-FIX.vbs rebuildWMI.txt
0
 
MarkieSCommented:
Dont forget to save rebuildWMI.txt as rebuildWMI.bat
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.