Integrating .NET updates into WIM?

[berkshireicttech]

Hi Guys

 

Am I able to inject the .NET updates into my Win 7 WIM file?

 

For the Office updates, I have been extracting the MSP files from the EXE's, then pop into updates folder of Office.

 

There are loads of .NET updates that need to be installed every time we run a deployment so would like to integrate them to save time. Is this possible and if so can someone tell me how?

 

Thanks Guys

[disk]

I never had any luck injecting .NET updates in our WIM images. I haven't looked into the possibility in at least a year however, so maybe there is something out there. Does your imaging solution have the capability of automatically running post-imaging tasks?

[free780]

I found .net and office updates can't be injected. Automating your build and capture seems the best approach.

[CraigM]

Unfortunately .NET updates are not available in MSP or CAB files, which you could inject into a WIM file. As such, during my imaging task, the latest .NET is downloaded and installed via WSUS. I dislike the fact that it takes up extra time, but such is life. With Office, I extracted the last service pack into the Updates folder, so that it's installed along with Office during the imaging task. All the rest of the updates come down again via WSUS.

 

I've managed to get my install time from boot to fully up to date Windows 7/Office 2010 down to 4.5 hours on a Core i3 with 4GB RAM PC.

[Arthur]

I found .NET updates can't be injected.

They can be. The two updates I've highlighted below are .NET 3.0 and 3.5.1 updates released last month.

 

Obviously you can't integrate .NET Framework v4.0/v4.5.x updates into Windows 7 images since the operating system didn't ship with those framework versions, but you can do the rest.

 

http://vgy.me/ETo4Qz.png

 

Unfortunately .NET updates are not available in MSP or CAB files, which you could inject into a WIM file.

.NET updates are available as .MSUs which can be integrated (as you can see above).

Edited April 17, 2015 by Arthur