Tag Archives: WDS

Adding Tools to our Linux Deployment

Adding Parted Magic to your WDS Server.

Read prior to configuring the server to have an idea of what you are doing and gain an understanding prior to commencement.

If you are reading​​ this, then I assume (good or bad) that you have read my guide on setting up a Windows 2012R2 WDS Server and played with deploying Linux as described in the article.

There is nothing special about using WDS as all we are basically providing is a PXE Boot server that has been configured to allow us to deploy Windows based images or a couple of Linux flavours.

Now, some may like other types of things, so this is where the “Tools” come in.

Parted Magic as we all know is a disk partitioning tool that actually runs GParted. It also contains a Disk Imaging tool based on Clonezilla.

I was going to include adding Clonezilla but Parted Magic is a little easier to get going and doesn’t rely on NFS shares or the like, as all the required bits will be situated in the​​ 

RemoteInstall\boot\x64\linux path.

OK, let’s begin, what’s needed; PMagic_2016_03_02.iso from​​ http://getintopc.com/softwares/utilities/parted-magic-2016-iso-free-download/​​ or anywhere else. This is the latest copy I could find that was free.​​ This page also has information on Computer requirements for running Parted Magic.

If this PMagic_2016_03_02.iso is not the one used, changes must be made to the section of the tools menu that loads the ISO.

This line INITRD LINUX/PMagic/pmagic_2016_03_02.iso​​ in the tools.menu must be edited to reflect the ISO used

Setting up the PMagic folder.

Drill down to the RemoteInstall\boot\x64 folder, and we should already have a sub folder called Linux where we set up Ubuntu and Centos. Make a folder called PMagic and extract the downloaded PMagic_2016_03_02.iso. Also place a copy of the ISO in this folder as shown

The PMagic Folder under Linux

Contents of the PMagic Folder

NOTE:​​ Prior​​ to booting up into Parted Magic, we need to edit the Syslinux.cfg located in the PMagic\boot folder. Open in notepad and replace vmalloc=512Mib with vmalloc=600MiB. I just did all instances.

The first time I booted into PMagic I was presented with an error along the lines of Increase vmalloc in the syslinux.cfg to​​ equal​​ the ISO size plus 32MiB. 600MiB is a nice round figure

From the previous post on deploying Linux from WDS, we should have 2 files in the RemoteInstall\boot\x64\pxelinux.cfg folder. The default file and the tools.menu

When the client PC or VM is PXE booted we are presented with the new Boot menu as previously configured.​​ 

Selecting =DISK TOOLS= gives us the Disk Tools Menu

From here we can select Part’d Magic Full ISO tool.

Selecting​​ Part’d Magic Full ISO will start the process of booting the ISO to a​​ live​​ environment

​​ As Clonezilla is in the menu, I will cover it quickly.​​ 

What’s​​ required?

Clonezilla-live-20161024-yakkety-amd64.zip​​ or ISO or *20161212-zesty-amd64.zip. I had a version​​ earlier​​ than the 20161024 and had no mouse, it just sat in the middle of the screen.​​ 

Create a Clonezilla folder in the following location RemoteInstall\boot\x64\linux

Create a Clonezilla folder in the {drive:\Linux-distributions}
Extract the ISO or zip file to the Clonezilla folder. Copy the Live folder to the​​ RemoteInstall\boot\x64\linux\Clonezilla folder.

Copy the vmlinuz file from the live folder back up to the​​ RemoteInstall\boot\x64\linux\Clonezilla folder

This needs to be done as kernel load line for clonezilla looks like this: Kernel Linux/Clonezilla/vmlinuz


Edit the tools.menu to this: Kernel Linux/Clonezilla/live/vmlinuz and it will work.


Good luck


Windows Deployment Server

This is a quick write-up on WDS, where I have separated the WDS from the DC/DHCP Server. Now, if you are reading this article you have probably setup WDS on the one server with the DC and DHCP roles configured.

What I wanted was a separate WDS Server.. Easy, well I thought so until I tried to deploy my first workstation. There are some gotchas.

What I will do is skip the installation parts covering WDS with MDT.

Starting with a configured DC and a DHCP scope on one server, and WDS/MDT installed on the 2nd server.

Import and configure images as per usual, create a CustomSettings.ini file and Bootstrap.ini to the way you want.
so, the actual settings. First of all, because the WDS Server isn’t on the DHCP server you need to untick both  boxes on the DHCP tab of the WDS Server properties

this shows the top box selected, and yes the deployment worked, but I took a checkpoint of my server, unchecked the top option and deployed another workstation.

DHCP, this is where its all at.

First, because neither option above is selected, there is no option 060 available to select when configuring DHCP scope or server options. So one must be created.

Open DHCP and right click on the IPv4 container. Select “Predefined Options”
IPv4 Pre Defined
then on the Predefined options screen, select Option Name and scroll to 060 PXEClient, click Add, set the Data Type to String, give it a description, set the Option name to PXEClient. click OK
DHCP Predefined PXE Option-2
Go back to DHCP, and into Server Options, and select Configure options
DHCP Server options1

add the following,
DHCP Server options
NOTE: The PXEClient option is set to point to the WDS Server. To do this, right click the option and select properties. Set the String Value to the FQDN or IP of the WDS server.

In the Scope Options, I have added the following
DHCP Scope Options

Select the Scope, and right click and select properties. Set DHCP/Boottp to “Both”
Scope properties
I have also included selected tab settings from the WDS Server properties.
WDS Properties-DHCP
WDS Properties-Boot
DHCP Predefined PXE Response
Restart DHCP and the WDS Services.
I have added a new VM and during the setup of the VM selected deploy an OS latter from a network. Note if a Gen 1 VM a Legacy NIC will be added. A Gen 2 VM will give a NIC that will be able to PXE boot. Either way, boo the new VM and wait for the F12 to PXE Boot prompt.