hi. i use sccm 2012 r2 to deploy windows 8.1 ent and have noticed that there are tons of updates being applied before the image is captured. this wastes time and uses up space on the disk. is there any way in which i can either download or build an up-to-date copy of windows 8.1 so that the least amount of updates get applied?

Not sure i understand what you mean. Because in the first part you say SCCM r2 apply patch before the WIM is apply ?

Well il try to answer anyway. You could using SCCM R2 make a build and capture task sequence and add all the window supdate in the wim and capture it after.

Info here: http://ebhava.com/blog/?p=78

If you want you could simply using SCCM 2012 R2 make a capture media. You install windows 8.1 install all the patch manually when you are satisfy with the image you run the capture media that SCCM made. This will give you a gold image with all the new patch.

You could also using SCCM 2012 R2 use offline servicing for the windows update (be aware this can break the wim and render it useless)

Normally we try to rebuild the gold image every few month to make sure the gold image is up to date.

Hope this help get you started

 

thanks. if i do a simple windows 8.1 deploy and then manually update it then capture it afterwards, could this captured wim file then be used by mdt 2013 as an operating system image which it uses to automate a build and capture task sequence? unfortunately we don't have a small golden image, which makes rebuilding tedious. we also have vs 2013 which has numerous updates. i have now loaded sccm software update point and i am thinking of using the wsus option in mdt (pointing to local server) instead of it pulling all the updates from the web. let me try that. 

Well if you have a huge image to make each time you should take the time to set up the build and capture to do everything you need so in the long term you will not have this issue.

Did you know in your MDT build and capture you could simply PAUSE the task sequence do the update and start the task sequence after :https://sysmgt.wordpress.com/2013/03/12/pause-mdt-2012-update-sp1-task-sequence/

To answer the question yes you could make a vanilla windows 8.1 with all the update and capture it using the media. After that import that wim into MDT or SCCM whit no issue.

• Edited by Frederick Dicaire 18 hours 33 minutes ago

currently i am doing exactly what you are referring to. i have a single task sequence that installs all the packages, runs scripts etc...pauses and then captures this image. my only concern is the time it takes. upwards of 7 hours!!

Well make your new windows 8.1 add all the update capture the WIM and replace the WIM in the build and capture and you will be done for the day. 

can this base or master wim file contain other updated apps like office 2013 so that i essentially start my new builds with "stuff" already updated and loaded?

Yes you can add anything in it that you need. Just keep in mind you should only put things that are require by everyone (update, office and such) because if you put some stuff and you need to remove it later it`s going to be a lot of trouble.

• Marked as answer by Karl van der Schyff 17 hours 44 minutes ago

ok, i will keep that in mind. i have a feeling this will save me a heap of time already. thanks for the help.

What you are referring to is call thick image where everything is inside the gold image to save some time. Me i like the hybrid a in between. Il give you a link for some good reading.

1. Thick Image. I like to refer to this as the old school approach to imaging where you basically build a reference machine, install all possible applications to ensure users have the applications they could ever possibly need and usually more. After that is done, you apply software updates for the operating system and all the applications, then you use Sysprep on the computer to capture the image. Then you make sure everything works and ensure that Sysprep didnt affect any applications.
2. Thin Image. This approach takes things to the other extreme. Little or nothing is installed on the reference computer, and you use Sysprep to capture that image. Or some will just use the image as shipped in the Windows 7 retail DVD or ISO with zero customization. This strategy assumes that youll be customizing the installation with applications and other necessary data dynamically at deploy time. This also means that all of your applications are packaged for an unattended installation, or you are willing to prestage them for users to install when they want, or you use something like Application Virtualization (App-V) so application profiles follow users regardless of the device they log on to.
3. Hybrid Image. In between Thick and Thin is a Hybrid Image, where applications that everyone uses or needs are captured in the base image (perhaps your VPN software, your antivirus software, your version of Microsoft Office, and the App-V client). Aside from those core applications, additional applications are layered on at deploy time based on user needs.

https://technet.microsoft.com/en-us/library/ee956904(v=ws.10).aspx

Well if you have a huge image to make each time you should take the time to set up the build and capture to do everything you need so in the long term you will not have this issue.

Did you know in your MDT build and capture you could simply PAUSE the task sequence do the update and start the task sequence after :https://sysmgt.wordpress.com/2013/03/12/pause-mdt-2012-update-sp1-task-sequence/

To answer the question yes you could make a vanilla windows 8.1 with all the update and capture it using the media. After that import that wim into MDT or SCCM whit no issue.

• Edited by Frederick Dicaire Tuesday, July 21, 2015 12:48 PM

Yes you can add anything in it that you need. Just keep in mind you should only put things that are require by everyone (update, office and such) because if you put some stuff and you need to remove it later it`s going to be a lot of trouble.

• Marked as answer by Karl van der Schyff Tuesday, July 21, 2015 1:37 PM