Config PC to use pxeboot.n12 for use in WDS

Question

_{Thursday, June 24, 2010 1:57 PM}

Hi,

WDS is running on server2008R2, captured XP machine, deployed it too succesfully.
Now we want to deploy the image to a number of PC's simultaniously using pxeboot.n12
How should we configure the PC ??

Thnx

All replies (7)

_{Friday, June 25, 2010 8:30 AM ✅Answered | 1 vote}

Hi Hvsys,

There’re several methods to skip F12 on PXE boot.

Method 1: Configure it from GUI Window.

1.       Launch WDS in Windows Server 2008 R2.

2.       Right click the WDS server and choose Properties.

3.       On the Boot tab, choose Always continue the PXE boot for known clients or unknown clients as necessary.

Method 2: Use WDSUtil command line utility to configure it.

1.       If you want to specify the boot program based on Architecture, please use the command below.

WDSUTIL /Set-Server /BootProgram:<Relative Path> /Architecture: {x86|ia64|x64}

For example: WDSUTIL /Set-Server /BootProgram:boot\x86\pxeboot.n12 /Architecture: x86

2.       If you want to specify the boot program for the prestaged client computers, please use the command below.

WDSUTIL /Set-Device /Device: <computer name> /BootProgram: <Relative path>

For example: WDSUTIL /Set-Device /Device: Computer1 /BootProgram:boot\x86\pxeboot.n12

Method 3: Rename the n12 boot program pxeboot.n12 to the default boot program name pxeboot.com.

1.       Under the directory of RemoteInstall\Boot\Architecture>, rename the default boot program pxeboot.com to pxeboot.com.old.

2.       Rename n12 boot program pxeboot.n12 to pxeboot.com.

Regards,

Karen Ji

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” This posting is provided "AS IS" with no warranties, and confers no rights.

_{Tuesday, June 29, 2010 2:01 AM ✅Answered}

Hi Hvsys,

Please refer to the link below.

http://technet.microsoft.com/en-us/library/cc771788(WS.10).aspx

Regards,

Karen Ji

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” This posting is provided "AS IS" with no warranties, and confers no rights.

_{Friday, June 25, 2010 6:54 AM}

It sounds to me like you've already done all the steps you require - you just need to do it on the remaining computers.

I imagine that you've setup WDS and created a Capture Image, which you've booted to using PXE on the client machine and captured the XP image?

You've deployed this image too, so I imagine you have a working install image that you can boot too from PXE.

I suggest that you create a multicast session inside WDS. Then boot your clients to the install image in PXE, select the image you wish to restore and restore it.

_{Friday, June 25, 2010 10:52 AM}

Hi Karen,

Thanks for your reply, but things are still blurry for me..
In fact, option 1 as described was set, but still we had to press F12 to get into PXEboot

I tried option 3, set the client PC to boot from network first, but after 20 times the line: "downloading pxeboot.n12 from TFTP" the boot procedure failed and te client PC exits PXEboot.

We really would like to find a solution for this, we are working on a school with several different images to be deployed in different locations.
Our goal is to start a WOL batch file or something similair, the target loaction PC's start up, booting into PXE and receive the appropiate image, without anyone else in school having the possibility to join the session.

I understand the complexity of the scenario but step by step it should be possible, agreed ?

So first this step.. how to get a client PC to boot automatically into PXE without any interference..

Cheers

Hans@school :-)

Edit: We are deploying XP SP3 by the way

_{Monday, June 28, 2010 1:46 AM}

Hi Hysys,

Please restart the WDS service after you 've configured the settings. Please also try to use WDSUTIL command line utility to change the network boot program.

Regards,

Karen Ji

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” This posting is provided "AS IS" with no warranties, and confers no rights.

_{Monday, June 28, 2010 11:01 AM}

Hi Karen,

Going to try the WDSUtil cmd an post the outcome, ok?

I'm surprised how little there is to find about my scenario.. do you happen to know some guides or helpfull links ??

Much appreciated.. :-)

_{Tuesday, June 29, 2010 10:42 AM}

Hi Karen,

Thanks again for your replies, and helpfull link.

Things are clearer now, and we managed to deploy an image without touching the client PC.
However, I think there is much to improve for WDS deployment...
Anyway, we're a few steps further, so thank you for your time and support.

Cheers

Hans