Collection Migration fails RRS feed

  • Question

  • We are trying SCCM migration from CM7 to CM2012 first on a test environment before moving to production. Many collection migrations fail with

    Entity ABCD with path SMS_Collection.xxxxxxxxxxxx   failed with Invalid Query for collection rule Query

    I can see some Attribute classes have not been migrated , that is why the collection can't migrate with those queries and it fails. How to correct it ?  The closest to this problem/solution was in an earlier thread here "Migrating Collections fails" . WE have the AD Forest Discovery turned on and the SCCM servers have been discovered. So, the  solution in that thread has not worked. Any ideas ?



    Saturday, May 10, 2014 11:15 AM

All replies

  • The first question would be very basic, do you have combined user-and-device collections? Solution: Not supported.

    The second question is a bit more advanced, did you had an extended hardware inventory and based a collection on that? Solution: Create the extended hardware inventory (and by that classes) first.

    If both don't apply, you might want to try to create a collection with the collection query manually.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Saturday, May 10, 2014 6:05 PM
  • Thanks for the reply Peter.

    The colelction won't be migrated at al if it is  a mixed one; so I am not bothered about it.

    Yes, we have extended hardware inventory in CM2007. I thought it is automatically migrated during SCCM Migration tool.

    I can see some Attributes on which the queries are based is not migrated, that is why the collection migration fails. So, how do we create extended hardware inventory in SCCM 2012, the best solution would be to migrate that also from CM 2007. Someone was saying , create a client first, then inventorying that would pull in extra hardware attribute classes. I don't know if it would work or not; but that would defeat the purpose of during migrations first before going for clients.

    Monday, May 12, 2014 8:48 AM
  • You cannot migrate hardware inventory customizations. See, also: http://technet.microsoft.com/en-us/library/gg712283.aspx#Planning_for_Inventory_data_migration

    Quote: "...you cannot migrate customizations for hardware inventory from a source hierarchy. You must introduce these to the destination hierarchy independently from migration."

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Monday, May 12, 2014 9:01 AM
  • OK, any pointers as to how to do that?


    Monday, May 12, 2014 9:04 AM
    1. Find the current additions to your configuration.mof file (ConfigMgr 2007) and add them to new configuration.mof (ConfigMgr 2012).
    2. Find the current additions to your sms_def.mof file (ConfigMgr 2007), safe them as a temporary mof file and import that mof file into the Client Settings (ConfigMgr 2012).

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    • Proposed as answer by Juke Chou Monday, May 12, 2014 3:45 PM
    Monday, May 12, 2014 10:04 AM
  • I believe all the extra hardware class definitions are there in the test SCCM 2012 site. Still while the Class definition is there, the attribute values are absent in the target SCCM. So, what someone sugegsted is to have a SCCM client , which will populate the database with inventory. Then it will be possible to migrate the collections. For convenience, we can divide into Server/workstation and 32/64 bits. So, once we have 4 types of clients, all the collections shouls migrate. That is what I will try today. To some extent, it changes our migration plan of putting Boundary Groups and Clients after the object migration has taken place.



    Wednesday, May 14, 2014 8:36 AM