j1mmyd3an Posted November 23, 2016 Report post Posted November 23, 2016 Hi there, I have a strange issue I haven't been able to resolve. I have one distribution point in our SCCM 2012 R2 environment that will not exceed 100 Mbps when clients are being imaged. For example, 5 clients PXE boot to the DP and begin running a task sequence. Each client gets 20 Mbps. When one client completes, the remaining 4 clients get 25 Mbps, and so on. This DP was not configured to behave this way intentionally and I have been unsuccessful trying to locate any setting to manipulate it. I have read posts about rate limiting inside IIS but none of that is configured. During client imaging while the server NIC is "stuck" at 100 Mbps, I can easily copy large amounts of data to the server and max out the 1 Gbps connection it is on. All of our distribution points are identical and I'm really stumped so I've come here for help. If anyone has any insight on how to troubleshoot this it would be greatly appreciated. Thank you. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted November 28, 2016 Report post Posted November 28, 2016 check the speed and duplex settings of the nic in question, perhaps they are hard coded to 100mb full duplex ? Quote Share this post Link to post Share on other sites More sharing options...
j1mmyd3an Posted November 28, 2016 Report post Posted November 28, 2016 Thank you for your response. The server NIC is set to auto and linked at 1Gbps. When I copy files to and from the server in question I can max out it's gigabit connection. This issue occurs only when serving an image to clients. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted November 29, 2016 Report post Posted November 29, 2016 have you applied this hotfix ? http://support.microsoft.com/kb/2905002/en-us Quote Share this post Link to post Share on other sites More sharing options...
j1mmyd3an Posted November 30, 2016 Report post Posted November 30, 2016 No I have not applied this fix. When I first read about it I didn't think it really applied in this case but after reading the description it just might. I'm hesitant only because I have 40 other servers as distribution points all configured the same and I have never run across this issue. Clearly I botched something in this servers config but I'm really stumped. I really appreciate your response. This is an outstanding forum. Cheers! 1 Quote Share this post Link to post Share on other sites More sharing options...