XSCCM

Ahh, ok. Great - once again thank you for your time

Thank you for the reply - I have looked into using the task sequence and set it going for three test servers over the weekend and it appears that the task sequence was executed and ran as I wanted which is fab. However, there is one thing I do not understand. The task sequence can only deploy updates which are already made available to the collection and as I underestand it to make them available to a given collection I would right click the software update package and click deploy. This then takes me through the deployment wizard asking for a date/time to deploy etc... How do I ensure that the updates are only installed by the task sequence and not the auto deployment via available updates? Many Thanks for your time.

We are deploying Windows updates to our servers in a controlled manner and require a restart after instalation even if the update itself doesn't require the restart. We have a software update package built and deploy the updates out to a collection but cannot see a force reboot option in the deploy software updates wizard. There is of course the tick box for "Syetem restart (If necessary)" however we would like to make the reboot mandatory once all available updates are deployed. What would be the best way to ensure this happens? Thanks.

Great, again thank you for taking the time to reply - its been a big help.

Thank you very much for taking the time to reply. I just wanted to ensure what I'm trying to do it possible! I'll not go away and figure out how to put it into practice. Just one further quick question, you say that I create one software update group and deploy that to each of the 12 collections as required - can that be scheduled, so week one depoly to group 1, week 2 deploy to group 2...etc. Or will manual intervention be required to assign the software update group to each collection on a weekly basis. Either option will be fine to be honest!

Hi, I'm after some basic advice and a gentle nudge in the right direction for a deployment I've been asked to look at as I'm pretty new to SCCM. We have SCCM already setup and configured along software updates being installed to Windows 7 clients weekly. We would like to use SCCM to deploy windows updates out to our server estate in a controlled manner (Server 2003 and 2008). This being that the windows updates will be deployed gradually, in 12 groups to control the number being updated and to control which updates are installed, so that over all our servers are updated once a quarter. So, I'm thinking that I can update the Software update group and then deploy the updates out to Group 1. Group1 would contain our test servers just in case any of the updates conflict with our applications. Beyond that we would then deploy weekly to group 2, group 3 and so on, but installing only the updates which were installed to Group 1. At the end of the cycle we would then want to add new updates to our Software group and start it again. After spending some time looking at this and following through the guides ,the bit I'm struggling to get my head around is how we can only install updates which have been installed in group 1. I've looked at the ADR but I'm not sure if this will give us what we need. Any help would be gratefully received. Thanks,