Worried about losing all the work you put into Software Delivery Solution 6.1? Learn how all that hard work can be moved and utilized in the new Notification Server 7.0 infrastructure. This will allow you to continue your software delivery policies through the new infrastructure while you learn the powerful new features in Client Management Suite 7.0, within the Software Management Framework.

*This article is based on a break-out session at ManageFusion in Las Vegas I will be presenting

Introduction

This guide will walk through how to upgrade so that your existing Software Delivery Objects are upgraded into the Symantec Management Platform version 7.0. Not all objects are available for migration between 6.x and 7.0. We'll cover how the old structure of Software Delivery fits into the new Software Management Framework, but furthermore we'll cover how to promote your migrated packages into the new Definitive Software Library, making them available for Managed Delivery policies.

Note that both the words upgrade and migrate are used in conjunction with the move from 6.x to 7.0. This is due to the nature of the upgrade. We are not conducting an actual 'in-place' upgrade, but are exporting supported data from the old database and then using a migrating wizard to put that data into the new structure after 7.0 is installed. For example the 'in-place' method of migrating exports the data, uninstalls all previous solutions and the NS 6.0 platform, installs the new, then runs the migration wizard that allows you to choose what will be migrated over.

Preparing for the Upgrade

Before you plan to upgrade to the Symantec Management Platform 7.0 from Notification Server 6.0, there are certain steps and safeguards you should use to prepare for it. Without these steps certain data and objects may be lost and not be properly moved over to the new framework. The following sections detail what steps should be taken to ensure a smooth transition to the new version.

Upgrade Method

There are two basic supported upgrade methods:

1. In-Place Upgrade - This method is executed directly on the Notification Server and will take the server from version 6.0 to version 7.0. The drawback to this method is that the 6.0 Notification Server is basically dismantled during the upgrade process. Reasons to use this method include:
   • The same hardware/server will be used for the new Symantec Management Server
   • No new hardware is available for the upgrade
   • Maintaining previous 6.0 Infrastructure is not necessary
2. New Server Upgrade - This method is recommended if possible. This will allow a 6.0 Notification Server to remain up and running while the Migration Wizard moves data over to the new install of Symantec Management Platform 7.0. Reasons to use this method include:
   • Many custom data/processes/objects reside within the 6.0 infrastructure and need to be available
   • Upgrading the hardware to a more robust server can meet the increased demands and functionality of the 7.0 Platform
   • Includes the ability to rollback and conduct the upgrade again should the need arise

Upgrade 6.x to 6.1 SP3 or SP4

Not all version of Software Delivery Solution 6.x are supported for upgrade. Because of various changes made in each Service Pack, only the most recent 2 are covered. SP3 is currently released, and SP4 is in development and will be released soon. Note the following:

• Software Delivery version 6.1.1058 (SP3) should be used as the base version.
• SVS, the Solution version, should be upgraded to version 2.1.3062, the latest release for the 6.x Platform. See this screenshot for an example:
  

  Click to view.

• Any additional point hot fixes applied to Software Delivery SP3 need not be applied before upgrade. Having the hot-fixes installed will not affect the upgrade if you do have them applied.
• Software Delivery Solution 6.1 SP4 will also be supported upon its release, current release target the first half of 2009.

Software Delivery and SVS Supported Objects

The following objects are available for upgrading/migrating:

• Software Delivery Packages - Imported as Software Package Resources into the Software Management Framework
  Note! These are not imported into the Software Library at this time. Migrated Packages will need to be promoted to the Software Library, which process is covered later
• Software Delivery Programs - Linked with the migrated Packages they were a part of in 6.x through Program Items. See the following screenshot:
  

  Click to view.

  Note the Execution Environment details set in the actual Program object. In the 7.0 Platform the execution environment resides in Tasks, not in the Program Items.

• Software Delivery Tasks - Imported as Legacy Software Delivery Policies
• Sequential Software Tasks - Imported as Managed Delivery Objects
• SVS Tasks - Imported as SVS Command Tasks

Software Portal

Much of the data stored in the Altiris database concerning the Software Portal will not be migrated into the 7.0 Platform. This includes:

