SCCM clients not downloading and Initializing policies

Are your SCCM clients not downloading and initializing policies?

You’ve already tested the following.

  • Client logs. Nothing stands out as being the problem.
  • Connectivity to the management point.
  • Boundaries and location information.
  • SCCM client health.
  • All the 1.2.3.4’s of the SCCM client.

Run the following query. Connect to the SCCM database using SQL management studio with an account that has permissions to make changes to the database.

Note: Making direct SCCM database changes is not supported by Microsoft. So tread with caution.

Run the following query within the SQL management studio.

SELECT * FROM ResPolicyMap
WHERE machineid = 0 AND
PADBID IN (
SELECT PADBID
FROM
PolicyAssignment
WHERE BodyHash IS NULL
)

Now, If you receive more than 1 row set of data. You’ve got a problem; just like you see in the below image.

SCCM client not receiving policy

Now the above step was just a query; A query that let you know that there was a problem.

Now let’s delete the above data. To delete the above data, run the following query.

DELETE FROM ResPolicyMap
WHERE machineid = 0 AND
PADBID IN (
SELECT PADBID
FROM
PolicyAssignment
WHERE BodyHash IS NULL
)

The last step is to restart the SCCM service on the Server and on the client. But this step automatically happens with time.

Advertisement: SOE magic – SCCM task sequence orchestrator.

Related Articles

SCCM task sequence UI – Set computer name and more during an SCCM task sequence deployment

It is always a unique challenge of having to build an OSD experience that includes providing a great user experience during the deployment of a new operating system.

The attached application would allow you to present a front-end to an active end-user who is executing the SCCM task sequence……

Keywords: SCCM tasksequence UI, SCCM Task Sequence User interface, SCCM task sequence Set computer name.

Responses

Are you an SCCM administrator?

SCCM Task Sequence deployment orchestrator.

built on best practices, learnings & insights of industry experts.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.