Jump to content

Search the Community

Showing results for tags 'Dependancies'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • 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
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • 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. Hi folks, Here's another one that got us today that's worth keeping in mind. If you have an Application which has, let's say, two Deployment Types, the first (priority 1) is configured to auto-install the second (as specified in the Dependancies tab). If you then make this application Available (i.e. not even Required) to a device, as expected it will appear as Available within Software Centre and do nothing until you hit Install... UNLESS the machine happens to meet the requirements of the Detection Method of the first Deployment Type in which case it will AUTOMATICALLY INSTALL THE SECOND DEPLOYMENT TYPE WITHOUT WARNING :angry: This will happend regardless of whether the application is deployed via Task Sequence or on its own. If you're in the habit of using Available deployments as we are, best make sure your Detection Methods in all Deployment Types are unique. I'd say this is similar to the issue that bit us earlier around supercedence causing Available applications to auto-uninstall superceded packages without warning ( http://www.windows-noob.com/forums/index.php?/topic/8952-possible-bug-in-sp1-cu1-client-applications-that-supersede-others-may-rollout-unexpectedly/?p=33797 ), both of which I'd call a bug rather than a feature.
  • Create New...