I agree. I am running Windows Server 2003 on a machine with a DG43NB board, and while the Web site says Server products are not supported, nearly all work (on 2003, at least). The only exception is "PCI Simple Communications Controller." While I can live without that, it seems that Intel really should support the high-end operating systems in common use.
I'm with you. I've always preferred Intel Motherboards for both the PC's and Servers I sell. Now I've got to find another brand to use and I'm dissapointed.
We need Server OS support for desktop boards.
Server OS support would be nice once they've ironed out bugs with desktop drivers first. It'd be nice to think Intel could offer drivers for Server OS's and even non-Windows OS's but they will need to prioritise according to the OS's the most users use first - and for Desktop boards that means Desktop versions of Windows.
I'm still waiting for a long standing audio bug with the 'latest' Intel/IDT drivers to be addressed for my Win 7 DG45ID based PC (it also affects other boards containing the same audio chipset) so if they can't even sort that, then what use would a server version of the same driver with 'issues' be (especially given server related drivers must be even more reliable)?
I think that if there is anything that may tend to 'encourage' Intel towards providing server drivers for (at least some) desktop boards, it may be if they see customers are buying other brands which do offer such support. Just as many people have forsaken using expensive SCSI HDDs in many 'light' server environments, to save money with other technologies such as SATA, many people want servers on the cheap for light use and buying a 'comparibly expensive' server board and case isn't a reasonable option. Vote with your wallets folks and go with the brands that do offer this support if you need it!
I was able to get almost all the required drivers to work with Windows Server 2008 R2 using a DH67CL Desktop Board by doing the following:
For the network driver (which was most important to me):
My desktop board uses the Intel 8259V Network Controller, so I right clicked my Ethernet Adapter in Device Manager, then I selected Update Driver Software -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Network Adapters -> Intel.
I then went through the list of device drivers available for Intel Network cards and selected that seemed the most similar to my network adapter, the Intel 82579LM Gigabit Network Connection and installed the driver (I ignored the errors saying that manually forcing it to install the driver may make the OS unstable). It worked perfectly.
I then inserted the CD that came with my motherboard and browsed the files on it (I didn't/couldn't use the setup program as it wouldn't list anything). In the Software/Drivers directory, I installed the following drivers without any issues by running the individual setup programs for each of them: Intel Chipset Drivers, USB3, and IMEI (PCI Simple Communications controller). I also tried installing the video drivers, which did partially install, but gave me an error towards the end of the installation process. Upon rebooting, the igfxUI.exe file threw errors, but the device driver seemed to work. The error annoyed me so I just uninstalled it since for a web server, it wasn't very important to me and the standard video driver gave me resolutions up to 1920x1080 anyways.
One note... using the web based auto detection for the Intel HD video driver on Intel's website (http://www.intel.com/p/en_US/support/detect/) crashed IE 9 on me when I ran the plug in (it installed, but refused to work on Firefox 9.0.1). I uninstalled it and the Java runtime it required.
Something that I came across that may help with identifying drivers on the Microsoft forums (Thanks Zeusman!):
If you go in device manager, click on the pci simple communications controller, go in property and then go in details. You will see a code like per example PCI/VEN_8086&DEV_27D8&SUBSYS...
The VEN code means vendor and the DEV code means device: in my case the vendor is 8086 and the device is 27D8.
Once you have the two codes, go to www.pcidatabse.com. Enter the two codes and you should get the name of your
hardware. From there you can search for a driver download for your hardware.
In my case the pci simple communications controller was a Microsoft UAA Bus HD audio. I also had another pci
device that didn't work properly, using the same method I found out that my pci device was an HSF PCI internal modem with code number CX11252-11. I had a hard time downloading one of the drivers, after 6 or 7 times the download started so be patient if you have the same hardware
NOTE: to access the device manager, go in control panel, then performance and maintenance, system, hardware and finally device manager.
Update: I tried installing this to a clean system and noticed that the option to use the Intel 82579LM Gigabit Network controller was not available. Thinking about it, I had tried to install the 64-bit driver on the system previously which did copy all the driver files, but failed to detect the adapter. It seems that once this has happened, the driver is then available for manual selection and does work with Windows Server 2008 R2! So you are using the Windows 64 bit driver (mine had the file name PROWinx64.exe) by first trying to install the driver (and letting setup fail) and then manually selecting it.
I also found the following link that may has Windows Server Drivers on it: http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Ethernet+Components&ProductLine=Ethernet+Controllers&ProductProduct=Intel%C2%AE+82579+Gigabit+Ethernet+Controller
Hope this helps!