free780 Posted October 11, 2013 Posted October 11, 2013 So after weeks of testing/playing etc. WDS on server 2012 as a VM guest on a hyper v host sucks at multicast 1000kbps (if your lucky) through the hyperv vm nic. About 7000-8000kbps though the legacy adapter. Does anybody know how you can force a slowdown request to the wds server? I don't really want to use the legacy nic as its not recommended, it also eats up the cpu. The client is getting flooded with packets due the host being on a gig port. Flow Control helps but only if available on hyper v vm nics (which it isn't).
AngryTechnician Posted October 11, 2013 Posted October 11, 2013 Perhaps enable bandwidth management on the NIC in the VM settings? Will affect the whole VM unfortunately, not just WDS, but might be worth a try.
free780 Posted October 11, 2013 Author Posted October 11, 2013 Tried it. No change. Other than I can throttle it down below 1000kbps.
chazzy2501 Posted October 14, 2013 Posted October 14, 2013 I was told never to use hardware flow control (or I suppose emulated hardware) as the TCP/IP Stack has flow control built in and they conflict?
free780 Posted October 14, 2013 Author Posted October 14, 2013 (edited) Solved it: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Protocol Change TpMaxBandwidth to 1 (the default is 100) that's decimal not hex. This works with a mdt server in hyper v with a 1gbps physical nic and 100mbps clients. If anyone ever has a issue with this let me know as I have literally spent 2 months on this issue. I wish M$ would document all registry keys. Edited October 14, 2013 by free780
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now