Agents will install on 2 DC's but will not get configurations

[menz]

Hello,

I have 2 DC's that when i install the MECM agent on them, they will install but will not get the configuration files and when i open the client on the machines its missing the configurations tab and the action tab only has 2 actions. also, on the general tab of the client, the Client Certificate says "none"

I know the easy answer is this is a "boundary issue" but it is not. i have other servers with the same IP address range and they have no issue getting the client fully configured. It is not a local firewall issue as i tried turning it off and got the same results. in the ccmsetup logs i am seeing this "Failed to get MDM_ConfigSetting instance, 0x80041013"

 

can anyone please help figure out what is going on here??

thanks in advance

[GarthMJ]

90% of the time if you only see two action on the device, it is because your boundaries are wrong. Are you ONLY using IP Ranges for boundaries? BTW you log file looks fine.

[menz]

37 minutes ago, GarthMJ said:

90% of the time if you only see two action on the device, it is because your boundaries are wrong. Are you ONLY using IP Ranges for boundaries? BTW you log file looks fine.

hello,

thank you for the reply. I am not trying to argue, after all, i came here looking for help. I have to ask, how can it be a boundaries issue? i have other servers in that same IP range that do not have any issue with the MECM agent. i also have built new machines recently in that IP address range and they all received the MECM agent without any issue or manual intervention. the only thing different between these two servers and the others in that IP range is that these 2 servers are DC's. i have other DC's in other IP ranges and they are getting the agent without issue as well. 

you say that my logs look fine but i am seeing errors and those errors seem to point to the issue of not getting the configuration files as well so i am guessing that it is related.

I do have a mix of IP Ranges and 4 Active Directory sites. These have been in place since 2020 and as i said above, i do not have any issues deploying the MECM agent anywhere else except just these two servers.

[menz]

On 4/11/2025 at 2:06 PM, GarthMJ said:

90% of the time if you only see two action on the device, it is because your boundaries are wrong. Are you ONLY using IP Ranges for boundaries? BTW you log file looks fine.

so i deleted the Active Directory sites and now only habe IP address ranges. client on just those 2 servers still acting the same. i did a repair and that did not work either. 

any other ideas anyone?

[GarthMJ]

On 4/11/2025 at 2:55 PM, menz said:

hello,

thank you for the reply. I am not trying to argue, after all, i came here looking for help. I have to ask, how can it be a boundaries issue? i have other servers in that same IP range that do not have any issue with the MECM agent. i also have built new machines recently in that IP address range and they all received the MECM agent without any issue or manual intervention. the only thing different between these two servers and the others in that IP range is that these 2 servers are DC's. i have other DC's in other IP ranges and they are getting the agent without issue as well. 

you say that my logs look fine but i am seeing errors and those errors seem to point to the issue of not getting the configuration files as well so i am guessing that it is related.

I do have a mix of IP Ranges and 4 Active Directory sites. These have been in place since 2020 and as i said above, i do not have any issues deploying the MECM agent anywhere else except just these two servers.

Did you review the logs to see what boundary? Did you trigger the machine policies. 

[menz]

Did you review the logs to see what boundary? - what do you mean by this? which of the many logs are you talking about? i have been reviewing logs but the errors i am seeing i am not finding a fix for. i will say one thing that changed... i am now getting 

Failed to get MDM_ConfigSetting instance, 0x80041010    ccmsetup    4/14/2025 1:55:52 PM    7104 (0x1BC0)
 

the error number has changed... it was 0x80041013

and yes i have triggered machine policy updates but they are not doing anything

[menz]

@GarthMJ so it was NOT a boundary issue as i expected. on another forum, someone pointed me to the locationservice.log had a line in that cause me to google for answers and it led me to the ClientIDManagerSetup.log where there was another warning for me to google. and that led me to this page which was the fix for both of my DC's

How to correct Client certificate: None error in ConfigMgr | Hasitha Willarachchi

this was the correct fix for my issue

[GarthMJ]

I was just looking up the logs for you. ClientLocation.log will show you which site you are assigned to. Until that shows at site you will have only two actions. 

BTW I you ask about what logs, to look at where, this is my go to for logs and what they do. https://learn.microsoft.com/en-us/intune/configmgr/core/plan-design/hierarchy/log-files

Glad that you found the issue.