Jared Heinrichs

  • Technology Blog
  • Winnipeg Computer Repair
  • Winnipeg Photographer
  • Cooking With Jared
You are here: Home / 2016 / Archives for May 2016

Archives for May 2016

May 30, 2016 By Jared Heinrichs Leave a Comment

How to Sysprep & Capture a Windows 10 Image for Windows Deployment Services (WDS)

This post will go over “How to Sysprep & Capture a Windows 10 Image for Windows Deployment Services (WDS)”.

I am going to assume that you have WDS up and running already. If not you might want to check out my other post on how to setup WDS.

Since my last post on WDS I have added a Windows 10 Enterprise Install and Boot “.wim”

How-to-Sysprep-and-capture-image-WDS-001

How-to-Sysprep-and-capture-image-WDS-002

The reason why I needed to show you those last two screenshots is that you capture an image based off a “Gold” level image file you have already loaded into WDS.

How to Capture an image in WDS

You need to click on “Boot Images” and then Right click the image you want to make a capture of.

How-to-Sysprep-and-capture-image-WDS-003

In the Wizard that opens up fill it out like so. I changed the name from “Setup” to “Capture”.  Also the location and file name is where you want the image to be created! You don’t want to be linking to a real .wim file here. I copy and paste the image name into the location/name box.

How-to-Sysprep-and-capture-image-WDS-004

The Wizard will begin to capture an image and save it.

How-to-Sysprep-and-capture-image-WDS-005

Click “add image” and “finish”.

How-to-Sysprep-and-capture-image-WDS-006

It will then pop-up a window asking where the image is that you want to add. It will be pre-filled out and will be in the same location you specified.

How-to-Sysprep-and-capture-image-WDS-007

Accept the defaults and hit “Next”.

How-to-Sysprep-and-capture-image-WDS-008

Next

How-to-Sysprep-and-capture-image-WDS-009

You will see it working.

How-to-Sysprep-and-capture-image-WDS-010

Hit Finish

How-to-Sysprep-and-capture-image-WDS-011

Verify the file is there in Explorer:

How-to-Sysprep-and-capture-image-WDS-012

How-to-Sysprep-and-capture-image-WDS-013

There are several things we need to do now.

  1. Install a clean version of Windows 10 on a machine.
  2. Install some extra 3rd party apps
  3. Make an image of the updated Machine so that we can use it over and over on other machines.

Because we’ve installed a machine before using WDS I will only show you what has changed.

After saying to boot from PXE you will now see that there are several boot images you can select. Because we want to use the “Gold” version we will select the first item.

How-to-Sysprep-and-capture-image-WDS-014

Much like last time you will be asked to install the image using Domain credentials. Enter them

How-to-install-windows-using-WDS-012

Select Windows 10

How-to-Sysprep-and-capture-image-WDS-015

As the wizard progresses just accept the defaults. When the Machine boots up you will be able to log into the machine as the domain admin.

The first thing you will want to do is install some 3rd party applications that you want as part of the image. In my case I downloaded 4 items that I thought would serv as a good example.

  • Adobe Reader
  • The GIMP
  • Notepad ++
  • Wireshark

How-to-Sysprep-and-capture-image-WDS-016

I won’t bore you with install screenshots. Just believe me when I say I have them installed.

How-to-Sysprep-and-capture-image-WDS-017

Now that everything is installed you need to sysprep the machine in order to make the machine imagable. Sysprep can be found in the “C:\Windows\System32\Sysprep” folder.

How-to-Sysprep-and-capture-image-WDS-018

You want to make sure the System Cleanup is set to OOBE. You also want to make sure Generalize and Shutdown is selected. It is important to select “Generalize” is checked because it will remote any unique identifiers from the machine like Serial number and SID. It is also important to make sure shutdown is selected. If the machine reboots it will start the wizard to setup the machine. If it starts the machine will create a new SID so the whole clean up will have been for nothing.

How-to-Sysprep-and-capture-image-WDS-019

You will see something like this:

How-to-Sysprep-and-capture-image-WDS-020

Make sure to set the machine to boot from the network with PXE then let then machine boot. Hit “ENTER” and “ENTER” to get to this screen. You want to use the “Capture” image.

How-to-Sysprep-and-capture-image-WDS-021

You will notice it will start booting from the image you created.

How-to-Sysprep-and-capture-image-WDS-022

The WDS image capture Wizard will start. I’ve highlighted the most important parts of the note. Click “NEXT”

How-to-Sysprep-and-capture-image-WDS-023

