none
Cannot Migrate Collections that use SMS_CM_RES_COLL_<CollectionID>

    Question

  • I have many collections in SCCM 2007 that include other collections in SCCM 2007.

    These are done by (Select ResourceID from SMS_CM_RES_COLL_ABC00A83)

    ---- Migration Error from migmctrl.log ----

     The rule may be based on a Hardware Inventory class not collected at the destination, or be based on a ConfigMgr extension which is not present at the destination, or refers to a collection class like 'SMS_CM_RES_COLL_<CollectionID>

    Is there a way to do includes and excludes in 2007 without using "SMS_CM_RES_COLL_"

    Thursday, April 17, 2014 3:55 PM

All replies

  • I normally used SMS_FullCollectionMember in 2007 to accomplish this task.

    Remember that ConfigMgr 2012 has include rules now so it shouldn't be critical for you to migrate these rules over.


    Jason | http://blog.configmgrftw.com

    Thursday, April 17, 2014 5:48 PM
  • Hello ,

    I am also facing the same error. during collection migration.

    Could you please let me know, How did u resolved this issue.

    Thanks,

    Shilpa

    Friday, April 24, 2015 1:48 PM
  • There is no magic here -- ConfigMgr does not modify or evaluate query rules during migration as there is no way for it to figure out your intent particularly since collections may or may not be migrated and there are no sub-collections in 2012. You need to do some analysis and make the modifications and adjustments manually.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, April 24, 2015 2:25 PM
  • Hi Jason,

    Thanks for your quick reply,

    I am new learner, Could you please elaborate bit more.

    It will be greate help fom you if you share little more information on what kind of modifications and adjustment need to be done manually.

    Thanks,

    Shilpa

    Tuesday, April 28, 2015 4:28 AM
  •  The rule may be based on a Hardware Inventory class not collected at the destination, or be based on a ConfigMgr extension which is not present at the destination, or refers to a collection class like 'SMS_CM_RES_COLL_<CollectionID>


    The error message already tells all details. A collection cannot be migrated because either (a) it is using a hardware inventory class that is not enabled at the target site or (b) you are using a WQL query in the source site that uses sms_res_coll_% to include/exclude other collections. Solution: (a) adjust hardware inventory and (b) use include/exclude collections in CM12 (which requires manual work).

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 28, 2015 5:54 AM
  • That is completely dependent upon the query -- there is no generic answer -- as mentioned, you need to evaluate and analyze the query. From that, you can determine the adjustments needed.

    Getting rid of the use of direct references to collection views would be a good start though and instead use collection IDs or collection names. It simply depends.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, April 28, 2015 1:07 PM
  • Just as an FYI, this is still valid for a migration from sccm 2012 to sccm cb.  Collection queries utilizing subselects

    in (Select resourceID from sms_cm_res_coll_S0200018)

    should be changed to 

     in (Select resourceID from SMS_FullCollectionMembership where CollectionID = "S0200018")
    or just use the built in include\exclude method.

    Not doing so will produce failures like:

    Unknown error. See migmctrl.log and smsprov.log for more information. Code 134217727 Details .

    Wednesday, March 30, 2016 10:52 PM
  • Hello,

    Make sure all of the proper discovery methods are enabled. There are 3 collection types in total (0 - other, 1 - user, 2- device). If you happen to be attempting to migrate a collection that's dependent on the correlating discovery methods (along with attributes the queries rely on), you will see the error above that started this string ("The rule may be based on a Hardware Inventory class not collected at the destination, or be based on a ConfigMgr extension which is not present at the destination, or refers to a collection class like 'SMS_CM_RES_COLL_<CollectionID>").

    Also you can start looking in the DB.. A simple 'select * from v_collections' will return the collections, and you can then filter on CollectionType which is a column value in that view. 

    0- Other

    1- User

    2- Device

    - Trevor Stuart (PFE)

    https://moderncloudmanagement.com




    Friday, July 6, 2018 12:39 AM