Solved

win 7 sysprep and unsigned drivers

Posted on 2011-09-14
6
1,003 Views
Last Modified: 2012-05-12
Hello experts

Ive been trying to tweak my driver inf files for install as part of my sysprep imaged deployment but have obviously changed the inf files deeming them unsigned (All im doing is turning off non required tray icons added to registry or setting default registry values like enabling pme for nics etc) which im assuming is why now after sysprep and deployment the machine isnt auto installing my drivers as before. Im curious what other people do in this situation, is it possible to turn off the driver signing requirements or to some how sign and trust the files again ? Any help is greatly appreicated
0
Comment
Question by:Jarrod
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 17

Expert Comment

by:xema
ID: 36545673
Porka;
I'm assuming you are preparing an image to be deployed to similar machines.
In the past I've created sysprep images, just do a complete install of the OS and the drivers then run the sysprep aplication and save the image.
With that image you can install the OS with the drivers with out the problem of unsigned drivers. Or at least it was my experience BEFORE Win 7.
0
 
LVL 6

Author Comment

by:Jarrod
ID: 36546293
The image is for about 7 machine types all up and covers about 700 machines so wanted to make sure I get it right. The master machine is actually a vm so I never install any drivers in it as such and use the pnputil method to add support for them which was working well until I tried to modify the inf files where now with pnputil im asked if I wanted to install an unsigned driver and even though I agree after deployment in a test environment the machines no longer auto install the driver for the inf files ive modified so I would assume driver signing issues stop the auto install
0
 
LVL 17

Accepted Solution

by:
xema earned 500 total points
ID: 36546541
A cumbersome task, but I did it with a smaller group, four types of machines.
Set up one machine of each model and do a sysprep, you'll end up with several different installation disks one for each type.
That way you won't have issues with the installation.
0
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

 
LVL 17

Expert Comment

by:xema
ID: 36546553
I forgot;
You'll need the drivers for each chipset type, video, audio, etc. at the end you'll end up with a big installation with lots of unused drivers, some thing I wouldn't recomend. So preparing an installation disk for each type of machine will givw you a more cleaner installation
0
 
LVL 6

Author Comment

by:Jarrod
ID: 36553397
I was trying to avoid keeping multiple images and future proofing to a point where possible but as a last resort Im probably going to use a reg file in the setupcomplete.cmd after the deployment to clean up instead, just would have liked to streamline the driver install a bit better
0
 
LVL 17

Expert Comment

by:xema
ID: 36560539
Porka;
You can prepare a single disk, but you'll have to use it on all of the types of machine you have.
Prepare an sysprep image with type I equipment, deploy it on type II, load the drivers prepare an sysprep image, and so on until you have cover all of the posible combinations.  That way you'll have a single image for all of your types of machines.
That's the only way I think you could prepare a single installation disk tha won't have issues with different types of equipement.
0

Featured Post

How Blockchain Is Impacting Every Industry

Blockchain expert Alex Tapscott talks to Acronis VP Frank Jablonski about this revolutionary technology and how it's making inroads into other industries and facets of everyday life.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
There are many software programs on offer that will claim to magically speed up your computer. The best advice I can give you is to avoid them like the plague, because they will often cause far more problems than they solve. Try some of these "do it…
This Micro Tutorial will go in depth within Systems and Security in Windows 7 and will go into detail regarding Action Center, Windows Firewall, System, etc. This will be demonstrated using Windows 7 operating system.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question