Software Virtualization Solution in the Notification Server Infrastructure uses the basic NS Software Delivery mechanisms. Software Delivery Solution extends this basic functionality with both Sequential Tasks, the Software Portal (already integrated with SVS), including additional options for Packages, Programs, and Tasks. How can these features be used to manage VSPs in a Software Virtualized environment? This article discusses the standard program/task options including how to integrate SVS into the Solution.

Introduction

Learn how to use SVS with the extended functionality of Software Delivery Solution. Feature sets include Sequential Tasks (running multiple action commands against one or more VSA in a designated sequence), Running actions against multiple users who log onto a single system, and other items to extend the management functionality of delivering, maintaining, and running actions against SVS layers and VSPs. This requires the know-how on how SVS works so that the same required objects can be applied to a standard Software Delivery Task. This article will discuss the integration and standard Task extensions.

Versioning: Notification Server 6.0 SP3 -- Software Delivery Solution 6.1 -- SVS Solution 2.1

Integration

The first and most important part of using the SVS components within the greater Software Delivery Solution is to understand what items are required to turn a Software Delivery Solution Package into a VSP, a standard SWD Program into an SVS action, and how to utilize the SWD Task.

Primary Integration Steps

The following process details how to integrate. Standard options will not be covered (such as Name, Publisher fields, etc) but the focus will be on those steps that will tie the VSA to the Software Delivery Package:

1. Go to View > Solutions > Software Delivery > Packages > right-click on Windows and choose New > Software Delivery Package.
2. Choose the appropriate Package Source on what method you will be pointing to the VSA file (via the folder).
3. Browse to the folder the VSA file resides in. This will be the package that contains the required file. This has been covered in previous articles in this series but is important to know. In SVS it appears you are selecting a single file when creating an SVS package, but in reality you are choosing the folder the VSA resides in. In Software Delivery this is correctly displayed as a folder selection.
4. Obtain the Guid of the VSA. This is done using the standard Software Virtualization Solution in Notification Server with the following process:
   1. Create or use an existing SVS package.
   2. Browse to the VSA to be used in the Software Delivery mechanism.
   3. Once selected, click on the Programs tab.
   4. The Guid will be automatically located in the command-line field. Copy this Guid out. Cancel the edit to the package unless otherwise desired.
      
      

      Click to view.

5. Click the Programs tab.
6. Click the 'New' button to the right of the Program dropdown.
7. Input the command-line for the actions you wish to take against the VSA (Import, Activate, etc). Use the Guid obtained in step #4.
8. For Import commands, the Guid of the SWD Package must be obtained to be used in the PATH reference. You may need to save the package before finishing the command-line so you can right-click on the package reference and choose 'Properties', and obtain the Package Guid from the properties page.
9. In the 'Working directory:' field, input 'C:\Program Files\Altiris\Software Virtualization Agent\' (without the single quotes). Note to take into account if you have changed the default install of the Altiris Agent and the Software Virtualization Agent. The default path is shown in this example.
10. Repeat steps 5 through 8 to include those executions you wish available for the VSA file to be delivered. To see a list of the default command lines, look at an SVS package from the SVS Solution in NS, under the Programs tab. The drop down provides actions, and when selected will provide the command-line. Note that the GUID in the command-line is tied to the VSP being delivered.
11. Change the 'Run with rights:' section to System Account.
12. Click 'Apply', followed by 'Update Distribution Points'. The Package and Programs have now been defined.

Integration Points

This package is now available to be used by any of the following mechanisms:

• Software Delivery Standard Task -- This does include additional functionality not available in the Software Virtualization Solution for Notification Server
• Software Delivery Sequential Task -- Sequencing allows you to sequentially tie Programs together, whether from the same VSP or multiple. This is especially useful for large rollouts of Virtual Software.
• Software Portal -- SVS provides Software Portal Functionality, but through Software Delivery Sequential Tasks can also be accessed in conjunction with SVS.

Software Delivery Functionality

Software Delivery Solution Programs and Tasks provide a few functionality expansions not available to the Notification Server core Software Delivery Mechanisms. By using the above Integration process, these items are now available to be used in conjunction with Virtual Software.

Software Delivery Programs

If you compare the Programs tab from an SVS Program and a Software Delivery Program you will note that they are not the same. Many of the functions are available on both, but Software Delivery Solutions provides the following additions:

• Working Directory
• Success and Failure Codes
• User Input Required checkbox
• Run once for options
• Connection parameters

The following screenshot shows the extent of the Programs tab under a Software Delivery Package:

Click to view.

Working Directory

This option allows the execution point to change. While generally the location of the Software Virtualization Agent should be used, this can be modified if the location may be different based on a stand-alone Agent install.

Success and failure codes

Do you have a different success code than 0? With Software Delivery Solution you can add additional return codes to the success list. Despite what the UI suggests, it's only necessary to put those codes that you consider a success. Failure codes will already include anything that's not defined in the 'Success codes'.

User Input Required checkbox

This checkbox is usually used for piping an execution to a user's desktop, however the background functionality not only loads the currently logged on user's desktop, but also loads a fuller user stack for the execution. For applications that are user-based this can be essential for proper execution.

Run Once for options

There are two options available in the 'Run once for' function:

1. Each logged on user -- If a specific application requires activation per user, or a maintenance action is required for every user on the system, this option can be used.
2. Specific users or groups -- For targeted rollouts this option can be handy. Instead of targeting specific systems, use an inclusive collection and target specific OU groups or users.

Connection parameters

The option can be checked 'This program requires a network connection', with a minimum connection speed set. This can be used when the VSP is located remotely, or if the action may require a network resource.

Software Delivery Standard Task

Software Delivery Tasks provide additional options on the standard Notification Server Task. The following items are available for Software Delivery Solution standard tasks above what's available in SVS:

• General tab
  • Priority -- This can help raise or lower the priority of the VSA action for the task. For critical tasks that require the action to be moved to the front of the execution queue on the Altiris Agent (this includes all other tasks from any Solution) the priority can be raised to high or very high.
• Advanced
  • Run from the server if bandwidth is above -- This option allows the execution of the VSP to be done remotely from a server (Notification Server or designated Package Server). The subsequent dropdown provides different bandwidth options.

Package Option

There is one more option available in Software Delivery Solution under the Package tab of a Package. Under the Package tab there are options for Installers found, but this functionality is not generally useful for SVS deployment and administration. However the option 'Package files will be deleted from the client computer if usused for:' can be used to manage VSPs left in the cache folder on the client system. Normally it's recommended to leave the VSA in place so that all tasks can be run against it as necessary, but in cases where space may be an issue, this option can be used to remove the package after a given time once the tasks have all been disabled (an enabled task will leave the package alone).

Conclusion

Sequential Tasks will not be covered in this article as another article will be dedicated to that subject. Keep in mind when using Software Delivery Solution with the above described extended options that results may not be as expected. It is highly recommended to test any rollout before making the changes in a production environment. Testing was completed on all primary functions, but these were not tested in the Altiris labs. As such these are provided as suggestions and do not contain support from Altiris, neither guarantees nor warranties, whether stated or implied, verbally or otherwise. Happy customizing!

In the future the SVS component in Notification Server will fully integrate into Software Management Framework. This means all options will be available without the integration steps outlined in this article. This will occur when the 7.0 versions of NS, SVS, and Software Delivery are released.