• All Software Portal Requests - This includes the auto-generated items of a Software Request type
• Software Portal Tasks - Tasks generated either by an automatically approved request or a manually approved request will not be migrated, including links to the single computer collections generated, including Sequential Tasks
• Alert Manager Portal Requests - The Helpdesk/Alert Manager incidents created when someone requests software that requires approval will not be migrated
• Security - Security determines what software a user can see based on what permissions that user has been given to the Package/Program. Take snapshots of all Portal configurations, found under the Software Portal tab of a Package/Program or a Sequential Task

Software Delivery Custom Reports

Custom Reports are not migrated from Software Delivery Solution 6.x to Software Management Solution 7.0. This is due for the following reasons:

• The events/tables etc are not the same between Software Delivery 6.x and the Software Management Solution 7.0
• Task migrations do not include any event data captured from the 6.x framework
• Event data is not migrated with the Core Notification Server migration
• Task Server drives the majority of Tasks in the 7.0 Framework
• Software Management Solution has more robust, comprehensive reports that consolidate like data and provide a greater range of flexibility

Backup the Notification Server Database

This is for any upgrade being performed for Notification Server, but I feel it is important to call this out. Normally the Altiris database is not removed or modified during the upgrade to 7.0 as 7.0 creates a new database. Still, it is important to have a backup before the Migration Tool runs on the 6.0 install.

1. Open SQL Enterprise Studio
2. Browse under the instance and into Databases
3. Right-click on the Altiris database and choose Tasks > Backup.
4. Make sure the Backup type is FULL, and set the Destination to a known location.
5. Click OK
6. The database will be backed up when you receive a confirmation of success.

Application Management

Application Management is being joined with Software Management Solution. The functionality can then be incorporated into the larger Software Management Framework, extending the possibilities. The drawback is the lack of migration support available between Application Management 6.x and Software Management Solution. Note the following:

• No Policies are migrated between 6.x and 7.0
• Record Settings and Configurations for all active policies being used within Application Management
  • Windows Installer applications and tasks to update Windows Installer source paths re-created as Application Management tasks
  • Installation state management policies must be re-created as Managed Delivery policies

During the Upgrade

Use this process in guiding you when upgrading. The actual Installation of the Symantec Management Platform and all selected Solutions will install first. The Migration takes place after the install for data to be moved. This is true whether conducting an in-place upgrade or a server to server upgrade. Note that this process normally is conducted during the full upgrade, meaning that all Solutions will be selected or deselected to move data over into the new infrastructure.

1. Download the suite package or EXE of AIM to your Notification Server.
2. Install AIM by running the EXE, whether AIM directly or a suite package.
3. You'll get the following message if the extraction of AIM or the full suite is successful:
   • The files were successfully written to <Path> - Symantec Installation Manager Setup will now launch.
4. After SIM is installed, you can automatically launch SIM by keeping the box checked as shown in this screenshot:
   

   Click to view.

5. You will see a notice about which product listing file is being used. Normally accepting the defaults is the right choice.
6. Check the option for which suite you wish to install (CMS typically). Note the following:

   BEST PRACTICES: Should you have issues with a full suite installation, it is recommended to install first only the Symantec Management Platform. Do this by following these steps:

   1. Under the Install New Products wizard, select the dropdown defaulted to Filter: Suites and choose All instead.
   2. Only check the box labeled Symantec Management Platform as seen in this screenshot:
      

      Click to view.

   3. Conduct the Installation. When it is complete, go back to the Install New Products wizard and choose the suite you wish to install.
7. After choosing the suite and clicking through the summary pages, you'll need to select to accept the license agreements. Once next is clicked on this screen, all the installation packages will be verified before proceeding with the install.
9. At the end of the verification process you'll see a dialog as shown in this screenshot that gives you the option to run the Migration Wizard if you are doing an in-place upgrade:
   

   Click to view.

   If this is a fresh server you will not be prompted and the wizard will continue. Move to step 12.

10. When selecting to run the Migration Wizard, you'll get the following prompt:
    • Symantec Installation Manager will now download files necessary for the data migration process and then launch the Migration Wizard to step you through export of your Notification Server 6 data. Once the wizard is complete, Symantec Installation Manager will guide you through the rest of the Notification Server 7 installation.
