Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Configuration Manager client update is not installed successfully on Windows XP or Windows Server 2003 clients


View products that this article applies to.

Symptoms

You install an update to any version of Microsoft System Center 2012 Configuration Manager or System Center Configuration Manager 2007 Service Pack 2 (SP2) sites. However, you can't successfully deploy the update to Windows XP-based or Windows Server 2003-based client computers. When this problem occurs, the following event is recorded in the Windows installer log:

Action start 15:34:27: CcmCheckFreeDiskSpace. MSI (s) (B8:A8) [15:34:27:809]: Product: Configuration Manager Client -- There is not enough available disk space on  to complete this operation. Installation requires at least 90MB free disk space. 
Note This specific problem occurs only when the Configuration Manager client is installed on a nonsystem partition. For example, the Windows system is installed on partition C and you install the Configuration Manager client on partition D. This issue occurs even if sufficient free disk space exists on the partition on which the Configuration Manager client is installed.

This problem occurs only on Windows XP-based and Windows Server 2003-based clients.

↑ Back to the top


Cause

This problem is caused by a product issue in Windows Installer. This issue may be exposed when you install the client updates to a nonsystem partition in No UI mode.

↑ Back to the top


Workaround

To work around this problem, use one of the following methods:
  • Do not install the Configuration Manager client on a nonsystem partition.
  • Change the command line of the client update package by removing the /q parameter. The /q parameter specifies "Quiet mode" to Windows Installer. By default, Windows Installer installs this package in No UI mode if this parameter is encountered. After you change the command line, you must also change the following options:

    Program can run: Only when a user is logged on

    Run mode: Run with user’s rights
    These changes are necessary because of the behavior of Windows Installer if the package is run in a noninteractive session. In this situation, Windows Installer always enables the No UI mode regardless of whether the /q parameter is used. After you change these options, the package will be installed in a logon session that has user interaction. Therefore, Windows Installer honors the /q parameter that is specified by Configuration Manager.

↑ Back to the top


More Information

For more information about how to enable the Windows Installer log, see the following Microsoft Knowledge Base article:
223300 How to enable Windows Installer logging

↑ Back to the top


Keywords: kbsurveynew, kbexpertiseadvanced, kb, SCCM

↑ Back to the top

Article Info
Article ID : 2923401
Revision : 2
Created on : 4/26/2017
Published on : 4/26/2017
Exists online : False
Views : 407