I purchased an ASUS Z87-PLUS for use as a value server.
Unfortunately, when installing Windows Server 2012 Essentials, the Intel I217 network controller is not supported. And no driver is available, either from ASUS or from Intel.
Looking into the issue, I see that ASUS installs the Intel I217V chipset into Z87 motherboards, not the I217UM. And according to Intel, only the 'UM' chip is supported for server operating systems.
see:http://www.intel.com/content/dam/ww...efs/ethernet-controller-i217-family-brief.pdf
*sigh* Intel, ASUS, why do you shaft us so? The difference between these chips appears to be microscopic and artificial in order to 'segment' the market and force us server users into upscale (read: high profit-margin) equipment. Don't you guys understand yet that every time new equipment doesn't 'just work' like it should you're only hurting yourself??
Will the I217V ever be supported by Windows Server 2012 or is it a fool's errand to wait for a proper driver to be released??
Raja, can you please look into this and help explain why this is so and if there are any workarounds other than being forced into stupid solutions like installing an external NIC??
Unfortunately, when installing Windows Server 2012 Essentials, the Intel I217 network controller is not supported. And no driver is available, either from ASUS or from Intel.
Looking into the issue, I see that ASUS installs the Intel I217V chipset into Z87 motherboards, not the I217UM. And according to Intel, only the 'UM' chip is supported for server operating systems.
see:http://www.intel.com/content/dam/ww...efs/ethernet-controller-i217-family-brief.pdf
*sigh* Intel, ASUS, why do you shaft us so? The difference between these chips appears to be microscopic and artificial in order to 'segment' the market and force us server users into upscale (read: high profit-margin) equipment. Don't you guys understand yet that every time new equipment doesn't 'just work' like it should you're only hurting yourself??
Will the I217V ever be supported by Windows Server 2012 or is it a fool's errand to wait for a proper driver to be released??
Raja, can you please look into this and help explain why this is so and if there are any workarounds other than being forced into stupid solutions like installing an external NIC??
Last edited: