{"id":275,"date":"2016-01-28T10:56:41","date_gmt":"2016-01-28T15:56:41","guid":{"rendered":"https:\/\/www.ccrossan.com\/?p=275"},"modified":"2016-07-07T08:02:40","modified_gmt":"2016-07-07T12:02:40","slug":"sccm-1511-driver-migration-fails","status":"publish","type":"post","link":"https:\/\/crossan007.dev\/blog\/sccm\/sccm-1511-driver-migration-fails\/","title":{"rendered":"SCCM 1511 Driver Migration Fails"},"content":{"rendered":"\n
Tweet<\/a><\/div>\n

While migrating drivers from SCCM 2012 to SCCM 1511, the migration can fail with the following error message:<\/p>\n

Couldn't find the specified instance SMS_CategoryInstance.CategoryInstance_UniqueID='DriverCategories:<\/code><\/p>\n

This occurs given the following scenario:<\/p>\n

    \n
  1. A driver is added to SCCM<\/li>\n
  2. A category is assigned to the driver<\/li>\n
  3. The category is deleted from the driver<\/li>\n
  4. The migration job attempts to migrate the driver to a new SCCM environment<\/li>\n<\/ol>\n

    Consider the following error message:<\/p>\n

    Couldn't find the specified instance SMS_CategoryInstance.CategoryInstance_UniqueID='DriverCategories:78266da1-ebac-4c12-b2c8-89451383b03e<\/code><\/p>\n

    An In-depth analysis shows that the driver category\u00a0does not\u00a0appear in the WMI Class SMS_CategoryInstance:<\/p>\n

    Get-WmiObject -Namespace $Namespace -Class SMS_CategoryInstance -Filter \"CategoryInstance_UniqueID = 'DriverCategories:78266da1-ebac-4c12-b2c8-89451383b03e'\"
    \n<\/code>
    \nReturns Null, but a SQL query indicates that the Category Instance still exists:
    \nSELECT * FROM CI_CategoryInstances<\/code><\/p>\n

    WHERE CategoryInstance_UniqueID
    \nLIKE ‘%78266da1-ebac-4c12-b2c8-89451383b03e%’<\/p>\n

     <\/p>\n

    Returns the following:<\/p>\n

    CategoryInstanceID CategoryInstance_UniqueID CategoryTypeName DateLastModified SourceSite ParentCategoryInstanceID IsDeleted rowversion<\/code>
    \n16777602 DriverCategories:78266da1-ebac-4c12-b2c8-89451383b03e DriverCategories 2015-07-27 11:52:33.000 CM1 NULL 1 0x000000000A36B34D
    \n<\/code><\/p>\n

    Take note of the “IsDeleted” column – set to True<\/p>\n

    So, at this point, WMI reports that this category no longer exists; however the category is still in the SQL Database, though this is not the root of the problem.<\/p>\n

    Now consider the WMI Class\u00a0SMS_CategoryInstanceMembership:
    \nThis class contains a correlation of Objects to CategoryIDs. \u00a0This is not limited to Driver <-> Driver Category correlation.<\/p>\n

    The true bug seems to be that when a driver category is removed, the entry for that driver category in the\u00a0\u00a0SMS_CategoryInstanceMembership class is not removed. \u00a0In order to fix this, and have a successful migration, we need to manually remove the CategoryInstanceMembership object for any drivers that were\u00a0<\/em>assigned a\u00a0now deleted<\/em> category.<\/p>\n

    to Fix:<\/p>\n

      \n
    1. Fire Up SQL Server Management Studio<\/li>\n
    2. Create a New Query, and select your Site Database<\/li>\n
    3. For each failing driver entry (as seen in “C:\\Program Files\\Microsoft Configuration Manager\\Logs\\migmctrl.log”),\n
        \n
      1. Run the following SQL Query:
        \nSELECT * FROM CI_CategoryInstances
        \nWHERE CategoryInstance_UniqueID
        \nLIKE '%c6e9d9e3-1371-46ba-b7f1-bb46c5b6bc06%'<\/code><\/li>\n
      2. Note the CategoryInstanceID \u00a0(should be like\u00a016777601)<\/li>\n
      3. On your SCCM Server, from an administrative PowerShell run the following code to remove the association, substituting the CategoryInstanceID you discovered in step 3-2:
        \n<\/code>Get-WmiObject -Namespace $Namespace -Class SMS_CategoryInstanceMembership -Filter \"CategoryInstanceID = '16777601'\" | Foreach-Object {
        \nRemove-WmiObject -InputObject $_
        \n}<\/code><\/li>\n<\/ol>\n<\/li>\n
      4. Repeat the above section for each unique\u00a0CategoryInstance_UniqueID listed in the “C:\\Program Files\\Microsoft Configuration Manager\\Logs\\migmctrl.log” file.<\/li>\n
      5. When complete, retry the migration, and examine for any additional missing\u00a0CategoryInstance_UniqueID errors.<\/li>\n<\/ol>\n

        References (In order of usefulness):<\/p>\n

          \n
        1. http:\/\/cm12sdk.net\/?p=981<\/a><\/li>\n
        2. https:\/\/www.reddit.com\/r\/SCCM\/comments\/34b18i\/delete_multiple_driver_admin_categories\/<\/a><\/li>\n
        3. https:\/\/technet.microsoft.com\/en-us\/library\/hh849820.aspx<\/a><\/li>\n
        4. https:\/\/technet.microsoft.com\/en-us\/library\/dn151092(v=sc.20).aspx<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

          While migrating drivers from SCCM 2012 to SCCM 1511, the migration can fail with the following error message: Couldn’t find the specified instance SMS_CategoryInstance.CategoryInstance_UniqueID=’DriverCategories: This occurs given the following scenario: A driver is added to SCCM A category is assigned to the driver The category is deleted from the driver The migration job attempts to … Continue reading SCCM 1511 Driver Migration Fails<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[110],"tags":[113,171,114,47,111,60,112],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n