Application contents are duplicated in stand-alone media in System Center 2012 R2 Configuration Manager

Applies to: Microsoft System Center 2012 R2 Configuration Manager

Symptoms


Application contents are duplicated in the client cache folder for every Install Application step that is used in a task sequence in Microsoft System Center 2012 R2 Configuration Manager. This affects only clients that are deployed by using stand-alone media.

For example, a task sequence is created that has two Install Application steps, and each has a separate .msi file:

Install Application: Application1.msi
Install Application: Application2.msi

On the client that is installed by using this stand-alone media, the client cache folder (by default, this is Windows\CCMCache) contains two copies of each .msi file:

\Windows\CCMCache\1\Application1.msi
\Windows\CCMCache\2\Application2.msi
\Windows\CCMCache\3\Application1.msi
\Windows\CCMCache\4\Application2.msi

Resolution


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Installation information

To install this hotfix during a Configuration Manager operating system deployment task sequence, follow these steps:
  1. Apply this hotfix on the site server. The Configuration Manager client update files for this hotfix are dropped to hotfix\KB2928122\Client\architecture\ under the Configuration Manager Server installation folder. 
  2. Copy the client updates to the folder where the Configuration Manager client installation package resides, and then make sure that you update the distribution points.
  3. Copy the .msp file to the Configuration Manager Client Installation Packages folder. To do this, use one of the following commands:

    Copy SMS_Installation_folder\hotfix\KB2928122\Client\i386 to SMS_Installation_folder\Client\i386

    Copy SMS_Installation_folder\hotfix\KB2928122\Client\x64 to SMS_Installation_folder\Client\x64


  4. Right-click the task sequence that you have to change, and then click Edit.
  5. Click Setup Windows and ConfigMgr.
  6. In the Installation properties box, type one of the following strings.

    For the i386 image, add the i386 client update:

    PATCH="C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB2928122\ConfigMgr2012AC-R2-KB2928122-i386.msp" 

    For the x64 image, add the x64 client update:

    PATCH="C:\_SMSTaskSequence\OSD\<Package_ID>\x64\hotfix\KB2928122\ConfigMgr2012AC-R2-KB2928122-x64.msp"
Notes
  • The placeholder Package_ID represents the package ID of the Configuration Manager client installation package in Configuration Manager.
  • Make sure that you include the quotation marks as part of the path. However, do not include the brackets that are around the placeholder.
  • Make sure that you use the package ID of the Configuration Manager client installation package instead of the package ID of the KB2928122 hotfix package.
  • The _SMSTaskSequence cache folder will reside on the drive that has the most disk space. If the computer has multiple drives or partitions, the _SMSTaskSequence folder may reside on a drive other than drive C. In this scenario, change the path so that it points to the drive that contains the _SMSTaskSequence folder. We do not recommend that you use the variable _SMSTSMDataPath in the path because the drive letter in this path can enumerate differently in Windows PE than in the full Windows operating system.
  • As an alternative to the local path that points to the Configuration Manager client installation files in the local Task Sequence cache, you can specify a UNC path that points to the Configuration Manager client installation files in the original package source or on a distribution point.
  • Verify the name of the .msp file that is located in the \hotfix\KB\2928122\Client directory of the Configuration Manager Server installation folder. The name may differ. If the name differs from the name of the .msp file name that is used in the PATCH= command line in step 6, adjust the name accordingly.

Prerequisites

To apply this hotfix, you must have System Center 2012 R2 Configuration Manager installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Note We recommend that you close Configuration Manager Administration Console before you apply this hotfix package.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform
Configmgr2012ac-r2-kb2928122-x64.mspNot applicable1,102,33601-Oct-201301:30Not applicable
Smsappinstall.exe5.0.7958.1106264,88001-Oct-201301:30x64
Configmgr2012ac-r2-kb2928122-i386.mspNot applicable912,89601-Oct-201301:30Not applicable
Configmgr2012adminui-r2-kb2928122-i386.mspNot applicable2,354,68801-Oct-201301:30Not applicable
Smsappinstall.exe5.0.7958.1106202,41601-Oct-201301:30x86


Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


for more information about Media Operating System deployment and the client cache folder, see the following Microsoft TechNet articles :


Learn about the terminology that Microsoft uses to describe software updates.