frazeraccount

Thanks for the post. Similar symptom on a 2012 client's WUAHandler.log: OnSearchComplete - Failed to end search job. Error = 0x80244007 Resolution was to disable Windows Firewall.

I have question about the clientlocation.log file on a client within the ip range boundary of a secondary site. Everything seems to be working just fine with the client, however I'm a bit concerned about what I see in the clientlocation.log file. Here are the facts. Names have been changed to protect the innocent. :-) You will notice that the "current management point" alternates between the primary and secondary site server. This has been going on ever since the client was installed. The same loop repeats itself every few minutes. Primary Site Server Name: sccmpri Secondary Site Server Name: sccmsec Log contents excerpt: GetCurrentManagementPointEx ClientLocation 2/29/2012 12:56:28 PM 1300 (0x0514) Current Management Point is sccmsec.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 12:56:28 PM 1300 (0x0514) GetCurrentManagementPointEx ClientLocation 2/29/2012 12:56:28 PM 1300 (0x0514) Current Management Point is sccmpri.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 12:56:28 PM 1300 (0x0514) GetCurrentManagementPointEx ClientLocation 2/29/2012 1:03:22 PM 5912 (0x1718) Current Management Point is sccmsec.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 1:03:22 PM 5912 (0x1718) GetCurrentManagementPointEx ClientLocation 2/29/2012 1:03:22 PM 5912 (0x1718) Current Management Point is sccmpri.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 1:03:22 PM 5912 (0x1718) GetCurrentManagementPointEx ClientLocation 2/29/2012 1:06:28 PM 5212 (0x145C) Current Management Point is sccmsec.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 1:06:28 PM 5212 (0x145C) GetCurrentManagementPointEx ClientLocation 2/29/2012 1:06:28 PM 5212 (0x145C) Current Management Point is sccmpri.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 1:06:28 PM 5212 (0x145C) GetCurrentManagementPointEx ClientLocation 2/29/2012 1:13:22 PM 6640 (0x19F0) Current Management Point is sccmsec.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 1:13:22 PM 6640 (0x19F0) GetCurrentManagementPointEx ClientLocation 2/29/2012 1:13:22 PM 6640 (0x19F0) Current Management Point is sccmpri.domain.com with version 3000 and capabilities: <Capabilities></Capabilities>. ClientLocation 2/29/2012 1:13:22 PM 6640 (0x19F0) I searched the Internet for sample clientlocation.log files but came up with bupkus. Does this look normal, or do I have a problem? Any feedback would be appreciated!

I had SCCM 2007 working just fine. I added the SCCM 2007 dashboard Solution Accelerator from MS, which required installation of Windows Sharepoint Services 3.0 SP2. I installed it on my Central Site Server and being naive about Sharepoint I didn't realize it installs on port 80, which caused my management point site running on port 80 to stop. I had to extend the sharepoint site to a new site using a different port and delete the sharepoint site using port 80. After that I was able to restart the management point site. During the time the management point site was down, the client could be deployed but they would exhibit the same symptoms discussed in this thread...unable to get the SCCM site version. Once the site came back up, everything worked as expected on the client. Moral of the story is, make sure your management point site is working. If your client can't reach it, it can't determine the version. Use the following URL to connect to your primary site server. It should list each management point's name, FQDN, version, and capabilities schema version: http://<site server name>/sms_mp/.sms_aut?mplist Sample Ouput: - <MPList> - <MP Name="<Site Server 1>" FQDN="<Site Server 1>.yourdomain.xxx"> <Version>6487</Version> <Capabilities SchemaVersion="1.0" /> </MP> - <MP Name="<Site Server 2>" FQDN="<Site Server 2>.yourdomain.xxx"> <Version>6487</Version> <Capabilities SchemaVersion="1.0" /> </MP> </MPList>

Hotfix available: http://support.microsoft.com/kb/978021