MECM OSD intermittent application install failures

Question

MECM version: 2211

• Verified no overlapping boundaries, all boundaries by IP range.
• Appropriate DPs/MPs are associated with Boundaries and BGs.
• We ship our devices directly to users at home so application install steps are set to fail on error.
• We have about 20 servers in our environment in different regions so MPs are not accessible from other regions.

I took over the OSD task sequence in Sep 2023 from another team member that is no longer with us. I recently changed over from using packages in the TS to application packages in our task sequence.

Since doing this there has been intermittent failure (20-30%) of application install during the TS.

On device failing the TS:

SMSTS log

Application install fails with error 0x80004005

Unable to load profiler: 0x80004005

The correct DP is listed for

Sending error status message InstallApplication 3/4/2024 7:25:36 AM 7700 (0x1E14)

and

CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: CorrectServerName.com:80 CCM_POST /ccm_system/request InstallApplication 3/4/2024 7:25:36 AM 7700 (0x1E14)

Further investigation shows these details from the DataTransferService.log:

Successful DTS jobs when correct MP is selected (in same log as failures):

UpdateURLWithTransportSettings(): NEW URL - http://CorrectServerName.com:80/SMS_MP DataTransferService 3/4/2024 7:10:49 AM 2064 (0x0810)

DataTransferService: DTSJob({C80602F1-0625-4984-AB64-F1621DF0B17F}) - created to download from 'http://CorrectServer.com:80/SMS_MP' to 'C:\WINDOWS\CCM\CIDownloader\Staging'.

DTSJob({C80602F1-0625-4984-AB64-F1621DF0B17F}): Job has completed: Status : SUCCESS, Start time : 03/04/2024 07:10:49, Completion time : 03/04/2024 07:11:00, Elapsed time : 11 seconds DataTransferService 3/4/2024 7:11:00 AM 2064 (0x0810)

Failed DTS job when incorrect MP is selected:

UpdateURLWithTransportSettings(): NEW URL - http://InaccessibleServerName.com:80/SMS_MP DataTransferService 3/4/2024 7:10:49 AM 2092 (0x082C)

DataTransferService: DTSJob({E10BD35D-7596-41EA-B57D-49D04A9CEC85}) - created to download from 'http://InaccessibleServerName.com:80/SMS_MP' to 'C:\WINDOWS\CCM\CIDownloader\Staging'. DataTransferService 3/4/2024 7:10:49 AM 2092 (0x082C)

DTSJob({E10BD35D-7596-41EA-B57D-49D04A9CEC85}):CDTSJob::HandleErrors - BITS Job '{D815D5D6-2291-4A9B-BEAC-1F01B3B1FF54}' under user 'S-1-5-18', OldErrorCount=26, NewErrorCount=27, ErrorCode 0x80072EFD, ErrorText='BITS error: 'A connection with the server could not be established' Context: 'The error occurred while the remote file was being processed.'' DataTransferService 3/4/2024 7:37:46 AM 9012 (0x2334)

DTSJob({E10BD35D-7596-41EA-B57D-49D04A9CEC85}):CDTSJob::HandleErrors - URL='http://InaccessibleServerName.com:80/SMS_MP' ProtType=1 DataTransferService 3/4/2024 7:37:46 AM 9012 (0x2334)

Tried Registry fix:

On one of the MP/DPs used for imaging I have set "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP\ManagementPoints" to just the Sever in that subnet. It doesn't seem to have changed anything. Still the same error rate.

The issues seems to be with the devices selecting a MP that is not accessible on that subnet to download the application policy. So this results in the application not downloading to the machine from the DP (CCMcache is empty). Is there a straightforward way to ensure newly imaged devices select the correct MP for downloading content?

I've tried to be as comprehensive in providing details as possible to head off any red herrings.

Answer 1

Hi,

SCCM supports overlapping boundary configurations for content location.

When a client requests content, and the client network location belongs to multiple boundary groups, Configuration Manager sends the client a list of all Distribution Points that have the content.

For the detail information, please refer to the link below:

Configure SCCM 2012 Boundaries

Answer 2

Hi,

Here is an article about how clients find MP for your reference.

https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/understand-how-clients-find-site-resources-and-services

Is there a straightforward way to ensure newly imaged devices select the correct MP for downloading content?

You can use client installation properties to set the assigned management point for a client. For more information, see Client installation properties.

Answer 3

We put in a case with MS and the results were that we have our MPs segregated by network/region. They cannot communicate with one another. Unfortunately per MS the system is not designed for this. During OSD it will randomly reach out to different MPs for Application Package policy.

They did supply a workaround: Set the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM:AllowedMPs key with the local MP fqdn.

I have added this setting to the TS before the application installs and then remove it at the end of the TS. It has drastically reduced the number of failures to a 'normal' level.