Endpoint Management and Virtualization Trusted Advisors Community merge into SED TA Community

Hello again all,

We continue moving forward on our Altiris 7.1 upgrade, but have run into a bit of a stumbling block.  Basically, we have created several dozen Software Products in our 7.1 Test SMP box, and now need to migrate them (hopefully en masse) to the Prod box.  First I tried using the Export function after selecting "Software Products" under Deliverable Software.  I can export an .XML file, but haven't figured the right place to then import it again.  I tried using Manage > All Resources, then drilled down to Default > All Resources > Software Product, but get a warning that I can't import something into an Organizational View.  I was able to create a new folder and imported the .xml, but it doesn't show up when I go into Manage > Software Catalog.

So, what's the trick?  How do you export Software Products from TST to Production?  Do you actually use the "Migration Package" for migrating from 6.x7.0 to 7.1?

Use <drive>:\Program Files\Altiris\Notification Server\Bin\Tools\ImportExportUtil.exe

I haven't exported/imported a Software Product before, however, so let me know how that goes for you!

that is part of the Software Product?

I've just tried it on a test system of mine, you need to find a Software Release that is included in the Software Product. The best way to do this is use the old Software Catalog View, Settings > All Settings > Notification Server > Console Settings > Views > Software > Software Catalog > Deliverable Software. Look in the "Product Name" column in the right hand pane, find a Software Release with that Product, right click > Actions > Detailed Export and select "Product..." and "Package...".

Go to the same place in the console you want to import into, right-click on "Deliverable Software" and select import.

You might need to tweak the data you export depending on how you manage package sources etc.

Thanks Mike and Andy, I'll take a shot at your suggestion Andy.  I'm really hoping this works; my coworker has spent a lot of time staging all of our packages from NS 6.0 into 7.1 and I really don't want to have to do it all again from scratch!  Obviously the "software Product" is a complex concept with ties to many tables and resources, but it seems like it should be doable.

We'll give your method a try and I'll let you know what we find!

Hi KSchroeder,

there is another option to migrate Software Packages

Try the following link: http://www.symantec.com/docs/TECH166711

This tool allows a migration from 7.1 to 7.1

Supported Notification Server versions
The following source Notification Server versions are supported by the Symantec Software Resource Replicator utility:

• ITMS 7.0 MR2
• ITMS 7.0 MR3
• ITMS 7.0 MR4 (both clean and with Rollup 6)
• ITMS 7.1
• ITMS 7.1 SP1
• ITMS 7.1 SP2

The following target Notification Server versions are supported by the Symantec Software Resource Replicator utility:  

• ITMS 7.1 SP1
• ITMS 7.1 SP2

Network23

This looks like exactly what I'm after, thanks Network23 (assuming that is your real name!)  I'll give it a try today!

I have the same "issue" We have a dev box that I have built and tested about 50 software applications on and have everything working perfectly on the dev box. Looking into it I was able to migrate my software library from dev to prod but none of my software resources came over during the so called migration. I was able to export all my quick delivery tasks but without being linked to a software resource they all must be rebuilt. Going to give this a try first thing tomorrow and see how it goes...

Couldnt wait, had to try the tool this afternoon and all went swimmingly!! thanks Network23!

One additional question...so that works and we can export/import SW Resources.  But how do you go about bringing the actual physical files over?  Right now we have few enough items that I'm just doing a Robocopy of the \\testsmp71\swlibrary$ to \\prodsmp71\swlibrary$ /e, but that seems like a kind of brute force method.  Are the actual package source locations brought into the target NS somewhere, or is that source path lost once the package is in the SW Library?