252 posts tagged with "Windows"

Upgrading MDT (Microsoft Deployment Toolkit) is generally not an issue – the main points are:

• Upgrade the Windows ADK before upgrading MDT.
• Make sure you have a backup (or can restore to a pre-upgraded MDT) of the Deployment Share – the Upgrade will upgrade the schema of the MDT database – including allowing new ADK features for your Deployment Share.

Now that we have a backup it is now time to go through the Windows ADK (Windows Assessment and Deployment Kit) upgrade on the MDT server and MDT current branch update. Follow the guide below to complete.

Upgrade Windows ADK​

I will be using Windows ADK for Windows 10, version 1607 in my example.

1. Download the latest Windows ADK – https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit and save the setup file to your MDT server.

1. If you try to install the ADK without upgrading, you will get the following error:

1. So open Program and Features and select Windows Assessment and Deployment Kit – Windows 10 and select Uninstall to uninstall the old ADK (in this example I am uninstalling the v1511 Windows 10 ADK).

1. Select Yes to uninstall the Windows ADK and Close when the uninstall has been completed

1. Now that the old Windows ADK has been uninstalled you can now launch the new Windows ADK downloaded in Step 1 and make sure Install the Windows Assessment and Deployment Kit – Windows 10 to this computer is selected and the install path is correct and click Next

6. You can either select Yes or No to allow Microsoft to collect usage data – I am just going to select No and click Next to proceed with the install

7. Click Accept on the license agreement

8. You will now get greeted by a dialog for installing the features of the Windows ADK – you need: Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tool (USMT) and select Install

9. Once the Windows Assessment and Deployment Kit installation has been completed, restart your MDT server (this is not required – but I prefer to do it to make sure any registered DLLs or registry changes have taken affect and it is in a clean state).

Upgrade MDT​

1. Now that the Windows ADK has been updated – it is time to download the Microsoft Deployment Toolkit – https://www.microsoft.com/en-us/download/details.aspx?id=54259 by selecting Download

2. We are upgrading the x64 version so select this and click Next (same process for x32 – just download that instead).

12. Select Run to start the install

3. You will now have the Install Microsoft Deployment Toolkit Setup wizard – select Next to start the install

4. Accept the License Agreement and select Next

5. Make sure that Microsoft Deployment Toolkit – Documents and Tools and Templates are select and the install path is correct (matches your current MDT install) and click Next

6. Select Yes or No to joining the Customer Experience Improvement Program and select Next

7. Finally – click Install to start the MDT install

8. Once installed click Finish

9. Open the Deployment Workbench

10. It should automatically have your Deployment Share listed under Deployment Shares – if you will need to click File, Add Deployment Share to add your deployment share. Right click your deployment share and select Upgrade Deployment Share

11. Verify that the information is correct and click Next to start the Upgrade

12. This will start the upgrade of the Deployment Share

13. Once the Upgrade of the Deployment Share has been completed – it is time to upgrade the Boot Image

14. Right click your Deployment Share again – and instead of Upgrade, there will be Update. Select Update Deployment Share

15. You will be greeted by the Update Deployment Share Wizard – select completely regenerate the boot images and click Next

16. You will then be forwarded to a review page, verify the permissions are correct and click Next to start regenerating the boot images.

17. Once completed you are finished. You have now hopefully successfully upgraded the ADK, MDT and Boot Images.

One of the problems with Hyper-V 2012 R2 on an Intel NUC – NUC5i7RYH was because of the ‘Client’ network card chipset. Windows Server 2012 would not install the Ethernet Adapter for the Server operating system.

Once I made the manual adjustments to the Network drivers to get this going, I then slipstreamed the drivers and Server 2012 R2 updates (as of Feb 2016) into a Hyper-V 2012 R2 ISO which can then be made bootable for future Hyper-V installations.

Changing the Intel Network Drivers Manually​

7-Zip or WinRAR will be needed to extract the EXE to a folder location. In these examples, I am using 7-Zip.

• Download the Intel x64 Network Drivers here: https://downloadcenter.intel.com/download/23071/Network-Adapter-Driver-for-Windows-8-1-

  (20.7 Date: 2/11/2016)

