We are running SCCM 2007 SP2 in mixed mode. We are trying to update one of our images that employees use at home (workgroup not domain pc). The image had SCCM SP1. We ran SP2, but the components never go to enabled and clicking discover produces automatic site discovery was unsuccessful. We do have SLP defined in WINS. Any help at what to look at would be appreciated. from locationservices.log Raising event: instance of CCM_CcmHttp_Status{ ClientID = "GUID:4F90A0CC-F0EE-4D16-A060-AE10E461F927"; DateTime = "20100403042055.031000+000"; HostName = "SMSPRI001.HOSP.NET"; HRESULT = "0x00000000"; ProcessID = 2456; StatusCode = 0; ThreadID = 2212;}; LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)Failed to validate thumbprint with error 0x80070057. LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)Raising event: instance of CCM_CcmHttp_Status{ ClientID = "GUID:4F90A0CC-F0EE-4D16-A060-AE10E461F927"; DateTime = "20100403042055.062000+000"; HostName = "SMSPRI001.HOSP.NET"; HRESULT = "0x00000000"; ProcessID = 2456; StatusCode = 0; ThreadID = 2212;}; LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)Failed to refresh trusted key info with error '0x80040304'. LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)Failed to validate the certificate '308201EA30820153A003020102021023EAC09059553C9D4916150F0EDB3824300D06092A864886F70D01010505003026311630140603550403130D46484F53534D53505249303031310C300A06035504031303534D533020170D3130303332373137313733375A180F32313130303330343137313733375A3026311630140603550403130D46484F53534D53505249303031310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D00308189028181009AEEEA80A38B2B011C48697058F419CDB9E5D22777859D1871E60E6718B51C8983F4FBBD434F2C067D8C898D9A72E28ED63EC97C7AD5739CA9C34B05A4F6744C8611A6B1B134D107BE542B0107196D93C38E13274433A725D0B91AE611C0A7E0F1DBAB79A73E3266A7F8206F017167BCDA02A95A9BE1391D52D5AD621586FDAB0203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D0101050500038181000FCA5117A734F4F3232F385255B3D1449B901F407EF171BC61D168ECCC62A4A26B5973BDAA77A54AE169166CD70FE9262F4F9EACAF0C928308AFD1E0CF05AE4F65D12D416B5BF58AC199FE849094B7B5DB80213014EAE18E68FD47F60A6C3C70F05028FDB370FB81B98F6DB2C6DF6CA3A1425AD7660B083E75FFC3B2BA7B9FA9' from management point 'SMSPRI001' LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)Raising event: instance of CCM_LocationServices_ManagementPointCertificate_CrossVerificationFailure{ ClientID = "GUID:4F90A0CC-F0EE-4D16-A060-AE10E461F927"; DateTime = "20100403042055.078000+000"; ManagementPoint = "SMSPRI001"; ProcessID = 2456; ThreadID = 2212;}; LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)Refreshed Certificate Information over HTTP LocationServices 4/3/2010 12:20:55 AM 2212 (0x08A4)DhcpGetOriginalSubnetMask entry point not supported. LocationServices 4/3/2010 12:25:02 AM 3772 (0x0EBC)Unable to retrieve AD site membership LocationServices 4/3/2010 12:25:02 AM 3772 (0x0EBC)Raising event: instance of CCM_CcmHttp_Status{ ClientID = "GUID:4F90A0CC-F0EE-4D16-A060-AE10E461F927"; DateTime = "20100403042503.062000+000"; HostName = "172.24.235.90"; HRESULT = "0x00000000"; ProcessID = 172; StatusCode = 0; ThreadID = 3772;}; LocationServices 4/3/2010 12:25:03 AM 3772 (0x0EBC)LSGetAssignedSiteFromSLP : No site code returned from SLP LocationServices 4/3/2010 12:25:03 AM 3772 (0x0EBC)------------------------------------------------------------ From CCmexec Raising event: instance of CCM_CcmHttp_Status{ ClientID = "GUID:4F90A0CC-F0EE-4D16-A060-AE10E461F927"; DateTime = "20100403042455.171000+000"; HostName = "SMSPRI001.HOSP.NET"; HRESULT = "0x00000000"; ProcessID = 2456; StatusCode = 0; ThreadID = 2212;}; CCMEXEC 4/3/2010 12:24:55 AM 2212 (0x08A4)HandleRemoteSyncSend failed (0x80040309). CCMEXEC 4/3/2010 12:24:55 AM 2212 (0x08A4)CForwarder_Sync::Send failed (0x80040309). CCMEXEC 4/3/2010 12:24:55 AM 2212 (0x08A4)CForwarder_Base::Send failed (0x80040309). CCMEXEC 4/3/2010 12:24:55 AM 2212 (0x08A4)

}; LocationServices 4/3/2010 12:25:03 AM 3772 (0x0EBC)LSGetAssignedSiteFromSLP : No site code returned from SLP LocationServices 4/3/2010 12:25:03 AM 3772 (0x0EBC)------------------------------------------------------------ Hello, I would doublecheck the SLP/WINS records... the boundaries etc.. Aren't you using some new VLAN/subnet dedicated to the Home pc..?Checking NSLOOKUP also for name resolution possible problems.. One the server, no interesting logs ? After a SP2 Upgrade, I force me to look in quite every piece of Logs..(and mostly if in native mode)do you publish in DNS ? is the SLP role running Well ? Which results when you install the client with the parameters ? ( client.msi property SMSSLP=<server locator point name>) Concerning the image, personaly, I use both following methode to generate the Images:1 - I use of course the Build and Capture TS ..2 - or I don't put the sccm agent in the master image.. and I use one MDT-integrated "Capture WIM" TS to capture the syspreped image I like both, 2- can be used to quickly build one image outside of SCCM, with only the OS, sysprep and capture, then test the deployment...2 - also bring the possibilities to use one WIM for many images.. Most valued url is the following one :) http://technet.microsoft.com/en-us/library/bb632435.aspx Configuration Manager and Service Location (Site Information and Management Points) How Clients Find a Server Locator Point If clients require a server locator point, this site system's IP address, short name, or fully qualified domain name (FQDN) can be specified when the client is installed using the client.msi property SMSSLP=<server locator point name>. Make sure that a specified short name or FQDN can be resolved using WINS or DNS. For more information about client installation command line options, see About Configuration Manager Client Installation Properties. If the server locator point is not directly assigned during client installation, clients can locate it through Active Directory Domain Services or WINS: Clients can automatically find a server locator point through Active Directory publishing if they are in the same Active Directory forest as the site server. This scenario applies if the Active Directory schema has been extended for SMS 2003 but not extended for Configuration Manager 2007. When these conditions apply, there is no requirement to specify the server locator point during installation or manually publish it in WINS. If you have not extended the Active Directory schema for either SMS 2003 or Configuration Manager 2007, clients can automatically find a server locator point if it is manually published in WINS and if clients have not been installed with the SMDDIRECTORYLOOKUP installation property. For more information about manually publishing the server locator point in WINS, see How to Manually Add Configuration Manager Site Information to WINS. Note Although native mode clients cannot locate management points through WINS, they can locate server locator points through WINS. Clients cannot locate server locator points using DNS publishing. Clients first try to use the server locator point if it is specified on the command line, and if this fails they then try to locate a server locator point from Active Directory Domain Services, and if this fails they then try WINS.