OS Images - Schedule Updates - What's the impact?

Hi all,

In SCCM 2012 when you use the 'Schedule Updates' function under 'Operating System Images' in the Software Library, when an update is actually happening (in my case I want to add Windows updates), what is the impact to the SCCM environment?

What I mean is what will it do/what services will it impact, bring offline etc? To me it makes sense that the WIM file being updated is unavailable which is fine, but does it stop anything else?

A website I found said something about action being taken on the site so it recommends doing it out of hours. That's lead me to ask this question cos it worried me a tad. As I'm only adding the IE11 update to the WIM it shouldn't take long but I don't want to impact other areas of our I.T. that use SCCM.

Hopefully this question has made sense. Basically I just want to perform an OS Image update and trying to determine the impact of doing it during office hours.

As a sub question - what do others do to protect the WIM file in case something goes wrong. Do your rely on the auto backup? Take a copy of the WIM yourself first? I've done the latter.

Thanks.

May 26th, 2015 9:41pm

What it does, is basically just injecting Windows updates (component based servicing ones) to your .wim -image through DISM commands. All the released updates cannot be injected to image with this feature.

More on CBS: http://blogs.technet.com/b/askperf/archive/2008/04/23/understanding-component-based-servicing.aspx

Sometimes the offline servicing feature works, sometimes not so well.. always test, test and test your .wims when using the feature.

