All, I have this issue where the client fails. Upon checking i see that it happens immediately after it tries to smsinstallprepdrvr........ I suspect something is to with that. Initially it had warning when it tries uninstall PrepDrvr.Sys . Anyone has any input on this? A snipet of the setup log. MSI: Action 2:59:26: StopServices. Stopping services ccmsetup 5/31/2011 2:59:26 AM 19916 (0x4DCC) MSI: Action 2:59:26: SmsUninstallPrepDrvrAMD64. Uninstalling Software Metering PREP Driver ccmsetup 5/31/2011 2:59:26 AM 19916 (0x4DCC) MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 5/31/2011 2:59:26 AM 19916 (0x4DCC) MSI: Action 2:59:26: SmsStopUIComponents. Stopping UI Components ccmsetup 5/31/2011 2:59:26 AM 19916 (0x4DCC) {Logs truncated } MSI: Action 2:59:56: CcmRegisterPerfCountersRollback. ccmsetup 5/31/2011 2:59:56 AM 19916 (0x4DCC) MSI: Action 2:59:56: CcmRegisterPerfCounters. Registering performance counters ccmsetup 5/31/2011 2:59:56 AM 19916 (0x4DCC) MSI: Action 2:59:56: CcmRegisterComponentsRollback. ccmsetup 5/31/2011 2:59:56 AM 19916 (0x4DCC) MSI: Action 2:59:56: CcmRegisterComponents. Registering CCM Components ccmsetup 5/31/2011 2:59:56 AM 19916 (0x4DCC) MSI: Action 2:59:56: SmsSetLUAAccessPermissions. Setting Access Permissions ccmsetup 5/31/2011 2:59:56 AM 19916 (0x4DCC) MSI: Action 2:59:56: InstallServices. Installing new services ccmsetup 5/31/2011 2:59:56 AM 19916 (0x4DCC) MSI: Action 2:59:57: WriteEnvironmentStrings. Updating environment strings ccmsetup 5/31/2011 2:59:57 AM 19916 (0x4DCC) MSI: Action 2:59:57: CcmSetServiceConfig. Configuring service ccmsetup 5/31/2011 2:59:57 AM 19916 (0x4DCC) MSI: Action 2:59:58: SmsMigrateInventory. Migrating SMS Legacy Client inventory settings ccmsetup 5/31/2011 2:59:58 AM 19916 (0x4DCC) MSI: Action 2:59:58: CcmConfigDCOM. Configuring service ccmsetup 5/31/2011 2:59:58 AM 19916 (0x4DCC) MSI: Action 2:59:58: SmsShellNotify. Setting SMS configuration ccmsetup 5/31/2011 2:59:58 AM 19916 (0x4DCC) MSI: Action 2:59:58: CcmInitializePolicy. Initializing policy ccmsetup 5/31/2011 2:59:58 AM 19916 (0x4DCC) MSI: Action 3:00:00: SmsSetClientConfig. Setting SMS configuration ccmsetup 5/31/2011 3:00:00 AM 19916 (0x4DCC) MSI: Action 3:00:00: CcmMigrateDownloadSchema. ccmsetup 5/31/2011 3:00:00 AM 19916 (0x4DCC) MSI: Action 3:00:00: CcmRegisterProduct. Registering product ccmsetup 5/31/2011 3:00:00 AM 19916 (0x4DCC) MSI: Action 3:00:00: CcmRegisterProductRollback. Registering product ccmsetup 5/31/2011 3:00:00 AM 19916 (0x4DCC) MSI: Action 3:00:00: SmsInstallPrepDrvr. Installing Software Metering PREP Driver ccmsetup 5/31/2011 3:00:00 AM 19916 (0x4DCC) MSI: Action 3:00:00: Rollback. Rolling back action: ccmsetup 5/31/2011 3:00:00 AM 19916 (0x4DCC) Installation failed with error code 1603 ccmsetup 5/31/2011 3:00:11 AM 19916 (0x4DCC) Next retry in 120 minute(s)... ccmsetup 5/31/2011 3:00:11 AM 19916 (0x4DCC) Thanks Thanish.

You're looking in the wrong place in the log. The lines you have highlighted above are part of the rollback (or cleanup) after the failure. Here's a nice reference finding the root cause of 1603 errors in MSIs: http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

You're looking in the wrong place in the log. The lines you have highlighted above are part of the rollback (or cleanup) after the failure. Here's a nice reference finding the root cause of 1603 errors in MSIs: http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys thank you Jason. I tried that but the log are not being created in temp. i did searched for such log in other location just in case it did not create in temp but no success. i would try a reboot before trying again to install and will update. Thanks, Thanish.

Reboot solved it. Installed the client.

No one said the log was in temp. You were looking at the correct log (the one you posted the snippet from). Specifically, the correct log file for the ConfigMgr agent setup is client.msi.log and is located in c:\Windows\system32\ccmsetup (32-bit) or c:\Windows\ccmsetup (64-bit). The aticle was about finding the cause of the 1603 because that is the generic MSI error which basically means "go dig through the log".Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

While I know that this topic hasn't been discussed in 7 months, a simple reboot on your end may have fixed the issue but I have rebooted the asset I'm trying to fix several times as well as run the WMI fix yet the error still exists when attempting to re-install SCCM. It is running WIN7 64bit. This is the exact error as it appears in the log file when I run a Trace32 on it: MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. Has anyone else received this error or know what it's about as running a google search on this error only pointed to this post and one other that was of no help.

With Windows 2008 32-bit. Similar situation. SCCM Client was successfully installed in 2012, after the removal of Microsoft WIMGAPI.