Category: Installation

The blog post of Jay about running Windows Server 2012 R2 on an Intel NUC 54250WYKH and the problems with the on-board network card do apply to Windows Server 2016 CTP4 too.

Keith H. contacted me today (2016/02/23) about the Wireless network card on the Intel NUC 5i5 RYH. I added the steps to install the Wireless network card on the bottom.

Today I installed Windows Server 2016 CTP 4 on my Intel NUC 5i5RYH and encountered the same problem with a non-recognized network card. Intel has decided in all its wisdom to not let you install network card drivers when you are using a Microsoft Server operating system. As described in the blog post of Jay it is however possible to install the network card drivers. The method described works on most hardware with drivers that do not support a Windows Server operating system. The details will change with different hardware.

Warning!To install drivers with an edited INF file you need to trick Windows to install them. With some BCDEDIT commands this can be done. Please make sure the drivers you want to install are legitimate Intel drivers and not downloaded from some rogue site. Because you make some changes to the INF file Windows cannot verify the source of the drivers. There are some checksums for the driver files (included the INF file) and when you edit them the checksum is not valid anymore. When you use the official Intel drivers from the Intel site and you only adjust the INF file as mentioned below you are reasonably safe.

Be very careful not to install drivers from a non-trustworthy source!

Below the steps I took for the Intel NUC 5i5RYH:

  • Login to your Intel NUC 5i5RYH after you installed Windows Server 2016 CTP4
  • Run a CMD command prompt with Administrator privileges (Windows key + R and type CMD and press CTRL + SHIFT + ENTER) and run the following BCDEDIT commands.

bcdedit /set LOADOPTIONS DISABLE_INTEGRITY_CHECKS
bcdedit /set TESTSIGNING ON
bcdedit /set nointegritychecks ON

  • These commands switch the Driver Enforcement off so non verified drivers can be installed.
  • Restart the Intel NUC 5i5RYH.
  • The following part must be done on another computer because you still have no network on your NUC.
  • Download the latest driver for the Intel NUC 5i5RYH network card (link). I downloaded to [C:\Install].
  • Download WinRAR (link).
  • Expand using WinRAR the network card driver package. I unpacked to [C:\Install\LAN_Win10_64_20.4.1].
  • Look at the properties of the network card in [Computer Management], [Device Manager], [Details] and [Hardware ids]. In case of the Intel NUC 5i5RYH the string of text you need is: [VEN_8086&DEV_15A].

clip_image002

  • Using PowerShell find the INF files in the directory where you unpacked the drivers files.
    • Get-ChildItem -recurse | Select-String -pattern “VEN_8086&DEV_15A” | group path | select name
  • The result should look like this:

clip_image004

  • The INF file you need depends on the operating system you are using. [e1d65x64.inf] is for Windows 10 and Windows 2016, [e1d64x64.inf] is for Windows 8.1 and Windows 2012 R2.
  • In my case I needed the driver for Windows 2016 so browse to the directory with the [e1d65x64.inf] file.
  • Open the [e1d65x64.inf] file with notepad and change the following lines:
  • Change the following lines:

[ControlFlags]
ExcludeFromSelect = \
PCI\VEN_8086&DEV_153A,\
PCI\VEN_8086&DEV_153B

  • To: (put an [;] before the three lines after [ControlFlags])

[ControlFlags]
;ExcludeFromSelect = \
; PCI\VEN_8086&DEV_153A,\
; PCI\VEN_8086&DEV_153B

  • Next find the following lines below the [ControlFlags] section, the lines are marked blue below and copy those lines.

clip_image006

  • Next find the [Intel.NTamd64.10.1] section and paste the blue lines below the last line of this section.

clip_image008

  • The result should look like this:

clip_image010

  • Save the file and copy the C:\Install directory to an USB stick.
  • Log on to your Intel NUC 5i5RYH.
  • Copy all of the files from the USB stick to the C:\Install directory on your Intel NUC 5i5RYH.
  • Before you move on check if the message [Test Mode] is visible. If not then go back to the first step and run the BCDEDIT commands again and reboot.

clip_image012

  • Go to [Device Manager], [Properties] of the network card and choose [Update Driver…] from the [General] tab.

clip_image014

  • Next choose [Browse my computer for driver software].

clip_image016

  • Browse to the location of the edited driver files, in this case [C:\Install\LAN_Win10_64_20.4.1\PRO1000], and click [Next].

clip_image018

  • When the drivers are found and installed a warning will be displayed [Windows can’t verify the publisher of this driver software] choose [Install this driver software anyway].

clip_image020

  • After the installation of the driver software is finished the message should look like this:

clip_image022

  • Click [Close] and go back to [Device Manager] to check if the network adapter is now correctly installed.

clip_image024

  • Next run the following BDCEDIT commands:

