Icangoogle Posted July 13, 2015 Posted July 13, 2015 I currently use SCCM to image laptops. Once the image is complete after a numerous restarts there is 105 updates. Is there away to combine the updates without creating a new base image.
synaesthesia Posted July 13, 2015 Posted July 13, 2015 "Combine?" You can slipstream windows updates into an image, however frankly it'd just be quicker to do the base image. 1
halbaradkenafin Posted July 13, 2015 Posted July 13, 2015 I currently use SCCM to image laptops. Once the image is complete after a numerous restarts there is 105 updates. Is there away to combine the updates without creating a new base image. Which version of SCCM are you using? 2012 has an option to slipstream updates into the image file, you can also add the Install Updates task to a OSD task sequence and it will install any updates that have been marked for deployment to that device (other than Office, .net and similar unless they are already installed when the task comes up). You can also slipstream the updates into the WIM file "manually" using DISM through either batch file or powershell. We use the first option every 6 months or so and just keep the Install Updates task in place to catch the rest. 1
mrbios Posted July 13, 2015 Posted July 13, 2015 Making sure that the updates are approved and downloaded on the SCCM server first, then go to operating system images > right click your image > schedule updates
Norphy Posted July 13, 2015 Posted July 13, 2015 Making sure that the updates are approved and downloaded on the SCCM server first, then go to operating system images > right click your image > schedule updates Bear in mind that this will only slipstream Windows updates, Office Updates will still need applying post deployment. 1
mrbios Posted July 13, 2015 Posted July 13, 2015 Bear in mind that this will only slipstream Windows updates, Office Updates will still need applying post deployment. I'd suggest giving this a shot so that office updates are installed during deployment rather than post deployment: Henk's blog: Workaround for installing Office updates during task sequence Not tried it myself yet but have always planned to get round to that. 1
halbaradkenafin Posted July 13, 2015 Posted July 13, 2015 The other option for Office 2013 updates is to drop the msp files into the Updates folder in the Office folder. It will run any msp files in there as part of the install, this is also where the config file for install options goes so I generally rename it to 1 config.msp or something so it is the first one ran. 1
Arthur Posted July 13, 2015 Posted July 13, 2015 Making sure that the updates are approved and downloaded on the SCCM server first, then go to operating system images > right click your image > schedule updates Isn't that method meant to be a bit unreliable? Software Updates of reference image via the SUP is simply not very reliable, it may succeed, it may fail… It’s been like that since ConfigMgr 2007, and even to this day (March 2014, with ConfigMgr 2012 R2) I run into customers were the software updates action dies when you feed it with too many updates at once. Just a few updates, and it works perfect, feed 120 updates to the task sequence, and it’s likely to die. Source: Deployment Research 1
mrbios Posted July 13, 2015 Posted July 13, 2015 (edited) Isn't that method meant to be a bit unreliable? Source: Deployment Research I've never had an issue under SCCM2012R2. Initially going back 2 or so years i must have issued a good chunk of 80 updates or so to it. Now i do it every month for 5-20 updates and it works fine every month. It's worth noting that it does do a backup of your wim file pre-updates too, so if it does fail you can always revert to the backup. EDIT: Isn't that snippet talking about the software updates component of a task sequence? Which i agree is pretty useless. It doesn't mention the scheduled updates slipstreaming specifically, and i don't think this function existed in 2007 which it also refers to? Edited July 13, 2015 by mrbios 2
Arthur Posted July 13, 2015 Posted July 13, 2015 I've never had an issue under SCCM2012R2. That's good to know.
mrbios Posted July 13, 2015 Posted July 13, 2015 That's good to know. See my edit, i think we may be talking about two different things
Icangoogle Posted July 14, 2015 Author Posted July 14, 2015 How do approve the updates and download them as they aren't appearing when I right click the image Making sure that the updates are approved and downloaded on the SCCM server first, then go to operating system images > right click your image > schedule updates http://awscdn.cdngeek.net/images/smilies/smile.png
mrbios Posted July 14, 2015 Posted July 14, 2015 (edited) How do approve the updates and download them as they aren't appearing when I right click the image So first you need to go into All software updates, and filter for what updates you want to download. Personally when i started i put all the updates up to that date into one software update group and named it for example "Windows 7 x64 - Up to X date" then every month after i do a new software update group of "Windows 7 x64 - August 2015" for example. Then i save two search filters to search for all windows 7 updates of 64bit in the last month. Just add something into your calender for a date after the 2nd tuesday of each month to remind you to create a new group of updates. Anyway, in all software updates, add search criteria for the OS, architecture and "within last X days" if need be, then select them all and add them to a software update group. During this process you'll create a deployment package and be asked if you want to download the updates. It's this process in actually downloading the updates that causes them to become available to the scheduled update section of the OS image window. Someone may have a better way of organising it than me, i've kind of got to this point of having a software update group for each month through my own trial and error rather than any recommendation. I'm not really sure whether you're better off making one windows 7 deployment package and adding to it constantly or if you're better off making one per update group (which is the way i do it at the moment) either. If you use SCEP though then you should definitely setup an automatic deployment rule for the SCEP definitions. If you wanted you could split your updates into security update groups and other updates so that you can deploy security fixes asap too while not deploying the rest. I don't generally tend to deploy all updates straight away myself, i tend to wait a week to see if any news of updates breaking things appear. Which also isn't really recommended practice with security updates i don't think. Edited July 14, 2015 by mrbios 1
halbaradkenafin Posted July 14, 2015 Posted July 14, 2015 I do it by monthly groups as well. It makes it much easier to manage and work out which updates are new. I do a Windows 7 group in general though and put both x86 and x64 together but that's because we've only got 3 x64 machines on the network so no need for their own collection. I also deploy the updates to a small group of PCs used by trusted staff, warn them in advance that the next lot of updates are going out and to report any problems. After a few days of regular use I push out the updates to the rest of the network, scheduled to install over the nearest weekend.
cooka Posted July 16, 2015 Posted July 16, 2015 Sorry I haven't read the entire post. But if your using SCCM 2012 R2, in software library\operating system images click on the image and in the ribbon at the top click on schedule updates. This should mount the image and insert the updates into your image
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now