Hi, I have search through the forum and Google extensively but I am not able to get any useful solution, I have around 100 machines in my environment and out of those only one of the windows 7 machine is having issues installing sccm client, I have tried installing manually but the same error appears. Any help would be highly appreciated. MSI (s) (C8!DC) [10:48:46:241]: Closing MSIHANDLE (4977) of type 790531 for thread 7132 MSI (s) (C8!DC) [10:48:46:241]: Closing MSIHANDLE (4972) of type 790540 for thread 7132 MSI (s) (C8!DC) [10:48:46:241]: Creating MSIHANDLE (4978) of type 790531 for thread 7132 MSI (s) (C8!DC) [10:48:46:242]: Creating MSIHANDLE (4979) of type 790531 for thread 7132 Action start 10:48:46: CcmSetObjectSecurityInit. MSI (s) (C8!DC) [10:48:46:242]: Closing MSIHANDLE (4979) of type 790531 for thread 7132 [10:48:46] @@ERR:25001 Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (C8!DC) [10:48:46:243]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances The error code is 80004005 MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4971) of type 790531 for thread 7132 MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4970) of type 790540 for thread 7132 MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4978) of type 790531 for thread 7132 MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4969) of type 790541 for thread 7132 MSI (s) (C8:20) [10:48:46:245]: Closing MSIHANDLE (4968) of type 790542 for thread 6432 CustomAction CcmSetObjectSecurityInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (C8:20) [10:48:46:247]: Machine policy value 'DisableRollback' is 0 MSI (s) (C8:20) [10:48:46:247]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 10:48:46: CcmSetObjectSecurityInit. Return value 3. MSI (s) (C8:20) [10:48:46:247]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (C8:20) [10:48:46:247]: No System Restore sequence number for this installation. MSI (s) (C8:20) [10:48:46:247]: Unlocking Server Action ended 10:48:46: 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\ Property(S): Redist.51D569E3_8A28_11D2_B962_006097C4DE24 = C:\Windows\SysWOW64\

You may refer the following article to rebuild WMI. Rebuilding and reinstalling the WMI Repository http://www.madanmohan.com/2010/10/rebuilding-wmi-repository.html If it does not work, temporary disable the antivirus and firewall on that client and try again. Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the response Xie, but I am still not able to install the client, I have tried rebuilding the wmi repository, any other ideas what to look for ?

Any chance that IIS is installed on the machine?Torsten Meringer | http://www.mssccmfaq.de

yes, IIS is installed on this system.

I've seen this issue before, but I can't remember any details. I has something to do with IIS and corresponding accounts or something like that. Removing IIS should solve the issue (I know that this might not be an option). See http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/baf8302f-e61b-4a63-bd1d-ec197480cc6c for further information.Torsten Meringer | http://www.mssccmfaq.de