11. The installation for Data Migration will then proceed, as shown here:
    

    Click to view.

12. The actual Migration Wizard needs to be carefully utilized to ensure the data you want that is available for export is, in fact, exported. Follow these steps to complete the migration wizard:
    1. Select the radial for: Export data from an Altiris Notification Server to a file store.
    2. Choose a location and filename for the export file that will contain all your 6 data for migration (it is recommended to use a reliable destination to store this file) and click Next.
    3. Check or uncheck items you want or do not want to migrate. This should be done for every solution. By default most options are checked, but not all. See this screenshot for an example:
       

       Click to view.

    4. See the section below titled Software Management Migration Wizard.
    5. The next screen will show you Solutions or components that are not supported by the wizard or do not have enough usage or data to conduct a migration. In my example I had Patch Management showing up as failing to meet baseline requirements since I've never configured or used the solution, but for Software Management and Inventory these do not show here as having problems. Double-check to ensure none of your migrating solutions show here.
    6. You'll get the splash screen stating: The product readiness check has found that not all the requirements have been met. The product data may not be exported correctly. Do you want to continue? Choose yes if step e. showed no issues.
    7. At the summary screen click Next to begin the migration. See this screenshot for an example:
       

       Click to view.

       NOTE! You'll often see yellow warnings within the exporter, but often these are not true issues with the data you need moved. You'll also inevitably see the message:
       • Data export completed with errors. Please see the Notification Server log for more details.
    8. SIM will launch again if this is an in-place upgrade, otherwise simply click Finish.
13. Next you'll see the Install Readiness Check. It is recommended to meet each requirement listed here. Many of the components will have a link to help you fix any noncompliance. Click Next to continue once all items are checked.
14. The next screen allows you to install licenses. If you ran the migration wizard you will already have previous licenses loaded here. Click Next to continue.
15. Next you'll first need to enter the Server details much like you did in Notification Server 6.0. Enter the following:
    • Application Identity, the account used for most NS-based functions
    • Email configuration (optional)
    • Database details
    NOTE: You need to choose to create a new database and NOT use the existing Altiris database! It is not supported to install to an existing 6.0 database.
16. The next screen allows you to predefine rolling out the Altiris Agent to. This step can either be configured now or skipped by simply clicking Begin install.
17. If this is an in-place installation the first sequence during the install is to uninstall version 6.0 and all Solutions and components. The second sequence involves the actual MSI installation of all 7.0 components that are part of the suite you selected. Lastly, the configuration, which creates most of the database objects, is run on all the Solutions.

    NOTE: This process can take a very long time, depending on what resources are available, how many solutions you have installed, and how many are to be installed and configured moving to 7.0. See the following screenshot for reference to the Progress screen:

    

    Click to view.

18. Take a break. You deserve it.
19. When installation completes, you'll receive the following screen:
    

    Click to view.

    Make sure the box: Notification Server 6 Migration Wizard is checked to continue with the upgrade process. Click Finish to continue.

20. If your Notification Server 6.0 installation is not on box, or you are doing a server to server migration, it is important to follow the instructions on this dialog so you are able to run the Migration Wizard on your NS 6 before continuing:
    

    Click to view.

    The link takes you to the location: \Program Files\Altiris\Symantec Installation Manager\MigrationPackage. Copy this over to your NS 6 and run to export data, as detailed at steps 9-11 above.

21. In the Migration wizard dialog, browse to the location of your exported data from NS 6.0.
22. The Migration Wizard will load the importers, and you'll see a list that looks identical to the Exporter one save they are marked as Importers and you will not see any importers that were not checked during the export. See the section Software Management Migration Wizard below for details.
23. When you click Next, you may find entries that indicate a product will not be migrated. Unlike the previous list during the export, this list specifically targets existing data in the file and usually means that data will not make it into version 7.0. See this for an example where RTSM, which should have been installed with CMS, was not:
    

    Click to view.

    It is important to correct these if the data referenced is important. In the above example running the install for RTSM via SIM would resolve the issue.

