Greetings, like many others who I see found out that you now need a dual layer DVD media (a dual layer reader on your servers) for the latest update repository download, have come across repository manager and thought it was a great idea (although being able to download a bootable CD just for your system would be better...). In any case I've so far managed to use it to create a repository DVD (single layer) with just my PowerEdge systems on it . But what I was hopeful for was it to create a single bootable CD for my servers that still have only CD readers on them. I thought I found this in the DEPLOYMENT MEDIA option in the exporter, and indeed a bootable CD was created, but when I booted it, after choosing the PowerEdge model, all that happened after that were text lines saying what files it was working with, but no real options such as telling you what your system firmware on such and such is, and your media has this available, do you want it? Now I do have to admit that I ran this on a machine other than the intended PEDGE server because I wanted to see what it was going to do (didn't want to find out it was going to format the drives or something...).
Have I done something wrong in creating the bootable CD, or is the deployment media option not the correct choice for what I'm looking (ideally need a bootable CD with the build & update utility along with the bundles associated just with my system(s)).
Thanks for the quick response. So if I want the reassuring "show me what you're doing before you do it" screen I have to go with the Build & Update Utility boot DVD (no longer CD) and then put in the repository DVD (either the download one or one I create in Repository Manager).
If I have a server that only has a CD drive, then I have to go the route of creating a CD with the repository manager and then checking the firmware revs and so on after it's run to see what got updated (if I'm physically at the server). I did try on a PE2800 to use a USB DVD drive but while it booted to the drive, it wouldn't pop it out for the repository (kept popping out the CD tray - I tried physically removing the int CD drive but it still didn't work - maybe if I disable the int drive in the BIOS... next time...).
you have it right, but the bootable media option boots into a linux environment and just runs a bundle that will only raise your versions to what is on the disc. it will not lower the versions if you are already at a higher version. if you create a disc for a single system, it automatically runs that bundle once you boot to it, but if you create the disc to update multiple models, it will present you with choices for which one system you want to update. RM's bootable media doesnt have an inventory collector to verfiy the versions you currently have on your system, thats why you dont get a menu.
correct, SBUU is your option in that case. Just to be sure, you realize you can use the SUU directory or SUU iso option as well and do the updates from within the operating system (linux/windows). Also, for your PE2800, you can also swap (almost)any Latitude D series and most Inspiron DVD drives to replace the cdrom drive in your 2800. You might have to remove the drive bezel from the laptop drive, but it can be swapped that way temporarily at least.
MarioKarter
3 Posts
850
0
Posted July 30th, 2010 15:00
Thanks for the quick response. So if I want the reassuring "show me what you're doing before you do it" screen I have to go with the Build & Update Utility boot DVD (no longer CD) and then put in the repository DVD (either the download one or one I create in Repository Manager).
If I have a server that only has a CD drive, then I have to go the route of creating a CD with the repository manager and then checking the firmware revs and so on after it's run to see what got updated (if I'm physically at the server). I did try on a PE2800 to use a USB DVD drive but while it booted to the drive, it wouldn't pop it out for the repository (kept popping out the CD tray - I tried physically removing the int CD drive but it still didn't work - maybe if I disable the int drive in the BIOS... next time...).
Thanks
James