[mdt] Better ways to change the base OS, when new updates come out.

[denmyos]

Every time microsoft push out new updates to win7 I would deploy a virtuel image, update with latest updates and the go into MDT and import it and attach a TS to it etc etc.

 

Is there a easier why to do it, so I don't have to go through all the steps once a week.

 

If I'm to busy i would just make two TS that runs a windows updates when deploying the image.

The problem with that, is it takes hell of lot time to deploy.

 

 

What do you guys do when windows comes out with new updates.?

 

I don't have a wsus server.

[tmcd35]

 

I don't have a wsus server.

 

Set up a WSUS server?

[Norphy]

You can use DISM to apply updates to a WIM directly without having to boot from it. If you're really insistent on doing it that way, you could do that.

 

But seriously, set up a WSUS server. It will make your life easier.

[Rodan]

You could use a scheduled batch file to do the following:

Use wsus offline to download the relevant patches

Use wdsutil to export the wim

Use dism to mount the wim

wrap dism injection in a for loop

Use dism to commit and unmount the image

Use wdsutil to re-import the wim

 

You then need to manually catalog the wim, unless anyone has found a way to script that

Then re-import into MDT OS' and the task sequence ready for re-use.

 

Wsusoffline here: WSUS Offline Update - Update Microsoft Windows and Office without an Internet connection

[SHimmer45]

i was going to suggest Wsus offline as well.

 

WSUS isnt that complicated to setup and only needs a server with reasonable disk space depending on which updates your caching.

the biggest headache is making sure GPO is set properly to stop it rebooting / prompting for updates when users are trying to use it

[halbaradkenafin]

You can use DISM to apply updates to a WIM directly without having to boot from it. If you're really insistent on doing it that way, you could do that.

 

This is what we do every few months, just to roll up any updates that have come out. But we deploy them through SCCM a few weeks after they've come out to allow time for others to test them and find bugs etc.

 

You then need to manually catalog the wim, unless anyone has found a way to script that

Then re-import into MDT OS' and the task sequence ready for re-use.

 

We've just been using DISM on the WIM file that is in the source directory that MDT uses and never had any issues with it after slipstreaming updates into it.

Edited January 22, 2015 by halbaradkenafin

[Norphy]

If your image is in SCCM, you don't have to use DISM by hand to integrate your updates into your image. Instead, find the image in your console, right click on it and click "Schedule updates". It will then bring up a list of updates which are applicable to your image and integrate them for you.

 

I have no idea if this works if you have MDT integrated into your SCCM though. I personally don't.

[denmyos]

I don't have Sccm.

So it seems like i have to set up a wsus server.

 

the biggest headache is making sure GPO is set properly to stop it rebooting / prompting for updates when users are trying to use it

 

That is done by Deep freeze thawed period.

You can point it to a wsus server to get updates.

 

 

Thanks alot

[CraigM]

I deploy with MDT and have a WSUS server set up. What I've started to do lately is to inject as many updates as I can into the Windows 7 WIM file. It saves a lot of time when setting up individual PC's like I'm doing for classrooms at the moment. Windows 7 has a lot of updates available for it and once you throw Office in it also has a lot of patches to download and install. My main goal really is to shave off as much time as I can from the imaging process. It really isn't fun watching a new build suck down 2GB worth of updates and then spend over an hour patching itself...