Search the Community

Hello all, I've successfully gotten 3rd party software updates working with ADR's, however, I was wondering if there way to remove Adobe Acrobat / Reader 3rd party updates that I no longer need published? If there is a way great, if not is there a way to not have to continually adjust my ADR as new versions of software come out? Example: My ADR for Flash and Acrobat, I'm using title filters to only include the latest version.

I recently went through the trouble of configuring the use of Windows 10 Servicing Plans only to discover that they are close to redundant. Servicing Plans (SP) are literally Automatic Deployment Rules (ADR) which has some different options. You could achieve something almost identical using ADRs only. I discovered this because I had started testing my deployments of SPs and all was going well, then I noticed that Feature Updates were also being added to my ADRs for Windows 10. This is where I discovered SPs are ADRs with extra bits. My understanding is that SPs were going to be put in place for ease of upgrade to new versions of Windows 10 and to make it as easy as possible for SCCM admins. This has been a catastrophic failure due to the huge bugs in each release of Windows 10, even once they are classed as "business ready." The most recent one is a problem with certificates. Is anyone using Servicing Plans as they were originally intended, that is completely automating it? Are you finding it is more trouble than it is worth?

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 concerns expressed are: -When we do the sync with Microsoft something will go wrong and the wrong updates will be applied to the wrong computers (I can't possibly see this happening) -There will be issues when we eventually upgrade to R2. (I have not been able to find any evidence that this would happen) Has anyone experienced issues with ADR bad enough to not use it? Can someone help me assure my co-administrator and manager that this level of caution is not necessary?

This is actually pertaining to SCCM 2012 R2 but I'm sure this would apply to SCCM 2012 as well. I'm trying to determine how SCCM handles scenarios where you have two or more software update deployments, and each deployment is configured to deploy to a different collection, and one or more clients are members of each of those collections. Is this a valid scenario or can you only have multiple software deployments going to collections with unique memberships i.e. a client is a member of only one of those targeted collections. The reason I ask this is because it seems that only one software update deployment is going to the first collection that this client is a member of and any other deployments are being ignored or not being processed for this client. To further clarify, this is a Win81 client which is a member of a Win8x Managed Systems collection. I configured a "Deploy Win8x Updates" deployment to the "Win8x Managed Systems" collection and the associated Win81 updates will show up in Software Center on the client system. Now, I also configured a "Deploy Office 2013 Updates" deployment to the "All Managed Client Systems" collection which this Win81 client system is also a member of. This collection contains all the managed systems in our infrastructure and the client OSes are Win7, Win8, and Win81. The Office 2013 deployment deploys to this larger collection (25 systems right now) because the client OS is not a concern but the version of MS Office running on these clients is. I configured the available time for both of these deployments to be "as soon as possible" but I staggered the deadlines by six hours since I wanted both deployments to do a forced install after the deadline which was over the past weekend. The goal here is to have all these updates apply themselves automatically to unattended systems. The problem is that only the applicable Windows 8.1 updates show up in Software Center but the Office 2013 updates do not and I know these Office updates are needed on this Win81 client system. Also, do Software Update Groups with superceded (black X icon ) or invalid (red X icon) updates in them affect the software deployment? Will the deployment not work when the update groups are in this state? Thank you in advance for your help on this! RA

Hello, The guy the use to do the server updates retired and my boss would like to utilize SCCM 2012 to do the updates. They are currently getting there updates from WSUS and group policy. He has specific policies setup to restart specific servers at certain times of the day according to what works for the users. I'm thinking the best way of doing this with SCCM would be to create a software update group that contains those servers he had in the policy which can get restarted on the same day or at the same time. My question is that these servers are Server 2003, Server 2008 and Server 2012 systems. Can I have one group that contains three different Operating Systems and apply all security and critical updates to these servers or should each group only contain one specific Operating System? Any help on the best way to setup these groups and deploy windows updates to them would be greatly appreciated. How does your organization go about deploying Windows Updates to your servers\desktops? Thanks Pat

Hello All, I got a quick question on the behaviour of Software Update Groups. By folloiwing the Part 6. Deploying Endpoint Protection Role... I have created the following: 1. The servershare for SCEP updates - \\servername\source\windowsupdates\EndpointProtection 2. An ADR Template which created the new package and put it in above unc path (not enabled) 3. Several ADR's for below items with the setting "Add to existing Software Update Group" - Managed Clients - Managed DHCP - Managed DNS - Managed ADDS - And so on. Now when I look in the Software Update Groups on the ones that now have been created, they all have a Total Asset Count of all the clients running SCEP where the ADR's have been deployd. I.e. 400 clients, 35 servers (with different roles) So when the ADR ADR - SCEP - Managed Servers - DHCP is highlighted and I check the Summary of it it shows a total asset count of 435, while there are only 2 DHCP servers in the environment and I have targeted the ADR towards the DHCP Device Collection. Is this per design or have I missed something really basic? SCCM 2012 is running SP1 CU2. If there are any withstanding questions on this, don't hesitate to reply!

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 don't set that time frame it will create a new group each month with all the current updates and over time that will put me over the 1000 update mark esplecially if I incorprate SCUP. What should i do to set that first deployment or how should i setup my property filters? Any thoughts?