Hi guys,

I'm currently implementing SCCM 2012 R2 for a WW company. I'm testing Operating system Deployment. this feature works great except that client computer bandwidth is limited to around 20Mbps.

TThe problem is that masters are about 10GB each (Windows + Office 2010 + updates). So file transfer is really long. on server side I've checked for bandwidth limitation = no limitation.

Do you know a way to unlock file transfer ?

By advance, thank you

Rgis

This isn't a limitation in ConfigMgr. The content is being transferred using WebDAV over HTTP directly from IIS to the target system.

You'll have to review your network infrastructure and perhaps the server side NIC and perf in general.

Hi Jason,

I'm not using SCCM 2007, but SCCM 2012. So Webdav isn't used.

From the same WinPE environment, when I perform a download with Powershell as in the following Post (https://social.technet.microsoft.com/Forums/en-US/4c72ae27-198f-4751-b0d6-340a11b52bd4/insanely-slow-os-download-in-2012-r2-winpe?forum=configmanagerosd.) I'm able to perform a 100 Mbps download.

By consequences, it seems to be a limitation from SCCM binaries (TSCore.dll) : not WinPE or DP.

In the post previously mentionned, Microsoft has released a hotfix : https://support.microsoft.com/fr-fr/kb/2905002/en-us. This Hotfix Applies to SCCM 2012 R2 but no to SCCM 2012 R2 CU3.  

Is it possible to bypass pre checks for hofix installation, or do I have to contact Microsoft?

Rgis

I'm not using SCCM 2007, but SCCM 2012. So Webdav isn't used.

That is not correct. WebDAV is always used in 2012. The lack of installing the WebDAV server component is not the same as the WebDAV protocol not being used. The product team simply chose to implement their own WebDAV provider directly into the core product instead of leveraging the Windows Server component.

As for the hotfix, it is included in CU2 for R2 (and above of course).

Have you updated your boot images since installin

Boot images where updated since CU2/3 installation.

In the same time, I've successfully installed hotfix by unzipping it.

Installing this hotfix and updating boot images solved the problem.

Thank you Jason for your help.

Regards,

Rgis

• Marked as answer by Régis Lainé 15 hours 9 minutes ago