Fresh 2008 R2 box SCCM 2007 SP2 client install issues, other machines in the forest work just fine and can be seen by the Primary site server. The machine that succeeded and the machine that failed are both fresh images and identical in everyway including OU/Container and local permissions. I didn't see an option to attached the logs here. Below are the errors that stand out, though they are generic. The below flags were set on the install on both machines. ccmsetup /noservice smsmp=PRIMARYSITESERVER smssitecode=PRI fsp=PRIMARYSITESERVER smsslp=PRIMARYSITESERVER dnssuffix=PRIMARYSITESERVERSUFFIX Client.msi CCM_Service_ErrorHandlerRegistration.Clsid="{0F95BCE5-2209-488a-B4BC-4396AD233C8D}" Property(S): WelcomeDialog_Info = This will install the Systems Management Server Advanced Client. Property(S): WelcomeDialog_DesktopWarning = WARNING: The SMS Legacy Client or SMS 2.0 Client is already installed on this machine. Continuing will cause the SMS Legacy Client or SMS 2.0 Client to be removed. Property(S): WelcomeDialog_EULA = The software you are about to install is provided as part of Systems Management Server 2003 and as such, is subject to the End User License Agreement already accepted by your system administrator. If you have any questions, please contact your system administrator. Property(S): ConfigDialog_Title = Configuration Property(S): ConfigDialog_SubTitle = Select installation options Property(S): ConfigDialog_Info = Enter configuration options for the Configuration Manager Client. Property(S): ConfigDialog_SiteCode = SMS Site: Property(S): ConfigDialog_InvalidSiteCode = The site code you have entered is not valid Property(S): InstallDialog_Title = Install Property(S): InstallDialog_SubTitle = The product is now ready to install Property(S): InstallDialog_Info = Click Next to proceed. Property(S): InstallDialog_Warning = WARNING: Installing the advanced client on this computer may cause the Windows Management Instrumentation (WMI) and Background Intelligent Transfer Service (BITS) services to stop and restart. Property(S): ProgressDialog_Title = Please Wait Property(S): ProgressDialog_SubTitle = Setup is configuring your system. Property(S): CompleteDialog_Title = Setup Complete Property(S): CompleteDialog_SubTitle = Setup has finished updating your system. Property(S): CompleteDialog_Info = The Configuration Manager Client setup was successful. Property(S): UserExitDialog_Title = Setup Aborted Property(S): UserExitDialog_SubTitle = Setup was cancelled Property(S): UserExitDialog_Info = The Configuration Manager Client setup was cancelled. Property(S): InstallErrorDialog_Title = Setup Aborted Property(S): InstallErrorDialog_SubTitle = Setup failed Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue. Property(S): UATData.9180931B_6ABA_475F_8007_1211E0D725BA = C:\Windows\SysWOW64\CCM\UATData\ Property(S): bin.9180931B_6ABA_475F_8007_1211E0D725BA = C:\Windows\SysWOW64\CCM\core\bin\ Property(S): WelcomeDialog_Info = This will install the Systems Management Server Advanced Client. Property(S): WelcomeDialog_DesktopWarning = WARNING: The SMS Legacy Client or SMS 2.0 Client is already installed on this machine. Continuing will cause the SMS Legacy Client or SMS 2.0 Client to be removed. Property(S): WelcomeDialog_EULA = The software you are about to install is provided as part of Systems Management Server 2003 and as such, is subject to the End User License Agreement already accepted by your system administrator. If you have any questions, please contact your system administrator. Property(S): ConfigDialog_Title = Configuration Property(S): ConfigDialog_SubTitle = Select installation options Property(S): ConfigDialog_Info = Enter configuration options for the Configuration Manager Client. Property(S): ConfigDialog_SiteCode = SMS Site: Property(S): ConfigDialog_InvalidSiteCode = The site code you have entered is not valid Property(S): InstallDialog_Title = Install Property(S): InstallDialog_SubTitle = The product is now ready to install Property(S): InstallDialog_Info = Click Next to proceed. Property(S): InstallDialog_Warning = WARNING: Installing the advanced client on this computer may cause the Windows Management Instrumentation (WMI) and Background Intelligent Transfer Service (BITS) services to stop and restart. Property(S): ProgressDialog_Title = Please Wait Property(S): ProgressDialog_SubTitle = Setup is configuring your system. Property(S): CompleteDialog_Title = Setup Complete Property(S): CompleteDialog_SubTitle = Setup has finished updating your system. Property(S): CompleteDialog_Info = The Configuration Manager Client setup was successful. Property(S): UserExitDialog_Title = Setup Aborted Property(S): UserExitDialog_SubTitle = Setup was cancelled Property(S): UserExitDialog_Info = The Configuration Manager Client setup was cancelled. Property(S): InstallErrorDialog_Title = Setup Aborted Property(S): InstallErrorDialog_SubTitle = Setup failed Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue. Property(S): UATData.9180931B_6ABA_475F_8007_1211E0D725BA = C:\Windows\SysWOW64\CCM\UATData\ Property(S): bin.9180931B_6ABA_475F_8007_1211E0D725BA = C:\Windows\SysWOW64\CCM\core\bin\ CCMsetup.log simply generates the below generic errors. MSI: Setup failed due to unexpected circumstances The error code is 80004005 ccmsetup 2/8/2011 1:59:55 PM 3964 (0x0F7C) Installation failed with error code 1603 ccmsetup 2/8/2011 1:59:55 PM 3964 (0x0F7C)

