Hi,

SCCM 2007 R3 on Win2008 R2 Std

I have a problem with SCCM Client, installation completes and i can see the Configuration Manager (32Bit) icon in the Control Panel but when i am trying to advertise packages it doesn't work  then i found that under Configuration Manager (32Bit) - Action - it shows only two items as in the screen below.

i checked the ccmsetup log file and found this warning message.

There is a similar case on this forum but its not exactly the same in my situation.

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/3ee35189-ed41-4c69-a12d-74f70c7e36e1

and i followed these to fix this but still the same.

http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/dd605cc7-0510-4cae-83e5-cd3bd7b138c0/

 on this one it suggest manually uninstalling Microsoft WIMGAPI? but i am not sure how.

http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/2d56caeb-d439-415a-a499-e6566bae4215

1 - I tried Installing through GPO, manual and all other options Client 

2 - Restarting machine

3 - and i also used "SCCM Client Center (SMSCliCtr)" product to test the client machine from SCCM server everything seems to be fine.

I have seen this specifically happening with Win7 Enterprise OS now two cases so far.

Please suggest.

Regards,

M

do you have the same error on all sccm clients or just this one?

I would start by looking at the clients' locationservices.log and clientlocation.log, then check if the IP address of the client is under any of the boundaries you have configured or not?

more info over here: http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx

Right now just one machine with this problem and i could see this client on SCCM Server with correct boundaries and everything.

Regards,

maqsood

If you have the control panel applet, then setup finished and thus looking at ccmsetup log is not going to help.

You need to look at the operational logs like clientlocation.log and locationservices.log?

You said you can "see" the client on the server. What does that mean? Is it marked with client = Yes?

Hi Jason,

It shows this for the client.

And i am trying to get the log files from the machine as the user is not available at the moment.

Regards,

Maqsood

Actually, that's not the client if it says "no". That's just a resource that was discovered. If client = "no" like this in the console, that means the client is not successfully communicating with the site.

Thus, you need to start looking at client side log files as suggested.

Hi Jason,

I have another instance of the same issue and i am going through the logs and out of all files i found this on  in the CCM\Logs\LocationService.log file

Does this relate to the problem?

and this on SmsClientMethodProvider.log

And on smscliui.log file i find many errors, please suggest.

It appears to be a WMI issue

Try the below

For Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, you can run winmgmt /verifyrepository from a command prompt.If repository is found to be inconsistent:

    a. For Vista and newer, run from elevated command prompt:

Winmgmt /salvagerepository

Note this command will take the content of the inconsistent repository and merge it into the rebuilt repository if it is readable

If the above doesnt work, then run:

Winmgmt /resetrepository

After which restart your machine and check the logs again

I tried these already.

winmgmt /verifyrepository 

Winmgmt /salvagerepository

Winmgmt /resetrepository

Regards,

Maqsood

I found the issue with duplicate DNS records as SCCM was resolving the client name to the old IP address so after cleaning up DNS the client started reporting on the Server.

Regards,

Maqsood

That's coincidental and not the source of the issue. Once the client agent is installed on a system, *all* client communication is client initiated which means the server never performs a DNS lookup of the client because it is simply responding back to traffic using the source IP.

It's possible that the server re-pushed the client agent (using the updated DNS record) and that fixed the client issue, but I wouldn't really put a high probability to that but I can't say for sure.