pxedave Posted February 21, 2012 Report post Posted February 21, 2012 NOTE: Since creating this post I've learned that you can define .CMD and .EXE installations as Applications (as well as MSI and App-V) by choosing the Manual option on the first screen of the Application creation wizzard. I don't see any reason why anyone would define anything new as a Package anymore; I see Packages as being a legacy thing for those importing data from an existing SCCM 2007 setup. Starter for ten: Like Applications, Packages can be deployed as Available or Required. Like Applications, packages deployed as Required show up in the Software Centre. With Applications, as well as specifying which OS it CAN installed on (i.e. whitelist) you can also specifiy which OS it CAN NOT install on (i.e. blacklist). With Packages you can only specify which OS it CAN install on. UDA and OS deployment does not work with Packages; Packages being deployed (Required) to User Collections do not get installed until after the user logs on for the first time whereas Applications get installed ahead of the user logging on. Quote Share this post Link to post Share on other sites More sharing options...
pxedave Posted February 22, 2012 Report post Posted February 22, 2012 Like Applications, Package that have been made Available (as opposed to Required) are also displayed in the Application Catalog. Quote Share this post Link to post Share on other sites More sharing options...
ashridge uk Posted February 29, 2012 Report post Posted February 29, 2012 Hi, new to all this SCCM stuff, guides have been excellent and we're cooking on gas so far ;-) but I cannot get any of my applications to "require administrator approval if users request this application" it's always greyed out ??? Quote Share this post Link to post Share on other sites More sharing options...
