Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, July 1, 2014 5:53 AM
Hello,
Let me start by saying that I have my OSD task sequence working and I am able to deploy it to multiple computers and it all works fine.
However, I am experiencing a slight annoyance. When the Task Sequence begins the download of the Operation System wim file to apply to the HDD, the download is very slow. Looking at SCCM Data rates, the server is only sending it out at 40 mbps which means it takes like 45-60 minutes just to download the wim file.
I tried the F8 option into CMD and tried manually copying the wim file over from the server and the server sent the file at 600 mbps which is ideally what you want for a gigabit network.
I am running 2012 R2 CU1 which contains the KB2905002 update which supposedly fixed the issue. I have been searching and search all day and I am officially out of ideas and fixes for this problem. BITS throttling is disabled, there are no rate limits on the DP. No errors in the smsts.log file. I am stumped.
I currently run a Primary Site Server with the DP located on the same server. This is a single box setup, no remote DP's or secondary sites.
I would appreciate if anybody who had similar issues could help me out with this?
I look forward to your response.
Regards,
Kyle.
All replies (10)
Tuesday, July 1, 2014 6:09 AM âś…Answered | 1 vote
Have you re-created your Boot images after applying the hotfix / CU1? You will need to do this otherwise the problem with slow wim downloads will still occur.
To fully fix the issue you should also be using the patch command as part of your Setup Windows and ConfigMgr step so the client is patched at the point of installation following the Apply Operating System step.
I assume you are running the latest version of the Windows ADK also?
Cheers
Damon
Tuesday, July 1, 2014 7:24 AM
I think with Damon advices you probably will find the reason. Additionally, By any chance have you enabled multicast?
Tuesday, July 1, 2014 10:45 PM
I feel like I should have been smart enough to realise this.... Wow....
Thanks so much Damon! I just tried it and before I can even finish typing this it is already halfway done!
Cheers,
Kyle.
Wednesday, July 2, 2014 6:56 AM
No worries!
Cheers
Damon
Monday, August 25, 2014 7:01 PM
Have you re-created your Boot images after applying the hotfix / CU1? You will need to do this otherwise the problem with slow wim downloads will still occur.
To fully fix the issue you should also be using the patch command as part of your Setup Windows and ConfigMgr step so the client is patched at the point of installation following the Apply Operating System step.
I assume you are running the latest version of the Windows ADK also?
Cheers
Damon
In the 2012 R2 CU1 hotfix information I don't see anything about needing to rebuild the boot image. I had installed this update primarily to try and troubleshoot slow WIM downloads as well, however it doesn't seem to have resolved anything for me. I followed the steps which note to update the DPs. Did I miss a where it says to rebuild the boot image?
Testing copying the WIM between my PXE DP and the client I can transfer between 50Mb/s - 75Mb/s (just file copy). When I deploy a TS, the WIM download portion is 1.5Mb/s - 2Mb/s. So is this the boot image possibly?
Can you clarify on what you are saying about using the patch command as part of your setup windows and configmgr step? Do you mean that the client update package is part of just the client that is deployed? So no client + update package to get to client version XXX.1203?
Monday, August 25, 2014 9:58 PM | 1 vote
Hi, yes you will need to re-create the boot images. I'm not sure why its not documented, probably because the patch has been released, then re-released then included as part of CU1.
Here is the original article: http://support.microsoft.com/kb/2905002
In the notes of this KB:
- All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.
- To fully fix the problem in Issue 2, the client side .msp file has to be installed during the "Setup Windows and ConfigMgr task by using the PATCH= command.
- For more information about how to update boot images, see the How to Manage Boot Images in Configuration Manager topic on the Microsoft TechNet website.
Here is a blog that I have followed in the past when implementing the PATCH command as part of the Setup Windows and ConfigMgr step.
Cheers
Damon
Tuesday, August 26, 2014 2:15 PM
- All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.
- To fully fix the problem in Issue 2, the client side .msp file has to be installed during the "Setup Windows and ConfigMgr task by using the PATCH= command.
- For more information about how to update boot images, see the How to Manage Boot Images in Configuration Manager topic on the Microsoft TechNet website.
But the media it discusses re-creating are boot process that wouldn't normally have access to the boot image from the DP. This media was stuff that was created potentially 1x and now exists outside of the environment. I currently have CU1 applied. When I recreate the boot image I see that is still seems to be the same OS version (6.3.9600.16384), should this have changed? What version are you seeing in your 2012 R2 environment that you are having speedy WIM downloads with? It looks like there is a revision to ADK 8.1 that maybe I don't have? It looks like that may take WinPE to 5.1, which is still OS version 6.3 (like I have) but 6.3.9600.17031. http://blogs.technet.com/b/configmgrteam/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-configmgr-osd.aspx . I wonder if I should have that?
I am also trying to figure out how the PATCH command is supposed to affect WIM download speeds. The Setup Windows and Configmgr step of the task sequence is after the WIM would already be downloaded.
Tuesday, August 26, 2014 11:52 PM | 1 vote
Applying CU1 will not change the boot image OS version, it just patches some files that were the root cause of the original issue. I don't exactly know which ones. The version of WinPE with regards to the slow WIM file download really isn't relevant because the version of WinPE that SCCM 2012 R2 uses is tied to the ADK version.
You should have the latest ADK 8.1 installed though if your using SCCM 2012 R2 CU1. If you don't just update it and re-generate your boot images (again).
The use of the PATCH command doesn't affect the download speed of the WIM at all. Its just recommended as patching the client as part of OSD is considered by most to be best practice.
Technically I guess you don't have to apply the CU1 patch at the point of the client installation during the setup Windows and Config Manager step but then you would have new builds always updating to the latest client version post build which is pretty messy.
I guess you have to put this in context. SCCM 2012 R2 was released along with the ADK 8.1 - People updated and some noticed slow WIM download speeds. Microsoft released a hotfix - people applied that and as part of the fix you had to re-generate your boot images and it was recommended that you also patch your client during OSD at the Setup Windows and Config Manager step.
Then that patch was included with CU1 and a newer version of the ADK 8.1 was released with minor bug fixes.
If your still having slowness issues after applying CU1 (Assume you have ADK 8.1 installed) and you have regenerated your boot images and updated your DP's, then I would suggest you log a Premiere Support Case with Microsoft.
Regards
Damon
Wednesday, August 27, 2014 2:38 PM
Hmmm I will have to see whats going on here. My install is currently 2012 R2 CU1 and the install / upgrade path has been:
-Original install of 2012 SP1
-Install ADK 8.1.
-Upgrade site to R2
-Install CU1 upgrade.
I am pretty sure I have an earlier version of ADK 8.1 installed. My winpe.wim files are dated 8/22/2013 and I installed this 12/16/2013. the ADK 8.1 update http://www.microsoft.com/en-us/download/details.aspx?id=39982 came out 4/2/2014 and the CU1 upgrade came out before this.
Would I expect to see those winpe.wim files touched though (and the date updated) after I installed CU1? Maybe I will just uninstall 8.1 and install this 8.1 update, recreate the boots, import them, etc. Thoughts?
Thursday, August 28, 2014 1:27 AM
It shouldn't be required to fix the slow WIM download but if your still having the issue then yes installing that latest version of the ADK 8.1 would be a good idea + re-generate (add) and replicate your boot images.
If you do apply that latest version you might like to update your User State Migration Tool for Windows 8.1 package as the latest version includes some fixes for USMT.