So, as it turns out, it never hurts to ask. I'm throwing this up as a blog post later.
At a client recently for a side-by-side 2012 R2 SCCM migration, I was testing image build on desktop and laptop models, and noticed that some 2007 clients were able to detect the 2012 MP and were trying to download content from them! That was very undesired, and so we delved into AD Sites and Services and discovered that some of the subnets in a particular site were more expansive than previously thought. We then noticed a perfectly innocuous looking Site, 'CompanyLocation_TestLab' and found that this corresponded to a switch in a testing area nearby. Perfect! I quickly edited the boundaries and set them to this new AD Site and resumed image testing. And so began the slow. Image transfer, and content download dropped to a standstill, even though I applied the slow OSD KB to the boot images, CAS and DPs. I finally asked if there was some sort of traffic bandwidth management/shaping protocol in affect on the testlab subnet. Well, turns out there it! There was a bandwidth shaping device in place for this subnet that has transfers throttled down to much slower than t1 speeds, in order to test remote office performance for the slowest of remote sites. Copying a 3 GB image takes an astounding 12 hours. On Wed, Feb 5, 2014 at 7:40 PM, Johns, Damon (DoJ) < [email protected]> wrote: > One thing that should increase the speed of your boot file downloads > would be trying this > http://www.sccm.biz/2013/05/how-to-boost-up-pxe-tftp-boot-speed.html > > > > But if you have an underlying issue then it may not result in an > improvement as Jason mentioned. > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Owen > *Sent:* Thursday, 6 February 2014 10:46 AM > *To:* [email protected] > *Subject:* Re: [mssms] After installing slow OSD KB in R2, it is still > slow? Did I miss something? > > > > Hmm..is it possible that you have to restart after applying the update? I > just remembered that I installed the update and restarted my primary > servers, but not my Central server...I'm thinking perhaps I need to update > the CAS, as thats where I'm updating the boot.wims from. > > > > Its all I have to go on now, so I'll give it a shot. > > > > On Wed, Feb 5, 2014 at 5:48 PM, Stephen Owen <[email protected]> wrote: > > Could you recommend any troubleshooting steps or tools to use to try to > isolate the issue? Image downloading, MDT Package Download and any data > transfer are all incredibly slow. > > > > On Wed, Feb 5, 2014 at 1:29 PM, Jason Sandys <[email protected]> wrote: > > The hotfix only addressed the actual OS image downloading slowly. > > > > Boot images come down via TFTP and the other content comes down via the > normal content distribution process and BITS. > > > > If you are seeing slow download times on multiple different methods (as > you've described), you've got other issues. > > > > J > ------------------------------ > > *From:* [email protected] <[email protected]> > on behalf of Stephen Owen <[email protected]> > *Sent:* Wednesday, February 5, 2014 11:53 AM > *To:* [email protected] > *Subject:* [mssms] After installing slow OSD KB in R2, it is still slow? > Did I miss something? > > > > Downloading the WinPE image, downloading the toolkit package, all still > taking forever to download. I recreated the WIM after installing the OSD > fix, and applied it to the CAS and each primary. Do I need to restart SCCM > or WDS or anything else? > > > > > > > > > > > > > > > > ------------------------------ > > CONFIDENTIALITY NOTICE AND DISCLAIMER > The information in this transmission may be confidential and/or protected > by legal professional privilege, and is intended only for the person or > persons to whom it is addressed. If you are not such a person, you are > warned that any disclosure, copying or dissemination of the information is > unauthorised. If you have received the transmission in error, please > immediately contact this office by telephone, fax or email, to inform us of > the error and to enable arrangements to be made for the destruction of the > transmission, or its return at our cost. No liability is accepted for any > unauthorised use of the information contained in this transmission. > >
