- Nov 18, 2005
- 28,799
- 359
- 126
Intro:
Of course, first time installing a Server OS on my desktop itself, I get to immediately face some odd quirks.
I should have realized driver support with a Server OS will be different, and have less native support for Desktop-level hardware.
My NIC, well the main one that's enabled in BIOS, is the Intel 82579V Gigabit Adapter (onboard, Z68-based motherboard).
Problem:
It appears, natively, this adapter is not supported. A similar model, the 82579LM, is a bundled driver. So, having zero internet access in the OS, and not wanting to invest a great deal of time with some odd solutions I found and rebooting into another OS, I forced the "LM" adapter to install. I get internet, all is well and joyful.
And then I reboot into my Windows 8 install, and I have no internet. And I have no active adapters. And Driver Manager tells me there is a problem with my Intel 82579LM adapter. Huh? Hey Windows, you previously understood it to be an 82579V, and it works just fine thank you.
Uninstall the device, reinstall it and all is well and good.
Discussion:
I have NOT rebooted into WS2012, partially out of fear to discover I have to repeat this whole dance. But also, well just because I haven't.
But what gives? Why would two completely separate installs (one two distinct hard drives) cause driver grief across both systems?
Is this something easily cleared up by installing the specific Intel software/driver package on WS2012? I was just utilizing the provided drivers (base install). On my Windows 8 (prev. Windows 7) system, that was a package I installed at first, alongside all the other base Intel and system driver/software packages when I built the PC.
And have I committed some sinful act by forcing the non-quite-the-same driver in Windows Server?
I figure, if this continues to cause grief, I have a simple solution (pending WS2012 compatibility): I'll re-enable the Realtek onboard ethernet adapter (it's a dual-NIC mobo), connect a second ethernet cable to the switch, and just tell Windows 8 to use the Intel model, and WS2012 to use the Realtek model.
Of course, imho, it would be a far simpler solution to utilize the same adapter, and unless I'm missing something, it shouldn't cause any issues.
Thoughts?
Of course, first time installing a Server OS on my desktop itself, I get to immediately face some odd quirks.
I should have realized driver support with a Server OS will be different, and have less native support for Desktop-level hardware.
My NIC, well the main one that's enabled in BIOS, is the Intel 82579V Gigabit Adapter (onboard, Z68-based motherboard).
Problem:
It appears, natively, this adapter is not supported. A similar model, the 82579LM, is a bundled driver. So, having zero internet access in the OS, and not wanting to invest a great deal of time with some odd solutions I found and rebooting into another OS, I forced the "LM" adapter to install. I get internet, all is well and joyful.
And then I reboot into my Windows 8 install, and I have no internet. And I have no active adapters. And Driver Manager tells me there is a problem with my Intel 82579LM adapter. Huh? Hey Windows, you previously understood it to be an 82579V, and it works just fine thank you.
Uninstall the device, reinstall it and all is well and good.
Discussion:
I have NOT rebooted into WS2012, partially out of fear to discover I have to repeat this whole dance. But also, well just because I haven't.
But what gives? Why would two completely separate installs (one two distinct hard drives) cause driver grief across both systems?
Is this something easily cleared up by installing the specific Intel software/driver package on WS2012? I was just utilizing the provided drivers (base install). On my Windows 8 (prev. Windows 7) system, that was a package I installed at first, alongside all the other base Intel and system driver/software packages when I built the PC.
And have I committed some sinful act by forcing the non-quite-the-same driver in Windows Server?
I figure, if this continues to cause grief, I have a simple solution (pending WS2012 compatibility): I'll re-enable the Realtek onboard ethernet adapter (it's a dual-NIC mobo), connect a second ethernet cable to the switch, and just tell Windows 8 to use the Intel model, and WS2012 to use the Realtek model.
Of course, imho, it would be a far simpler solution to utilize the same adapter, and unless I'm missing something, it shouldn't cause any issues.
Thoughts?
Last edited:
Facebook
Twitter