We have an extremely large environment and we cannot enable PXE on some networks. I currently have bootable KBEs on thumb drives that boot directly to the needed RSA for that building. I'm looking at getting all of these on one since we're about to spin up another six RSA's, and I would like to prevent the techs from carrying multiple thumb drives.

I just found this out, and they would like to have something by next week. I looked at a few third party tools that should take care of this, but I'm wondering if anyone else has done something similiar?

Yumi sounds like it would work. Has anyone used it?

http://www.makeuseof.com/tag/boot-multiple-live-cds-usb-disk-yumi-windows/

Answer Summary:
Cancel
2 Comments   [ + ] Show Comments

Comments

  • Looks promising, please let us know if it is successful!
  • Yes I use YUMI for our images. We currently boot up to Ghost and the put the image on that way. The one in my pocket right now has three images, a Windows 7 install and some virus protection tools.
Please log in to comment

Community Chosen Answer

3

I ended up using yumi. It was an extremely simple setup, and it looks to be working so far.

I created my boot environments using the KBE manipulator and setting the static IP for each RSA. After is was created I navigated to Deployments>Boot Environments and selected my KBE. I then selected "Download bootable ISO for this Boot Environment" for each of my KBEs.

The link above pretty much covered everything. I did select "Try Unlisted ISO (GRUB)" for the distribution. After clicking create everything was working. 

After booting to the drive I wasn't too happy with the default menus it provided. I found this link that described how to customize it some more to match what our company is looking for.

http://philliprearick.hubpages.com/hub/How-To-Make-A-Custom-Multiboot-USB-Drive#

For the most part everything is self explanatory. I created my background. I then adjusted my menus to match what I needed. In the \multiboot directory edit the syslinux.cfg file. This is the first menu that you will see. 

This may be too much info. If you do not want it customized you can skip all of this.

label Replication Shares

menu label Replication Shares ->

MENU INDENT 1

KERNEL /multiboot/grub.exe

APPEND --config-file=/multiboot/menu/menu.lst

 

label K2000 Appliance

menu label K2000 Appliance ->

MENU INDENT 1

KERNEL /multiboot/grub.exe

APPEND --config-file=/multiboot/menu/menu1.lst
 
I added another menu to boot directly to my K2000s just in case. I copied the "/mulitboot.menu/menu.lst" and edited the K2000 label to point to it (/mulitboot.menu/menu1.lst on the last line).
 
Menu.lst file snip:

 
title --- STP Replication Shares ---
root
 
title <-- Back to Main Menu
root (hd0,0)
chainloader (hd0)+1
rootnoverify (hd0)
 
#start SWIKBOXREP1
#Modify the following entry if it does not boot
title CW/MW/UW Images
find --set-root --ignore-floppies --ignore-cd /multiboot/ISOS/SWIKBOXREP1.iso
map --heads=0 --sectors-per-track=0 /multiboot/ISOS/SWIKBOXREP1.iso (hd32)
map --hook
chainloader (hd32)
#end SWIKBOXREP1
 
title --- ZL Replication Shares ---
root
 
title <-- Back to Main Menu
root (hd0,0)
chainloader (hd0)+1
rootnoverify (hd0)
 
#start SWIKBOXREP2
#Modify the following entry if it does not boot
title Managed Machine Images (CW/UW)
find --set-root --ignore-floppies --ignore-cd /multiboot/ISOS/SWIKBOXREP2.iso
map --heads=0 --sectors-per-track=0 /multiboot/ISOS/SWIKBOXREP2.iso (hd32)
map --hook
chainloader (hd32)
#end SWIKBOXREP2
 
Menu1.lst File:
 
 
# This Menu created with YUMI (Your Universal Multiboot Installer) http://www.pendrivelinux.com
default 1
timeout 30
color NORMAL HIGHLIGHT HELPTEXT HEADING
splashimage=/multiboot/menu/yumi.xpm.gz
foreground=FFFFFF
background=000000
 
title --- K2000 Appliances ---
root
 
title <-- Back to Main Menu
root (hd0,0)
chainloader (hd0)+1
rootnoverify (hd0)
 
#start K2000
#Modify the following entry if it does not boot
title K2000 Appliance
find --set-root --ignore-floppies --ignore-cd /multiboot/ISOS/K2000.iso
map --heads=0 --sectors-per-track=0 /multiboot/ISOS/K2000.iso (hd32)
map --hook
chainloader (hd32)
#end K2000
 
 
 
 
Answered 01/03/2014 by: dugullett
Red Belt

Please log in to comment

Answers

0

you can create a special startnet.cmd that gives choices via a menu of what rsa they want and then have it load an applicable sub.cmd file to load the values for that particular rsa.  You could use the windows choice command in the startnet.cmd

Answered 01/02/2014 by: SMal.tmcc
Red Belt

  • I looked into editing the startnet.cmd as my first option. I think for our setup it may be too much since we change pretty frequently.
Please log in to comment
Answer this question or Comment on this question for clarity