For those not familiar with the CM database, it can be confusing at times to locate the specific client to which an error message within SMS_MP_CONTROL_MANAGER is referring.<\/p>\n
Let\u2019s take the following error as an example:<\/p>\n
Message ID:<\/strong>\u00a0 5447 When looking at the CM database, specifically at the view, v_R_System, one would notice that there are two columns which have names explicitly containing the label \u201cGUID\u201d \u2013 Object_GUID0 and SMBIOS_GUID0, neither of which match up to the GUID referred to in the error message shown above.\u00a0 Looking at the properties of these two columns, we find that Object_GUID0 is related to the Active Directory object of the resource and SMBIOS_GUID0 is the BIOS GUID of the resource.<\/p>\n So, where can one find the information needed to track down the resource to which the above error message is referring?\u00a0 The answer is the v_R_System column named SMS_Unique_Indentifier0 \u2013 intuitive, isn\u2019t it?\u00a0 Reviewing the properties of this column, we find that this refers to the Unique ID of the resource, which is exactly what the error is returning, the source identifier.\u00a0 I\u2019ve included a couple methods for identifying the resource below.<\/p>\n SQL Method:\u00a0 (Query against the CM database)<\/p>\n SELECT FROM WHERE PowerShell Method: $params = @{Namespace=”ROOT\\SMS\\site_[YOURSITECODE]”; For those not familiar with the CM database, it can be confusing at times to locate the specific client to which an error message within SMS_MP_CONTROL_MANAGER is referring. Let\u2019s take the following error as an example: Message ID:\u00a0 5447 Description:\u00a0 MP has rejected a message from GUID:F36C6053-12D7-404C-AAF6-E406F84DAF50 because the signature could not be validated. If … Continue reading CM 2012–Troubleshooting – MP has rejected a message from GUID:XXXXX<\/span>
\nDescription:<\/strong>\u00a0 MP has rejected a message from GUID:F36C6053-12D7-404C-AAF6-E406F84DAF50 because the signature could not be validated. If this is a valid client,\u00a0 it will attempt to re-register automatically so its signature can be correctly validated.<\/p>\n
\nName0,
\nSMS_Unique_Identifier0<\/p>\n
\nv_R_System<\/p>\n
\nSMS_Unique_Identifier0 = ‘GUID:F36C6053-12D7-404C-AAF6-E406F84DAF50’<\/p>\n
\nEnter your data where the [] are, but omit the brackets.<\/p>\n
\nClass=”SMS_R_System”;
\nComputerName=”[YOURSITESERVER]”;
\nFilter=’SMSUniqueIdentifier = “GUID:F36C6053-12D7-404C-AAF6-E406F84DAF50″‘}
\nGet-WmiObject @params | ForEach-Object {
\n$Name = $_.Name
\n$Name = ” Computer Name:\u00a0 $Name”
\n$ResourceID = $_.ResourceID
\n$ResourceID = ”\u00a0\u00a0 Resource ID:\u00a0 $ResourceID”
\n$ClientVersion = $_.ClientVersion
\n$ClientVersion = “Client Version:\u00a0 $ClientVersion”
\nReturn $Name, $ResourceID, $ClientVersion
\n}<\/p>\n","protected":false},"excerpt":{"rendered":"