ArtinSoft's Blogs

Software Migration Experts
Welcome to ArtinSoft's Blogs Sign in | Join | Help
in Search

Jose Aguilar's Blog

All things migrations, software and technology

Changing the PXE ROM Boot Program for a Specific Machine with WDS

You can specify the rom boot program to use with a specific machine when using WDS. This allows you to set the machines to always try a PXE boot first, and control its behavior from WDS.  WDS comes with three x86 boot roms, each with different functionality (this also applies to x64 and Itanium – since I only have x86 machines available for testing, I’ll use those roms):

  • Boot\x86\pxeboot.com: Normal boot ROM. It presents the prompt for F12 and boots from WDS ONLY if F12 is pressed
  • Boot\x86\pxeboot.n12: Boots directly from the network (PXE) without waiting for F12 to be pressed
  • Boot\x86\abortpxe.com: Aborts the PXE boot process and continues booting from the next boot device

In order to change the boot rom, you need to have the machine pre-staged in Active Directory, and use the wdsutil command line program. You also need to know either the name or the MAC address of the machine. With that information, you can issue the command:

      wdsutil.exe /set-device /Device:SERVER01 /BootProgram:Boot\x86\pxeboot.n12

OR

      wdsutil.exe /set-device /ID:AA-BB-CC-DD-EE-FF /BootProgram:Boot\x86\pxeboot.n12

The previous lines change the boot rom to pxeboot.n12 of the machine SERVER01.

By using this, when you have to restore an image to a machine, you can just change the boot rom to pxeboot.n12, and the process will take place automatically (depending on how you have it configured). Once it is restored, you can change it back to abortpxe.com, and it will continue booting from the hard drive every time.

Published May 16 2007, 09:42 PM by Jaguilar
Filed under:

Comments

 

jamerr said:

not good

May 30, 2008 10:44 PM
 

Atte said:

Hi,

Perfect, thanks so much for the information. Thats what i have been searching for!

Regards,

Atte

February 7, 2009 5:09 PM
 

Hambone said:

In the second example of the command it seems you still need the Device Name as supplied from the /Device:{WS-Name} parameter ?

May 21, 2009 7:13 AM
 

Jose Aguilar said:

I don't have the required setup available to test it, but IIRC, it was either one of them. If you used the /Device switch, you didn't need to use the /ID, and viceversa.

I test this originally with Windows Server 2003 R2, BTW, this may have changed in newer versions of Windows.

May 21, 2009 8:48 AM
 

Xueling Han said:

"In order to change the boot rom, you need to have the machine pre-staged in Active Directory, and use the wdsutil command line program. "

Does wdsutil prestage the machine in AD or I should do something in addition to the wdsutil to make N12 happen?

June 25, 2009 10:17 AM
 

Jaguilar said:

You Actually need to prestage the machines in Active Directory first. This link over at Technet contains the steps you need to take to prestage the machines:

Prestage client computers

technet.microsoft.com/.../cc759196(WS.10).aspx

Hope that helps!

June 25, 2009 12:03 PM
 

Tom said:

Dude, I can not undo this command , how do I reset it ?

June 6, 2010 6:29 PM

Leave a Comment

(required) 
(optional)
(required) 
Submit

About Jaguilar

Jose A. Aguilar has been working at ArtinSoft for more than 6 years, starting out with Informix to Java migrations and moving on to VB6 to .NET conversions using the Visual Basic Upgrade Companion. He currently works as both Senior Software Migration Consultant and Program Manager for the Visual Basic Upgrade Companion, helping clients to leverage their existing investments in VB6 by moving them to .NET Framework.

This Blog

Syndication

Powered by Community Server (Non-Commercial Edition), by Telligent Systems