How to update local source media to add roles and features

re: How to update local source media to add roles and features

joscon [Microsoft] — Tue, 07 May 2013 16:54:21 GMT

You would need to update the install.wim and then re-extract it I believe.

re: How to update local source media to add roles and features

Gai-jin — Tue, 07 May 2013 16:51:36 GMT

Also, if we have created a network based side-by-side store, with the winsxs source files extracted from the install.wim, is it possible to update the network sxs store directly, or is the only option going to be to update an install.wim and extract the updated contents of the winsxs directory from the wim each time?

re: How to update local source media to add roles and features

joscon [Microsoft] — Tue, 07 May 2013 16:42:02 GMT

You do this in the same way, just use the sxs path.

re: How to update local source media to add roles and features

Gai-jin — Tue, 07 May 2013 16:34:34 GMT

How would you update the bits that aren't part of the install.wim on the 2012 media, such as the install files for the .Net 3.5 feature?

re: How to update local source media to add roles and features

Jim Britt [MSFT] — Tue, 19 Mar 2013 17:34:07 GMT

Joseph, great detail and process - thanks for sharing this as well as Ben!

re: How to update local source media to add roles and features

joscon [Microsoft] — Mon, 26 Nov 2012 16:07:09 GMT

@Adam;

I added a small blurb at the end of this post to reflect that you'll need to update this anytime a new update is released to keep the source current. There isnt an automated way to do this in product currently.

re: How to update local source media to add roles and features

joscon [Microsoft] — Tue, 20 Nov 2012 23:14:53 GMT

@Adam,

Thanks for the comment. I'll look into amending this post or writing something new that speaks to this.

re: How to update local source media to add roles and features

Adam Stasiak — Mon, 19 Nov 2012 20:54:11 GMT

Is there a way to automate this, or at least to tell which patch you need to include reinstall a feature?

At this point in the 2012 lifecycle it's not too bad, but in a year or two, when there are a couple dozen patches, maybe a service pack, it seems like it would be a big pain in the neck.

You get to either maintain a source image with every patch that you've added to your servers, or you need to go hunting down the right patch when you want to install a feature.

It seems like this makes features on demand rather unappealing as it now stands.

Also, if you put the SxS folder in a network share for this same purpose, is there a way to achieve the same thing, or can this only be done on a WIM?