[mdt] MDT and Windows Updates

[dany2010]

Looks like you can't apply updates the the install.wim file.

 

Tried using DISM to inject updates from the wsuscontent folder and windows update still reports there are no updates installed when you check and wants to install over 100.

 

Edit. Changed drivers to updates.

Edited July 3, 2013 by dany2010

[sted]

thats because drivers are inf files and updates are msu/msi/exe.

 

its just easier to deploy to a vm. install updates and capture a new image

[dany2010]

I said drivers again didn't I. Meant updates

[sted]

Injecting Windows Updates into install WIM files via MDT | deKay's Blog

 

but seriously just set up a vm install updates snapshot and capture you would of been done by now rather than messing with dism

[steewy]

Ok,

 

Let's sort this out.

 

To have my main image up to date I use a VM on VMWARE.

Before capturing the image using the MDT server I take a snapshot of my VM and put a the current date as a refrence.

 

When there is too many updates I just use my virtual machine, restore the snapshot, install all the new updates and also the updates of the software that are on my image (even if I tend to install them after deploy by GPO), and I capture the image again. Once I have my new image I just replace it in MDT and deploy the new one.

 

I find it quicker and also you are sure that you have all the updates in your image, no need to use the command prompt.

[dany2010]

Injecting Windows Updates into install WIM files via MDT | deKay's Blog

 

but seriously just set up a vm install updates snapshot and capture you would of been done by now rather than messing with dism

 

Installing a machine now to take a image .

 

Would have liked to get the other way working as its more like installing straight from the disk but this way seems easier.

 

I'm thinking of installing office to before taking the image. Are there any issues with keys and sysprep.

[steewy]

Installing a machine now to take a image .

 

Would have liked to get the other way working as its more like installing straight from the disk but this way seems easier.

 

I'm thinking of installing office to before taking the image. Are there any issues with keys and sysprep.

 

 

I don't know because I deploy office by using a task sequence in MDT.

 

You can create an admin mst file to deploy office with your serial and settings. It's better that way so you can include all the office updates in the installation folder.

 

if you need further help for that create a topic or PM.

Edited July 3, 2013 by steewy

[sted]

as long as you sysprep office before imaging no

[warren17c]

Hello all, only just registered as this topic peaked my interest...

 

Some things I have picked up on this subject and thought I would share...

 

If you are going to Capture an Image, ALWAYS use a VM enviroment (VMWare / Hyper-V etc) As doing it off a real device means you have real device issues. Perhaps you have to install a little applicaiton to get the keyboard working, or a reg key under HKLM to get it to do what you want - These things will be in your reference Image!! - Also snapshots and cscript.exe %scriptroot%\ltisuspend.wsf are a life saver here.

 

There are 3 types of Images Thin, Think and Hybrid.

A. Thin Imags - This is just the out of the box ISO from MS.

B. Thick Images - Everything, Apps, updates kitchen sinks...

C. Hybrid - A bit of both

 

All have their advantages. For me I use hybrid. Some closer to Thin than others. I would play with thin and Hybrid on your network, see how each pan out. (time them both on your network) use the faster and or most stable. (I have AV issues scanning my deployment share, I argue it doesnt need it, but the guys above me say it needs to).

 

Finally, if your not using drivergroups and using a seperate task sequence per model, PM I will walk you through it. All you need is a TS per OS (Win7pro / Win7Ent etc) Some clever work and your life becomes easier.

 

 

There is no right or wrong with them. Use whatever works.

Edited August 1, 2013 by warren17c