24. Click Next and then proceed with the Import. As with the export, you may see import warnings concerning data not being migrated properly. Usually these are not cause of issue as it may be an item that does not involve your custom data. When it completes you can review the data for any issues.

    BEST PRACTICES: Please take note of what items are not imported properly that you need imported. By noting these you can run the Migration Wizard again against just these items to retry the import, and this information can be available if you contact Support for troubleshooting should it be required.

    NOTE: This process will take much longer than the export. Plan on sufficient time to allow the import to proceed.

25. Click Finish to complete the process!

If you need to run the Migration Wizard a second time either on the 6.0 Notification Server for additional exports, or on the Symantec Management Platform 7.0 for retries or additional imports, run NSUpgradeWizard.exe found under C:\Program Files\Altiris\Upgrade (default path, use alternate path if one was chosen).

I found that retrying a Solution that failed singly by unchecking all other imports from the file increased the success rate.

Software Management Migration Wizard

The Migration Wizard Supports the following objects as shown in the Migration Wizard:

1. Software Delivery Solution for Windows License Certificate Exporter - Importer - This will be used to migrate your Software Delivery Solution license over to the new Software Management Solution.
2. Software Delivery Package and Program Exporter - Importer - This will export or import all Packages and Programs, as previously defined.
3. Software Delivery Package File Exporter - Importer - This will export or import locally stored package files, not UNC or HTTP based. This option is deselected by default.
4. Software Delivery Task Exporter - Importer - Exports or imports standard Software Delivery Tasks.
5. Virtual Software Package and Program Exporter - Importer - Similar to the Software Delivery one, only SVS objects of the same kind are targeted.
6. Virtual Software Package File Exporter - Importer - This will export or import physical VSPs stored locally on the Notification Server. This option is deselected by default.
7. Virtual Software Task Exporter - Importer - Similar to SWD but for SVS Tasks.
8. Sequential Software Delivery Task Exporter - Importer - This will export or import specifically Sequential Tasks, including the links to the multiple Packages and Programs.
9. Delivery Software Task Exporter - Importer - This exports or imports Task Server-based Tasks run by the Software Delivery Agent for Task Server Plug-in.
10. Virtual Software Command Task Exporter - Importer - SVS Tasks contained within Task Server
11. Virtual Software Data Class Data Exporter - Importer - Exports or imports Events and Inventory for SVS

Validation

Once the upgrade process has completed, with the Install completed and the Migration Wizard finished, It is important to validate that the items you wished to migrate were, in fact, migrated. The most crucial items are Packages, listed below.

Software Packages

Once the upgrade/migration is complete, the data can be used. By default the migrated packages can be used with Delivery Software and Quick Delivery Tasks within the Task Server infrastructure. To see how to use these objects using the same basic structure and functions from Software Delivery 6.1 in the 7.0 framework: Introduction to Software Management in Notification Server 7.0, Part 1: Software Delivery

The Packages are located in the Symantec Management Console under Manage > Resources > Organizational Views > Default > All Resources > Package > Software Package. Please look through the list to ensure the Packages you had created on the 6.x platform show up in this location. See this screenshot for an example:

Click to view.

The rest of the validation will be covered in the next section: What's Next?.

What's Next?

After you've upgraded, migrated, and validated the upgrade, what's next for Software Management? This section walks through the common items that will get you up and running.

Promoting Packages

To promote your packages to the Definitive Software Library, follow one of the below sets of steps. Once you have completed the wizard for a given Package, you will not be able to promote that package again, so ensure you are choosing the right options.

To promote a package to a new Software Resources, following these steps:

1. In the Symantec Management Console, browse under Manage > Resources > Organizational Views > Default > All Resources > Package > Software Package.
2. On the Package you wish to promote, double-click or right-click on the package and choose Resource Manager.
3. Click on the link Assign to Software Resource in the left-hand pane.
4. You'll receive the following Wizard to convert the Package into a Software Resource, which will put it into the Software Library:
   

   Click to view.

