Look here for more information: 
http://www.david-obrien.net/2014/01/22/multiple-copy-applications-configmgr-task-sequence/

They made that hotfix for one of my last customers in Germany.

 

David

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: 26 March 2014 07:36
To: [email protected]
Subject: [mssms] FW: HOTFIX: Application contents are duplicated in stand-alone 
media in System Center 2012 R2 Configuration Manager

 

FYI

 

Daniel Ratliff

 

Feed: The Configuration Manager Support Team Blog
Posted on: Tuesday, March 25, 2014 3:50 PM
Author: J.C. Hornbeck
Subject: HOTFIX: Application contents are duplicated in stand-alone media in 
System Center 2012 R2 Configuration Manager

 


 <http://support.microsoft.com/kb/2928122> Issue: 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 (ConfigMgr 2012 R2). 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

For additional details and a link to a ConfigMgr hotfix that resolves this 
issue please see the following:

KB2928122 <http://support.microsoft.com/kb/2928122>  - Application contents are 
duplicated in stand-alone media in System Center 2012 R2 Configuration Manager 
(http://support.microsoft.com/kb/2928122)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security 
Division

Get the latest System Center news on  
<https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410>
 Facebook and  <https://twitter.com/#!/MS_SystemCenter> Twitter:

 
<http://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410> 
 <http://www.twitter.com/MS_SystemCenter> 

System Center All Up: http://blogs.technet.com/b/systemcenter/ 
System Center – Configuration Manager Support Team blog: 
http://blogs.technet.com/configurationmgr/ 
System Center – Data Protection Manager Team blog: 
http://blogs.technet.com/dpm/ 
System Center – Orchestrator Support Team blog: 
http://blogs.technet.com/b/orchestrator/ 
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ 
System Center – Service Manager Team blog: 
http://blogs.technet.com/b/servicemanager 
System Center – Virtual Machine Manager Team blog: 
http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/ 
WSUS Support Team blog: http://blogs.technet.com/sus/ 
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/ 
MED-V Team blog: http://blogs.technet.com/medv/ 
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : 
http://blogs.technet.com/b/clientsecurity/ 
The Forefront Identity Manager blog : 
http://blogs.msdn.com/b/ms-identity-support/ 
The Forefront TMG blog: http://blogs.technet.com/b/isablog/ 
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

  
<http://blogs.technet.com/aggbug.aspx?PostID=3625950&AppID=6906&AppType=Weblog&ContentType=0>
 


View article... 
<http://blogs.technet.com/b/configurationmgr/archive/2014/03/25/hotfix-application-contents-are-duplicated-in-stand-alone-media-in-system-center-2012-r2-configuration-manager.aspx>
 


The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.

 




Reply via email to