Specify the drive directory to capture. Make sure to name the image really well and click “NEXT”

How-to-Sysprep-and-capture-image-WDS-024

Fill out the setting like so. You will need to authenticate to the server

How-to-Sysprep-and-capture-image-WDS-025

How-to-Sysprep-and-capture-image-WDS-025a

The imaging process will then start when you hit next. this is what will look like. The time for this process is fairly long and depends on network and hard drive speeds on both ends.

How-to-Sysprep-and-capture-image-WDS-026

It will eventually finish. Click “Finish”.

How-to-Sysprep-and-capture-image-WDS-027

It’s a good idea to verify that the client uploaded the .wim file correctly to the WDS server. To verify that the file has been uploaded open the WDS tool and go to the “workstations” group. The file you just made should be there!

How-to-Sysprep-and-capture-image-WDS-028

The machine that you syspreped and captured it’s image will have rebooted now. You will notice that the machine will start to go through the setup wizard. The machine is now ready to go.

How-to-Sysprep-and-capture-image-WDS-029

It’s important for us to now to test the newly captured .wim file on another machine. Once we have verified it works it doesn’t matter how many other machines we will want to have this image.

Boot the new machine up with PXE boot and select “Microsoft Windows 10 Setup (x64)”

How-to-Sysprep-and-capture-image-WDS-030

Setup should now start. Choose the local and keyboard input

How-to-Sysprep-and-capture-image-WDS-031

Enter the proper credentials:

How-to-Sysprep-and-capture-image-WDS-032

Select the new image you just created

How-to-Sysprep-and-capture-image-WDS-033

Specify the location

How-to-Sysprep-and-capture-image-WDS-034

The process will start

How-to-Sysprep-and-capture-image-WDS-035

This is normally a good sign! The streaming process has begun!

How-to-Sysprep-and-capture-image-WDS-036

The machine will reboot

How-to-Sysprep-and-capture-image-WDS-037

You will be asked to enter some very basic info

How-to-Sysprep-and-capture-image-WDS-029

The machine will do the reset auto-magically!

If you ever have an issue like the error “Windows could not complete the installation. To install Windows on this computer, restart the installation.” you will want to try hitting Shift-f10. Then typing:

  • CD C:\windows\system32\oobe    [hit enter]
  • msoobe  [hit enter]

Restart the virtual machine and make sure that you have the proper language and country/region entered.

How-to-Sysprep-and-capture-image-WDS-038

 

More to Come!

 

 

Filed Under: Windows Deployment Services

May 30, 2016 By Jared Heinrichs Leave a Comment

How to use WDS to install Windows

If you haven’t checked out this post yet you might want to in order to see “How to setup WDS (Windows Deployment Services)“. Once you have a running copy of WDS you can then proceed with this post.

I will be doing the install on a Hyper-V virtual machine but the process will be identical on real hardware or on other virtual machine software.

How-to-install-windows-using-WDS-001

I will specify “Generation 2”

How-to-install-windows-using-WDS-002

Enter 1024MB for memory. On machines with low memory, you might want to use “Dynamic Memory” as well.

How-to-install-windows-using-WDS-003

Put the VM on the same network as the WDS server

How-to-install-windows-using-WDS-004

Put the VM in a location that has lots of space.

How-to-install-windows-using-WDS-005

Tell Hyper-V you want to install the OS using the network.

How-to-install-windows-using-WDS-006

Verify that the machine will be installed from the network.

How-to-install-windows-using-WDS-007

When you start up the Virtual machine you will see a couple of things. First you should see the mention of “PXE Boot”.

How-to-install-windows-using-WDS-008

Then you will be shown the “WDS Boot Manager”. You must hit “ENTER” pretty fast otherwise you will need to hit “Enter” again to get back to this screen.

How-to-install-windows-using-WDS-009

WDS will show you the Boot.wim very quickly

How-to-install-windows-using-WDS-010

The setup of the OS will start.

How-to-install-windows-using-WDS-011

You will be asked to authenticate yourself

How-to-install-windows-using-WDS-012

You will need to pick the OS

How-to-install-windows-using-WDS-013

The rest of the wizard will look like your typical OS install.

How-to-install-windows-using-WDS-014

It will wait on the server for a few seconds and then the install will go through

How-to-install-windows-using-WDS-015

How-to-install-windows-using-WDS-016

Specify the settings and hit “NEXT”.

How-to-install-windows-using-WDS-017

Agree to the terms

How-to-install-windows-using-WDS-018

Enter Password

How-to-install-windows-using-WDS-019

