Graeme Bray

Real World Automation and Deployment

Build and Capture Task Sequence

leave a comment »

Hello all.  Time for one of my first posts with my real world deployment problems.  One of the things that I struggled with in my deployments is image updates.  I would image a system on a VM using MDT, make my updates manually, take a snapshot, then start a capture task sequence.

What a pain.

After finding some time, I was determined to make this simpler.  I ignored our legacy deployments (Server 2003), and went for only 2008 R2+ deployments.  What I came up with, was integrating as much base Microsoft components as possible.  Being server deployments, I plan on as thin of an image as possible for less attack vectors on a completed and production system.

Below is my completed image build task sequence.  There are no OS or Registry customizations done inside the build.  Everything is done afterwards in case we find a major issue with some entry we are creating (or Microsoft finds it).

Image

You’ll notice that I left most of the base Imaging steps from a base Server.xml Task Sequence template.

I use Windows Update (via a WSUS auto-authorized system) to automatically update.  Doing this allows only needed updates to be installed (thus eliminating the “superseded” updates from applying and being unnecessary.  This slims down the dreaded WINSXS folder as there is no cleanup for it like there is in Windows 7.

That’s all for now.

Advertisements

Written by Graeme

December 19, 2013 at 3:39 AM

Posted in MDT

Tagged with , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: