/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


K2000 - Winpe10 - Does it support Windows 7?

10/14/2016 3099 views
If I want to be able to deploy Windows 10 and 7 from the same K2000, do I just add the KBE Driver Pack for Windows 10 and recache or do I have to add multiple driver packs?  Sorry, but I don't understand the KBE creation process very well.  When I navigate to \\k2000\drivers, I see a bunch of folders (kbe_windows_x64, kbe_windows_x86, windows_7_x64....).  None of the windows_* folders have anything in them.  Only the kbe_windows_* folders do.  If I navigate into kbe_windows_x64, I see "dell-winpe10-a01"...so that's my winPE 10 environment for 64-bit...I get that, but if I want to add support for Windows 7, do I just copy winPE 3 into the same directory?  So I in the directory "\\k2000\drivers\kbe_windows_x64\" I would have 2 folders...1 for winPE10 and another folder for winPE3?  Then I would recache and upload a new KBE?

Thanks for any info.
Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

0
The WINPE10 Driver pack and Windows 10 ADK tool set is a valid configuration to deploy or capture images of Windows 7 OS.

Having the drivers only located in the kbe_windows_x64 or kbe_windows_x86 folders is the best way as when you are looking to see what drivers are going to be used just look into the architecture folder instead of having to look through all the folders. Just want the single WINPE10 Driver Pack to be installed, having the other WINPE versions usually causes driver conflicts which results in the KBE failing.

When testing the new KBE, if it fails with a could not connect to peinst or you see 1231 error this would mean to use the drvier feed and download the WIn10xXX of the model, then copy the network folder from //ikbox/drivers_postinstall into the //ikbox/drivers/kbe_windows_xXX/custom/[model] path (may need to create folders if custom and model folders do not exist). Recache the drivers and re-create the KBE as this will then add the network drivers for that model into the KBE resolving any 1231 error. 
Answered 10/17/2016 by: TheAustinDave
Brown Belt

  • I know this is a old thread, but need someone to clear things up for me,
    So by downloading the Win10 drivers from the feed, then copying the network driver and storage drivers to the KBE_Windows_xXX folder, Will you be able to run a scripted Windows 7 deployment? Or do you need to get the Windows 7 driver feed and place the Network and storage drivers in another directory?
    • You will likely get errors running a scripted install because the windows 7 setup.exe is not compatible with win10PE. Copying an image works fine as DISM is used to apply image not setup.exe

      This site and k2000, has a preinstall script that ignores errors, also some have tried copying over mismatched files to get around the error.

      The best solution I have seen is to use the setup files (the files of install iso) for win 10 but replace the install.wim with your windows 7 Make sure you still upload as win 7 so kace copies the right drivers down.
    • The WINPE10 will work for windows 7 installs, but will give you a pop-up warning that only has the OK to select. The other item to be cautious is if the system has a PCIe hard drive, scripted install of these for Win7 is not able to be completed as the driver needed for the storage is not included in the ISO file from Microsoft.

All Answers

1
WinPE10 is backwards compatible, so you can deploy W7 with a WinPE10, but not vice versa (well, mostly also this works, but you will not have the right drivers on the machine, since WinPE3,4,5 are not aware of WinPE10)
Answered 10/15/2016 by: Nico_K
Red Belt

 
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