Thursday, November 20, 2008
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
Forgot Password ?

Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Forums > Related Technologies > Windows Deployment Services
Subject: WDS Boot Manager Menu
Prev Next
You are not authorized to post a reply.

AuthorMessages
tedkarUser is Offline

Posts:22

Send Message
02/06/2008 11:44 AM  

Does anyone know how to reorder the boot manager menu?  I have 7 different boot images but I would like to moved them around?  I am in mixed mode so the legacy RIS entry is listed there as well but this seems to be at the bottom.

Thanks

Ted

 

Mike DzikowskiUser is Offline
Deployment Forum MVP

Posts:120

Send Message
02/06/2008 4:43 PM  
I'm curious as to why so many?

 

Mike Dzikowski
Mike Dzikowski, MCP
tedkarUser is Offline

Posts:22

Send Message
02/06/2008 8:45 PM  
At some point, some will be gone but for now here are the different images:

1. Lab Deployment - This uses the original Vista DVD to create the reference PC and that image is captured and used in 2 and 3.

2. QA Image Share - This is used for me to QA the image created in #1 prior to posting to the production Network deployment point in #3.

3. Prod Image Network Share - This is used by the deployment team to send out the image.

4. Packaging Image Network Share - This is used by our application packaging team to create their systems. Completely different build of Vista.

5. XP Imaging Boot CD (new) - This is a CD that boots to our network to deploy XP. This utilizes IMAGEX and all images have been converted to WIM. This will eventually replace 6 and 7.

6. Image Boot CD - This is used in case someone needs to create an image of a Vista system and then bring it down again (ex. failed hard drives). Also, uses IMAGEX.

7. Legacy RIS. Now contained in there is the current XP imaging CD (using PQIDEPLOY) and all the reference PC builds.

Thanks
KrishUser is Offline

Posts:3

Send Message
02/18/2008 7:38 PM  

Hi,

I'm not sure if this is the case with you since it is a mixed mode WDS. The display order is stored in the BCD file. Strangely, it looks like WDS store this in \RemoteInstall\Tmp folder by default. There are different bcd files with platform.{guid}.bcd for each platform. You can try editing the bcd file relevant to you.  If  it is x86 platform, use the file x86.{guid}.bcd file and,

bcdedit -store x86.{guid}.bcd /enum

will show you the current entires. Display order is the first thing it displays, so you will have to scroll up. Display order is specified as series of Guids for each entry.

Then set the boot order requred with

bcdedit -store x86.{guid}.bcd -set {bootmgr} displayorder {guid1} {guid2} .....{guid7}

Bcdedit is available in vista/vista winpe.

This works for me, but I don't have as many entries as you :-) Please take a copy of the file before you edit in case if it did not work for you.

Hope this helps.

Krish

 

tedkarUser is Offline

Posts:22

Send Message
02/19/2008 11:42 AM  
That worked great!  Thank you.
SeanlvUser is Offline

Posts:1

Send Message
11/10/2008 11:40 PM  
Posted By Krish on 02/18/2008 7:38 PM

Hi,

I'm not sure if this is the case with you since it is a mixed mode WDS. The display order is stored in the BCD file. Strangely, it looks like WDS store this in \RemoteInstall\Tmp folder by default. There are different bcd files with platform.{guid}.bcd for each platform. You can try editing the bcd file relevant to you.  If  it is x86 platform, use the file x86.{guid}.bcd file and,

bcdedit -store x86.{guid}.bcd /enum

will show you the current entires. Display order is the first thing it displays, so you will have to scroll up. Display order is specified as series of Guids for each entry.

Then set the boot order requred with

bcdedit -store x86.{guid}.bcd -set {bootmgr} displayorder {guid1} {guid2} .....{guid7}

Bcdedit is available in vista/vista winpe.

This works for me, but I don't have as many entries as you :-) Please take a copy of the file before you edit in case if it did not work for you.

Hope this helps.

Krish

 

Thanks for your sharing. This method is not for permanent changing the order. When you restart WDS Service, you will find the Boot Manager Menu change to before status.     Now, I know we can change the phycical boot image filename like,  001_LitePE.wim    002_FullPE.wim  in the  RemoteInstall\Boot\x86\Images\ folder. Then you will see 001_LitePE.wim  above 002_FullPE.wim in the Boot Manager Menu.   However, my approaching is NOT perfect.  If a x64-based PC boot from WDS PXE, the Boot Manager Menu will show x64 AND x86 boot image. You will find x64 boot image always below the x86 boot images, although you may have a boot image named 000_LitePE_x64.wim in the RemoteInstall\Boot\x64\Images\ folder.
Anyone who have a better solution, pls share.
 


You are not authorized to post a reply.
Forums > Related Technologies > Windows Deployment Services > WDS Boot Manager Menu



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.
Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt