Forum Discussion
Agents will install on 2 DC's but will not get configurations
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
7 Replies
The log look perfect. 90% of the time if you have only two actions. It is a boundary issue. Make you are only using up ranges.
Garth-MVPas i have stated on the other forum that you answered me on, this is NOT a boundary issue and I asked you to show me where or how you can prove that it is when i have multiple other servers in the same IP range that have no issues with the client and have all the actions. i have also stated that i can deploy a brand new server to the same IP range and it will automatically get the client installed and will have all the actions.
please tell me where to look so i will say... "WOW Garth was right and it was a boundary issue". I would love to be proven wrong and eat some crow.
for the others that may look at this thread.... i have also done countless WMI repairs as well. i have used scripts to repair the WMI and have ran through the manual steps as well
hi,
try running ccmsetup.exe with this flag. i would remove it first then run it with normal (managment point and site code) flags plus the below one.
this flags reset the ccm client certificate
RESETKEYINFORMATION=TRUE
Thank you, i was soooooo hoping that would work, but it did not. same exact outcome. so here is what i did..
- ran ccmclean and uninstalled the old client.
- deleted the CCM folder, the CCMSetup folder and the SMSCFG.ini from c:\windows
- rebooted the system
- installed the client using an elevated command prompt and the command:
\\mdt-sccm2019\SMS_EC1\Client\ccmsetup.exe RESETKEYINFORMATION=TRUE /mp:mdt-sccm2019.<domainname> /logon SMSSITECODE=EC1
and as i said the same results...
would you check the locationservice.log for errors. it is under CCM\logs folder
