Advertisement

How to Use ConfigMgr SCCM 2012 R2 Change Package Content Ownership Tool

In SCCM 2012 (ConfigMgr), package content ownership is also changed much from SCCM 2007 days. To unlock (or to change the ownership of) the packages in SCCM 2007, we used to follow an unsupported way to update Data Base with SQL queries like “SMSPackages set SourceSite=’IT1′ where SourceSite=’TMP'”. More details about unlocking collections, packages and advertisements here.

Now Microsoft has provided a tool (Content Ownership Tool) to change the Owner ship of the content or package without editing DB. This Content Ownership Change Tool (ContentOwnershipTool.exe.exe) helps change the ownership of orphan packages. Orphaned packages are packages without an owner site server. Packages that are created at a site can become orphaned by removing the site server while they are still owned by this site server.

You won’t be able to filter The SCCM ConfigMgr Content Ownership Tool (ContentOwnershipTool.exe) with package ID rather you’ll be able to filter or search this with Package Name, Site Code and Types of Packages. This tools also provides a feature to filter depending up on the package type. a) SMS_package (Normal SCCM classic packages), b) SMS_BootImagePackage (SCCM Boot Images), c) SMS_SoftwareUpdatesPackage (Software Update related packages) and d) SMS_ContentPackage (New Application packages introduced in SCCM 2012).

You can explore more about other SCCM 2012 R2 tools here Content Library Explorer Tool and Collection Evaluation Viewer Tool.

Pre-Requisite or Requirement 

You can run the ContentOwnershipTool.exe from any site server in the hierarchy. However, when you try to run it on another machines, you may get following error. The Content Ownership Tool must be run while logged in as an Administrative User that has sufficient package permissions.

To run this application, you must install one of the following version of the .NET framework: V4.0.30319. Contact your application publisher for instructions about obtaining the appropriate version of the .NET framework.

Walk through of Content Ownership Tool (ContentOwnershipTool.exe) 

1. I’m running the The SCCM ConfigMgr Content Ownership Tool from SCCM 2012 CAS server. You can either run it from Primary server or any other site server in your SCCM 2012 hierarchy.

Content Ownership Manager Tool Connected to CAS

Content Ownership Manager Tool Connected to CAS

2. In my case, there is NO orphan packages that is why in the above screen shot you’re NOT able to see any packages. When you select all packages option in the filtering section you can see all the packages.

Content Ownership Manager Tool Connected All packages Option

Content Ownership Manager Tool Connected All packages Option

3. The Content Ownership Manager Tool can be used to filter different types of packages like

SMS_package (Normal SCCM classic packages), SMS_BootImagePackage (SCCM Boot Images), SMS_SoftwareUpdatesPackage (Software Update related packages) and SMS_ContentPackage (New Application packages introduced in SCCM 2012).

Content Ownership Manager Tool Type of Packages

Content Ownership Manager Tool Type of Packages

4. How to Change the ownership of orphan package or content using The SCCM ConfigMgr Content Ownership Tool ?

I’m changing a package created at primary site. The ownership of that package is PRI server. I’m changing it to CAS server.

a) Select the package which you wanted to change the ownership.

b) Select the site details from the drop down menu “Change Site Ownership to

c) Click on APPLY and Click on View Log button to check whether the ownership is changed successfully.

Content Ownership Manager Tool Change OwnerShip

Content Ownership Manager Tool Change Ownership

5. View the log file called ContentOwnershipTool.log located at %temp%. Where is the location The SCCM ConfigMgr Content Ownership Tool  log file?

Successfully changed the site code of the package to CAS. Before the Content Ownership Change the owner of the package was PRI site (check the pic above). And at the bottom of the content Ownership tool, you can see the message successfully changed the source site of a object to CAS.

Content Ownership Manager Tool Chnaged the Ownership and Source Site

Content Ownership Manager Tool Changed the Ownership and Source Site

Following are the normal log entries

INFO: STARTING ContentOwnershipTool…
INFO: Refreshing package list from WMI…
INFO: InitializeSmsProviderScope: Connected to \\root\sms successfully.
INFO: InitializeSmsProviderScope: Connected to Site CAS
INFO: Setting package properties in the background.
INFO: Filtering package list by Name(), SiteCode(), Type(), Orphaned-Only?(False)…
INFO: Filtering package list by Name(), SiteCode(), Type(SMS_SoftwareUpdatesPackage), Orphaned-Only?(False)…
INFO: Filtering package list by Name(), SiteCode(), Type(SMS_BootImagePackage), Orphaned-Only?(False)…
INFO: Filtering package list by Name(), SiteCode(), Type(SMS_ContentPackage), Orphaned-Only?(False)…
INFO: Filtering package list by Name(), SiteCode(), Type(SMS_Package), Orphaned-Only?(False)…
INFO: Filtering package list by Name(), SiteCode(), Type(), Orphaned-Only?(False)…
INFO: Changing sitecode for Package PR100001 from PR1 to CAS…
INFO: InitializeSmsProviderScope: Already connected to site CAS. Returning true.
INFO: Setting package properties in the background.
INFO: Filtering package list by Name(), SiteCode(), Type(), Orphaned-Only?(False)…

About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: CM2012, ConfigMgr (SCCM), Configmgr2012, SCCM 2012 R2, System Center 2012 R2, System Center Configuration Manager, Tools

Leave a Comment and Contact Anoop