/build/static/layout/Breadcrumb_cap_w.png

Question about KBE creation

Hi, I have a question about making KBE's. my goal is to fix/get working the scripted OS installs and post install software install tasks here at work. so far I have used the media manager to upload a win7 x64 pro install DVD, and used WAIK to create a KBE from my PC,

question is, do I need to make a new KBE for every hardware platform that I intend to install windows on? ex: a KBE for our i5 desktops, a KBE for our i3 desktops, a KBE for our i5 laptops, etc... 

 


0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
the media manager takes the winpe.wim file and adds the drivers found in \\ikbox\drivers\kbe_windows_x64 and all subdirectories. When we get a new model in at TMCC the first thing done is someone will try to pxe boot it. If it does not boot the machine is given to me. I go and download the nic boot files and add them to the Ikbox and then create a test boot env with the media manager and then I test to see if it boots PXE with the test env. If successful I rename the env from test to a production name and switch my default pxe boot to the new one on the k2000 and archive the old one for 30 days.
Posted by: SMal.tmcc 12 years ago
Red Belt
0

No you need to just provide the drivers for the media manager to package for the other models.  You need a boot for each OS and 32/64 bits, Mac OSX you plan on imaging.


Comments:
  • The best thing to do on models is PXE boot them to the Kace and see if they get to the menu, if they do you are good, if they do not, you need to add drivers to the KBE and recompile. The other thing I did was added the drviers for the Advanced Format Drives to my KBE. You can place the files manually on the K2000. Attach to the box with your admin PC \\ikbox\drivers name .\admin password is the one you set under control panel. Copy any needed drivers to \\ikbox\drivers\kbe_windows_x32 or x64\kace in their own subdirectories and when you recompile with the media manager it will add those. - SMal.tmcc 12 years ago
Posted by: PowerChucker 12 years ago
Senior White Belt
0

Hi, thanks for the reply, is there any way you could elaborate on that, meaning, how do i provide drivers for the media manager?

when i ran the KBE creation and pointed it to the WAIK directory, a CMD window came up providing status of the process, then i noticed that it said 70 drivers found, then it went through and processed the 70 driver packages it found on my PC. not sure what that all meant..


Comments:
  • the media manager takes the winpe.wim file and adds the drivers found in \\ikbox\drivers\kbe_windows_x64 and all subdirectories. When we get a new model in at TMCC the first thing done is someone will try to pxe boot it. If it does not boot the machine is given to me. I go and download the nic boot files and add them to the Ikbox and then create a test boot env with the media manager and then I test to see if it boots PXE with the test env. If successful I rename the env from test to a production name and switch my default pxe boot to the new one on the k2000 and archive the old one for 30 days. - SMal.tmcc 12 years ago
Posted by: SMal.tmcc 12 years ago
Red Belt
0

Posted by: PowerChucker 12 years ago
Senior White Belt
0

thank you for taking the time to clear this up for me! 


Comments:
  • no problem, you can create your own subdirectories and it will still read them. The biggest thing is decompress the files in the directories. Make sure to put answer in summary and you will get some ninja points for that. - SMal.tmcc 12 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