Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About legion99

  • Rank
  1. Branchecache does not work for updates on the version of SCCM that I have stated we have, like I said we haven't updated yet. Also as I have stated I am not looking for a recommendation on what you think we need to do in our environment. You don't know our environment or why we have things setup the way we do. And our environment has been in place for 2 years we're not changing it. Again the question is about the risks involved in using ADR's please only answer the question asked.
  2. The original question was about risk. What risk is there is using ADR? It makes sense to us to use ADR to deploy updates at night when it won't affect users bandwidth, not sure why that doesn't make sense to you but that's not the question. As I said we don't have BIT's throttling, if it were up to me we would but we don't. We only have one DP, again not my decision. I'm trying to work with what we have.
  3. We do have them split into SU Groups. We do deploy to a pilot group and test, using ADRS would only involve one additional step which would be after the updates are piloted and working highlight them all and set the Custom severity, it's 4 clicks extra which is obviously not a lot of extra work. And we would have the ADRs deploying to different areas at different times as I have already explained. So we already have it planned exactly as you suggest. The difference is we would be using ADR's which would mean we can deploy to slow network sites in the middle of the night after hours ins
  4. Sorry but no it doesn't contradict anything if you use ADR's a certain way. You don't have to let ADR have complete control of deployments. The rule would be based on Custom Severity which by default is none. After we properly test the update we would set the severity so it's included in the rule, until you manually set the severity it won't be deployed so testing is not an issue. It's not complicated and not risky. We would still be testing and deploying in a staggered fashion as I already described. Again this is not difficult with ADR, you can have more than one rule and more tha
  5. What risk are you referring to? That's what I'm trying to understand. We test and pilot our updates before we approve them for ADR and we spread out our updates over a two week period in an environment of 8000 machines so we can stop the scheduling any time there are issues. And we wait a month after "Patch Tuesday" before testing patches in case there are revisions.
  6. But as a consultant have you seen ADR cause issues with the two concerns I mentioned? That is the question. Obviously we have a valid reason for using ADR and are going to document a plan.
  7. We are in an SCCM 2012 Windows 7 environment and would like to use Automatic Deployment Rules to deploy updates. I have worked out a strategy of using the Custom Severity to allow us to manually choose which updates we want to apply as well as creating multiple rules for multiple locations to spread out the distribution throughout our environment. They have been tested and work correctly. However our SCCM co-administrator is demonstrating what is in my opinion an extreme over abundance of caution regarding these rules and does not want them applied in our environment. The two concern
  • Create New...