NEW SCCM BITS error: 'Not found (404).

[Maiker2k]

Good afternoon.

There is a single-site SCCM 2103 infrastructure, with 4 distribution points, used only for ordinary PCs and laptops, within the organization's network.

Configured interaction via Https, clients receive PKI and configured SUP via https, updates are working.


After recently switched to sccm 2103, errors appear on clients in windows logs every half hour -

The client failed to download policy. The data transfer service returned "BITS error: 'Not found (404).
'Context:' 5 '"(-2147024894).

In Client Settings
Backround Intelligent Transfer Setting Set to - No

On the client in the log DataTransferService.log

DTSJob {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} in state 'DownloadingData'.
CDTSJob :: JobError: DTS Job ID = '{C2038C3A-C89C-4739-9F0D-2407D4FE65B2}' BITS Job ID = '{944D4446-81B4-4692-99B2-BC1B7BE78A0B}' ErrorCode = 0x80190194
CDTSJob :: JobError: DTS Job ID = '{C2038C3A-C89C-4739-9F0D-2407D4FE65B2}' URL = 'https: //sccm.domen.ru: 443 / SMS_MP' ProtType = 3
DTS job {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} BITS job {944D4446-81B4-4692-99B2-BC1B7BE78A0B} failed to download source file https://sccm.domen.ru:443/SMS_MP/.sms_pol?%F7BF22 -0F6F-447B-9114-25750AA2A956% 7D / 30.SHA256: E90E9FCB78F68657562114737C84CA5C1A7D04922A8DFBEA251075DA6C76FAF5 to destination C: \ WINDOWS \ CCM \ StagingB6 {F2295DF.00
DTS job {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} BITS job {944D4446-81B4-4692-99B2-BC1B7BE78A0B} partially completed 0/1 with error 0x80190194 context 5
DTS job {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} BITS job {944D4446-81B4-4692-99B2-BC1B7BE78A0B} partially completed 0/1 with error 0x80190194 context 5
DTSJob {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} in state 'Error'.
DTSJob {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} in state 'NotifiedComplete'.
DTS job {C2038C3A-C89C-4739-9F0D-2407D4FE65B2} has completed:
Status: ERROR (0x80070002),
Start time: 09/25/2021 16:48:31,
Completion time: 09/25/2021 16:48:31,
Elapsed time: 0 seconds

Tell me how you can remove this error? all machines get this error ...