jonasthehobbit Posted February 6, 2013 Report post Posted February 6, 2013 Ok so i am a total noob as it were to SCCM! I am slowly but surely getting to grips with the produce but one thing i am struggling with is applications that are not MSI installs. Specifically dependencies... i have .net 4.0 and Windows Management Framework 3.0 that i want installing within my OS Deployment TS, i have created the OS deployment (works) and am now in the process of creating the applications to install. i have managed to create a dependency for .net 4.0 (regkey) but am struggling to create one for WMF3.0 (which is an MSU file). further to this i want to know how you would go about packaging other applications that are not MSI files and how you would figure out a dependency for the installation, at the moment i am painstakingly installing the app on a test server and monitoring the process (process monitor) looking for a regkey created that i can use as a dependency. Surely there's a better way? Thanks in advance. J Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted February 6, 2013 Report post Posted February 6, 2013 i have managed to create a dependency for .net 4.0 (regkey) but am struggling to create one for WMF3.0 (which is an MSU file). Is it that you think you need to create a dependency in order to create an application?? Applications do not need you to create a dependency, the option is optional so to speak. Also I see you are trying deploy WMF3.0 as part of your OSD?? Is this not the update that breaks SCCM management point and windows7 client communication!! It was released approx a couple of months ago and wreaked havoc on many SCCM infrastructures! http://myitforum.com/myitforumwp/2012/12/15/wmf3-0-hits-microsft-update-catalog-possible-issues-with-configmgr-2012/ Pay particular attention to the last paragraph! Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted February 6, 2013 Report post Posted February 6, 2013 First create a new global condition to query the updates through WMI The KB Names without the leading "-" of course As requirement chose the custom type and the new global condition. That's it Edit: It's good enough to set the rule type to existential. No reason for double definition Quote Share this post Link to post Share on other sites More sharing options...