Hello I am starting to use SCCM for Windows Deployment. I have an image and task sequence which seem to workj fine. The problem is, it takes about 2:30 to image and build a Windows 7 machine. The part which takes the longest is downloading my image (approximately 2:00). I have enabled BITS transfer now and even tried telling my advertisment to access the Distribution Point directly. The WinPE error log is reporting Access Denied to a file share on my site system even though my Network Access account has full control over this path. I have even tried setting the network access account as me as I am a domain admin. This is really frustrating and I would appreciate any help which can be given. Regards Peter Deegan

is bits throttling confiured ? if so try removing it and see does your speed improve (check client agents, Computer Client Agent, BITS) My step by step SCCM Guides I'm on Twitter > ncbrady

if bits throttling is properly configured, you could try checking which duplex mode your switches are operating on and compare it to the .inf files of the network adapter drivers you are using. in my past experience, had to set my switches to 100 Full Duplex.

Is it taking a long time for OSD boot media to load too? If so, try updating your BIOS.

Check NIC settings on ConfigMgr server and Switches, if they are right configured (100/1000 Full Duplex). On Windows Server 2008 also disable Receive Side Scaling (RSS) in advanced properties from Network properties. Also use another device for making sure it's not the device itself which has an issue. Thanks to my collegue Stephan Wibier for the advise. Hope this helps! My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Please let me know whether you enabled the Multicast feature for a Configuration Manager 2007 distribution point running on Windows Server 2008 R2? If so, it caused by Windows Deployment Server (WDS) Services on Windows Server 2008 R2 sends out larger, fragmented packages by default to reduce the number of package hashes that need to be created. This can cause excessive NACK replies from clients, resulting in package resends, if the network switches are unable to keep up. Resolution Setting the "Transfer rate" setting on a Multicast Distribution Point running on Windows Server 2008 R2 has no effect, so the transfer rate needs to be lowered by editing the registry. This can be done by changing the ApBlockSize value in the HKLM\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSMC\Protocol key. When configuring the multicast block size, the most important thing to consider is the MTU of the network. For most ethernet networks, the MTU is 1500 bytes. Since WDS uses IPv4 UDP multicast, we need to subtract the size of those headers as well. WDS also uses a packet header to identify it's protocol, so we must include this also. IPv4 header = 20 bytes UDP header = 8 bytes WDS header = 87 bytes in default configuration Please note that ApBlockSize represents the size of the data block being sent to the client, not the overall size of the packet that WDS is sending. 1500 - (20 + 8 + 87) = 1385. This is the best size to use for ApBlockSize if you do not want packet fragmentation to occur. Hope it helps.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Peter, your issue is probably the Content Library. In SCCM 2007 you would set all the task sequence to 'Access content directly from a distribution point' as opposed to downloading the content as needed. This affects the perfomance very heavily especially when installing things like device drivers or Office. In this new solution its pretty awkward to get that to work, despite having gone through and creating packages for everything it seems to want to reset it to Download content locally anyway. I'm still trying to find some way to get the SCCM 2012 OSD performance up to an acceptable level.