Reactivating computers back after excluding them by "SAM - Adjust installs for excluded CIs" does not result in primary key of the associated software installs being recalculatedDescriptionReactivating computers back after excluding them by "SAM - Adjust installs for excluded CIs" does not result in primary key of the associated software installs being recalculatedSteps to Reproduce On a ServiceNow Instance with Software Asset Management Professional plugin activated: 1. Follow the next ServiceNow documentation to use "Exclude software assets on CIs" feature to exclude software installs on a sample server: https://docs.servicenow.com/en-US/bundle/sandiego-it-asset-management/page/product/software-asset-management2/task/exclude-software-assets-cis.html 2. After the software installs are excluded, set u_exclude_from_sam value to false on the sample server to include the software install again in your software reconciliation operation. Expected Behavior: The software installs should have the primary key and discovery model values populated to allow them to match their respective software models. Actual Behavior: You will notice that the software installs do not have primary key and discovery model value which can result in not including these installs in the software reconciliation process. WorkaroundAs a workaround, you may run ReanimateInstalls attached fix script "sys_script_fix_d3d4b5c8b1951110f877dfff0e547a14.xml" to populate the primary key and discovery model values for the affected software installs due to PRB1594601. Please import and test the fix script first in a sub-production environment before performing the same in a production instance. This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.Related Problem: PRB1594601