NEW MECM 2207: MP LM: EnumerateMPLocation Request (failed inventory)

[Jeshu]

I'm having trouble collecting hardware inventory on PCs, but this is only happening on connected machines at Secondary Sites.
First, it doesn't show me the "Hardware Inventory Cycle" option in the actions tab of the client's Configuration Manager. Then when forcing the inventory cycle from the "Configuration Manager Support Center Client Tools", the following error is generated in the InventoryAgent.log


Going a little deeper, it seems to me that the origin of this error is that when starting the agent (I also tried with the secquency of commands: "net stop ccmexec" then "net start ccmexec"), this strange error 0x8000fff is shown in the CmmMessaging.log in the client, and I understand that the message “MESSAGE PAYLOAD TRANSFER COMPLETE” should be shown at some point, but doesn´t.


And at that time, on the respective secondary site server, these errors are displayed in the MP_Location.log "MP LM: EnumerateMPLocation Request: Assigned site code provided by the client doesn't match the site code of the MP. Rejecting the request." , it always shows below the line starting with "MP_GetInternetMPListForSite" but before that line, it seems to respond normal.

According to the error, it has to do with the site assignment, but I have already checked the following:

- The site assigned in the client corresponds to the correct secondary site.
- In the Boundary Group configuration that I defined for this Site, I assigned the respective secondary site in the "References" tab.
- I have tried configuring the Boundary Group adding the boundary of the AD Site (I previously made sure that the client subnet is within the defined Site in theAD), as well as adding boundaries based on the subnets, but in both cases have the same result.
- I made sure in Monitoring, that there are no errors in the components of the Sites, as well as in the Database Replication. All OK (aparently).

Everything seems to indicate that I need to complete some configuration that may be missing, but I don't understand what it could be. Could someone please help me with a clue, I've been investigating this issue for days, and it affects all 7 secondary sites that I have deployed.

Thanks in advance.

 

[Garth]

Are you using IP Ranges ONLY for your boundaries? AD Boundaries do NOT grantee that the client is within them.

 

[Jeshu]

Are you using IP Ranges ONLY for your boundaries? AD Boundaries do NOT grantee that the client is within them.

Hi Garth, thanks for your reply. Yes, I already tried only with IP Subnet Boundaries and only with AD Site boundaries, but in both cases I get the same result.

 

[Garth]

Hi Garth, thanks for your reply. Yes, I already tried only with IP Subnet Boundaries and only with AD Site boundaries, but in both cases I get the same result.

Just to be 100% clear, you setup ONLY IP Ranges and NOT AD sites or IP subnets.

 

[Jeshu]

Just to be 100% clear, you setup ONLY IP Ranges and NOT AD sites or IP subnets.

Exactly, only with IP of subnets (not supernet)

 

[Garth]

Exactly, only with IP of subnets (not supernet)

IP subnet is NOT the same as IP ranges. Please use IP ranges only for your boundaries.

 

[Jeshu]

IP subnet is NOT the same as IP ranges. Please use IP ranges only for your boundaries.

Thanks Garth. I've removed limits by subnet and configured only by IP range, and I'm still having the same issue.
I'm even thinking of removing these Sites, and setting up the servers as just simple MPs from primary site, which I think will work. but I understand that it would not be the most correct

 

[Garth]

Do you have two sites within the same AD? Did you EVER has another site? Did you reuse a site code?

 

[Jeshu]

Hi Garth!
Yes, in the AD you have created 7 sites. Regarding the Site code, specifically this is a new one, however, there used to be an SCMC 2012 installation (with a couple of Sites, but not this one specifically) that I couldn't properly uninstall because the SQL server no longer existed, so that before installing this new server, I deleted what was in the "System Management" container. So I suspect there might be some trace left somewhere in the AD, which is causing these weird errors.