![]() And the usual response from Microsoft is “we heard you but we don’t talk about futures”. We want NIC teaming! That was the cry … every time, every event, every month. And guess what, just about every networking issue I’ve heard on on Hyper-V was driver or NIC teaming related.Īs a result, I’ve always recommended against NIC teaming using OEM software. If you had a problem, MSFT might ask you to remove it. NIC teaming is something that the likes of HP, Dell, Intel and Broadcom provided using their software. True, MSFT hasn’t had NIC teaming and there’s a KB article which says they don’t support it. The last objection was NIC teaming … VMware had it but Microsoft didn’t have a supported solution. Every objection, one after the next, was knocked down: Live Migration, CSV, Dynamic Memory, and so on. With the current W2008 R2 SP release, I reckon that we have a solution that is superior to most vSphere deployments (think of licensed or employed features). Every time Microsoft gave us a new version of Hyper-V (including W2008 R2 SP1) we got more features to get the solution closer in functionality to the competition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |