Injecting Windows updates in to a .WIM using Microsofts DISM utility

So we have recently deployed IE10 to our Department (behind the times I know) and now have the need to include it in our SOE.

For this I have chosen to use Micrsofts DISM (Deployment Image Servicing and Management) Tool.

Getting IE10 and the pre-requisites on there was easy enough.

So I decided to try injecting all the Windows updates which our SCCM server server normally takes care of in to the .WIM as well to try and cut down on deployment time for new machines. Currently after applying the reference image during OSD it goes through over 100 updates which takes some time.

I found a nifty utility called DISM GUI created by a guy called Mike Celone. You can find it here: http://dismgui.codeplex.com/

Using this made the task of injecting the mass of updates much easier for sure. However even after importing the finalised .WIM back in to SCCM and reloading the file ready for deployment, the OSD sequence still saw fit to download and install over 90 updates… I am currently looking in to why this is the case!

The following sites have been helpful in my quest:
http://www.utilizewindows.com/7/deployment/203-apply-updates-to-windows-7-image-using-dism

 

Update: So after some log trawling, it looks like injecting these updates might not guarantee them to be installed. Doing a /get-packages on the mounted .WIM using the DISM tool we see the following. 130 updates needing attention once things get going.

DISM updates

Next stop will be to try and remove the Install Updates section of the SOE task sequence in SCCM and see if these updates still get installed correctly, as one would think that by injecting them with this tool should bypass that step…

Update2: So removing the Install Updates step out of the SOE task sequence did nothing to help the situation. After 10 odd minutes of waiting once a refresh of the SCCM client was done it proceeded to download over 100 software updates from the SCCM server and wait for a installation window. Looks like multiple Install Software Updates tasks and Restart Computer will be the way. At least this will prevent it from happening once the desktop is reached.

Update3: Multiple Install Software Updates and Restart Computer steps in the task sequence caused the OSD to error and stop. The smsts logs did not give much info as to what was wrong in this regard so I have left it as one restart and 2 software update install steps which is working.