5. Choose the radial option: Create new software resource.
6. Provide a Name for the new Software Resource.
7. Choose a Type (If you are unsure of the type, choose Software Release).
8. The Version field can be used for your tracking updates and changes to the Software Resource.
9. The Software Product field isn't required but can be configured at this point. Click Next.
10. The conversion takes a Package/Program from 6.x and converts it into a Package and Command-line for the 7.0 Platform.
11. When promoting the package the command-line goes with it and can be configured at this point. During the migration the Installation File type is set to what we believe the type should be, so review to ensure it is accurate.
12. Click Finish to complete the Wizard.

To promote a package to an existing Software Resource, following these steps:

1. In the Symantec Management Console, browse under Manage > Resources > Organizational Views > Default > All Resources > Package > Software Package.
2. On the Package you wish to promote, double-click or right-click on the package and choose Resource Manager.
3. Click on the link Assign to Software Resource in the left-hand pane.
4. Choose the radial option: Use Existing software resource.
5. Click on the blue under-lined link to the right of the field: Select software resource
6. Choose from the list the Software Resource you wish to promote the selected package to.
7. Review the command-line parameters to ensure they are set correctly.
8. Click Finish to complete the Wizard.

Software Portal

The Software Portal security settings configured in Notification Server 6.0 do migrate with Packages. A Package must be promoted per the above instructions for the Portal security items to be fully migrated. Note that the default security is not migrated, including Altiris Administrators, the Application ID, and the creator of the Package if applicable. Follow the Promote Package steps above to complete the Software Portal security objects migration.

To access the configuration of the Software Portal, browse in the Symantec Management Console under Manage > Software > Software Catalog > Deliverable Software > Releases (or if you promoted the package to another location, browse to that location under Managed > Software). Double-click on the desired package and then click on the Software Publishing tab.

See the following screenshot for an example:

Click to view.

Legacy Standard Tasks

Standard Software Delivery Tasks are migrated over as Legacy Software Delivery Policies. These will all be disabled by default but can be enabled and configured to continue rollout.

To enable and use one of these policies, follow these steps:

1. Browse in the Symantec Management Console under Manage > Policies > browse under Policies > Software > Legacy Software Delivery > Select the desired Policy.
2. You'll see the following screen:
   

   Click to view.

3. Note the following in what has changed between versions:
   • The Go to Package link pulls up the Legacy package details and does not tie into the Software Library. This link will not include the ability to look at the "Program".
   • The Go to Program link actually brings up the command-line interface as type Program doesn't exist in 7.
   • The Advanced tab now contains the Execution Environment, pulled from the Program of the 6.x Package this Task was assigned to.
4. Check all settings to ensure they meet your requirements.
5. The former "Collection" that was assigned to the task is now a Target. Expand the Applies To section to review, modify, or change what systems are targeted by this Policy.
6. Expand the Schedule section and set the schedule, including setting the options:
   1. Run ASAP
   2. User can run
   3. Notify user when the task is available
   4. Warn before running, can defer for ___ minutes
7. Scroll to the bottom of the right-hand pane and click 'Save Changes' if any changes were required.
8. On the bar Policy Rules/Actions turn on the policy by clicking the dropdown to the far right and choosing green: On.

Sequential Tasks

Sequential Tasks you created previously will now be Managed Delivery Jobs. Despite this migration, not all Sequential Tasks translate well into Managed Delivery jobs. Moving forward you need to determine whether a Managed Delivery policy or a Task Server Job best fits your needs for your former Sequential Tasks. To access the migrated Sequential Tasks browse in the Symantec Management Console under Manage > Policies > browse under Policies > Software > Managed Software Delivery. See the following screenshot to see how these tasks show up:

Click to view.

Below are the criteria I recommend in determining what mechanism should be used:

1. Task Server Jobs
   • Multiple Software rollouts
   • Complex jobs that include other mechanisms aside from Software rollouts (AMT functionality, Task Server scripting, etc)
   • One-time rollouts for unmanaged targeting
2. Managed Delivery
   • Application State Management
   • Versioning control
   • Intelligent deployment

As your Package and Programs are already migrated, you can setup your new Task Server Job or Managed Delivery Policy depending on which works best for what the former Sequential Task was doing.

Task Server Plug-in Tasks

