Deployment Solution

Hello all,

 

I am in the process of creating a universal sysprep image.  I currently have about 20 different computer models to include desktop, laptops, and tablets.  I have base sysprep loads in which i use for the different computers.  I am looking to add all drivers to my five base sysprep images but I have been unable to do this using any of the utilities I have located.  Does anyone have any suggestions on how to proceed with injecting drivers into a sysprep image. 

 

Roy Gibson

Systems Engineer

Hi Roy, I moved your question into a new discussion thread.

Also, are you using Altiris, and if so, what version and solutions? There are many approaches to this; we use omnifs to copy the driver bundle in during the automation stage.

If you are using Deployment Solution 7.1 you should start with the built in DeployAnywhere technology. 

If you find the manual a bit daunting, start here:

http://www.symantec.com/docs/HOWTO63351

Then read this:

http://www.symantec.com/docs/TECH186664

I am using Ghost version 2.5.  We have Altiris but have not setup the program to begin using.  I appreciate you moving the comment!  Thank You!

Are your images XP or Windows 7? For Windows 7 you want to look at the windows dism tool.

Hi Roy,

If you let us know what os you are creating your image for, we can respond with more tuned advice.

Also, your deployment strategy for the image would be useful too -as that tells us whether all the drivers need to be in the image, or whether the correct drivers can be injected at deployment time.

Kind Regards,
Ian./

There is no way to inject drivers to the Image (In Altiris DS and Ghost solution suite 2.5.1) ; As in one of the above comments it is mentioned that you need to use DeployAnywhere to achieve Hardware independent imaging.

I will just list down some basic steps for performing a Hardware independent imaging;

1. Identify a machine of which you will prepare an image

2. Perform Prepare capture image task which will execute Sysprep and make your machine ready for generic image.

3.Take a image of above machine , Here you got a generic (base) image.

4. Identify machines on which you will be deploying above image ; Here more importantly find out what kind of devices / hardware these target machines has (e.g Network cards, MSD's)

5.Import all required Drivers to the driver database [Both applicable to Altiris DS and Ghost solution suite 2.5.1] ; Here it is users responsibility to add required driver to DriverDB [Vendor's driver CD/DVD or Vendor's site is the best place to get Drivers]

6.Deploy an image by enabling DeployAnywhere Option

You are done , DeployAnywhere will take care of finding missing drivers and copying and targeting matching drivers from Driver database.

 

Hi Yogesh,

I have to strongly disagree with your comment that there is no way to inject drivers into Altiris DS and Ghost Solution Suite. I've been injecting drivers into images for many years with scripts (as have many others on this site).

DeployAnywhere is simply the option that Symantec supports. It also however has some failings which mean that some choose (with good reason) to continue with their custom driver injection scripts.

Agree with Ian on this one.  

Ian helps us understand what kind of scripts do you use to inject drivers?  do u use the audit mode in sysprep or do you use OS specific options?

Nelo

Ian , What you have mentioned is correct , user can always use the script wherever possible for injecting drivers.

I have mentioned the steps which are possible from DS and GSS console.And i have mentioned specifically in my first line.

I would also like to know what script you used for Driver injection.

 

Hi guys, for Windows XP our process is,

1) Automation Boot
2) Deploy sysprep image
3) Copy Drivers specific to model across to C:\Drivers
4) Production boot
5) Allow mini-setup to set scheduled task at first boot to install Deployment Agent

As we standardise the way sysprep.inf works for driver hunting, we keep a static OemPnPDriversPath string here.

For Windows 7, our process is very similar,

 

1) Automation Boot
2) Deploy sysprep image
3) Copy Drivers specific to model across to C:\Drivers
4) Use DISM to add drivers offline to the newly deployed image using the drivers available in C:\Drivers
5) Production Boot
6) Allow specialise phase to set scheduled task at first boot to install Deployment Agent

There is nothing special about DISM itself. What is important for us however is that the drivers are controlled, and when we deploy model x we always know what drivers will be delivered to that model at deployment time.

The scripts are cumbersome (as there is much logging, agent configuration and sysprep shinanigans), but if you feel it's worth as write up I'll push on with that.

Kind Regards,
Ian./

 

We do much the same thing as Ian for XP. If you check the Sample image jobs that came with DS 6.9, there are examples of the scripts that we started with.

I'd like to see a write up for Windows 7. We used DISM to inject the drivers before creating the image, which eventually will make the image too large. Didn't have the time and resources to figure out how to do it after deployment, so I'd like to get that if possible.