Video Screencast Help

HELP Setting up the software portal - Software component or Managed Soft.Delivery

Created: 17 Aug 2013 | 7 comments

Hello everyone

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

Operating Systems:

Comments 7 CommentsJump to latest comment

Dmitri Dragunov's picture


Publishing of the Software Resource is designed for fast simple deliveries, without any dependencies. If you whant to setup any dependencies you should use Managed Delivery Policy.

Publishing for users is designed to add ability to some user to install the software on all computers he have access to. Publishing to user is not depend on Managed Delivery Policy computer target and user may push software to any computer where software portal installed.
To push the installation of the Office 2010 I recomend you to use Managed Delivery Policy with reoccurring schedule and some specific target (not only publishing). Installing of the Software from the portal it's the run once operation. And of cause if you have proper detection check it will detect that some software is uninstalled and policy will install it again, but this will happed only once after request.



efyuze's picture

Hello Dmitri,

thank you for your reply.

Actually our main reason for using the  Software Portal was to give users the opportunity to migrate their version of Office suite at their own time instead of forcing the installation on everyone (Managed Software Delivery) 

So with the explaination that you gave, I think we could go the Software Component way. I will set up Office2010 to automatically uninstall Office2007 (via .msp file). I would also need to install Visio2010 + Project2010, so in total 3 command lines to publish on the portal.


etk1131's picture

You can still use a Managed Software Delivery and still allow your users to do the upgrade on their own time.

To accomplish this, set up your Managed Software Delivery, and in the Schedule section, under User Interaction, check the "User must turn on from the Symantec Management Agent" box, which will just put the policy on the end-user systems, and will allow them to upgrade at their convenience.

And it gives the added bonus of eventually forcing the upgrade should they not comply within a reasonable amount of time. :)

efyuze's picture

Hello etk1131

thank you for your reply. So If checked the option "User mucst turn on Symantec Agent" tested it and it worked fine !! thanks. But as for the compliance section, I should not set a schedule? right?

thanks again

efyuze's picture

hi again etk1131

think i was too fast to reply, I couldnt save, the compliance schedule is required. so I think  I could set it to a far date in the future

etk1131's picture

If you set your remediation to Immediately, you shouldn't need a schedule.

I attached a screenshot of my Office 2010 Managed Software Delivery schedule.