1 Reply by LunchBox

(11 replies, posted in Windows 7 tools)

Yes, I agree.  I like to add script when possible as I found its easier to modify a WIM vs having to build a new one.  At least for me since I build hybrid images.

Well thank you everyone for your suggestions.  I will play around with the SAD2 utility as I seen quite a few threads on how folks are using it and it will come in handy once I finish this project I'm on.

Go to forum: Windows 7 tools

2 Reply by LunchBox

(11 replies, posted in Windows 7 tools)

Thank you everyone for your suggestions.  I will test the methods suggested.

OverFlow - Sorry I missed read your thread (probably tired).  Yes, I don't understand why they do what they do here.  I'm new at this company and everything is very irritating (very).  But, I always look for the positive in things and here I discovered a new method.

I came across a Task in MDT called "LiteTouch OEM Task Sequence".  This wil allow me to build a normal task sequence and the OEM task sequence will allow normal task sequence to be copied to the HD.  When the HD first loads it will use the normal task sequence I created which will install the apps, drivers etc.

Have any of you every used or heard of the OEM task sequence?

Go to forum: Windows 7 tools

3 Reply by LunchBox

(11 replies, posted in Windows 7 tools)

Yes, it would be much better to spend money, however, I went do that road only to be told no.  (not sure but maybe there is something going on with the company).

On a previous job I had I created a self contain USB flash drive which the techs used to install the OS based on the role and model of the PC.  The OS was applied using ImageX and then once the of steps I copied the Driver folder in teh the C:\Windows\INF.  This worked great but I can't use it in my scenario because I won't know where the clone drives wil be used.

I thought I could use DISM or a script inside the SetupComplete.cmd file to add the drivers as the OS is botting.  If this won't work I guess I might just have to suck it up and inject the drivers for 3 models of desktops into the WIM and let Windows decise what to install.

This scenerio is only for mass disk duplication where the HDs wil eventually be used on one of the 3 models we have.

I will eventually build an MDT server (PXE not allowed)

Any ideas on a methods, perhaps using the unattended answer file to detec the hardware and then install drivers, or copy the drivers into the INF folder or using DISM to inject the drivers?

Thank for for all the suggestion s for far though.

Go to forum: Windows 7 tools

4 Reply by LunchBox

(11 replies, posted in Windows 7 tools)

Jeff, thank you for your repsonse.

We can't spend money on Ghost as eventually we will use WDS with PXE so management does not want to spend money at all.


I though about using the SAD2 script, however does it detect the hardware of the machine?  Example  The machne is a Dell 790 but I have drivers each in its own folder as such  C:\DRivers\Dell790 - :\DRivers\Dell710  etc.

Does SAD2 detec the hardhware and then install the correct drivers from the correct folder or just allow any drivers from within the C:\Drivers folder.

Yes, I want to use DISM, however, I was laid off (while working from home) and never got a chance to copy my notes which had how to detect using WMIC then point to the correct folder and then run DISM.  (yes, I've learned to keep a copy of my notes now)

I was thinking the setupcomplete would have something like this ->


If ComputerModel 790 GoTo 790

:790

DISM (need to check which switches I really need to use)


Or in the Setupcomplete.cmd I can add the pointer to the SAD2 scrip.  I prefer to learn to use DISM and WMIC


Thank you

Go to forum: Windows 7 tools

5 Topic by LunchBox

(11 replies, posted in Windows 7 tools)

Greetings,

I"m posting here because after googling I found that this site has the most out of the box thinking when it comes to figuring things out.  I have posted this question in 2 forums (I changed the question slightly) and I realized that although those folks were helping, I could not use their advise due to the unique scenario I have.

For my question, please do not suggest MDT, WDS, SCCM Acronis etc as I can't use it.  Well I can, however, I'm working on an image for a remote site that currently does not have servers.  Eventually they will so I need to create a (probably)  USB flash drive that is self contained with the images/drivers etc.  I can figure out the rest as long as I can overcome the following

I think I need to use the "SetupComplete.cmd" script to do the following

use WMIC to detect the hardware and either do the following

1. Copy the appropriate folder with the drivers into c:\windows\inf        or
2. Use Dism to inject the appropriate drivers                                       or
3. Add the folders that contained the drivers each in its own model into c:\windows\inf

Reason

We are doing massive imaging.  My plan is to have a SysPrep image.  So when it boots up the SetupComplete.cmd will detect the hardware and install the correct drivers based on my 3 questions (unless you can think of a different way)

Once I have the logic of installing the drivers, I will have the WIM and applied to 1 drive which will be the master.  Using this master we will close many hard drives using a Disk Duplicator machine which can do multiple hard drives at one.  Since we have 4 of these duplications we can prep many drives

I know I can use in SetupComplete.cmd  ->  wmic computesystem to find the model
Then I can't figure out the rest.

Or should I just store the 3 folders with the drivers for 3 models of desktops in c:\windows\inf and let windows pick.  I much rather use logic in a the script and make it install the correct drivers.

Thank you

Go to forum: Windows 7 tools