warren17c

Personally, I would go with either Just Model's under your Win7 folders (windows 7 x86\%cleanmodel%) or have both cleanmake and clean model (windows 7 x86\%cleanmake%\%Cleanmodel%) I would also eliminate the spaces, Just so that the full path has nothing to complain about, not sure if it will need quotes round the string because of them or not, or if it even accepts it with the quotes. let us know how it goes.

good work! what i also do is, change the Install drivers task. I change it to Install Drivers - %cleanmake% - %cleanmodel% then during the Task sequence, you get to see that it is picking the right drivers (peace of mind when you dony believe that it can be this simple!)

I dont think it matters but if you want to be precice, name it something differnet (stick a 1 at the end) then rename it back with the correct Capialization. I use the copy to clipboard function of @Jamo's tool whack it in a text file then use that from MDT.

I must say a huge Thanks (and have clicked to indicate) Samsung is the reason I went looking and found. makes my life a lot easier!

for the useralias script, you reference it in your Customsettings.ini its an userexit script. It then generates 2 new vaialbles: modelalias and makealias. in your out of box drivers folder, you create new folders based on model name (The same that modelalias produces) put all the drivers for that model in there. out-of-box drivers ->Win7x86 -->E5500 ---> Dell Drivers (x86) -->HP Compaq Elite 8300 Touch All-in-One PC --->HP Drivers (x86) ->Win7x64 --->E5500 ---> Dell Drivers (x86) -->HP Compaq Elite 8300 Touch All-in-One PC --->HP Drivers (x86) if that makes sense? In your TS, before you get to the Inject drivers (pre install) you add a new TS variable "DriverGroup001" and you reference your model folders in Out-of-box drivers like "win7x86\%modelalias%" Then set inject drivers selection profile to "nothing" and select "Install all drivers from selection profile" I personally dont use this method, because I am lazy and dont have lenovo's (lenovo model names are 8 digits long but the last 4 are batch so change even among the same range). I use a similar one called "Cleanmakeandmodel" it works similar, but you add a script to your scripts folder, run it before you create you DriverGroup001 variable, then use %cleanmake% and %cleanmodel% works just as well, and the guy who wrote it created a little app that gets he info on the local and remote machines with a button that drops the relevnat field onto the clipboard, meaning, you dont get spelling mistakes! heres the link to cleanmakeandmodel

What OS are you deploying? I have had issues with Vista acting exactly as you say but no issues with Win 7 (enterprise or Pro). Win 7, actually reboots itself in the Windows update pass (Be that from your WSUS server or from MS) then carries on with another pass. In Vista we had a tierd effort. I created a new WIM with just OS+Office+Updates, captured it then used that as base image. I then added multiple passes of Windows updates through my Task sequence (Just before i rebooted for certain apps) this covered us. I have got round this now as I have migrated them to WIN7, so removed all the passes. BTW, you are using cscript.exe "%scriptroot%\ztiwindowsupdate.wsf" in your TS?

Hello all, only just registered as this topic peaked my interest... Some things I have picked up on this subject and thought I would share... If you are going to Capture an Image, ALWAYS use a VM enviroment (VMWare / Hyper-V etc) As doing it off a real device means you have real device issues. Perhaps you have to install a little applicaiton to get the keyboard working, or a reg key under HKLM to get it to do what you want - These things will be in your reference Image!! - Also snapshots and cscript.exe %scriptroot%\ltisuspend.wsf are a life saver here. There are 3 types of Images Thin, Think and Hybrid. A. Thin Imags - This is just the out of the box ISO from MS. B. Thick Images - Everything, Apps, updates kitchen sinks... C. Hybrid - A bit of both All have their advantages. For me I use hybrid. Some closer to Thin than others. I would play with thin and Hybrid on your network, see how each pan out. (time them both on your network) use the faster and or most stable. (I have AV issues scanning my deployment share, I argue it doesnt need it, but the guys above me say it needs to). Finally, if your not using drivergroups and using a seperate task sequence per model, PM I will walk you through it. All you need is a TS per OS (Win7pro / Win7Ent etc) Some clever work and your life becomes easier. There is no right or wrong with them. Use whatever works.