• Once downloaded. Right click the ‘PROWinx64.exe’ and select 7-Zip and Extract to “PROWinx64” this will extract the driver executable to a folder

• Once extracted navigate to: \PROWinx64\PRO1000\Winx64\NDIS64Find ‘e1d64x64.INF’ and right click and select Open to open with Notepad
• Find the Heading ‘[Intel.NTamd64.6.3.1]’ and copy the devices in this section

• Navigate to the Heading ‘[Intel.NTamd64.6.3]’ and paste underneath the Devices (for example – underneath: PCI\VEN\8086&DEV_15B7&SUBSYS_00011179 – the last line):

• So it looks like the below with the devices from the top copied onto the bottom. You may have some duplicate Device IDs on the bottom section, you can remove these if you want to. I left mine in there. Once confirmed, save the file: e1d64x64.INF.

• Once completed, copy the: NDIS64 folder to a USB flash drive and plug it into one of the Intel NUCs Flash drive slots.
• Open the command prompt and type the following commands to allow unsigned/driver testing drivers:

• Once ran, restart the NUC.
• Once restarted and logged in navigate back to the Command Prompt again and navigate to your USB Flash drive – time to install the drivers.
• Type in the below and press Enter:

• Wait a minute while it installs the driver. Once you have the Windows Security Dialog “Windows can’t verify the publisher of this driver software” select “Install this software anyway”
• Once installed. Restart your Hyper-V server the Network Adapter should now be installed.
• You can then disable the unsigned/driver testing drivers if needed in the Command Prompt window:

• Back at the Server Configuration window (type sconfig in the Command Prompt if missing it) you can now select 8 to configure your Network settings, remember to specify the Computer Name an add it to a Domain if needed.

References: Thanks to an article written by Jay “Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2” for a lot of assistance in getting this going, was able to easily adapt it for the NUC5i7RYH.

Downloading Intel Network Drivers – NUC5i7RYH Compatible​

I have bundled the tweaked driver packed I used into a ZIP file – You can download it here: Intel_NUC_2012R2_NUC5i7RYH_Drivers.zip

(20.7 Date: 2/11/2016). This will take you to Step 8 of the guide above. This driver pack should also be able to be used in a normal Windows Server 2012 R2 x64 environment.

Intel NUC5i7RYH Hyper-V 2012 R2 ISO​

As mentioned earlier. I have created an ISO (which I then used to create my Hyper-V server on my NUC) which I have added the recommended (excluding .Net) Windows Updates (as of Feb 2016) and added the Intel NUC drivers too. This allowed me to easily rebuild my Hyper-V server on the Intel NUC NUC5i7RYH a few times during testing, minimizing the need to do the Network drivers manually and reduced the amount of Windows Updates I had to install.

The ISO I used as a source was Hyper-V Core RTM (9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVERHYPERCORE_EN-US-IRM_SHV_X64FRE_EN-US_DV5) downloaded directly from Microsoft.

I then used a WSUS server to download the 2012 R2 updates and slipstreamed them into the Retail ISO. Then I added the NUC Intel Drivers.

Other than the above: 2012 R2 Updates, Intel Ethernet Drivers for the Intel NUC and enabling the .Net 3.5 feature this is untouched.

This can be downloaded here: SERVERHYPERVCORE_EN-US-NUC_NUCi57RYH_Feb2016.ISO

_README

_

_————

_

_This Hyper-V Core DVD ISO was created by: Luke Murray (Luke.Geek.NZ) on the: 05/03/16

_

_The following adjustments have been made (no other adjustments have been made and should be RTM)

_

_This 2012 R2 server core ISO has the latest Windows Updates slipstreamed (except .net updates) to: Feb 2016.

_

_This 2012 server core also has the following Intel drivers for the Intel NUC system:

_

_Note: Please note Intel does not fully support Windows Server 2012 R2 on the NUC5i7RYH due to using a client Network chipset.

_

_The Network driver’s configurations had to be tweaked to allow installation.

_

_Intel(R) Network Drivers 20.7 (January 21, 2016)

_Intel® 82599EB 10 Gigabit Ethernet Controller

_Intel® 82580EB Gigabit Ethernet Controller

_Intel® Ethernet Server Adapter I340-F4

_Intel® Ethernet Converged Network Adapter X520-SR1

