I figured I start a new post on this. My CIO and I have been going back and forth on this question for several days now and I want to share some insight and get some opinions. We used this post as a starting point http://blogs.technet...nager-2012.aspx
Our Goals
Protect all Windows 7 Machines with the latest security patches (Builten Id:MS) and Updates
Protect all deployments of Mircrosoft - Now Windows Desktop (Office, Visual Studio, ETC) with latest security patches and updates
Protect all Windows 2008R2 Servers with the latest security patches and Updates
Protect all deployments of Adobe Acrobat, Adobe Reader, Adobe Flash with securty Updates and Patches
Deploy Latest Drivers and Updates to our Dell PC's
Monitor Compliance of Deployments
Implementation, Limitations & Concerns
All Updates
Create an All Update Group for Reporting Purposes. We Selected all updates and put them in this group. DO NOT DEPLOY this group to anyone. We will use it only for reporting Purposes. (Not sure exactly how yet)
WIndows 7 Machines
Inital Setup
1. Create an Initial Updates Package. We called it "Windows 7 Software Udpates - Initial". This package contained all updates up to and including 05.31.2012. Our Search Criteria consisted of:
Product=WIndows7
Expired=no
Superseeded=No
Date Released or Revised is less than or equal to 05/31/2012
This gave us at the time of writing this 286 Updates
2. Create The Monthly Update Package for June 2012. We called it "Windows 7 Software Updates - 2012 06" This Package contained all the updates in the month of June. Similiar Search criteria as above only different Date Range.
This gave us 37 More Updates
3. Both of these Software Updates Groups where then deployed to a "Windows 7 Machines" Device Collection we created based on the following WMI Query:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Workstation 6.1%"
Monthly Procedure
Create a New Monthly Update Package after each "Patch Tuesday" and Deploy it to our Windows 7 Machine Device Collection. (We may do an Automatic Deployment Rule for this that we can later Green Light, not sure how to yet. We are currently using an ADR for Endpoint Protection Definiton Updates)
Remove all the Expired and Superseeded updates from all Deployments - Just create a search criteria for Expried and Supersceded to yes and Edit Membership. Uncheck the Check Box and they will remove themselves from your deployment group and delete themselves off the server in 7 days. Another good post about this procedure http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
Update the All Software Group with New Updates
Concern - We will never be able to delete any of our Monthly Updates or the Intitial Update package as that would create a hole in our security Updates. I.E. If a laptop left the network for 6 months and came back. I am not sure if I care, it's just that in 5 years I will have 60 of these Update Groups. I also do not know if having so many deployments will effect Client / Server Performance in anyway.
Microsoft - Non-Windows
Inital Setup
1. Create an Initial Updates Package. We called it "Microsoft Udpates - Initial". This package contained all updates up to and including 05.31.2012. Our Search Criteria consisted of:
Product=Expression Design 4
Product=Office 2010
Product=Visual Studio 2010
Expired=no
Superseded=No
Date Released or Revised is less than or equal to 05/31/2012
This gave us at the time of writing this 103 Updates
2. Create The Monthly Update Package for June 2012. We called it "Microsoft Updates - 2012 06" This Package contained all the updates in the month of June. Similiar Search criteria as above only different Date Range.
This gave us 2 More Updates
3. We had to create serveral deployments for this. One for each application that we deployed.
Concern/Question
1. Again you will not be able to delete any of these deployments for threat of creating a security hole.
2.. Should we just combine the packages and deploy them to all Windows 7 Machines? Will this create any Client/Server Performance Issues?
Adobe Updates
**This Assumes you have already setup SCUP and have an understanding of it. We used this youtube tutorial to get started. http://www.youtube.com/watch?v=fyEGWSFWyy0
SCUP
In SCUP we are going to Create 2 Publications. One for the intial Deployment and then another for the Monthly Updates. You will find that the updates here or a bit more infrequent and you may switch to a quaterly update
1. The Inital Publication we selected all updates, there were 39.
2. We assign the updates to a new Publication called "Adobe Updates - Inital"
3. We published Full Content
4. We will do the same thing for "Adobe Updates- 2012 06" ***Not 100% sure we need to seperate out these updates or if we can publish to an all encompasing group.
Inital Setup
1. Create an Initial Updates Package. We called it "Adobe Udpates - Initial". This package contained all updates up to and including 05.31.2012. Our Search Criteria consisted of:
Product=Adobe Acrobat
Product=Adobe Reader
Product=Adobe Flash Player
Expired=no
Superseded=No
Date Released or Revised is less than or equal to 05/31/2012
This gave us at the time of writing this 39 Updates
2. Create The Monthly Update Package for June 2012. We called it "Adobe Updates - 2012 06" This Package contained all the updates in the month of June. Similiar Search criteria as above only different Date Range.
This gave us 2 More Updates
3. We had to create serveral deployments for this. One for each application that we deployed.
Same Concerns and Questions
1. Again you will not be able to delete any of these deployments for threat of creating a security hole.
2.. Should we just combine the packages and deploy them to all Windows 7 Machines? Will this create any Client/Server Performance Issues?
Conclusions
I know I left out a bunch here, Still have to discuss Windows Server 2008 Updates and Dell Update. THe main thing we are still trying to figure out if it is OK just to have Several Big Intial Updates and then Just one Software Update for Everything. How will that effect client/server performance. I will clean this post up over time. Just wanted to get some feed back to start. Not sure if I am overthinking this or not..