I have SCCM 2007 SP2 R2 installed on 2008 R2 64 bit server, with SQL 2008 installed on a 2008 R2 64 bit server. I'm installing the SCCM Client using the GPO install. It worked great installing on my XP SP3 workstations and Win 7 workstations, however I can't get the client to install on any of my servers most of which are Win 2003 SP2 with a few 2008 R2 servers thrown in just for fun. The GPO is set to use the FQDN of the SCCM server which is also my WSUS server (ver 3.x). Here is what is in the windowsupdate.log 2010-09-30 13:14:33:164 980 4bc AU Featured notifications is disabled. 2010-09-30 13:14:33:164 980 4bc AU Setting AU scheduled install time to 2010-10-02 02:00:00 2010-09-30 13:14:36:445 980 82c Report REPORT EVENT: {C8BC1716-29DF-4EEF-A90F-F58EDC8519CE} 2010-09-30 13:14:31:445-0600 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 1 updates. 2010-09-30 13:14:36:445 980 82c Report REPORT EVENT: {180E47FC-F3DD-4D30-91CA-9AFDCCB91747} 2010-09-30 13:14:31:445-0600 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status. 2010-09-30 13:14:36:445 980 82c Report REPORT EVENT: {06D341E6-E5D1-4162-8877-D1DCFEA00EF8} 2010-09-30 13:14:31:461-0600 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Thursday, September 30, 2010 at 1:14 PM: - Configuration Manager Client Installation 2010-09-30 13:14:36:445 980 82c Report REPORT EVENT: {5DDBA46B-A6CC-4E6A-BF37-952F837A278B} 2010-09-30 13:14:32:086-0600 1 182 101 {72EB686F-B396-4D62-B16F-5284FD2543EE} 1 80070643 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Configuration Manager Client Installation. Of course the error 0x80070643 is just the microsoft "we don't know" code. Any Ideas??? I see lots of articles about updates and SQL failures but nothing on the client failure. Stan

Hex 643 = 1603 which is the generic MSI error code and means you must check the log file for details. You should have a CCMSETUP directory in either c:\windows (64 bit systems) or c:\windows\system32 (32-bit systems) that contains a client.msi.log file that will have more details. Typically, searching for error code 3 will get you close to what the error is, but not always. Finding errors in an msi log is somewhat of an art. Make sure you ignore all of the lines at the end of the log that begin with "PROPERTY", these are just a listing ogf the public properties used by the MSI.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Looked on my servers in both the system32 and sysWOW64 directories for the client.msi.log but don't have one. I do have the CCM directory and the log directory. I see where the policy was started but nothing about it failing. The locationServices.log shows it pointing to the correct management point.

For client.msi.log, make sure you look in the ccmsetup directory in c:\windows (for 64-bit).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I added the AD Site name into the Boundry and my issue went away. Sorry for the delay on this but you how it goes some times.Stan