The conversion of Task Server Deliver Software tasks to the new standard Software Management Task is simple in that Task Server is still the delivery mechanism via a Quick Delivery Task. The Package-Programs used in the Tasks are already converted as previously covered. The new Package Delivery tasks will contain the links to the Package and Command-line as previously configured on the 6.x platform. To access these Tasks to run, schedule, or modify, follow these steps:

1. In the Symantec Management Console browse through Manage > Jobs and Tasks > and browse down through Jobs and Tasks > System Jobs and Tasks > Software > Package Delivery.
2. Highlight the migrated Task Server Task you wish to review. See this screenshot for an example:
   

   Click to view.

3. The main screen only shows what Package and command-line that will be used. Along with the ability to schedule the Task.
4. Click Advanced to get more Task-related information, including the execution environment.
5. Make any changes to the details and click Save changes.
6. To use the task, use the standard Task Server mechanism found under the Task Status section.

Troubleshooting

I wanted to also share what Troubleshooting methods I used to get past issues I ran into while walking through the upgrade. For the most part retrying failed processes resolved the issue.

1. SIM - The install fails part way through the installation of the Suite
   • Restart but only install the Symantec Management Platform and not the whole suite. When that completes correctly then go in and walk through the install of the suite.
   • Sometimes the caches used by the install get in a funny state. I rebooted my server which cleared up the last SIM issue I had, allowing the rest to install without issue.
2. Migration Wizard - The Migration wizard fails to Import exported Software Delivery or Software Management data from the 6.x platform
   • I found that retrying the Migration Wizard but only selecting Software Management data usually resolved the issue.
   • Rerun by using the file NSUpgradeWizard.exe located at \Program Files\Altiris\Upgrade\ and when you reach the configuration screen uncheck all options but the ones listed under Software Management section. You can either uncheck options further though some items are required and you'll receive a message if you don't have everything you need checked from a dependency standpoint.
3. Licensing - I discovered that licensing wasn't working properly due to the number of licenses of various sorts that got migrated over from the 6.x platform. If you see errors in the server logs on license after the upgrade, and/or the license frame doesn't load with your installed licenses under Home > Notification Server Management > Portal, follow these steps. Note that in this case the Software Management Solution could not verify the license and did not allow usage of the Solution until fixed:
   1. Go to Start > Run > type mmc > click OK.
   2. Go to File > Add/Remove Snap-in...
   3. Click the Add button.
   4. Select Certificates and click the Add button.
   5. On the subsequent screen, select the Computer account radial and click Next.
   6. Leave the selection Local Computer: (the computer this console is running on) radial selected and click Finish.
   7. Click the close on the next window.
   8. Click OK on the Add/Remove Snap-in screen.
   9. In the right-hand tree of the MMC browse under Certificates (Local Computer) > Altiris Licensing > and select Certificates.
   10. Highlight all certificates listed and press the Delete key.
   11. Go back into the Symantec Management Console and reapply the license under Home > Notification Server Management > Portal, using the link Add Licenses.
4. Repairing - If an install failed or did not complete correctly, a repair can be run but the following method should be used:
   1. Browse to the extraction location you used on the Notification Server when you first downloaded and executed the Suite or AIM. That location will have a subfolder structure as follows:

      Altiris\Components\
      
      

   2. Find the MSI for the component you need to Repair. For Software Management, I ran two installers, as listed here:
      1. Altiris_softwaremanagement_7_0_x86.msi
      2. Altiris_softwaremanagement_7_0_kb43875_sp1_x86.msi
      3. Altiris_softwaremanagementsolution_7_0_x86.msi
   3. Right-click on the MSI and choose Repair. You can also double-click to launch the MSI interface. If you get a message indicating that SIM (Symantec Installation Manager) is required to use the MSI, run the MSI from a commandline with the following parameter:

      SKIPAIM=1
      
      

      NOTE: This parameter should not be used lightly due to dependencies between the hundreds of MSIs in the Suites.

Conclusion

Using this guide you should be able to migrate from the Notification Server 6.0 infrastructure to the Symantec Management Platform 7.0, knowing what is migrated and what to do once the migration is complete. This should also help you understand what work is involved in migrating Software Delivery to the new and much improved Software Management.