The schedulling (or injecting) process is done on the ConfigMgr site server, the server takes a copy of your .wim (from the source folder you've defined), mounts it and injects the updates to it, unmounts it and copies it back to the source and then distributes it to your distribution points. The impact doing this during office hours shouldn't be any problem because all is done on the server side. You can view the process by checking OfflineServicingMgr.log on your site server.

Taking backups of your .wims is a good idea, specially when dealing with technology like this, that has been seen to cause problems for some.

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 11:39pm

Hi and thanks for the reply,

Do you know if this method will support adding the actual IE11 update itself? So not just updates for IE11 but the browser as well?

If not, what's the best way to get the browser to install during the OSD task sequence? I tried adding the 'Install Windows Updates' task but it didn't do anything unfortunately. At my previous company I deployed it as an application but they're not so keen on that here. For existing PC's they want to use SCCM Windows Updates and get it installing during build time.

Based on that, updating the WIM seemed easiest. What this SCCM process is doing is actually what I used to do manually at an old company (using DISM to inject updates) but I don't remember if IE11 worked.

May 27th, 2015 2:07am

Do you know if this method will support adding the actual IE11 update itself? So not just updates for IE11 but the browser as well?

To my knowledge, no, you cannot use the Offline Updates feature to inject IE11. You can however do it manually using DISM: http://www.catonrug.net/2014/08/slipstream-internet-explorer-11-into-windows-7-sp1-x86-source.html . The trick as outlined on that page is also injecting all of the pre-reqs (many of which are not in the WSUS catalog and so also have to be done manually using DISM).
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 9:14am

Hey mate,

So I manually added IE11 to the WIM file using DISM and all that was successful. By the end of it, my WIM was 200mb bigger so there's visible evidence of it going in.

You know what though? Deployed it via SCCM and still got IE8.

Any idea how that's possible?

Thanks.

May 28th, 2015 4:00am

Are you sure you deployed the updated WIM? Specifically, did you update the correct WIM, import it into the console or reload it in the console, and update the DPs? Did you verify the WIM on the DPs is the one with the updates in it? Did you also add all of the pre-reqs?
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 9:30am

Hi,

I best cover each of your questions one by one:

"Specifically, did you update the correct WIM, import it into the console or reload it in the console" - I took a copy of our production WIM and put it in a temp folder at the source location. I updated that copy and have created a test 'Operating System Image' which references that WIM in SCCM. Since posting my last message I have redistributed the new OS Image to the DP, although I had already clicked 'Update DP' before my test.

"Did you verify the WIM on the DPs is the one with the updates in it?" - I tried, but it seems the image is stored on the DP in a funny way. By funny I mean in multiple folders which only add up to a few hundred MB. So I'll admit here I'm a bit confused, maybe I'm looking in the wrong spot but when I redistributed the OS image, I saw new folders appear before my eyes on the DP.

"Did you also add all of the pre-reqs?" - I added all the pre-reqs on that URL you sent me. One of the pre-reqs failed and IE wouldn't inject. I re-downloaded the pre-req and it went in OK so must have been corrupt. Once that went in, IE injected happily and committed the WIM.

So all that points to everything being done correctly right? So that's why I'm confused. Now that I've redistributed content and the re-deployed the task sequence, I'm going to test again now. If it works I will reply on here again but if I don't, let's assume I still got IE8.

Cheers for you responses once again.


May 28th, 2015 7:50pm

Hi,

I best cover each of your questions one by one:

"Specifically, did you update the correct WIM, import it into the console or reload it in the console" - I took a copy of our production WIM and put it in a temp folder at the source location. I updated that copy and have created a test 'Operating System Image' which references that WIM in SCCM. Since posting my last message I have redistributed the new OS Image to the DP, although I had already clicked 'Update DP' before my test.

"Did you verify the WIM on the DPs is the one with the updates in it?" - I tried, but it seems the image is stored on the DP in a funny way. By funny I mean in multiple folders which only add up to a few hundred MB. So I'll admit here I'm a bit confused, maybe I'm looking in the wrong spot but when I redistributed the OS image, I saw new folders appear before my eyes on the DP.

"Did you also add all of the pre-reqs?" - I added all the pre-reqs on that URL you sent me. One of the pre-reqs failed and IE wouldn't inject. I re-downloaded the pre-req and it went in OK so must have been corrupt. Once that went in, IE injected happily and committed the WIM.

So all that points to everything being done correctly right? So that's why I'm confused. Now that I've redistributed content and the re-deployed the task sequence, I'm going to test again now. If it works I will reply on here again but if I don't, let's assume I still got IE8.

Cheers for you responses once again.


Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 11:50pm

Hi,

I best cover each of your questions one by one:

"Specifically, did you update the correct WIM, import it into the console or reload it in the console" - I took a copy of our production WIM and put it in a temp folder at the source location. I updated that copy and have created a test 'Operating System Image' which references that WIM in SCCM. Since posting my last message I have redistributed the new OS Image to the DP, although I had already clicked 'Update DP' before my test.

"Did you verify the WIM on the DPs is the one with the updates in it?" - I tried, but it seems the image is stored on the DP in a funny way. By funny I mean in multiple folders which only add up to a few hundred MB. So I'll admit here I'm a bit confused, maybe I'm looking in the wrong spot but when I redistributed the OS image, I saw new folders appear before my eyes on the DP.

"Did you also add all of the pre-reqs?" - I added all the pre-reqs on that URL you sent me. One of the pre-reqs failed and IE wouldn't inject. I re-downloaded the pre-req and it went in OK so must have been corrupt. Once that went in, IE injected happily and committed the WIM.

So all that points to everything being done correctly right? So that's why I'm confused. Now that I've redistributed content and the re-deployed the task sequence, I'm going to test again now. If it works I will reply on here again but if I don't, let's assume I still got IE8.

Cheers for you responses once again.


May 28th, 2015 11:50pm

I just started over. Got the original WIM, injected IE11 and it's pre-requisites and this time it worked. Not sure what the difference was.

So updating an image with IE11 via SCCM doesn't work, as suggested. Adding to WIM directly was the only way.

  • Marked as answer by Norton_San 7 hours 29 minutes ago
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 8:20pm

I just started over. Got the original WIM, injected IE11 and it's pre-requisites and this time it worked. Not sure what the difference was.

So updating an image with IE11 via SCCM doesn't work, as suggested. Adding to WIM directly was the only way.

  • Marked as answer by Norton_San Wednesday, June 10, 2015 12:17 AM
June 10th, 2015 12:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics