Jump to content


Gareth86

Slow image deployment download since SCCM 2012 R2 upgrade

Recommended Posts

Firstly can I say I love this website, it has helped me out lots of times, I've never had official SCCM training and I've implemented and support SCCM at my college, with great help from here!

 

The problem I'm having now is since I've upgraded to SCCM 2012R2 its extremely slow at downloading images when deploying an OS to a computer. It was working fine on SCCM 2012 SP1.

 

The SCCM Server is running on VMware 5.1 and is using the VMXNET 3 network card.

 

Hope someone can help.

 

Thank you.

Share this post


Link to post
Share on other sites


I've noticed that if I use a WinPE4 Boot Image the download of the OS .wim file is fast else if I use a WinPE5 Boot Image the download is slower.

 

EDIT: seems it's after upgrading to MDT 2013.

Share this post


Link to post
Share on other sites

I've also noticed images are taking a LOT longer to download during deployment and I haven't changed anything that would affect the process bar upgrading to SCCM 2012 R2 from SP1. I'm hoping that there is a quick fix for this as our deployment time has just blown out by at least another 30mins, maybe more....

Share this post


Link to post
Share on other sites

That is something totaly different. it serves as a tweak to load Winpe faster, but does not apply to actual TS deployments inside winpe. But the link you provided is something that all users of SCCM should actualy change to get winpe loading faster. It's a matter of seconds instead of minutes to load winpe when this value is set to at least 8192. 16384 does not work on all devices but the very newest computers.

Share this post


Link to post
Share on other sites

Exactly the same scenario as the OP here, esx 5.1U1 where my SCCM server is running, VMXNET3 NIC, SCCM2012R2 and downloading the image takes a very long time.

Share this post


Link to post
Share on other sites

are all of you using vmware ? have you checked for any updates to vmware to support the newer boot images ?

Share this post


Link to post
Share on other sites

I wonder if there is any update available for your vmware server solution ? can you tell us what version you are running ?

Share this post


Link to post
Share on other sites

I am using ESXi 5.5 to host SCCM 2012 R2 server. Laptops that I apply image to is Lenovo T431S, which was very fast inded with Winpe 4.0. As some have stated above 4.0 is still fast after upgrade to SCCM 2012R2. This makes me beleive the problem lies within Winpe 5.0.

Share this post


Link to post
Share on other sites

Just after checking this out and same problem also:

Hyper-V 2012, DP on Server 2012......chronic download speeds even testing on a VM that sits on the same Virtual network switch as the DP.

 

It seems fine if you specify to Access all content from DP which is the setting I use but just wanted to check this out and it seems to be a problem that has just arose from the upgrade to R2 as this has been tested before on SCCM Sp1 without any issues.

 

50% downloaded and 5 mins have went past on a 2gb wim.

Share this post


Link to post
Share on other sites

ok the problem has been identified apparently (on a separate list) and here's what they said

 

we have identified root cause and Sustained Engineering is going to start working on a hotfix. Basically the block size for how often the Task Sequence Progress bar updated was changed and it was updating much more frequently, causing the download the slow down significantly. I’ll provide more details as I have them. Engineers are working on to create a Hotfix and it make take few weeks before we can see the hotfix

 

 

so i guess a hotfix is coming

 

cheers

niall

  • Like 1

Share this post


Link to post
Share on other sites

Just after checking this out and same problem also:

Hyper-V 2012, DP on Server 2012......chronic download speeds even testing on a VM that sits on the same Virtual network switch as the DP.

 

It seems fine if you specify to Access all content from DP which is the setting I use but just wanted to check this out and it seems to be a problem that has just arose from the upgrade to R2 as this has been tested before on SCCM Sp1 without any issues.

 

50% downloaded and 5 mins have went past on a 2gb wim.

I've never used the "Access all content from DP" option before, I've always used download and run locally but i was testing it today and found the same thing, much quicker.....but would i be right in thinking that this change is the reason some of my packages that run batch scripts didn't work? Two of which execute .bat files with multiple lines. I assume that running them in a "remote run" scenario causes them to execute with a \\server\share based path for the executable rather than a local drive letter which is why they'd failed?

 

.....I spent ages trying to work out why they kept getting an error and I've eventually come to that conclusion, can someone confirm if it sounds correct?

Share this post


Link to post
Share on other sites

Yes it would be a reason.....my Task Sequence fails at some packages if i download all content as my packages are designed and built for accessing from DP first!

Share this post


Link to post
Share on other sites

Yes it would be a reason.....my Task Sequence fails at some packages if i download all content as my packages are designed and built for accessing from DP first!

Is there of distinguishing different task sequence components to use different methods of installation?

 

For example i'd prefer that the OS install went from DP first rather than download then for drivers to download and run locally as this seems to be quicker again on my setup, then again for the apps that run batch files to run locally rather than from the DP.

Share this post


Link to post
Share on other sites

Well that is possible but I am not sure about the driver part.

You could specify your deployment to access all content from DP which will allow for the OS to be installed via accessing from DP then for your packages you could copy each one locally and execute them locally via run command line. The driver part I am not sure as there is more going on to an attach driver package task behind the scenes.

Share this post


Link to post
Share on other sites

Just tried this and my network usage on the SCCM server went from around 30mbit when dowloading the .WIM to around 900mbit. Definitely fixed the problem

Share this post


Link to post
Share on other sites

Hi,

 

I have the same issue, I'll test the hotfix.

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...