[mdt] MDT and pxe boot

[shoggie]

Hi I have set up MDT to use to deloy my windows 7 enviroment but new to all of this and learning as I go. I have finished the install of MDT and I think all is ok for me to start testing but when I f12 on a client it tryes to boot but gets no where. I have set up windows deployment services and have some lite touch boot images.

 

Is there something more I need to do?

does this work over Vlans? Server in a diferent one to the client?

 

Could someone help and point me in the right direction

 

Thanks

[DrPerceptron]

It does work across VLANS but can't remember if I needed to do anything other than set 2x DHCP scope options:

 

066 Boot Server Host Name > .

067 Bootfile Name boot\x86\wdsnbp.com

[shoggie]

Thanks

 

Can you enlighten me more? I do not have DHCP working on the deployment server it is on another server in the domain does this matter? is there something I need to do on the DHCP server or the deploment server?

[DrPerceptron]

It's something we've got on our DHCP box (which is also seperate). Open up the DHCP tool, add your server, expand IPv4 right click on Server Options and "configure options". If you scroll down the list you should see those two options.

 

Then try again.

[PotNoodleTech]

Yes you need to add the entry on your DHCP server to point to your WDS server so that when you PXE boot a workstation it not only gets a DHCP address etc, it also gets pointed to your WDS server to boot the lite touch image.

 

You actually only need

 

066 Boot Server Host Name > .

 

The MDT lite touch image you copy to the WDS server will take care of booting the image. You can have multiple images on teh EDS server and it will automatically create a menu for you to choose from.

[shoggie]

Still no Joy can anyone post a more step by step instructions.

 

Thanks

[fiza]

Make sure when you look at the properties of your WDS Server in the WDS console that you have enabled PXE Response.

[shoggie]

In my windows deployment services I have respond to all clients computers (known or unknown) and PXE responce delay to 0.

onthe dhcp server i have under server options put in 066 boot server host name server name and domain. Also started "WinHTTP Web Proxy Auto Discover" service which I read else where.

 

But still no joy

[PotNoodleTech]

Does a DNS entry exist for your WDS server? If not you need one with exactly the same host name as in your 066 boot server DHCP entry.

[shoggie]

I have a DNS entry of the server yes but not with domain after it. In forward look up and a pointer to the server including domain name in reverse look up?

 

I do have 2 DHCP servers does this matter?

[shoggie]

i get the following error

 

No boot Filename Received

[shoggie]

could it have something to do with 067 not being in place but I would have thought it should find the boot .wim on its own?

[PotNoodleTech]

In WDS in the "%ServerName%\Boot Images" folder you need to right click and "Add boot image" the "LiteTouchPE_x86.wim" that MDS creates in "%MDS SERVER%\%DeploymentShare%\Boot"

 

Basically the process goes:

Workstation >> PXE Boot client >> DHCP Server >> DNS Server >> WDS Server\Boot Images\LiteTouchPE_x86.wim >> MDT Server

 

Dont forget when you make a change to your MDT settings you need to regenerate the image and re-import it into the WDS server.

[shoggie]

Boot.wim all in palce but still no joy

[PotNoodleTech]

Check you have a default boot image set in WDS.

 

WDS >> Servers >> %Servername% >> right click on server and properties >> "Boot" tab >> Default Boot Image (optional) Select your image for x86 architecture.

[shoggie]

Got that thanks. I think 1st problem was down to VLans and DHCP as moved the test pc into the server VLan and now get something different. (so lets see if we can sort this 1st before sorting the origanle problem out).

 

Now I get the Client ip coming up which I did not get before, then it says "downloaded WDSNBP..." but then it then it tells me to

 

press f12 for network service boot

 

Windows Deployment Services: PXE Boot Aborted.

 

PXE-M0F: Exiting HP PXE ROM

 

??????????

 

PS thanks to all that have helped so far on this one

[shoggie]

Quick one on this just pressed the f12 for the second time and it has started something Why F12 twice?

[shoggie]

OK now have it booting to Microsoft Solution Accelerator. But for some reason need to press F12 to start PXE then after it gets its IP address press F12 again before it fails this then kicks is.

 

Why F12 twice?

 

currently default boot image empty but have tried it with it set.

 

This must mean my 1st problem must have to do with VLans?

[PotNoodleTech]

Can get rid of the F12 thing by going:

 

WDS >> Servers >> %Servername% >> right click on server and properties >> "Boot" tab >> "PXE Boot Policy" settings. I use "Continue the PXE boot unless the user presses the ESC key.

 

Glad it's sorted.

[shoggie]

Can get rid of the F12 thing by going:

 

WDS >> Servers >> %Servername% >> right click on server and properties >> "Boot" tab >> "PXE Boot Policy" settings. I use "Continue the PXE boot unless the user presses the ESC key.

 

Glad it's sorted.

 

Thanks for that one

[shoggie]

So getting back to the 1st problem. It looks as if there is nothing wrong with my WDS as it now boots (not carried it on any further yet). But the last thing I want to be doing is putting all my computers into a different VLan to get to this stage. So does anyone have any help on getting it working over different VLans??

 

Must have something to do with the DCHP server Or possibly DNS but all looks as I think it should be in there.

 

Thanks

[camel]

have you setup the DHCP scope options within each scope, e.g. each subnet, rather than the server options?

[shoggie]

I have set up 066 Boot server host name on all 4 of my dhcp servers under Server options. with servername.domain.local.

 

this then appeares in each subnet.

 

is this wrong? Lot of repeating myself if I need to put this rule into every subnet on all 4 servers?

[DellOughta]

shoggie

Thats correct you need the

066 Boot Server Host Name set to IP Address of server (you can use name)

On all dhcp subnets

 

I also have

067 Bootfile Name set to Boot\x86\wdsnbp.com

 

This enables workstations that are plumbed into a particular network port on any of the vlans (subnets) you have in your environment find there way to the MDT\WDS server and the boot image

 

Regards

Mike

Edited March 27, 2012 by DellOughta

[camel]

I have set up 066 Boot server host name on all 4 of my dhcp servers under Server options. with servername.domain.local.

 

this then appeares in each subnet.

 

is this wrong? Lot of repeating myself if I need to put this rule into every subnet on all 4 servers?

 

It isn't wrong, it is a possibility and it is how we have setup here for just 2 subnets. I would prefer write once, read many for standard configurations.

 

On another note, I have the 066 Boot Server option set to just the NETBIOS name not the FQDN and, option 067 set to the path of our default boot image in WDS.