You will see that when the machine reboots it will be already joined to the Domain

How-to-install-windows-using-WDS-020

You can verify that the machine is on the domain. First check the name of the client machine.

** NOTE **

Notice that it is called the name of the person who installed the client plus the #1. The next time I were to install a client it would be the same except that the number will increment each time. If you don’t like this you can change this option in WDS.

How-to-install-windows-using-WDS-021

As you can see the computer is joined to the domain.

 

 

 

Filed Under: Windows Deployment Services

May 27, 2016 By Jared Heinrichs Leave a Comment

How to setup WDS (Windows Deployment Services)

Microsoft renamed Remote Installation Services (RIS) to Windows Deployment Services (WDS). I haven’t used it’s older brother in years but I wanted to get re-familiarized with WDS. I will be going over the setup of WDS on Windows Server 2012R2. This tutorial is going to go over setting up the entire Server since WDS is dependant on so many things. If your server already has DHCP, AD, or DNS installed you are most likely good to go however if you are having issue you might want to check out what I did to setup the services in this post.

What is WDS?

WDS is Microsoft’s way of streaming an image of a machine to a computer using PXE boot or booting off of Windows PE.

What are the Requirments for WDS?

  • A functioning Windows Server with Static IP address (IPv4 & IPv6)
  • AD/DNS
  • DHCP
  • Windows Deployment Services Role

How are the IP protocols setup on this server?

IPv4

  • Address: 192.168.100.1
  • Subnet: 255.255.255.0
  • Gateway: 192.168.100.254

IPv6

  • Address – 2001:db8::1234:1
  • Subnet Prefix – 64
  • DNS – 2001:db8::1234:1

** NOTE ** – Please note that if you don’t setup IPv6 as a static address then you will get a few errors along the way. We are at the stage where we need to learn to just deal with IPv6.

How to install the roles needed

Open server manager.

How-to-setup-WDS-001

You will need to select and install:

  • Active Directory Domain Services
  • DHCP Server
  • DNS Server
  • Windows Deployment Services
    • Deployment Server
    • Transport Server

How-to-setup-WDS-003

Leave features alone [NEXT].

Notice that you will need to Install AD first, followed by DHCP, DNS and then WDS!

How-to-setup-WDS-004

A friendly remnder if you are doing this on a live server.

How-to-setup-WDS-005

The DNS is pretty straight forward. Click next.

How-to-setup-WDS-006

I highlighted the items that are important. Many junior admins don’t read this info. It’s sad because Microsoft does a really great job of summing up what you need to do in order to get WDS to work!

Next screen you will need to set up Deployment and transport Servers.

Here is what each one does.

How-to-setup-WDS-007

Make sure to select both are checked off:

How-to-setup-WDS-008

Check off the “restart box” and click “Install”

How-to-setup-WDS-009

It’s a good idea to backup the configuration settings.

How-to-setup-WDS-010

Save the config to a safe location.

When the install is done you will need to configure the different roles starting with “Active Directory”.

Click on “AD DS” and then the “More” link.

How-to-setup-WDS-011

Click on “Promote this server to a domain Controller”.

How-to-setup-WDS-012

Enter domain… I entered: jaredheinrichs.prv  (prv ==> private)

How-to-setup-WDS-013

Enter DSRM password

How-to-setup-WDS-014

Verify Netbios domain name and hit next.

How-to-setup-WDS-015

Verify the folder locations

How-to-setup-WDS-016

It’s always a good idea to view the script and back it up. You can run this script using PowerShell.

How-to-setup-WDS-017

Here is the script that will setup Active Directory just as you have seen!

  • active-directory-install

The server will need to be rebooted and logged in with the domain credentials. When you log into the server you will need to select “DHCP” and click more.

How-to-setup-WDS-018

Click “Complete DHCP configuration”.

How-to-setup-WDS-019

Make sure username is entered. Then hit Commit.

How-to-setup-WDS-020

You will need to setup a new scope.

How-to-setup-WDS-021

 

How-to-setup-WDS-022

Enter the scope range. 1-50 won’t be used. We won’t use the Default Gateway address either 192.168.100.254 since the last number is 253.

How-to-setup-WDS-023

Use the defaults on the next couple of screens. Enter Gateway and hit Next.

How-to-setup-WDS-024

This next window should be pre-configured for you.

How-to-setup-WDS-025

You don’t need WINS

Open DNS Manager and verify DNS is up and running.

How-to-setup-WDS-026

One thing I have seen people forget is to setup is “Reverse Lookup Zones”.  Let’s set it up. You need to right click “Reverse Lookup Zone” and select “New Zone…”

