Common client agent settings for the client are missing from wmi
I know a similar question was asked in another post, but my issue is a bit different. I installed the client over the network and SCCM is showing that no client is installed. The client is showing the company name instead of "It Organization" and I can't find any errors other than "common client agent settings for the client are missing from wmi" in the smscliui.log file. ccmexec.log is fine and so are policyagent policyevaluator clientlocation locationservices
August 26th, 2010 1:54am

Few things I would check in the following order. 1 Go to the client control panel- configuration manager - Advanced Tab -- Discover -- It not successful.. then check the if the clients is part of SCCM boundaries. 2 Check the locationservices log if it is able to find the management point. 3 Update collection membership on collection to see if that updates the status of the client.
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2010 5:42am

Hi, Did this happen on every client or just some specific computers? Please try the following steps on one problematic client: 1. Copy the ccmdelcert.exe(it can be found where you have installed SMS 2003 Toolkit 2, "C:\Program Files\SMS 2003 Toolkit 2\" ) file to C:\ drive on client PC. Download details: Systems Management Server 2003 Toolkit 2 http://www.microsoft.com/downloads/details.aspx?FamilyID=61e4e21f-2652-42dd-a04d-b67f0573751d&displaylang=en Note: This toolkit is designed for SMS 2003, but the ccmdelcert command can be still used for SCCM client. 2. Open command prompt with Admin right and type command - net stop ccmexec .It will show message - SMS Agent has been stopped successfully. 3. Now type cd\ on command prompt and press Enter button. 4. Now type ccmdelcert.exe and press Enter button. It will show below message - Certificate has been deleted successfully. 5. Now type net start ccmexec. It will show message - SMS Agent host has been started successfully. After 5 min update collection membership for All System collection. if Still not updated check if there is problem with WMI on client PC Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
August 27th, 2010 8:56am

In going through my old posts, I realized that I never followed up on this issue. Although this problem continues to happen, here's the fix that works in my network: Update collection membership at the top level of the collections node. Search for the computer name, delete the entry labeled as obsolete if you have two records. Then, run machine policy and retrieval on the client, wait about 30 minutes, and then confirm that the SCCM server shows the client is installed. In extreme cases, you may have to do the following: Delete the computer out of AD, delete any records of that computer in SCCM under all systems. Run a discovery operation, wait 30 minutes or so. Then, right-click the top level collections node and select update collection membership. Check the all systems node and verify that the computer is now there and it should show no client installed. At this point, manually install the client on the computer. Then, run the machine policy and retrieval on the client, wait about 30 minutes and confirm that the SCCM server shows the client is installed. One last thing, make sure the computer falls within the boundary of your SCCM server. I know I didn't go into specifc details on how to complete all steps but if anyone needs more specifics, feel free to post a follow up or email me (I think my email address is on my profile).
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2011 8:11pm

Abraham, Not sure what brought me to this page, but I have issues with this as well. If I have all actions listed under the action tab, and using the RighClick tools I can initiate a discovery cycle from the server console, then I have had 0 issues with this. As far as getting it to update, that data discovery seems to take care of that. Although I have trouble viewing it in the same collection, If I search for it in another collection...or even better, add it to a collection, it will show up as a Yes under client installed. As long as it is functioning properly, I can deal with the lag in the all systems and other larger containers. Hope this helps someone, I've spent many hours dealing with client end corruption. ce
September 23rd, 2011 4:33pm

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

Other recent topics Other recent topics