bcdedit /set LOADOPTIONS ENABLE_INTEGRITY_CHECKS
bcdedit /set TESTSIGNING OFF
bcdedit /set nointegritychecks OFF

  • These commands switch the Driver Enforcement back on so non verified drivers cannot be installed anymore.
  • After running the BCDEDIT commands the Intel NUC 5i5RYH needs to be rebooted and now you have a functional network card.
  • To be sure check if the [Test Mode] message is removed from the desktop!

clip_image026

Good luck with installing the drivers on your Intel NUC 5i5RYH! This method will work for other hardware and drivers too. Just be careful not to install drivers from an untrustworthy source.

Steps to install the Wireless Network Card (added on 2016/02/23) thanks to Keith H.

  1. Clean install Windows Server 2016 TP4 build 10586 (downloaded from MSDN.microsoft.com)
  2. Add Wireless LAN feature; enable automatic restart
  3. Complete Wireless LAN feature installation (watching device manager correctly detects wireless LAN adapter… but I’m not able to connect to my access point)
  4. Reboot NUC
  5. Connect to access point correctly…

After these steps my WiFi card works perfectly. Good luck again!

If you need the drivers for the WiFi card they can be found here:

  1. Download the Windows 10 x64 drivers for the Intel Dual Band Wireless-AC 7265 network card

On the 17th of August Cumulative Update 2 for Microsoft SQL Server 2014 SP1 ​has been released​.

Prerequisites to connect an on premise network to Azure:
* A Microsoft Azure account with spending limit or a subscription
* A router that is supported by Microsoft to connect to Azure, in my situation I used the Cisco ASA 5505. A full list can be found here: https://azure.microsoft.com/en-us/documentation/articles/vpn-gateway-about-vpn-devices/
* A fixed IP address from your internet provide. A dynamic (DHCP) IP address wil work but when you get a new IP address from your provider the connection will be broken and some configuration changes must be made on the Azure site of the network. I will explain later what needs to be changed.
* To make a full Domain Network with on premise (virtual) machines and Azure virtual machines it would be nice to have a Domain  Controller on the on premise site.
* Java Runtime 6.39 to configure the Cisco ASA 5505 (if you are a die hard you can use the console but because my Surface Pro 3 and my work laptop do not have a serial port available I went for the dummy easy way with a GUI)

To configure your Cisco ASA device it turned out that you need to have Java Runtime 7.51 installed. Do not use higher then the ASDM software may not work. An old and not supported version anymore from the date of 15th of April 2015. After you installed Java and the ASDM software you probably need to change the first part of the target in the shortcut to “C:\Program Files\Java\jre6\Bin\javaw.exe”, do not use “C:\Program Files (x86)\Java\jre6\Bin\javaw.exe” because than you keep stuck in “Contacting the device”. But when you use the x64 version of javaw.exe you get the error: “Unable to launch Device Manager from 192.168.1.1”. If you keep using the original first part of the target in the shortcut at “C:\Windows\SysWOW64\javaw.exe” you also keep stuck in “Contacting the device”
My environment:
On Premise network:     192.168.1.0/24
On Premise network gateway (Cisco ASA 5505 router): 192.168.1.1
My (old) public IP address from my internet provider:  83.128.174.71
My On Premise network DNS Server name and IP address: HYP01 – 192.168.1.31

First you need to create a Virtual Network in Azure:
Click on +, Network Services, Virtual Network, Custom Create

01.PNG

Image 1: Custom Create Virtual Network

In the Virtual Network Details screen fill in the name for your Virtual Network (any name that describes you virtual network will do) and choose the location for your Virtual Network (West Europe for me because I live in West Europe). You will see the name you entered appear in the Network Preview image and click on the right pointed arrow in the lower right corner of the screen.

02.PNG

Image 2: Create Virtual Network (Details)

