I've been attempting to get the SCCM client (2007 R3 SP2) installed on several of our servers, and getting an error message that I can't seem to find out on the net anywhere. I've attempted to launch the install via the standard install from the admin console, manual install (see below for the command I'm using), and Right Click Tools. Everytime I run the install, I get an error message that says "Installation failed with error code 1632". Anyone ever see this before? (Command I'm running: ccmsetup.exe /mp:SCCMPSS01 smssitecode=ORG SMSFSP=SCCMPSS01) ----> I've run this from the ccmsetup folder and a mapped drive to the PSS. CCMSETUP.log ==========[ ccmsetup started in process 3856 ]========== ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Version: 4.0.6487.2000 ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /mp:SCCMPSS01 smssitecode=ORG SMSFSP=SCCMPSS01 ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) CCMHTTPPORT: 80 ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) CCMHTTPSPORT: 443 ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) CCMHTTPSSTATE: 2147483648 ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) CCMHTTPSCERTNAME: ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) FSP: SCCMPSS01v ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Config file: ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Retry time: 10 minute(s) ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) MSI log file: ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) MSI properties: SMSSITECODE="NSB" SMSFSP="SCCMPSS01v" CCMHTTPPORT="80" CCMHTTPSPORT="443" ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Source List: ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) MPs: ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) SCCMPSS01v ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) Sending Fallback Status Point message, STATEID='100'. ccmsetup 3/28/2012 2:01:37 PM 2080 (0x0820) State message with TopicType 800 and TopicId {FFFE010B-DDFE-4E51-9C3E-5A25EA837541} has been sent to the FSP FSPStateMessage 3/28/2012 2:01:37 PM 2080 (0x0820) Successfully started the ccmsetup service ccmsetup 3/28/2012 2:01:37 PM 5704 (0x1648) Running as user "SYSTEM" ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Detected 21902 MB free disk space on system drive. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Client OS Version is 5.2, Service Pack Version 2 ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Client OS is not a supported Windows Embedded Platform ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Deleted file C:\WINDOWS\system32\ccmsetup\client.msi ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Successfully ran BITS check. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Successfully loaded ccmsetup manifest file. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Couldn't get directory list for directory 'http://SCCMPSS01v/CCM_Client/ClientPatch'. This directory may not exist. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Adding file 'http://SCCMPSS01v:80/CCM_Client/i386/wimgapi.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\wimgapi.msi'. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Adding file 'http://SCCMPSS01v:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Couldn't get directory list for directory 'http://SCCMPSS01v/CCM_Client/i386/00000409'. This directory may not exist. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Starting BITS download for client deployment files. ccmsetup 3/28/2012 2:01:37 PM 4436 (0x1154) Download Update: 15424526 out of 18635264 bytes transferred. ccmsetup 3/28/2012 2:01:38 PM 4436 (0x1154) Successfully completed BITS download for client deployment files. ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) Successfully downloaded client files via BITS. ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) Couldn't verify 'C:\WINDOWS\system32\ccmsetup\wimgapi.msi' authenticode signature without revocation ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled. ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) Certificate doesn't have EKU, meaning good for all usages. ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) IsMSSignedByFileHash Verified file 'C:\WINDOWS\system32\ccmsetup\wimgapi.msi' is MS signed. ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) Running installation package Package: C:\WINDOWS\system32\ccmsetup\wimgapi.msi Log: C:\WINDOWS\system32\ccmsetup\wimgapi.msi.log Properties: REBOOT=Suppress ALLUSERS=1 ccmsetup 3/28/2012 2:01:39 PM 4436 (0x1154) Installation failed with error code 1632 ccmsetup 3/28/2012 2:01:40 PM 4436 (0x1154) Sending Fallback Status Point message, STATEID='311'. ccmsetup 3/28/2012 2:01:40 PM 4436 (0x1154) State message with TopicType 800 and TopicId {64033331-9CED-42DF-857D-68E7C51F8444} has been sent to the FSP FSPStateMessage 3/28/2012 2:01:40 PM 4436 (0x1154)  Nate

What's in the client.msi.log? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Couldn't find the client.msi.log in the CCMSetup directory.....Nate

Error code 1632 = "The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder."Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I have full admin rights on this server, and verified that I have rights to the Temp directory. Also, this server has several hundred GB of available space.Nate

That's the meaning of the error code though -- no ambiguity. The reason you don't have a client.msi.log is because ccmsetup hasn't gotten there yet; the installation of wimgapi.msi is the one throwing the 1632 error. Have you reviewed C:\WINDOWS\system32\ccmsetup\wimgapi.msi.log? Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Are you referring to the C:\WINDOWS\TEMP directory? Or the TEMP directory under Local Settings in my profile? I've found some information about the 1632 error for Office installs, and that it dumps information in a log file in the user profile...... sorry if that's a stupid question...... As for the wimgapi.msi.log file, after reading through that, I do see the 1632 error referenced in the bottom few lines of the log file. Nate

jason is correct, 1632 literally translates to exactly what he said. I would assume that means %temp% which unless the disk is full there's no limit on it so it can't be full. Having said that I'd check to make sure that variable hasn't been removed from the system and ensure it's pointing to the correct path and permissions are correct on it. http://www.itninja.com/question/help-with-msi-1632 John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

MSI log files are typically much more than the error code at the end though. You need to search through the log file for the place the error occured for (hopefully) more information about the root cause of the error. Finding this is usually an art though -- searching for "return value 3" typically gets you close though. As for temp directory, don't know. My guess would be c:\windows\temp. Is this system "locked down"? I've seen similar issues with security being changed on folders like the temp folder.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys