Jump to content


Sign in to follow this  
pxedave

Applications vs Packages - interesting observations so far

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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 ???

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...