I downloaded the file from here, Network Adapter Driver for Windows Server 2008*, Final Release
When I opened it, there appears no subfolder "\PRO1000\Winx64\NDIS64\". In the PRO1000 folder I saw only these subfolders:
Now I did that, but it is still a no-go. If I am not mistaken, I think the problem may be even more basic because this devices Ethernet Controller and Network Controller are not recognized by this operating system. In Windwos Device Manager, these two items appear in Other Devices with yellow exclamation points, along with a generic Unknown Device, which may be the Infrared port. When I right-click either the Ethernet Controller or Network Controller and select to install drivfer by browsing to the file according to your instructions, after going through the motions, it says it cannof find drivers for it, in both cases; or, when an installation program appears to finish, it ends up saying that it cannot complete because there are no Intel devices on your system!
I am not hardware expert, but it does seem like something more very basic is missing from the chain of drivers. If I do not even have recognition of an Ethernet Controller, I would not expect to see a network adapter either. I wish I understood enough to know what the precise problem is, but there is nothing more I can find and nothing more in the way of support than what I see here, as far as I am aware, unfortunately.
I now have this connecting with the native hardwired network adapter by following these instructions, which worked perfectly:
I really hope there is no problem with posting this solution here because it was an extraordinary find, and I am sure others will be glad to see it. If I can find a solution also for the wireless adapter or bluetooth, I shall post it here too. Thanks.
Thank you for the information you have shared with us and it is OK if you POST that information for others to take benefit of it; however, please be aware that Windows Server 2012-R2 has not been validated to work with this Intel® NUC and some drivers will not be available as you can see here:
I'm glad that my post was okay with Intel. I am quite happy with the NUC's performance, such as it is, but I have to say that I am disappointed with the decision not to support WS2012-R2 fully, which is one of the two flagship products from Microsoft, who is unquestionably an important and loyal partner of Intel. I suppose that an assessment of the number of customers who would use it for this purpose was factored into the decison. However, this count underestimates the leverage of this group because they are influential on the larger group of core customers for NUC and purchasers of Intel processors in general. We as a group do testing and evaluation of sorts, and our findings impact the decisions of others. It would not carry much weight if we tested with Home Editions of Windows.
I hope one of the wonderful team at Intel steps up and speaks out to urge the development of a complete set of NUC drivers for Windows Server 2012-R2. I have to believe that there are enough geniuses employed at Intel to overcome any difficulty in doing so, technical or otherwise. Technology and Art are very much akin, and what could be more beautiful than a NUC5i7RYH dancing in step with WS2012-R2? Thank you.
I’m sorry for any inconvenience and we really appreciate your feedback.
You can also see at the Intel® NUC Supported Operating Systems that some NUCs support Windows Server 2012 R2, in case you would like to take a look at it.
Thanks and regards!
It is pitty Windows 2012 R2 is not supported when problem is only in .inf file.
Also if you filter this NUC version in downloads, you will see 5 driver downloads provided for Windows 2012R2 so it leads to a mistaken impression this OS is supported.
Hopefully INTEL will reconsider it and will release compatible LAN and WIFI drivers for newer server OS.
I don't think that it is an issue of driver compatibility. It costs a *lot* of money to fully and properly validate an O/S release on the platform and Intel is not going to say (or imply by making drivers available) that they support an O/S without doing this level of validation. The question becomes: is it worth their while for Intel to do this validation for the 5 people who want to run this O/S release - especially when this expenditure would likely raise the unit cost for every other customer? Ok, maybe more than 5, but you get the thrust of what I am saying...