Quantcast
Channel: Category Name
Viewing all articles
Browse latest Browse all 5932

ConfigMgr 2012 support tip: Migrating an application to a new hierarchy creates new Content ID

$
0
0

~ John Philpott

FIXHi everyone, John Philpott here with a quick tip for you on an issue where applications may get a new content ID after migrating to a new System Center 2012 R2 Configuration Manager Service Pack 1 (SP1) environment.

The Scenario

You are migrating your current System Center 2012 Configuration Manager infrastructure to a new ConfigMgr 2012 R2 SP1 environment. Your original environment includes applications which are to be migrated over to the new environment. To allow for a phased migration, you have set up shared distribution points in the original environment.

The Problem

Once you migrate your applications to the new ConfigMgr 2012 R2 SP1 environment, you find that a large number of those applications have received a new Application Deployment Type Content_UniqueID. This causes clients to not be able to download content in the new environment from the shared distribution point, as they do not recognize the Content_UniqueID.

The Cause

This can occur if the applications that were created had a source directory that didn't end with a backslash (the \ character). This is because in ConfigMgr 2012 R2 SP1, any application created that doesn't have the trailing '\' in its source gets it added automatically.

The Resolution

To resolve this issue, or to prevent it from happening in the first place, from the old site, update the source path to include a trailing ‘\’ on any application that is missing one (or any app that is getting a new Content_UniqueID after migration).

If you have not begun your migration yet, no further steps are required. If you have discovered this issue post migration, after you complete the step above, re-migrate the application using the “overwrite” option.

After these steps, migrated applications will maintain the same Content_UniqueID.

NOTE In ConfigMgr 2012 R2 SP1 and/or ConfigMgr 2012 SP2, content paths will always have a trailing ‘\’ appended. Because of this, this issue should not occur with content created using those versions.

John Philpott | Support Escalation Engineer

Get the latest System Center news onFacebookandTwitter:

clip_image001clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/

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

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
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 Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

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/

ConfigMgr 2012 R2


Viewing all articles
Browse latest Browse all 5932

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>