How-to-setup-WDS-027

You want to create a primary Zone

How-to-setup-WDS-028

I normally say to replicate this throughout the entire forest. Unless there is some reason not to.

How-to-setup-WDS-029

You will be asked if you want to setup IP4 or IP6 reverse lookup. We’ll only do IPv4 for this tutorial.

How-to-setup-WDS-030

Specify the subnet that you want to create the Zone for

How-to-setup-WDS-031

Select “Secure” only.

How-to-setup-WDS-032

Hit Finish

Right click Server name and click “properties”.

How-to-setup-WDS-033

Make sure that the Reverse IP address for DC01 is in DNS otherwise, you will have issues later on.

Right click the zone you created and click properties.

How-to-setup-WDS-035

As you see the “IP address” is unknown. We need to click “Edit”.

How-to-setup-WDS-036

The server name should already be in the box. Click “resolve” and click “ok”.

How-to-setup-WDS-037

You should now see that “unknown” has changed to the correct IP address of the server.

How-to-setup-WDS-038

Select “Interfaces” tab and then click on “Only the following IP addresses”. Select the primary IPv4 address. Click “OK”.

How-to-setup-WDS-034

 

How to setup WDS

Ok! I bet you didn’t think we’d ever get to this point! You can maybe see why I setup everything before hand so you can see all the work that needs to be done before WDS can be configured.

Open “Windows Deployment Services” MMC. You will see that it says it is not Configured.

9How-to-setup-WDS-039

You will need to right click the server and configure it.

How-to-setup-WDS-040

First screen will remind you why we configured all the previous services on this server.

How-to-setup-WDS-041

Make sure you have “integrated” selected and click “NEXT”.

How-to-setup-WDS-042

You will be asked where do you want to put the files needed for WDS. Please note the warning. You will get a warning if you put the images on the same drive as the System Volume. ie C: drive. I would recommend that you use a different volume if at all possible.

How-to-setup-WDS-044

The warning

How-to-setup-WDS-045

Please read this next page. DHCP is running on this server so we will need to make sure that both check boxes are checked off!

How-to-setup-WDS-046

Make sure that you check “respond to all clients…” and click “Next”.

How-to-setup-WDS-047

** NOTE **

Now I have seen an error message come up several times at this next point. It will look like WDS is setup fine but it will say that the service failed to start up. I believe this happens more on Virtual machines that aren’t that beefy. (ie Doesn’t have a lot of Ram)

What you will need to do is to Right click the server and click “All Tasks “START”. This should “re-try” the starting of the WDS service and it should start up for you.

How-to-setup-WDS-048

Once you have verified that the WDS server is running I like to start making a few groups. You can make groups for your install images. You might want to create one called “Servers” and one called “Workstations”.

How-to-setup-WDS-049

We are going to start by adding a Windows 2012R2 install image.

How-to-setup-WDS-050

You will need to tell the wizard where the “install.wim” file is located. The screen tells you exactly where it is on the Server DVD.

How-to-setup-WDS-051

Browse the Server install path. Mine is “D:\Sources\install.wim”

How-to-setup-WDS-052

Select the versions you need.

How-to-setup-WDS-053

Confirm your selections

How-to-setup-WDS-054

This next part might take a little while. The service will verify the .sim’s integrity is fine. Plus it needs to copy the data from the location you specified to the drive folder you also specified in the setup steps.

How-to-setup-WDS-055

How-to-setup-WDS-055b

Verify that the images have been integrated with WDS.

How-to-setup-WDS-056

I also like to open explorer and verify what WDS did when importing the files. You will noticed that the folder “C:\RemoteInstall\Images\Servers” was created. There are also 3 files. 2 smaller files and one larger one. The larger one is the base image. The two others align with Server Standard Core or Server Standard (Full /w Gui).

How-to-setup-WDS-057

Now the next thing you will need to do is to setup the “Boot” image the machines will be using. Go down to Boot image – Right click and select “Add Boot Image…”

How-to-setup-WDS-058

Similar to the Install image you will need to point to the “boot image”. The Boot image is in the same location as the install image

How-to-setup-WDS-059

Rename the image name to something better. Click “NEXT”.

How-to-setup-WDS-060

View Summary

How-to-setup-WDS-061

Verify that the Boot image has been integrated propperly.

How-to-setup-WDS-062

Congradulations WDS has been setup. Check out this blog post on how to boot a client machine and have it install the Windows OS using WDS.

Filed Under: Uncategorized

