Copies of install logs are below. MSI installer is updated and WMI is healthy, other MSI installs work well. The client wasn't working properly so an /uninstall was used to remove the client and a reinstall was performed using the below. Runas /netonly /user:gs.fcs.farm\myaccount "\\lansingsccm01.fcs.farm\client\ccmsetup /noservice SMSMP=LANSINGSCCM01.FCS.FARM SMSSITECODE=PRI FSP=LANSINGSCCM01.FCS.FARM SMSSLP=LANSINGSCCM01.FCS.FARM DNSSUFFIX=fcs.farm" Having trouble uploading the ccmsetup.log and the client.msi.log, appears to be a character limit on pastes as well. Client.msi.log highlights CCM_Service_ErrorHandlerRegistration.Clsid="{0F95BCE5-2209-488a-B4BC-4396AD233C8D}" [9:50:08] WARNING: Upgrade Code [{252DA259-82CA-4177-B8D0-49C78937BA3E}] is not a recognized upgrade code MSI (s) (04!F0) [09:50:08:983]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (04!F0) [09:50:08:983]: Closing MSIHANDLE (4983) of type 790531 for thread 5616 MSI (s) (04!F0) [09:50:08:983]: Closing MSIHANDLE (4982) of type 790540 for thread 5616 MSI (s) (04!F0) [09:50:08:983]: Closing MSIHANDLE (4990) of type 790531 for thread 5616 MSI (s) (04!F0) [09:50:08:983]: Closing MSIHANDLE (4981) of type 790541 for thread 5616 MSI (s) (04:68) [09:50:08:983]: Closing MSIHANDLE (4980) of type 790542 for thread 5416 Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 CCMSETUP.og highlights MSI: Setup failed due to unexpected circumstances The error code is 80004005 ccmsetup 11/12/2010 9:50:08 AM 1156 (0x0484) Installation failed with error code 1603 ccmsetup 11/12/2010 9:50:09 AM 1156 (0x0484) Invalid argument: /MP:LANSINGSCCM01.FCS.FARM ccmsetup 11/12/2010 10:00:07 AM 3928 (0x0F58) Invalid ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 11/12/2010 10:00:07 AM 3928 (0x0F58) Property(S): SmsDetectDowngrade_ErrorMessage = A newer version of the Configuration Manager Client is already installed Property(S): SmsDetectColocationDowngrade_ErrorMessage = A newer version of the SMS Management Point is installed. Cannot continue installing this version of the client. Property(S): SmsMigrateQuarantineUpdateSchema_ActionText = Migrating content download schema. Property(S): SmsDetectUpgrade_ErrorMessage = An older version of the SMS Management Point is installed. Please upgrade the Management Point before attempting to upgrade the 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): InstallErrorDialog_Title = Setup Aborted Property(S): InstallErrorDialog_SubTitle = Setup failed Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue. MSI (s) (04:28) [09:50:09:218]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 4.00.6487.2000. Product Language: 1033. Installation success or error status: 1603.

Bueller?

Those property listings can be ignored completely - they just list properties. Search for "return value 3" in the msi logfile. The actual error should appear a few lines above it.

From the client.msi.log MSI (s) (6C!F0) [16:14:29:999]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (6C!F0) [16:14:29:999]: Closing MSIHANDLE (4983) of type 790531 for thread 2544 MSI (s) (6C!F0) [16:14:29:999]: Closing MSIHANDLE (4982) of type 790540 for thread 2544 MSI (s) (6C!F0) [16:14:29:999]: Closing MSIHANDLE (4990) of type 790531 for thread 2544 MSI (s) (6C!F0) [16:14:29:999]: Closing MSIHANDLE (4981) of type 790541 for thread 2544 MSI (s) (6C:80) [16:14:29:999]: Closing MSIHANDLE (4980) of type 790542 for thread 4420 Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (6C:44) [16:14:30:031]: Machine policy value 'DisableRollback' is 0 MSI (s) (6C:44) [16:14:30:031]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 16:14:29: CcmSetObjectSecurityInit. Return value 3. MSI (s) (6C:44) [16:14:30:031]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (6C:44) [16:14:30:031]: No System Restore sequence number for this installation. MSI (s) (6C:44) [16:14:30:031]: Unlocking Server Action ended 16:14:30: 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

