I need to try to inject updates into a windows 7 image (Our default WIM with Software installed) I have access to SCCM but it does not deploy images. I do not have access to our WDS.. I do have WAIK installed on my machine. I was hoping that I could use waik and inject them like I do drivers? But so far I have not worked it out. I thought I could also do it as part of a Task Sequence but that seems to only work if you have updates within SCCM Can some one point me in the right direction?

Slipstreaming SP1 is not possible. You should aquire media directly from Microsoft with SP1 already included and rerun your build and capture task sequence with the new OS source files to regenerate your reference image.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I just found this a few minutes ago and am trying it now. Looks like it is possible. http://www.urtech.ca/2011/05/solved-how-to-slipstream-inject-service-pack-1-for-windows-7-into-an-existing-rtm-build-dvd-wim/

Doesn't matter -- it's not supported and asking for pain upon pain upon pain. My suggestion above is the best course of action short-term and long-term.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Yeah had a quick look and it looks horrible. Surely there should be a way during a build and capture to make sure that all updates have been downloaded and installed. I have only been using SCCM for a few days so I could miss something simple.

Yes there is: use an Install Software Updates task. But for SP1, you should always start with media from Microsoft that already has it incorporated.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I run that task but when I check what updates are installed it says 0. Is there a log somewhere that will tell me why it is not installing? I have it set to "All software updates" assuming that's right. I also found these Scripts that should work but they seem to fail. Only gave 'em one run yesterday but have not had a chance to see why they fail.

Do you have an active deployment update containing the desired updates targeting the same collection as your TS advertisement?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I have no idea what that means.. I have just had SCCM dumped on me a few days ago. I didn't set up the system but have been asked to set up a windows 7 image for deployment (and upgrades) of our laptop fleet. I have used WDS before but even then not much, I always just did my imaging with WAIK and a USB drive. So the whole task sequence thing is very new to me.

I have no idea what that means.. I have just had SCCM dumped on me a few days ago. I didn't set up the system but have been asked to set up a windows 7 image for deployment (and upgrades) of our laptop fleet. I have used WDS before but even then not much, I always just did my imaging with WAIK and a USB drive. So the whole task sequence thing is very new to me. You've got a bit of work ahead of you to set this up. Not a biggy, its difficult first time around is all. http://technet.microsoft.com/en-us/library/bb680701.aspx You need to install WSUS onto your Site server, then install via the ConfigMgr console the Software Update Point (SUP) Role. Plenty of stuff to read on what you need to do with the WSUS installation, requires SQL or SQL express (might as well use full SQL as its on your primary site server), choose custom website, look for some ConfigMgr site installation guides, they will carry info on WSUS, better to refer to the ConfigMgr Microsoft documentation library (best source of information on the web) - http://technet.microsoft.com/en-us/library/bb680651.aspx Once you have the SUP functioning fine, find the patches you want, bundle them into an Update List, then using the Update List create a deployment, target a collection with your test machines in, then trigger the client into checking its Management Point (on the Client, Control Panel, ConfigMgr applet, Actions, Machine Policy retrieval and evaluation ... That's a seriously abridged version of the sequence of steps you need to go through to get ConfigMgr patching your Clients.

OK I see what is going on here. Looks like SCCM needs to take control and manage WSUS for it to work. As this will not work in my environment, is there a way to stop the task sequence in the middle so that I can make sure that all updates are downloaded and installed from WSUS (would require rebooting a few times) then have it finish the capture at the end?