I'm still working through the backlog of new Knowledge Base articles we're pushing out and thought I'd give you a heads up on another new ConfigMgr 2007 article we published this morning. This one describes a scenario where you get "MSI: Configuration Manager Client is not installed" trying to install the client:
=====
Symptoms
Attempts to install the System Center Configuration Manager 2007 client may fail with the following error messages in the ccmsetup.log:
MSI: Configuration Manager Client is not installed. ccmsetup 12-11-2010 16:26:12 3264 (0x0CC0)
Installation failed with error code 1603 ccmsetup 12-11-2010 16:26:12 3264 (0x0CC0)
If you check the client.msi.log you may notice the following lines:
MSI (s) (54:74) [16:26:11:416]: Checking in-progress install: install for same configuration.
MSI (s) (54:74) [16:26:11:416]: Suspended install detected. Resuming.
Cause
This can occur if a previously failed installation of the Configuration Manager client left behind an IPI installer file (.ipi) in the %systemroot%\installer directory on the target computer.
Resolution
Search for *.ipi files in the %systemroot%\installer directory on the target computer and temporarily move them to a different folder. Next run the setup of the client installation again and it should complete successfully.
=====
For the latest version of this article see the link below:
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
