Site server client won't connect

Chris Hall 0

Hi, I have a small deployment running 2309. I've deployed the agent successfully everywhere except for the site server itself. The policyagent log says "Client is not registered yet. Ignore the policy assignments request." ClientIDManagerStartup log says "[RegTask] - Server rejected registration request: 3". MP_RegistrationManager says "Failed to convert user name <domain><server>$ to a SID (0x8000ffff)", which I suspect is my actual issue. Any guidance on how to resolve this?

1 answer

XinGuo-MSFT 15,011 Reputation points

2024-05-22T09:32:00.6233333+00:00

Hi,

It seems like you’re dealing with the client registration.

“Client is not registered yet. Ignore the policy assignments request.”: This error typically occurs when the SCCM client is not properly registered with the management point. You might want to check the ccmsetup.log file located on the client in %WINDIR%\ccmsetup\Logs for any errors during the installation of the new SCCM client.

If the client is correctly installed and the SMS Host Agent service is up, check LocationServices.log file in C:\Program Files\SMS_CCM\Logs.
Please sign in to rate this answer.
Chris Hall 0 Reputation points

2024-05-22T14:33:13.4766667+00:00

Checking the setup log, the only issues I see are "Failed to get MDM_ConfigSetting instance, 0x80041013" and "Could not retrieve value for MDM_ConfigSetting . Error 0x80041013", but the client successfully installed. In locationservices.log, I see "Instance of CCM_WindowsDOClientConfig doesn't exist in WMI"

XinGuo-MSFT 15,011 Reputation points

2024-05-28T09:22:43.1466667+00:00

The errors you’re encountering are related to the WMI on your SCCM client. Here are some potential solutions based on the error messages:

Failed to get MDM_ConfigSetting instance, 0x80041013: This error often occurs due to issues with the boundaries or registry entries 1. A workaround suggested in a forum 2

Could not retrieve value for MDM_ConfigSetting . Error 0x80041013: This error is usually triggered by problematic boundaries or issues with the registry entries 1.

You may want to check the health of WMI on the machine 3.

Instance of CCM_WindowsDOClientConfig doesn’t exist in WMI: This error message indicates that the WMI class CCM_WindowsDOClientConfig does not exist. This could be due to a problem with the WMI repository on the client machine. You might want to try rebuilding the WMI repository 1.

Chris Hall 0 Reputation points

2024-05-28T17:53:10.24+00:00

I believe I've tried all these recommendations. I've rebuilt WMI, uninstalled and reinstalled the client again, all with the same result and same errors. I don't believe boundaries are an issue. This is a very simple network with a /16 IP range as my boundary. Again, it's only the primary site server that is having this issue, and it's well within the range. Windows Firewall is not enabled for domain and all the computer certificates appear to be valid. In addition, I've upgraded the site to 2403.
Sign in to comment

Share via

Site server client won't connect

1 answer