[wds] Sysprep?

[abillybob]

Hey Guys

 

Setup WDS thanks to all of you and the helpful links. Everything is working I can deploy Images and Capture Images just fine, although one final issue.

 

Before WDS will allow you to capture the client Image you must first Sysprep the machine, So I did, I booted into the client Sysprepped with Generalize ticked and Out Of The Box Experience selected. Problem being is it has removed all the third party drivers I had installed for things like the GPU, Chipset, Card Reader and more.

 

Is there anyway to include the drivers? Thus stopping Sysprep from deleting them?

 

Cheers Guys

[sted]

you need to add something to sysprep to tell it not to do this ive included one of my syprep.xml files for you to peruse lol with the bit in question marked in red. Also i run sysprep from command line like below(i always shutdown rather than reboot that way if i get distracted it dosent start booting windows again)

 

go to c:\windows\system32\sysprep\

 

sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\sysprep.xml

 

    

        

            true

            [color=#FF0000]true[/color]

        

    

    

        

            true

            true

            http://www.google.co.uk

        

        

            0809:00000809

            en-GB

            en-GB

            en-GB

            en-GB

        

        

            false

            some school

            some school

            GMT Standard Time

        

    

    


[/code

[scotyboy56]

Easiest way I find is to just add the drivers into WDS and it just installs them when it installs the OS

[Norphy]

Hey Guys

 

Setup WDS thanks to all of you and the helpful links. Everything is working I can deploy Images and Capture Images just fine, although one final issue.

 

Before WDS will allow you to capture the client Image you must first Sysprep the machine, So I did, I booted into the client Sysprepped with Generalize ticked and Out Of The Box Experience selected. Problem being is it has removed all the third party drivers I had installed for things like the GPU, Chipset, Card Reader and more.

 

Is there anyway to include the drivers? Thus stopping Sysprep from deleting them?

 

Cheers Guys

 

You're taking the wrong approach. You shouldn't be including drivers in your image as this defeats the object of generalising it. Instead, you should be using WDS to inject the drivers into the OS during the deployment process. If you look at your WDS Console, you'll see that there is a section for drivers. Add your drivers to that and that will sort your problems.

 

Plus it will mean that you'll be able to use a single image for EVERYTHING. When you get new hardware, all you'll need to do is add extra drivers to your driver store, no need to faff about with an image per piece of kit.

[abillybob]

You're taking the wrong approach. You shouldn't be including drivers in your image as this defeats the object of generalising it. Instead, you should be using WDS to inject the drivers into the OS during the deployment process. If you look at your WDS Console, you'll see that there is a section for drivers. Add your drivers to that and that will sort your problems.

 

Plus it will mean that you'll be able to use a single image for EVERYTHING. When you get new hardware, all you'll need to do is add extra drivers to your driver store, no need to faff about with an image per piece of kit.

@Norphy ok mate so is it just a case of adding the drivers into the drivers folder or do I have to link this with the install.wim file in some way?

[sted]

if you are going to start adding drivers via wds just use mdt its more flexible

[Norphy]

@Norphy ok mate so is it just a case of adding the drivers into the drivers folder or do I have to link this with the install.wim file in some way?

 

It's been a while since I've used vanilla WDS but yes, I think that all you need to do is add the drivers to the WDS store.

[abillybob]

if you are going to start adding drivers via wds just use mdt its more flexible

 

I don't want to use MDT looking at it as it's a lot more to set it up, plus we only have three types of computer in the school so wouldn't need to add that many drivers to it. I just need to know if it's just a case of adding the drivers into the drivers area or whether or not you some how have to link the installed drivers to the install.wim files via the wds console? Or whether I just add the drivers to wds and they automatically apply to every image on the WDS server?

[sted]

I don't want to use MDT looking at it as it's a lot more to set it up, plus we only have three types of computer in the school so wouldn't need to add that many drivers to it. I just need to know if it's just a case of adding the drivers into the drivers area or whether or not you some how have to link the installed drivers to the install.wim files via the wds console? Or whether I just add the drivers to wds and they automatically apply to every image on the WDS server?

 

with only 3 types of computer to set up mdt less than an hour i would say (excluding downloading the aik as its several gbs)

 

i assume youre going to install pc1 get software drivers etc installed then image pull to server repeat for pcs 2/3 and have 1 image for each pc type then?

[Norphy]

I don't want to use MDT looking at it as it's a lot more to set it up, plus we only have three types of computer in the school so wouldn't need to add that many drivers to it. I just need to know if it's just a case of adding the drivers into the drivers area or whether or not you some how have to link the installed drivers to the install.wim files via the wds console? Or whether I just add the drivers to wds and they automatically apply to every image on the WDS server?

 

The latter

[abillybob]

with only 3 types of computer to set up mdt less than an hour i would say (excluding downloading the aik as its several gbs)

 

i assume youre going to install pc1 get software drivers etc installed then image pull to server repeat for pcs 2/3 and have 1 image for each pc type then?

 

Yes that's what I was going to do, I just have no experience with setting up MDT and can't really see any benefits of doing so compared to WDS?

[LeMarchand]

Or whether I just add the drivers to wds and they automatically apply to every image on the WDS server?

 

I just add 'em into the store and WDS automagically gives them out to the right machines. IME W8/7 come with a lot of the drivers needed anyway, but a few graphics, card reader, fingerprint scanner and other more esoteric bits of hardware drivers need to be stuck in the WDS store.

[Norphy]

with only 3 types of computer to set up mdt less than an hour i would say (excluding downloading the aik as its several gbs)

 

i assume youre going to install pc1 get software drivers etc installed then image pull to server repeat for pcs 2/3 and have 1 image for each pc type then?

 

Why bother having an image per PC type? You don't need to with a generalised image any more and if you're going to have a fat image with all of your software installed, the need for MDT is reduced.

 

MDT is much more flexible, yes and if @abillybob ever wants to start customising the software loadout on machines depending on where they live then MDT is the solution but WDS is enough if he just wants a single image.

[Si2100]

What i found was install WAIK and use DISM to patched the image offline I didnt want to learn a load of cmd lines So i found thus: DISM GUI - Home

Gives you a nice UI for using DISM and patching drivers and removing them.