Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Allow editing of default "Quick Delivery" task settings

Created: 11 Feb 2010 • Updated: 01 Nov 2010 | 17 comments
JeffDG's picture
9 Agree
0 Disagree
+9 9 Votes
Login to vote

Of course you can modify these when necessary, but it would be nice to be able to set the defaults for your 80% solution...

See
https://www-secure.symantec.com/connect/forums/def...
 

Comments 17 CommentsJump to latest comment

noodleNT's picture

Quick Delivery Tasks that get created from the Software Portal in my environment can time out from time to time because a remote client will take a long time to download the software.

0
Login to vote
Kada's picture

Motivation: we will use SW portal and publish them SW Release with comand line. As installation tool we are using vbs script and we really need to run in hidden mode. It is not possible to setup for SW portal task. Or am  i wrong?

0
Login to vote
Andrew_Shishkov's picture

Hi,

How you launch the vbs script and what is included to it?

If you will launch it using cscript.exe /nologo <path to vbs script> command and include silent installation command lines to it, then installation should run silently if corresponding software  is requested from SW Portal.

Thanks,

Andrew.

0
Login to vote
Kada's picture

Andrew,

vbs script is reading the ini file where it is defined how to install SW. So vbs script calls msiexec or other tool for installation SW.

cscript /nologo did not work. I can still see the window.

 

 

0
Login to vote
Andrew_Shishkov's picture

Hi,

>>cscript /nologo did not work. I can still see the window.

What window do you see? Can you attach a screenshot of the window?

 

Thanks,

Andrew.

 

0
Login to vote
Kada's picture

Screen attached. You can see that PKGcontrol is installatin the SW in silent mode but still can see the vbscript window.

Second window is about some action with McAfee - part of the installation example

Cscript_nologo.png Cscript_nologo_1.png
0
Login to vote
Andrew_Shishkov's picture

Hi,

Sorry for delay. It seems like these windows are not caused by launching "cscript.exe /nologo", but related to commands launched by VBS script. Can you give an example of script for which you see these windows appearing?

 

Thanks,

Andrew. 

0
Login to vote
Kada's picture

Hi Andrew,

in attachment you can try this test script. Command line is cscript /nologo c:\temp\testscript.vbs

When I request it from SW portal it will open CMD window and wait for 20 seconds.

Let me please know if you are able to see the CMD window too.

Thank you

 

 

AttachmentSize
TestScript.txt 3.63 KB
0
Login to vote
Juri Tsjornoi's picture

I was able to reproduce the problem with CMD window appearing when requesting a script from the Software Portal executed via cscript command.

But if using command WSCRIPT.EXE <path to vbs script>, then no UI is shown when executing such command requested via the Software Portal. I have checked this with your sample script. So, please, try using WSCRIPT.EXE command to execute your script.

0
Login to vote
Kada's picture

For this simple script WSCRIPT is solution but we have more complex installation framework where more scripts are used. We tried to use WSCRIPT //B and still there can be some pop up windows showed for some time.

0
Login to vote
Juri Tsjornoi's picture

I guess that in more complex scripts pop up windows showed for some time are the cause of launching another processes inside that script. If the main script is executed without showing any UI, but later some pop up windows are still appearing during a script execution, then you should search your script for launching processes inside it, and try to launch those processes silently.

0
Login to vote
Kada's picture

We have more than 1500 Software so it is not easy to review installation process and modify it in short period. So for this time it is big issue for migration from 6.x to 7.1.

May we have status of this idea? Will Symantec offer possiblitity to edit default Quick delivery task settings? If yes, when?

Thank you for info.

0
Login to vote
Juri Tsjornoi's picture

Can you tell me, please, how have you configured your scripts on NS6 environment so that no UI was shown while executing those scripts after requesting them via the Software Portal? Have you set Software Delivery Package program property 'Starting window' to Hidden like it's shown on the attached screenshot 'ResourceMgr_NS6'?

If yes, then I can recommend you to use Managed Delivery policies available on ITMS 7 environment to install software on client machines. Managed Delivery policies can be also published to the Software Portal, and you can set an advanced option 'Display window' to Hidden for a delivery item added in the policy (please, see attached screenshot 'ManagedDelivery_ITMS7').

Also you can configure Managed Delivery global settings on Managed Delivery Settings page (please, see attached screenshot 'ManagedDeliverySettings'), so that all newly created policies will be automatically created with pre-defined settings. So if you need to edit default settings for your delivery before actually creating a software delivery, then we recommend to use Managed Delivery policies to rollout software.

ResourceMgr_NS6.PNG ManagedDelivery_ITMS7.png ManagedDeliverySettings.png
0
Login to vote
Kada's picture

Yes, in 6.x it is defined on the package level that Window is hidden.

Ok, we know then we can use MSD, but we decided to use SW resource publishing because when you compare showed date for MSD and SW res task on the SW portal there you can see in MSD there is showed date in past and for SW res there is defined current date/time plus 2 minutes or user can deffer. So from end user point of view MSD date is confusing about time when SW will be installed.

The other reason is when MSD is published, it will add into policy for SMA and end user can trigger this installation only in SMA, not again in SW portal because the policy is already there. SMA for end user is not visible so there is not option how to trigger SW installation again. For SW res end user can request again from SW portal and task will be trigger.

 

 

0
Login to vote
Juri Tsjornoi's picture

Actually requested Managed Delivery policy will still be automatically delivered to a machine from where it has been requested in no later than 5 minutes.

And also you can configure Managed Delivery policies in the way that end users won't be able to trigger them, so to not allow a user to turn on policy from the Symantec Management Agent. Please, see attached screenshot 'UserInteraction'

UserInteraction.png
0
Login to vote
Kada's picture

I tried to unmark user interaction but still policy is visible in the agent. And I did request the MSD again and again but SMA did not recognize, that new policy/task is requested on the SW portal. So there is not possible to request install action again.

I missed mentioned another reason why we don´t want to publish MSD. When MSD is changed, all PC having this policy requested from SW portal are affected and policy is triggered again. This action is not wanted and it is wanted only for PC who request it in the future.

 

0
Login to vote
Kada's picture

We discovered another unwanted behaviour. When the SW portal task is running and the user do logoff the installation is interrupted and will fail. It seems that default setting for Quick delivery task is "Allow user to interact with installing software" and Display window is "Normal".

We should not have "Allow user to interact with installing software" setup and then user can logoff and installation should continue.

I know that in MSD it is possible to setup like this but we can't use it because of the reasons mentioned above

0
Login to vote