Jump to content

Search the Community

Showing results for tags 'Assets and Compliance'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Found 1 result

  1. 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
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.