Windows 10: Do OSD deployments require an SCCM distribution point to be on-site?

Hi I want to know, if I want to deploy operating systems through SCCM, should the SCCM distribution point be in the site where I intend to deploy the operating systems. Thanks

:)

 

MECM/SCCM - Deployment Packages Failing to Distribute - CSendFileAction::SendFiles failed for path *.*. Error code = 0x80070003

Hi all,

I have seen loads of forum posts with this issue with various answers to the problem - all of which I have tried which don't seem to resolve the issue.

We are intermittently having an issues with distributing our Deployment Packages - the main culprit for this has been the Windows Defender Updates as we update these daily.

It is strange because it will be failing to distribute and then randomly decide to work perfectly....and then it will break again.

In the console we get the below message:

Package Transfer Manager failed to update the package "PACKAGEID", Version 11 on distribution point DP NAME . Review PkgXferMgr.log for more information about this failure.

Possible cause: Site server does not have sufficient rights to the source directory.

Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.

Possible cause: There is not enough disk space available on the distribution point.

Solution: Verify that there is enough free disk space available on the distribution point.

In the PkgXFerMgr.log we get the below message:

CSendFileAction::SendFiles failed for path .. Error code = 0x80070003 SMS_PACKAGE_TRANSFER_MANAGER 20/03/2023 09:25:35 43092 (0xA854)

CSendFileAction::SendContent failed; 0x80070003 SMS_PACKAGE_TRANSFER_MANAGER 20/03/2023 09:25:35 43092 (0xA854)

Sending failed. Failure count = 1, Restart time = 20/03/2023 09:55:35 -0000 SMS_PACKAGE_TRANSFER_MANAGER 20/03/2023 09:25:35 43092 (0xA854)

Just some background on the environment and what I have already tried:

Environment:

• MECM/SCCM Version 2211 with the latest hotfix
  
• Remote Content Library
  
• 2 Primary Site Servers - one active - one passive
  
• A mixture of Server 2012 and Server 2019 servers (we are currently migrating to newer Server 2019 servers)
  

What have I tried?

• Confirmed permissions to source directory - this is all fine because as I mentioned - it sometimes decides to work.
  
• Disk space isn't the issue
  
• Disabled Sophos AV on the DP, Primary Site Server.
  
• Recreated the deployment package - this sometimes works for a little while however the package ends up failing to distribute again later on.
  
• Created a brand new distribution point and added it into the environment - this again worked for a little while however package ends up failing to distribute again later on.
  
• Confirmed the DP functionality as I can distribute applications to the DP fine and as mentioned the deployment package has worked intermittently.
  
• Checked server specs DP to see if there was a strain or anything there.
  
• I read there was an issue with having the remote content library on a Server 2019 so I moved the content library back to the Server 2012 server. However a few weeks later the package ended up failing to distribute again and we are back to the state we are now.
  
• Confirmed the server didn't have an issue with the file path length as I read this somewhere too - again not an issue.
  

Thanks in advance,

Kieran

 

SCCM version 1602. Is there anything that we are missing that is causing the deployments to not succeed?

My company recently updated to 1602. We've sent out two patches for updates and neither are deploying to the field(One is at 4% after a month and a half, the other is at 0%). We've confirmed that the deployment package settings are identical to previous
patches that we've deployed. To give you the steps that we took to deploy the patches

• Created the software update group and added all the software for the monthly update to group. (the files are on all of our distribution points as of right now).
• Deployed to a group of test PCs using a specific template that has been in action
• Made the type of deployment required with detail levels showing "only success and error messages"
• For schedule I made available time ASAP as well as deadline.
• Under User Experience we hide notifications in software center, allows system restart (if necessary) outside of maintenance windows
• There are no alerts
• Deployment options are "download software updates from DP and install"

Is there anything that we are missing that is causing the deployments to not succeed?

 

SCCM 1802 Internet-only clients with CMG and CDP

Have successfully deployed SCCM with CMG+CDP and both CMG and CDP show up in SCCM console as Healthy and Ready. Also have success deploying a Client Setting to existing domain-installed SCCM client which can then roam and when on the Internet they can download
applications distributed to the CDP.

Also, manually installed SCCM clients that are Internet-only succeed in registering with the on-prem SCCM site via the CMG.

The breakdown (where I need help) is that Internet-only clients don't see the software deployments. I have searched every log on the client and don't see any clues and don't know how to troubleshoot.

Please can I get some tips on how to follow the chain of steps to get an Internet-only CMG+CDP client to see available and assigned software packages?

Thanks,