Hacking SBS and broadcom to allow teaming on SBS 2008 server how to

Can someone please tell me how to accomplish this?

Yes I know it breaks the wizards. I would like to utilize these 4 nics in teaming though. If there is ever an issue I will break the team, solve the issue and re-team it.

Really makes me wish I paid the extra $500 for the standard os though. Pretty lame of Microsoft...
E J PopeAsked:
Who is Participating?
suityou69Connect With a Mentor Commented:
vdixon79 - Broadcom disabled teaming through their software. The latest driver (v14 onwards), checks if its SBS its being installed on and prevents the teaming option, to adhere to MS guidelines.  Apparently the SBS wizards can break any teams that are configured. It is  SBS that doesn’t officially support teaming.  As SBS is purely a version of server 2008 with wizards and pre configured applications.

If you want teaming you'll need to ask dell for the older driver v12.x allows teaming as it doesn’t specifically check for SBS and allows teaming.

I'd suggest running any wizards and setup first then re-run this older driver setup to enable teaming.
I'd try it in powershell.  See this for reference.

No guarantee that it will work, but, that's what I would try first.

There's also the approach that you configure 1 NIC using the wizards, and then install additional NICs and use other software (NIC manufacturer's tool or may powershell) to configure the team and use the IP settings of the first NIC.

It's completely unsupported by the way (which I think you realize).  I haven't done it, so this is just what I would attempt were I in your shoes.
E J PopeAuthor Commented:
Whats interesting is I have a SBS 2011 Standard server I just built and it came with intel nics and it allowed teaming without a problem.

I have a Dell R710 piece of junk with SBS 2008 on it and Broadcom greys out the teaming options

So wtf is up with that?

Is there some older broadcom driver I can install or older Broadcom control software that doesn't check if the OS is SBS?
You could try using the command line Broadcom tool to see if it will do the trick.

Reference this:
E J PopeAuthor Commented:
I actually finally spent all day working on this after finding which files on dell went to where. They have so many different subsets of broadcom files its ridiculous. I tried the v12.8 at first and it was a pita to install but after several reboots it finally installed. Then I had all sorts of issues getting the server to boot up once the team was configured. It would sit at waiting for computer settings, or whatever that line is when you disable ipv6 that prevents you from logging in.

So I progressively went higher in versions till I got to  14.2. The exact file name is: Bcom_LAN_14.2.0_W2K3_8_64_A04.exe with file size: 23,565MB for those who might see this in the future. It installed perfectly fine without the weird system hang bug. So far I am on day one of this and it is working almost perfectly. I get the performance of the team, but when I look at the virtual nic's properties, it only shows it being a 1Gbps connection instead of a 2Gbps connection like most Intel teams I'm use to making. Does broadcom just not display the added connections like Intel? Or is there something I did wrong?

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.