HELP Setting up the software portal - Software component or Managed Soft.Delivery
I am currently working on setting up our software portal. After reading several articles, I learnt that i could publish software on the portal by using the 1) software component 2) Managed Soft. Delivery
1. Software component.
I tested this out and seems to work fine (as I already have my packages and tasks setup). My main concern with this option is that if I have a software component containing several packages (eg. prerequisite package - its own cmd line, main-install Package-own cmd line, tutorial package-own cmd line), then the user has to "know" to install the prereq before the main install file.
2. Managed Software Delivery
In a software delivery policy, I have my scheule and computer targets (with filters) all setup. But when actvating this policy for the portal, I have to set the users/groups that will have access to this software. Would users/groups set in the "Software Publishing" tab overwrite the computer targets? meaning if UserA has access to the software but login to a computer that is not included in the computer target, that user can have the software installed anyway on that non-targetted computer? The first application that I am trying to publish to the portal is Office 2010 (we are planning a migration from Office 2007 to 2010). By deliverying the software as a policy, if the computer has office 2010 unininstalled, would it be "forced" to have Office 2010 reinstalled (as this is a policy and it will check for computers that are not compliant?
My only reason (for now) to use the managed soft. delivery option is that only the Software name gets published to the user, and the user would not see the 3 or more tasks running at the background to install the software.
Which option do you use and what are your experienses?
Thank you all in advance