_Intel® Ethernet Converged Network Adapter X520-DA2

_Intel® Ethernet Controller I350-BT2

_Intel® Ethernet Controller I350-AM2

_Intel® Ethernet Controller I350-AM4

_Intel® Ethernet Controller I210-IT

_Intel® Ethernet Converged Network Adapter X540-T2

_Intel® Ethernet Server Adapter I350-F2

_Intel® Ethernet Server Adapter I350-F4

_Intel® Ethernet Controller X540-AT2

_Intel® Ethernet Connection I217-V

_Intel® Ethernet Connection I218-V

_Intel® Ethernet Connection I218-LM

_Intel® Ethernet Controller I210-AT

_Intel® Ethernet Controller I210-IS

_Intel® Ethernet Converged Network Adapter X520-DA4

_Intel® Ethernet Converged Network Adapter X520-QDA1

_Intel® Ethernet Converged Network Adapter X520-LR1

_Intel® 82599ES 10 Gigabit Ethernet Controller

_Intel® 82579LM Gigabit Ethernet PHY

_Intel® Ethernet Server Adapter I340-T4

_Intel® Ethernet Server Adapter I350-T2

_Intel® Ethernet Server Adapter I350-T4

_Intel® Ethernet Connection I217-LM

_Intel® Ethernet Converged Network Adapter X520-T2

_Intel® Ethernet Converged Network Adapter X520-SR2

_Intel® 82579V Gigabit Ethernet PHY

_Intel® Ethernet Converged Network Adapter X540-T1

_Intel® Ethernet Controller I211-AT

_Intel® 82599EN 10 Gigabit Ethernet Controller

_Intel® Ethernet Converged Network Adapter X520-DA1

_Intel® Ethernet Controller I210-AS

_Intel® Ethernet Controller I210-CS

_Note: I take no liability for loss or damage following these guides or using my driver pack or ISO. This is merely intended to help people

_

I recommend using Rufus to load the ISO to a USB flash drive using the settings below:

Once completed, put the USB drive into the NUC and restart. On startup press F10 to navigate to the Boot Menu and select the USB drive.

Some server based applications require to be logged into a service account to allow an Application or service to run, These applications usually require manual intervention by systems administrators to login to the account manually after a server restart.

There are many ways to setup Automatic Logon, using “control userpasswords2” via the Run Prompt, using Third Party utilities like LogonExpert or_ Sysinternals Autologon for Windows  _this simply using RegEdit and setting them manually.

I have created a PowerShell script for editing the registry to set this manually in a standardized way and could be run remotely. It is pretty simple and only requires version 1 of PowerShell.

#authors: [Luke] Murray (Luke.Geek.NZ) #Version: 0.1 #Purpose:

#The purpose of this PowerShell script is to set the AutoLogon and WinLogon registry strings using PowerShell, to setup a Windows Server #or Workstation for Automatic Logon. #The $UserName and $Password variables need to be configuration for your environment. Please make sure the $UserName variables follows #DOMAINNAME\SAMACCOUNTNAME format. #This needs to be ran using an Elevated PowerShell ISE or PowerShell window (with Admin access on the computer you are running this on).

$usrname = 'DOMAINNAME\SAMACCOUNTNAME' $password = 'PASSWORD' $RegistryLocation = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' Set-ItemProperty $RegistryLocation -Name 'AutoAdminLogon' -Value '1' Set-ItemProperty $RegistryLocation -Name 'DefaultUsername' -Value "$usrname" Set-ItemProperty $RegistryLocation -Name 'DefaultPassword' -Value "$password"

Note: Also note following this method, the username and password are not encrypted and stored as plain text in the registry.

.NET Framework 3.5 needs the source files off the Windows Server 2012 DVD in order to install. You can do this online and without needing a restart using DISM.

1. Go to a command prompt and enter this:

dism /online /enable-feature /featurename:NetFX3 /all /Source:d:sourcessxs /LimitAccess

Note: Source should be the Windows DVD location, ie d: /Source:x if x is your DVD mount point.

Note: This is not best practice and is not recommended to do in a production environment.

1. Open Server Manager
2. Click on Local Server (to the left)
3. Select IE Enhanced Security Configuration
4. Select Turn off and click Ok