26 Topic by unseen

(24 replies, posted in Universal Imaging)

Can you safely "roll your own" dpsfnshr.ini ?   

I ask as I've built my new "universal" image using our standard practices ie. plain xp cd, manually install all updates/software/etc..  The differences this time round beyond this is I'm building it for the first time on vmware and not on the actual hardware that it's going to be installed on (yes we lived in the dark ages until recently and hand rolled every image on the hardware it was destined for, until I got fed up of trying to maintain 15different images!!!)

I've basically got to the point where I believe I'm just about to check the final bits and realised I'd not really checked what needed to be done for dpsfnshr (many thanks to JakeLD for information he passed to me..)  I'll be using the sysprep driver scanner to embed the drivers into the system, but what needs to be done for dpsfnshr to execute correctly (in particularly regarding KTD)?

Hope I've made sense there!  I've not my appologies I've been at this all week!

Rob

Go to forum: Universal Imaging

27 Reply by unseen

(9 replies, posted in Universal Imaging)

JakeLD wrote:

Bigfoot, i use sysprep drievr scanner instead of devpath.exe and it runs before the whole sysprep process so my drivers have to stay in the same location (C:\D) If they get moved, it's over.

You can change the OEM info (my computer>properties)with sysprep driver scanner, that's the only reason why I use it.

Hi Jake,

I've been looking into the Sysprep Driver Scanner for some time now.. And was wondering, do you still run DPsFnshr to tidy up during the first boot after imaging?  What steps do you take normally to create an image.  Also been looking into another package I think you use MySysprep?  Looks like it will save me and my collegues some time when it comes to things like computer naming etc..

Rob

Go to forum: Universal Imaging

28 Reply by unseen

(17 replies, posted in Universal Imaging)

Another first poster (the sysprep crowd are slowly creeping out of the woodwork!)  I've been watching this thread and another I think by SkinLayer? (appologies if i'm wrong it's late!) and I'm curious about this one in particular :

kickarse wrote:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
(1) I split the drivers into two areas on root of the base workstation, pre-image. One is essential and the second is well secondary. Extract all 7zip files and then put them in the corresponding folders -
C:\D has CPU, Chipset, LAN
C:\D2 has Sound, Graphics, WLAN

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
(2) Run the utility called Sysprep Driver Scanner to enumerate and add the drivers to the registry, pre-sysprep. Put this program in the folder C:\D2
http://www.vernalex.com/tools/spdrvscn/index.shtml

If you use the driver scanner, does it correctly install for example the ATI CCC?  I'm about to take the plunge and try a universal image after spending way to long creating individual images for all our hardware, trying to piece together everyone's tips for "universal" or at least for arguements sake "semi-universal" images has been interesting.  So any advice or tips welcomed! Also if anyone needs anything testing I'm sure I can find some time to turn the odd box into a guinea pig wink

Rob

Go to forum: Universal Imaging