Cisco UCS M81KR NICs on Server 2012

We use Cisco UCS internally at my company because of its flexibility and sheer awesomeness. On top of the ridiculously cool NIC failover abilities, it lets us do crazy stuff like move entire Hyper-V servers between different physical blades in a matter of minutes.
I noticed today that after installing a new Server 2012 node from iSCSI boot only a single NIC was present on the server. I had added 3 other vNICs via UCS manager, but Windows had only activated the one iSCSI used for the boot process. I checked Device Manager and found all of the Cisco VIC Ethernet Interfaces appeared as if they were missing a driver. When I tried to update the driver Windows reported it was already up to date.

In order to fix this just open up the properties of the VIC in Device Manager, navigate to the Driver tab, and select Uninstall. Repeat for each VIC showing the yellow warning sign. At the end, right-click the Network adapters and choose Scan for hardware changes. The NICs should come right up with a functional driver.


Recent content I've written for you—just for you!— to enjoy while you're here.


Quick commentary and links to other sources you'll find interesting. I promise.


Some personal background, links to related projects, and other ways to connect.

Hi there. My name is Tom Pacyk and this is my small home on the web. I love the intersection of design, technology, and communication, which is a combination that led me to a career in sales and marketing roles at places like Zoom and ServiceNow. They're a bit old now, but I also had the opportunity to publish a couple of books along the way.

Portland, Oregon is home for me, my wife Beth, and our three kids, but I'm actually a Midwestern transplant—I grew up in the Chicago suburbs and went to school at Purdue and Illinois. When I find some free time I'm probably going to concerts, rooting for the Portland Timbers, or working on my Sunshine Burn Photography project.