In the ‘DNS Servers and VPN Connectivity’ screen you need to fill in the name and IP address of you local DNS Server and optional a second (or third) DNS Server (for example a public DNS Server if you need to get to the Internet from the Virtual Network. Next you need to select ‘Configure a site-to-site VPN’ under ‘Site-to-site Connectivity’ The ‘Network Preview’ should display the network on Azure and On Premise with the DNS Servers. Click on the right pointed arrow in the lower right corner of the screen.

03.PNG

Image 3: DNS Server and VPN Connectivity

In the ‘Site-to-Site Connectivity’ screen the name for the On Premise network, the public IP address from your internet provider and the address space of your On Premise network must be filled in. Click on the right pointed arrow in the lower right corner of the screen.

04.PNG

Image 4: Site to Site Connectivity

In the ‘Virtual Network Address Spaces’ screen the information for your virtual Azure network must be specified. In my case I am using a 10.10.0.0/22 address space with three subnets; 10.10.1.0/24, 10.10.2.0/24 and a gateway subnet 10.10.3.0/29. You can use only one subnet for your Virtual Machines but just to be able to test with different subnets I created two. The third, the gateway subnet, is mandatory to be able to route through the networks to you on premise network. Click on the ‘V’ in the lower right corner of the screen.

05.PNG

Image 5: Virtual Network Address Spaces

In the Azure website under ‘Networks’ and then the Network you just created you would see an almost finished network. There is still missing a public gateway. To create the gateway click on the bottom of the screen on ‘Create Gateway’ and choose a ‘Static Routing’. The Cisco ASA series do not support ‘Dynamic Routing’. Click on ‘Yes’ at the question if the gateway should be created for the virtual network. Creating a gateway may take some time. Just sit it out and behold! When you get the message ‘Succesfully created a gateway for virtual network Azure_Network’ you are ready to go.

09f.PNG

Image 6: Completed Azure Network overview

Next step is to configure the Cisco ASA 5505. To do so you need to download the VPN Device script from the ‘azure_network’ page. Click on the link ‘Download VPN Device Script’ Because in this situation I am using this type of router I select in the screen ‘Download a VPN Device Configuration Script’ for ‘Cisco Systems, Inc.’ at Vendor, ‘ASA 5500 Series Adaptive Security Appliances’ at Platform and ‘ASA Software 8.3’ at Operating System and click on the ‘V’. Save the script in your downloads location.

10.PNG

Image 7: Download a VPN Device Configuration Script

Next you can configure the ASA with this script so the connection can be established.

 

During my first installation of Microsoft SQL Server 2016 CTP2 on a VM I created for this I got an error message stating that Java Runtime was not installed… (during an full install – selected all features)

Error message: “Oracle JRE 7 Update 51 (64bit) or higher is required”

And when you click on “Failed”:

Yes, of course, I do not want any dependencies on Java Runtime on my SQL Server boxes. So the Java Runtime is not installed on my default machines. The bigger question is of course:

“Why has SQL Server all of a sudden the requirement of Java Runtime since SQL Server 2016 CTP2?”

It turns out that a new feature of SQL Server 2016 CTP2 is PolyBase. “PolyBase is a T-SQL front end that allows customers to query data stored in HDFS”. With PolyBase you can query, using T-SQL, Hadoop or Azure Blob Storage and query it in an adhoc fashion. It also lets you query semi-structured data and join the results with relational data sets stored in SQL Server. PolyBase is optimized for data warehousing workloads and intended for analytical query scenarios.

So the new feature is a great addition in accessing data like Hadoop and Azure Blob Storage together with SQL Server.

So if you need PolyBase then you must install Java Runtime too. I really hope that the Java Runtime dependency will be rewritten to a .Net variant. Or I need to get used to install Java Runtime together with SQL Server. Of course it is better to install the PolyBase feature on a standalone VM in a larger environment.

Word of advice: If you have no experience with installing Microsoft Server products and configuring a Domain Controller, DHCP server and WDS: Make sure you have plenty of time to learn all this or just follow a guide on the Internet to install Windows 8.1 via an USB stick. From here on I presume you have the knowledge to do all that and in fact already have done some or all of the work of setting up a Windows domain, DHCP server and WDS server

After I bought a Surface Pro I decided to reinstall Windows 8.1 Pro on it. Mainly because the device was pre-installed with an image of Windows 8.1 Pro in Spanish, Portuguese or Italian as language choice.

The first thing you need for this is an original Microsoft USB Ethernet adapter. Other brands will not work (for using PXE boot, after installation other USB Ethernet adapters will work). This is because of some firmware code that only supports the Microsoft USB Ethernet adapter.

The second step is to upgrade the firmware of the Surface Pro to the newest version. There is a download available with all the drivers and firmware software you need. Link to the download location.

To install the new firmware you have to go to Computer Management and Device Manager and expand the Firmware section. Update all four of the Firmware devices found there with the software from the link above. Just double click on the first, go to the second tab (Driver) and choose Update Driver. Point to the location of the downloaded software on your drive and let Windows do the magic. Repeat this for all four of the firmware items.

If you have not already installed a WDS server it is time to do so.

Install the WDS role on your server (if it is a home setup like I have, the easiest way is to use the DHCP server machine to install the WDS role).

Configure the WDS role by adding two boot images for Windows 8.1 (x64) (one specifically for the Surface and one for normal installations) and a Windows 8.1 install image. If you have a custom image for Windows 8.1 that could be added too. The second boot image can easily be renamed to Surface Boot Image (x64) or something else so you see the difference.

Add drivers to the WDS server by downloading the drivers from the above mentioned link. Next step is to add the driver of the USB network adapter to the boot image. Make sure the driver “msu30x64w8” is added to the Surface boot image.

After all this is done make sure the Surface Pro is completely off. Press, and hold, the Volume Up button and power on the Surface Pro. (keep the Volume Up pressed) and release the Volume Up button when you are in the settings screen of the firmware. Disable the Secure Boot Control option. Exit and reboot and immediately shutdown the machine by pressing the Power Button.

To install via PXE boot and WDS press an hold the Volume Down button and power on the Surface Pro. Keep the Volume Down pressed until the PXE boot information is displayed. After a few seconds you need to press Enter to start the network boot. From there on the installation is pretty straight forward.

Do not forget to enable the Secure Boot Control option in the firmware settings and install the default keys before you exit and save the firmware settings.