Those property listings can be safely ignored. They have nothing to do with the actual error. Search for "return value 3" and you'll find the real reason for the failure a few lines above it.

Below are the only two that return, generic error code is 80004005. I've already tried the steps outlined in http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/af6e3858-d79e-49e6-8caa-c36cb57cfdff MSI (s) (04:58) [13:59:55:032]: Doing action: CcmSetObjectSecurityInit Action ended 13:59:55: CcmFixupServiceConfigInit. Return value 1. MSI (s) (04:58) [13:59:55:032]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CcmSetObjectSecurityInit' MSI (s) (04:58) [13:59:55:032]: Creating MSIHANDLE (14932) of type 790542 for thread 4184 MSI (s) (04:74) [13:59:55:032]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB709.tmp, Entrypoint: CcmSetObjectSecurityInit MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14933) of type 790541 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14934) of type 790540 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14935) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14936) of type 790540 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14937) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Closing MSIHANDLE (14937) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14938) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Closing MSIHANDLE (14938) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14939) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Closing MSIHANDLE (14939) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14940) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Closing MSIHANDLE (14940) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:032]: Creating MSIHANDLE (14941) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:048]: Closing MSIHANDLE (14941) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:048]: Closing MSIHANDLE (14936) of type 790540 for thread 844 MSI (s) (04!4C) [13:59:55:048]: Creating MSIHANDLE (14942) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:048]: Creating MSIHANDLE (14943) of type 790531 for thread 844 Action start 13:59:55: CcmSetObjectSecurityInit. MSI (s) (04!4C) [13:59:55:063]: Closing MSIHANDLE (14943) of type 790531 for thread 844 [13:59:55] @@ERR:25001 MSI (s) (04!4C) [13:59:55:063]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (04!4C) [13:59:55:063]: Closing MSIHANDLE (14935) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:063]: Closing MSIHANDLE (14934) of type 790540 for thread 844 MSI (s) (04!4C) [13:59:55:063]: Closing MSIHANDLE (14942) of type 790531 for thread 844 MSI (s) (04!4C) [13:59:55:063]: Closing MSIHANDLE (14933) of type 790541 for thread 844 Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (04:74) [13:59:55:063]: Closing MSIHANDLE (14932) of type 790542 for thread 4184 CustomAction CcmSetObjectSecurityInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (04:58) [13:59:55:063]: Machine policy value 'DisableRollback' is 0 MSI (s) (04:58) [13:59:55:063]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 13:59:55: CcmSetObjectSecurityInit. Return value 3. MSI (s) (04:58) [13:59:55:063]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (04:58) [13:59:55:063]: No System Restore sequence number for this installation. MSI (s) (04:58) [13:59:55:063]: Unlocking Server Action ended 13:59:55: INSTALL. Return value 3. Property(S): UpgradeCode = {252DA259-82CA-4177-B8D0-49C78937BA3E} Property(S): SourceDir = C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\ Property(S): TARGETDIR = C:\Windows\SysWOW64\CCM\ Property(S): ALLUSERS = 1 Property(S): ErrorDialog = ErrorDialog Property(S): ProductName = Configuration Manager Client Property(S): ProductCode = {2609EDF1-34C4-4B03-B634-55F3B3BC4931} Property(S): PackageCode = {4CD82FBB-0AFC-4864-A089-15364DF5F14B} Property(S): Manufacturer = Microsoft Corporation Property(S): ProductVersion = 4.00.6487.2000 Property(S): ProductLanguage = 1033 Property(S): SystemFolder = C:\Windows\SysWOW64\

In an attempt to recreate the problem in a isolated training environment I am able to re-create the issue on another fully patched 2008 NON R2 box but not on a 2003 machine. Are they any known issues with 2008 server and 2008 R2 for the 2007 SCCM sp2 client that I am not aware of? All signs point to iwam or iusr issues but this is a 2008 R2 machine so if I understand correctly it doesn't have the _COMPUTER versions of those accounts.