/build/static/layout/Breadcrumb_cap_w.png

How to have Driver packs for both Win 7 and win 10 in the k2000

Hi guys.

We are about to add windows 10 machines into our network.

I will have to build a new KBE (WinPE 10) / Driver Pack 10.

We will still have a significant win 7 presence though.

So it going to be a mixed network of OS deployments.... (Both win 7 and win 10)

Now  my question.... I will need  WinPE 3 Driver Pack for win 7 deployments.....

and I will need  WinPE 10 Driver Pack for win 10 deployments.

But all the documentation from kace says .....and I Quote.........

(Please note that you should only have the drivers for one WinPE version at a time in the kbe_windows_xXX folders).

Does the win 10 Driver pack have drivers for win 10 and all previous window 8.1, 8.0, and 7 incorporated into it ??  OR do

I have to copy and re-cache the drivers for each KBE into the k2 driver folder for each time I deploy that

version ?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: chucksteel 6 years ago
Red Belt
2
You only need to change the driver pack when building the KBE. It is considered best practice to always download the latest driver pack and update the server before creating a new KBE. Once the KBE is created the drivers are no longer used. We still have our older Windows 7 KBE on the appliance as a boot option.

Comments:
  • Thanks @chucksteel - akmagnum 6 years ago
Posted by: Nico_K 6 years ago
Red Belt
0
you don't
It is also not nessesary.
You can build W7 systems with W10 KBE but not vice versa.

Comments:

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