Soon Software Delivery Solution will become a component of the Software Management Framework. Like any major version change, things do not look as they did previously. Things may not work the same under the hood, but the same basic features are available, plus a whole lot more. In this first part I'll show how the previous paradigm fits into the new version for Software Delivery Solution.

Introduction

Out with the old, in with the new, right? Well... that's a great slogan or cliché, but people resist change and are comfortable with what they are familiar with. In version 7 of the Altiris software suite, things have changed, in some cases dramatically. This article covers how the existing functionality of Software Delivery Solution in the 6.x versions now fit inside of the Software Management Framework. Subsequent articles will cover additional functionality provided by this new framework.

Software Packages

Previously, Package objects contained simple package details and any Programs created to run against the Package. In version 7 Packages no longer are simply repositories for a group of files. A lot of functionality and versatility exists in a Software Package, now called Software Release.

Creating a Package

To create a Software Release (required to create a package), please follow these directions:

1. In the Symantec Management Console browse under Manage > select Software > browse down through Software Catalog > Deliverable Software > and select Releases.
2. A list of existing Software Releases will appear in the right-hand pane. Click Add > and select Software Release.
3. The resulting window provides the configuration interface for the release. In this example we will leave it simple to correlate to the old Software Delivery model.
4. Give the Release a name, IE: Symantec, and a description if so desired.
5. Under the Package tab you'll see two sections, Package and Command Lines. This represents, respectively, the Package and Program tab within the 6.x architecture. Click the button "Add Package". See this screenshot for an example:
   

   Click to view.

6. Provide a name for the Package. For this example we'll use a local directory on the Notification Server, as shown in the above screenshot.
7. Supply a path to the package, IE: Click browse, browse to C:\Test Package.
8. Click OK to save the Package. Note that you can create multiple packages within a Software Release. Unlike 6.x, where only a package can have multiple command lines, now the packages are all available when configuring a command line.

The rest of the tabs, etc, do not necessarily need to be used for a rollout mirroring the 6.x architecture. As you may have surmised by the user interface, there is a lot more to a Software Release than a standard Package and Program.

Creating a Program

I used the 6.x terminology, but essentially the Program is the Command Lines configured for a Software Release. Use the following steps to create a Command Line for your Software Release:

1. Back at the Package tab within a Software Release, click the button "Add command".
2. Configure the Command line by giving it a Name and description, as shown in this screenshot:
   

   Click to view.

3. If you happen to not have files in this Software Release (if the files already exist on the target computers) you can uncheck the option 'Command line requires a package'. Note that you will have all available Packages within the Software Release to associate to.
4. The installation file type is important because it changes the nature of how the command-line will execute! Please choose the appropriate option (usually an MSI or EXE).
5. Command type is used as a categorization tool within the Software Management Framework. Choose the appropriate option for what the command-line accomplishes.
6. Set the command-line to be used. This command line mirrors the command line field in the 6.x versions of Software Delivery. Also note that an edit button is available. This button will populate a window based off of the Installation file type selected. If you select MSI you will have many options to help you build the command-line.
7. Provide any exit codes you wish to the three codes fields.
8. Click OK to save the Command Line. Note that unlike a Program in the 6.x versions of Software Delivery the execution environment is not configured in this section of the Software Release.
9. Make sure to click Save Changes to save all the work configuring this Software Release.

Software Tasks

If you're looking for a Task that most resembles the 6.x architecture, the Package Delivery Task is it. Follow these steps to setup a Software Delivery Task:

1. In the Symantec Management Console, browse under Manage > select Jobs and Tasks > browse under Jobs and Tasks > System Jobs and Tasks > Software > Package Delivery.
2. Right-click on the Package Delivery folder and choose New > Job or Task.
3. In the resulting tree, within the left-hand pane, browse down to Software > and select Package Delivery.
4. In the left-hand pane you'll see the Package Settings which allow you to select and Package and a correlating Command Line. Use the dropdown or search by typing the Package name into the Package field.
5. Once chosen, use the Command line dropdown to select the appropriate command line.
6. For more options, click the Advanced button. The resulting window provides more options, as shown in this screenshot:
   

   Click to view.

7. Note that the execution environment is contained within this Task.
8. Provide the appropriate authentication method. Note that you can now choose the Altiris Agent credentials, which is typically the Local System account.
9. The run options mirror those contained under the Advanced tab of a 6.x Software Delivery Task.
10. Under other you can set how the execution will appear. Note that this isn't useful if the 'Allow user interaction' box is not checked.
11. Click OK to save the settings, and then OK to have the Task created.
12. Now to schedule or run the Task, use the standard Task Server interface.

Sequential Software Tasks

Sequential Tasks no longer exist as they did in Notification Server 6.0, Software Delivery 6.1. If you're familiar with Task Server for 6.0 you'll be familiar with how a Job operates in Notification Server 7. This allows a much greater flexibility in what you can include in a sequenced job.

The following items expand the Sequential Task functionality into a Job:

• Include other Solution Tasks, such as Patch, Inventory, RTSM, etc
• Greater flexibility on post-execution action using Task Server conditions
• Use all the core function of Task Server, including power control and script execution

To configure a Job with a Software Delivery Task, follow these steps;

1. In the Symantec Management Console browse under Manage > Jobs > in the resulting right-hand tree browse through System Jobs and Tasks > Software. Where you put the Job is up to you. Simply browse down or create a folder, and continue.
2. Right-click on the desired folder and choose New > Job or Task.
3. In the resulting window, select 'Server Job' (Server jobs include all server and client functionality. If you know you'll only be selecting client functionality, you can alternately select Client Job. The definition of a Server Task is one that is executed from the Server, such as vPro actions, while a Client Task requires the use of the Altiris Agent and in cases a plug-in as well).
4. See the following screenshot for an example of a Job:
   

   Click to view.

5. You can click New > Task or Condition, or click Add Existing to create what occurs in the job. When you choose to execute a Package Delivery task you'll recognize the options as the same as those when creating a Package Delivery job in the previous segment of this article.
6. Provide a name and include any and all tasks or conditions you want to use for the Job. Note again that you can include any supported task available to the Notification Server.
7. After clicking OK to save the job, you can schedule or run it based on the Task Server interface, as with any individual Task.

Software Portal

The software portal has been revamped in Software Management 7.0. The portal is configured within the Software Release, under the Software Publishing tab. Browse to the same Software Release you created previously and browse to the Software Publishing tab.

The configuration is similar to 6.x, but beyond the setting of security items (which is more intuitive in this version), you can also check a box so this software shows up for the user in the portal by default. The portal has a different look, as shown in this screenshot:

Click to view.

I'll cover more on the Software Portal in a separate part of this article series. I'm pleased with the general feel of the Portal over the tree-design heavily utilized in the 6.x versions of Software Delivery.

Conclusion

In this article I've concentrated on revealing where the functionality from 6.x resides. The reality of the Software Management Framework will create a much more robust Solution allowing active management of Software Releases, including automated actions for Repair, install, uninstall, reconfigure depending on rules established. This, essentially, is realized in a Managed Software Delivery.