Best Practices for Content Management in Configuration Manager

 

Updated: May 14, 2015

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1

Use the following best practices for content management in System Center 2012 Configuration Manager:

Use a source file location for packages that has a fast and reliable network connection to the site that owns the package content source

When you create a package that contains source files, such as an application deployment type or deployment package, the site in which the package is created becomes the site owner for the package content source. The source files are copied from the source file path that you specify for the package to the content library on the site that owns the package content source. When you start the Update Content or Update Distribution Point actions, the content files are re-copied from the source file path to the content library on the site that owns the package content source. For more information about updating content, see the Update Content on Distribution Points section in the Operations and Maintenance for Content Management in Configuration Manager topic.

Before you create a package, consider the network connection between the source file location and the site that owns the package content source. As a best practice, use a source file location for packages that has a fast and reliable network connection to the site that owns the package content source.

Note

When you create an application, the site on which you created the application owns the package content source. The site also owns the content source for all deployment types for the application regardless of the site on which you create the deployment type. For example, when you create an application at Site X, Site X owns the package content source. When you create a deployment type for the application at Site Y, Site X continues to own the package content source. Therefore, the content for the deployment type is copied to Site X as the owner of the content.