Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Howard

  • Rank
  1. I am implenting ADR for patch managment and I am having a bit of a Property filter issue. I would like to create an ADR that creates monthly deployments for my patch managment that I have control on when deploying. So I have checked Create new Software Update Group under general and cleared the "enable the deployment after this rule is run". My problem is setting up the property filters under software updates. Here are my concern: If I check "date released or revised" and set it to last 30 days, my first Software Update Group will only have Updates valid for the last 30 days. If I
  2. 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 o
  3. I also found this which is an interesting read. http://blogs.technet.com/b/server-cloud/archive/2012/02/20/managing-software-updates-in-configuration-manager-2012.aspx
  4. I acutually like to bump this subject as I find myself struggling to come up with a normal or typical deployment. First Question I have is for JOSH. I like the idea of pushing your updates up to all software updates group to protect you from a security hole, but what happens when you reach 500 updates. I thought there was a limit to the amount updates you could store in a group. How do you deal with the managment of updates groups....i.e. dropping the expired updates form the group? I think the site would benefit as a whole with a recommended procedures guide for this. In your
  5. Fair point peter. I am a bit of a noob with SCCM. THe last time I used this tool was SMS so a lot has changed for me. I will do my research on Settings Management as it sounds like a powerful tool. Could you post an example of the script you are using to deploy your MSP's and take me through the workflow? For Example: Day 1 Adobe Releases Reader X 10.1.0 - You deliver the simple MSI to a target machine/user Collection Day 45 Adobe Release Reader X 10.1.1 - How do you deliver the MSP to your existing Collection. Day 90 Adobe releases Reader X 10.1.2 - How do you deliver the MSP t
  6. @ Peter 33 No sure I understand what "Setting Management" is? Is that something in SCUP? My plans is to do the following: Assume 10.0.1 is already packaged because no MSP is needed. We can talk about transforms if you like but that is a separate issue. 1. msiexec /a "PATHTO\AdbeRdr1010_en_US.msi" 2. Go through the prompts and put the files in a Network Location 3. msiexec /a "NetworkPATHTO\AdbeRdr1010_en_US.msi" /p "PATHTO\AdbeRdrUpd10.11.msp 4. Create A new package called Adobe Acrobat 10.1.2 and point to the Network MSI. You will notice that the MSI is now expanded and shoul
  7. So I have official given up on trying to patch the MSI and am using the AIP/Slipstream method. My only concern is that my CCMCACHE will get significantly bigger over time.
  8. So you guys recommend either using 1. SCUP for Adobe updates or 2. using AIP and deploying a new slipstreamed MSI with the patches that supersceedes the fist package. You couldn't just use a new package that superscedes the main package with a command like this: msiexec /i "AdbeRdr1010_en_US.msi" patch="\\sccm1\SCCM Sources\Acrobat Reader 10x\AdbeRdrUpd1012.msp" /q I've tried but have run into some issues getting it to deploy.
  • Create New...