/build/static/layout/Breadcrumb_cap_w.png

Managing System Images (.wim) & Drivers

Hey,

We've recently recieved our UK license and thus been able to upgrade to the 3.4 version of K2000.

Now, with all the .wim support files / updates done I'm yet to manage my system installations properly.

I'm looking to create 2 default images for my machines, 1 for staff and 1 for students, they will all be Windows 7 64-bit Enterprise. However using a 'clean' windows WIM doesn't seem to work as I wanted it to. The image is applied and all is well apart from the fact that no drivers are installed.

If I've understood everything right the driver feed isn't used in system imaging and the drivers have to be added through post-installation tasks?

What would be the easiest way to make the default images from here on? We're only using Dell machines and I'd rather not have a seperate image for every model we have if possible.

 


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: dugullett 11 years ago
Red Belt
2

Use this for the drivers on WIM and system images. The drivers should be placed in \\K2000\post_install. 

http://www.itninja.com/question/driver-feed-workaround-and-drivers 


Comments:
  • Will check it out, thanks! - SHUni 11 years ago
Posted by: SMal.tmcc 11 years ago
Red Belt
0

You should be syspreping to reset the SID so you can use this method I have been using with great success.

http://www.itninja.com/blog/view/creating-a-windows-7-sysprep-image-without-having-to-install-any-drivers-at-post-install-tasks

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