The Patch resource association is incorrect, and Patches are never showing as applicable
search cancel

The Patch resource association is incorrect, and Patches are never showing as applicable

book

Article ID: 390431

calendar_today

Updated On:

Products

IT Management Suite Patch Management Solution

Issue/Introduction

You have noticed what seems to be patch resource associations as incorrect, and the patches are never showing as applicable.

You have added Windows Server Azure edition, for example as seen here:

However, the software update is not associated with the version you are expecting. You are expecting to see these updates like this:

Environment

ITMS 8.7.x

Cause

PMImport information was not updated and the newer data feed information needs to be downloaded.

Resolution

Make sure the Patch update is properly associated with the desired release. 

Run the following query and see if you get the same results from one working SMP server:

select * from ResourceAssociation
where ParentResourceGuid = '12dfd24d-f125-453b-9031-f26f36c33bb7'  --GUID for the desired MSU. In this example "windows10.0-kb5046616-x64.msu"

In this example, you should get something like this:

ResourceAssociationTypeGuid    ParentResourceGuid    ChildResourceGuid    CreatedDate
F35C6627-F70C-44A0-AFB8-490CE4D3ECAF    12DFD24D-F125-453B-9031-F26F36C33BB7    01E86700-4A22-4205-8B40-7009696E9F5C    2024-12-19 18:23:00.933
644A995E-211A-4D94-AA8A-788413B7BE5D    12DFD24D-F125-453B-9031-F26F36C33BB7    E789C714-B71C-4797-B97A-CCF23BC4F171    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    6721F06D-0923-44F8-A870-2BDC37AF85B3    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    9E3D31E9-85EB-4C57-BD15-4C754E5E93DD    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    C109DEC6-7206-4528-8FF5-67B98E57C141    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    07809646-4779-4C24-AB1E-756C07354A7A    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    B4599D1C-7591-46D5-AFD5-BFAB1A2EB69F    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    86FFC603-A74F-48E3-B2F8-D8075434EC55    2024-12-19 18:23:00.933
9603714F-078D-4B85-989D-81FC23ABF397    12DFD24D-F125-453B-9031-F26F36C33BB7    5CEA226A-74A6-44D3-A291-DCF7B3BE07E1    2024-12-19 18:23:00.933
292DBD81-1526-423A-AE6D-F44EB46C5B16    12DFD24D-F125-453B-9031-F26F36C33BB7    9D5F6BB8-8ADF-49D1-9D84-2932CA46CE1E    2024-12-19 18:23:00.933

If you don't, then you need to get those associations.

Try the following if the associations are missing:

  1. Make sure you are up-to-date with what has been released:

    The current PMImport version can be found on KB 180967 "List of 8.x Windows PMImport Release Dates"

  2. Execute PMimport again as "Full" rather than "Delta" update:



  3. Remove the check mark for "