The following workarounds are applicable to IBM® ToolsCenter Bootable Media Creator.

When deploying Windows 2008 editions on an IBM System x®3250 M5 with or without ServeRAID C100 enabled, a blue screen might occur
To avoid this problem, complete the following steps:
  1. Open uEFI settings.
  2. Open the Device and I/O Ports setting.
  3. If the ServeRAID C100 is enabled, change the onboard SATA ports as to RAID or IDE.
  4. If the ServeRAID C100 is not enabled, change the onboard SATA ports as to IDE.
  5. Save the settings changes. The system will work normally when you reboot from the ServerGuide.
The keyboard does not work when confirming to exit ToolsCenter program
After booting a system with bootable media created using IBM ToolsCenter Bootable Media Creator, when you select to exit the ToolsCenter program, you are prompted to confirm the exit action. The keyboard cannot be used to confirm the exit action.
Workaround: Use the mouse to confirm the exit action, or create the media to run in TUI mode.
cygwin1.dll conflict
IBM ToolsCenter Bootable Media Creator ships the cygwin1.dll (version 1.5.24, renamed to cygwinz.dll), which is required by the mkisofs.exe and cdrecord.exe utilities. The cygwin DLL does not support multiple versions running at the same time. You must exit all other applications that depend on cygwin1.dll before running IBM ToolsCenter Bootable Media Creator on a Windows System.
IBM ToolsCenter Bootable Media Creator might fail to burn a CD or DVD if it runs on RHEL3 with an IDE CD-ROM or IDE DVD-ROM
Add hdx=ide-scsi to the boot loader configuration file. For example: /etc/lilo.conf for LILO or /boot/grub /menu.lst for GRUB), where hdx is either hda, hdb, hdc, or hdd, depending on where your CD or DVD drive is located.
USB flash drives that are used by Linux are not recognized by Windows
To enable Windows to recognize the USB flash drive so that it can be used by IBM ToolsCenter Bootable Media Creator on a Windows system, format the USB flash drive on a Linux system to FAT32 file format using the mkdosfs utility. For example: mkdosfs -I -F 32 /dev/sdb).
Failure when burning created ISO files to CD/DVD, or created CD/DVD fails to boot
If you are unable to burn created ISO files to CD or DVD media, or if the CD or DVD you have created fails to boot, try using an alternative media writing software or use a different brand and type of media.
IBM BladeCenter® HS22 fails to boot from SanDisk 4GB bootable USB key
When using the SanDisk 4GB bootable USB key created by Bootable Media Creator to boot HS22 (machine type 7870), the system might boot directly into the OS environment installed on the hard disk drive but not boot into the USB key.
Workaround: Update the uEFI firmware or use a Lexar USB key or a bootable CD.
USB key automatically mounts in noexec mode on SLES 10 sp4
As a security measure, USB keys can be mounted in noexec mode, which prevents executable files on the key from running. This will prevent you from using the BoMC binary, even after using chmod to change permissions.
Workaround: Copy the binary to the hard drive of the system, use chmod to give it proper permissions, and execute from the hard drive.