Our SCCM environment consists of a central site and a few primary child sites for each country. The buildin collections are only provided from out central site, so they are protected on each child site and can not be modified there.

Today we created a new collection on a child site and linked an inherited collection (All Windows 7 Systems) to this new collection:

                      link_to_collection_protected

As you can see, the collection is protected even if it’s only an instance, as in our case. If you now want to delete this instance you are not able to.

We searched the web and found no solution for this bug and we believe that it is one. So we have to digg into the SCCM collection management and found a solution.

Please be very careful if you try our solution, because a wrong handling may led to an inconsistent SCCM database. We don’t give any guarantee.

  1. Download the WMI Administrative Tools and install them on a client computer. We used a Windows XP computer.
     
  2. Start the WMI Object Browser, a part of the WMI Administrative Tools. The object browser starts in an internet explorer window and tries to connect to the default WMI namespace on the client computer:
                    wmi_object_browser_connect
     
  3. Connect to WMI namespace on your site server for the child site. Therefore klick on the small icon beside the selected namespace too browse to the SCCM site server you have the linked collection to be deleted, put in the site server name and as starting namespace use “root\sms” as shown:
                    wmi_object_browser_connect2 wmi_object_browser_connect3
    Klick on connect and put in appropriate credentials to connect to your site servers WMI. Select the namespace corresponding to your site code and klick ok. Now you have to specifiy the browser criteria which is the SMS_Collection class. Add it it and go further with ok:
                    wmi_object_browser_connect4
    You get another window where you have to choose the collection which helds the collection link to be deleted.  
                    collection_containing_link
    In our case it was the collection “Manage” with the ID “BCG0004F” and if you go ahead with ok you can see all the properties of your collection.
      
  4. Temporarily unset the protected flag for the collection to be deleted. To do that, open the object tree as shown in the following picture and select the trouble making collection. In our case the collection with id “ABC00048”:
    collection_edit 
    After choosing this collection you can see properties for this collection on the site-server!!! This is important to think of!!!

    Change the property “OwnedByThisSite” from false to true, save your change with the disk icon (marked with the arrow) and refresh the collection tree in your configuration manager console. Now you are able to delete the instance of this collection, like with any other collection not inherited.

    When deleted you should set the property to false afterwards, to get not in trouble with the central site

Again remember, the change we’ve made here was only for the child site, regarding a collection inherited from the central site!!!

So please be very careful of what you are doing.

Advertisements