JacobE

Hi all, Our maintenance windows here are not functioning correctly, from what I can see. There are no other conflicting maintenance windows setup either. Here is how they are set up at the moment. So the idea is that it starts on the Friday evening every week at 8pm and then finishes on Sunday morning at 5am, giving the whole weekend to allow for deployments. However, after this weekends patch deployments, quite a few machines have reported with error logs like below and are simply in a 'Downloaded Updates' state, where they have not installed the updates in the allocated time. As you can see the Maintenance window is coming on/off at times not specified. Is there something wrong in our configuration? Should they be set up differently? Thanks in advance Jake

Oh I did play about with this, but I was wondering if it would be required so I could balance my workload, that's all

Hmmm what error does it get when you try? I'd be surprised if you couldn't run the MSI considering how small the exe is compared to the MSI file. Have you looked inside the exe to see what files are in there?

Hi all, Ok, so I have another question regarding offline servicing. When playing around with injecting updates into the WIM within 2007 using MDT which worked fine, but I found with testing that the build would fail as .NET 4 isn't part of the original WIM. From memory I'm pretty sure the updates would inject but the build would fail applying the WIM due to .NET4 being missing at that stage. So my question is, is 2012 clever enough to know whether or not the updates will work and cause the TS to fail? I just don't want to schedule the WIM being updated over the weekend to come in on a Monday for the build to potentially fail? Any help appreciated. Jake

Thats cool. Yeah it won't be added until the company is compliant anyway so that's not an issue. I'll put it to the heads and see what they say. Thanks again for your help!

Ah ok, so it does mean the TS's will automatically use the new WIM. OK great, I'm not sure my managers would be too happy with using untested WIM's straight away. Assuming it's easy enough to revert back if required? (I know you have never done it, but you might know the process )

Hi mate, Thanks for the quick reply. The ADR stuff is awesome, we will run with that. So after the offline servicing runs it still only shows 1 WIM available?

Ah I've remembered now, what had happened is that the Boundary setup did not have a site system setup, once added the machines then started downloading fine.

We had this a little while ago. It was a boundary issue.

Morning all! Ok so we have recently moved to SCCM 2012 R2, and I've been asked to look into offline servicing and automatic deployment rules, I have done and have a few questions regarding both. Automatic Deployment Rules So first off, ADR. The idea behind it is great, set the rules up, and never have to touch the updates ever again, sounds like a dream and almost too good to be true, for our firm I believe this may be the case. The reason being, we have an Infosec department which dictates which updates are required each month. So for example we typically get a list, last month it was: MS14-011 MS14-012 MS14-013 MS14-014 MS14-015 Now, only having briefly looked at the ADR side of things, from what I can tell you cannot specify exact updates (which is fair enough, how is it going to know which updates the Infosec department wants?) but can only go by classification, severity etc. Which would ultimately result in a lot more updates being deployed than we want. So my question is, if I manually create the software update group with a specific name, for example "Monthly Updates" can I setup a rule to just pull the updates from that update group and deploy those without having to touch it? Or is it possible to specific a rule which will match the criteria that we need and just adjust it each month to the MS numbers? Offline Servicing We as a company, REALLY like the sound of this. Alongside our monthly patching we have another deployment which constantly runs which includes all updates deployed previously, the reason being so when machines are built, they see this deployment and within 24hrs of being built, are fully secure. It keeps everyone happy. With the correct implementation of offline servicing, our machines could be fully secure from the moment they hit the log on screen. Question for offline servicing is, during the process it takes the WIM file, copies it, and injects the updates into the copy of the WIM, then end result is that it gives you 2 WIM files, the original, and the new one with updates. Now, I think I know the answer to this, but I want someone with experience of it to confirm. When the process is finished, and it gives you the two WIM files...the task sequences will remain untouched won't they? So we will have to go into each task sequence and adjust the WIM file they deploy to the new one with updates? Obviously I don't want this process to run over the weekend, to come in on Monday to find all the task sequences potentially using a WIM that's untested! Thanks in advance for the help Jake.

One option would be to use offline servicing in 2012

Thank you, good to be here!

Hi there, Thought I'd finally register here after this website coming up a number of times when googling for SCCM related answers and finding it always friendly and helpful. Bit of background, been working in SCCM for about 3 years now, had 2007 at my last place and at my current firm we have just gone through the 2007 > 2012 R2 migration process. Otherwise been working in IT for 8-9 years blah blah blah...etc etc. Looking forward to being part of the community, with SCCM being part of my everyday job I can see me asking a lot of questions Best, Jake