What´s the sense of a build and capture task sequence?

[clickmaster]

Hi guys,

 

this is my first topic here .

 

I´m new to SCCM 2012 R2 and there is one thing I don´t understand.

 

What´s the sense of a build and capture task sequence? Why should I go through this complex process of building packages and doing some scripting just to capture an image after that?

Instead of doing this I could easily do a manual Windows 8.1 installation and run a capture only task sequence.

 

Or is there something I forgot to think about?

 

Don´t get me wrong. I understand the logic behind a package based task sequence. You have total flexibility and can modify the sequence very easily.

But why should I use this just to get an image?

 

Any help would appreciated .

[anyweb]

the logic behind it is to automate everything so that you dont have to do manual tasks, this becomes useful and apparent if you have to have many 'gold' images supporting servers, desktops and so on

[xc3ss1v3]

To expand up what Niall stated... using build and capture allows you to avoid having to install applications, updates, drivers, etc... that are going to be used on practically every system you service. Sure for a 1-off image you could simply manually install an OS then install all the necessary drivers, updates, applications then run a capture sequence. But, what happens when a certain application is either no longer needed or upgraded? That image now becomes unusable. Having a B&C sequence available allows you to simply go in to the TS steps, remove/change a step or two then run the sequence and walk away.

 

It's simply all about simplifying the image creation process.