How Can a VSA File be Delivered via Task Server?

Software Delivery packages can be delivered via Task Server, however, as SVS packages are not displayed in the Deliver Software Package Selector, how can they be delivered through Task Server?

System used for this article ran the following products:

• NS 6.0 SP3 R8
• Task Server 6.0 SP1 plus its Task Management Pack
• SWD 6.1 SP3
• SVS Solution 2.1.2095

Introduction

The only Task Server task that is available for SVS is the SVS Command Task, which doesn't provide a Deliver SVS Package option:

Click to view.

SVS Solution allows you to create SVS packages:

Click to view.

However, these SVS packages are not available in the SWD Task package selector (which is why the Deliver Software task cannot see them), but they can have a Virtual Software Task created for them via SVS Solution, and they can also be deployed via the SWD Portal:

Click to view.

Click to view.

Click to view.

Click to view.

So how can a VRA/VSA be deployed via Task Server?

This can be accomplished by first creating a Software Delivery package and not a SVS Package, and then creating a Job that contains a Delivery Software Task as well as a Script Task.

Prerequisites: NSAgent, Client Task Agent, Script Task Agent, and Software Delivery Agent for Task Server.

1. Create a SWD package that contains the VSA and then uses a similar command line in its Program:
   

   SVSCMD.exe I -P "C:\Program Files\Altiris\Altiris Agent\SWDAgentForTS\{FC2BC984-DAB1-48B8-9CEF-A7307493D6DC}\cache\IESpell 2.5.1 Build 106.vsa" -F 
   
   

   Note: As you can see, the command line will import the VSA file that gets delivered to the SWDAgentForTS package directory. The [I]mport command expects a VRA or VSA file, so the layers Guid cannot be used during an import.
2. Create a Job that contains a Deliver Software Task which uses this SWD package and program.
3. Add a Command Script Task that runs a command line that will manage the imported layer (this example shows how to activate the layer as well as set it to activate on startup):
   

   SVSCMD.exe "IESpell 2.5.1 Build 106" A AUTO -Y 
   
   

   Note: The reason why you cannot add any managing commands to an import syntax, is because SVSCMD tries to run them before the import has finished, which causes it to not find the layer. Either the layers name or Guid can be used at this stage.