How to specify what KBE to use with each automated deployment?

Our company utilises many different operating systems across many different laptops and we require deploying different OS images to machines all the time. As such, just having a "default KBE" doesn't make any sense. How do we modify what KBE is utilised with each image deployment without having to change the default everytime.

Thanks in advance,

0 Comments   [ + ] Show comments

Answers (1)

Posted by: Hobbsy 4 years ago
Red Belt
From a KACE perspective this is relatively simple, the answer is windows or apple, as such do not think of the KBE as being OS specific, more a means to an end. In saying that I mean that the KBE is loaded by the machine so that you can then load a new image of your selected OS or carry out a scripted installation. It makes no difference what OS that KBE is defined as it is transitory, so as long as it loads it enables the K2 to start and then deploy your chosen OS. 

A default KBE with the correct, generic hardware drivers, will allow you to boot any windows device and load any version of OS that you have stored i.e. windows 7, 8 or 10.

Apple of course is much the same, as long as you have a valid Netboot partition for the latest OSX, any apple hardware will load and you will be able to deploy your chosen image.

I hope that makes sense?

  • It makes sense but I do not see this outcome. When installing a windows 7 machine utilising a windows 10 KBE I receive errors that I do not see when utilising the Windows 7 KBE I have. Attempting this with my x86 KBE also doesn't work and displays a plethora of multicoloured squares whenever an installation starts. - abane 4 years ago
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