FYI, I've tried the below to no avail. http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/af6e3858-d79e-49e6-8caa-c36cb57cfdff/ How does everyone feel about the 2003 sccm clean used on 2007 clients?

To uninstall SCCM client please use ccmsetup.exe /uninstall There is no special sccmclean tool available for configmgr. Regards, Madan | www.madanmohan.com

Error logs, client.msi.log MSI (s) (24!04) [10:23:50:810]: Closing MSIHANDLE (4985) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:810]: Creating MSIHANDLE (4986) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:826]: Closing MSIHANDLE (4986) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:826]: Creating MSIHANDLE (4987) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:826]: Closing MSIHANDLE (4987) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:826]: Creating MSIHANDLE (4988) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:826]: Closing MSIHANDLE (4988) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:826]: Creating MSIHANDLE (4989) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4989) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4984) of type 790540 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Creating MSIHANDLE (4990) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Creating MSIHANDLE (4991) of type 790531 for thread 5892 Action start 10:23:50: CcmSetObjectSecurityInit. MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4991) of type 790531 for thread 5892 [10:23:50] @@ERR:25001 MSI (s) (24!04) [10:23:50:966]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4983) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4982) of type 790540 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4990) of type 790531 for thread 5892 MSI (s) (24!04) [10:23:50:966]: Closing MSIHANDLE (4981) of type 790541 for thread 5892 MSI (s) (24:44) [10:23:50:966]: Closing MSIHANDLE (4980) of type 790542 for thread 5588 Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (24:D4) [10:23:50:997]: Machine policy value 'DisableRollback' is 0 MSI (s) (24:D4) [10:23:50:997]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 10:23:50: CcmSetObjectSecurityInit. Return value 3. MSI (s) (24:D4) [10:23:50:997]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (24:D4) [10:23:50:997]: No System Restore sequence number for this installation. MSI (s) (24:D4) [10:23:50:997]: Unlocking Server Action ended 10:23:51: 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 ccmsetup.log MSI: Action 10:23:50: CcmCreateIISApplicationPoolsInit. ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: CcmCreateIISVirtualDirectoriesInit. ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: RegisterUser. Registering user ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: CcmFixupServiceConfigInit. ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: CcmSetObjectSecurityInit. Applying security permissions ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Setup failed due to unexpected circumstances The error code is 80004005 ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) Installation failed with error code 1603 ccmsetup 11/17/2010 10:23:51 AM 5100 (0x13EC) Next retry in 120 minute(s)... ccmsetup 11/17/2010 10:23:51 AM 5100 (0x13EC)

Anyone know of another forum that I could try? This one was most reputable but this is a really odd issue.

Anyone know of another forum that I could try? This one was most reputable but this is a really odd issue.

ccmsetup.log MSI: Action 10:23:50: CcmCreateIISApplicationPoolsInit. ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: CcmCreateIISVirtualDirectoriesInit. ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: RegisterUser. Registering user ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: CcmFixupServiceConfigInit. ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Action 10:23:50: CcmSetObjectSecurityInit. Applying security permissions ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) MSI: Setup failed due to unexpected circumstances The error code is 80004005 ccmsetup 11/17/2010 10:23:50 AM 5100 (0x13EC) Installation failed with error code 1603 ccmsetup 11/17/2010 10:23:51 AM 5100 (0x13EC) It could have something to do with IIS or permissions (but don't ask me which ones), because that's the last thing that was tried before it errored out. Maybe that leads you in the right direction?

Invalid argument: /MP:LANSINGSCCM01.FCS.FARM ccmsetup 11/12/2010 10:00:07 AM 3928 (0x0F58) Invalid ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 11/12/2010 10:00:07 AM 3928 (0x0F58) Could this be due to incorrect parameters are being passed to ccmsetup.exe? I noticed 80004005 error code when I used incorrect parameters. Regards, Madan