There can of course be many reasons for broken ConfigMgr content distribution – lack of space, physical security on disks and many, many others. This is one possibility though – can the site server actually reach the DP though WMI? If not, then this will undoubtedly cause problems.
This happened to my infrastructure, I suspect, through a patch deployment. See here for more information. Anyway, to test if this is an issue, run up a session of WBEMTEST and connect to the DP in question from your site server via:
\\<ConfigMgr DP>\root\CimV2
Assuming you’re getting ‘Access Denied’ (typically with an 80004005 error) this may well be the fix you’re looking for. You will also see the following in the SYSTEM eventlog of the DP:
The server-side authentication level policy does not allow the user XXX from address XXX to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.
You’ll likely see the following in Distribution Manager status messages:
SOLUTION:
In REGEDIT, browse to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\AppCompat
Create a DWORD value:
RequireIntegrityActivationAuthenticationLevel
Give this a value of 0, then restart the machine.
You should now be able to successfully connect via WMI, as will your site server.