Since the upgrade to 2012 R2 SP1 I've noticed a change in the dependencies, is our way of thinking wrong or is something wrong in the ConfigMgr engine? Pre R2 SP1 we've never had issues with this...
E.g. an Adobe Flash application with two deployment types: Plugin+ActiveX:
- Plugin - needed on all OS versions - no requirements - dependency on Deployment Type ActiveX with AutoInstall Enabled.
- ActiveX - not on Win 8/8.1/2012/2012R2 - requirements (none of 8/8.1/2012/2012R2)
On older OS versions, where both Deployment Types are needed there are no problems.
On Windows 8/8.1/2012/2012R2 the application isn't shown in the Software Center because AppIntentEval.log states the application isn't applicable because the requirements for the second deployment type aren't met.
In the past, when a requirement was not met on a dependent deployment type, the dependency was met...
Any advice? Thoughts?