May 27, 2016 By Jared Heinrichs Leave a Comment

How to fix: Windows installation encountered an unexpected error. Verify the installation sources are accessible, and restart the installation. Error code: 0xE0000100

You must be getting the “Windows installation encountered an unexpected error. Verify the installation sources are accessible, and restart the installation. Error code: 0xE0000100” error. This is actually a really easy error to fix!

Windows Cannot find the Micrsoft Software License Terms. Make sure the installatio sources are valid

The main reason for this on Hyper-V is that you have haven’t given Hyper-V enough memory. Because of this, Hyper-V/Windows Install could not pass some checks. The default is 512MB and I’ve noticed that on Windows Server  2012 (R2) Hyper-V this can be to little. I recommend 1024MB of RAM as the Minimum amount.

To change this go into the Memory section on the Virtual machine and change it from 512MB -> 1024MB

Windows Cannot find the Micrsoft Software License Terms. Make sure the installatio sources are valid-01

I hope this has helped you learn how to Fix: “Windows installation encountered an unexpected error. Verify the installation sources are accessible, and restart the installation. Error code: 0xE0000100” error!

Filed Under: Hyper-V

May 27, 2016 By Jared Heinrichs Leave a Comment

How to Fix: “Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation”

You must be getting the “Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation” error. This is actually a really easy error to fix!

Windows Cannot find the Micrsoft Software License Terms. Make sure the installatio sources are valid

The main reason for this on Hyper-V is that you have haven’t given Hyper-V enough memory. Because of this, Hyper-V/Windows Install could not pass some checks. The default is 512MB and I’ve noticed that on Windows Server  2012 (R2) Hyper-V this can be to little. I recommend 1024MB of RAM as the Minimum amount.

To change this go into the Memory section on the Virtual machine and change it from 512MB -> 1024MB

Windows Cannot find the Micrsoft Software License Terms. Make sure the installatio sources are valid-01

I hope this has helped you learn how to Fix: “Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation” error!

Filed Under: Hyper-V

  • 1
  • 2
  • Next Page »

Categories

  • Board Game Rules
  • Camera
  • Computer Hardware
    • Blackberry
    • drivers
    • iPad
    • Magic Jack
    • USB
  • Damn Small Linux
  • Exam Notes
  • Facebook
  • FREE Flashcards
  • Games
    • PC
      • League of Legends
    • Wii
    • xbox 360
  • Music
  • Networking
    • Cisco Certification
    • Mitel
    • Palo Alto Firewall
  • News
    • Google
    • Microsoft
  • Operating System
    • Active Directory (2003)
    • Android
    • Command Prompt
    • Damn Small Linux
    • Group Policy
    • Hyper-V
    • IIS
    • ISA 2006
    • Mac OS X
    • Microsoft Exchange Server
    • Powershell
    • Security
    • SME Server
    • Terminal Server 2003
    • Ubuntu Linux
      • Adito Web SSL VPN
      • OpenVpn-als
      • Webmin
    • Virtual Machine Manager
    • Windows 2003 SBS
    • Windows 2003 Server
    • Windows 2008
    • Windows 2008 R2
    • Windows 2012R2
    • Windows 7
    • Windows 8
    • Windows Command Line
    • Windows Deployment Services
    • Windows Server Backup
    • Windows Vista
    • Windows XP
  • Phones
  • Photography
  • Photos
    • Animals
    • Misc
    • Nature
    • Portraits
  • Portfolio
  • Programming
    • CSS
    • HTML
    • jQuery
    • MySQL
    • PHP
    • Script
  • Programs
    • Acrobat
    • Acrobat Reader
    • Adobe Dreamweaver
    • Adobe Illustrator
    • Adobe Photoshop
    • Anti-virus Software
    • Antivirus
    • Backup Exec
    • Bittorent
    • Blackberry BESADMIN
    • Internet Explorer 9
    • Lightroom
    • Microsoft Office
    • Netbeans
    • Onenote
    • Outlook
    • Shelby
    • Sysprep
    • Trend
    • Video Editing
    • Visual Studio
    • Windows Live Writer
    • WireShark
    • XP Mode
    • Zarafa
  • Recipe
  • Review
  • Software Links
  • Troubleshooting
  • Uncategorized
  • Videos
  • Web Applications
    • Brage
    • Google
    • Spiceworks
    • Wordpress
  • Web Browsers
    • Internet Explorer
  • Web Server
    • XAMPP
  • Winnipeg
    • ISP

Try searching this site!

Copyright © 2021 Winnipeg Web Design