Client Management Suite

I have successfully exported SW Delivery packages and imported them into my test enviroment. I exported about 160 SW Delivery packages from my production 6.x R13 SP3 NS. I got a couple of errors durring the export I figured that was not uncommon.

I imported the packages to the new 7.1 SMP, (See results image attached.) Now when promoting the sw packages into the sw library I get a blank page when I click the "Set command line properties" (see blank cmd line image). I get the same display with serveral packages I've tried.

SIM ver 7.1.206

SMP 7.1 SP2 7.1.8280

CMS 7.1 SP2b   7.1.32

to see if the command lines are in the migration package.

Try the export and import again but watch the Altiris NS log on each NS as you do it and see if there's any errors.

I've had problems with package paths being obsolete and hence non resolvable and owner SIDs having been deleted. Both have caused error messages in the log.

I tested the same emport job and to save time while importing I selected to import just 1 package. I imported the same package into my DEV server, and it worked. So that make me think my production server has a bad instalation of the Migration Wizard. Currently I'm running SIM on the prod server and installing the language packs in hopes to see the option to download/install the migration wizard again and hopefully it will correct the problem.

stops the processing of the remaining items in that class.

Looking at my record of a previous troublesome migration, here's what I wrote at the time:

"The owner was set to John Smith, whose AD account had been deleted so the SID mapped to a blank entry. When the Import was run the blank entries caused an error and the item import to fail, some of which were folder items, some collections, some programs and some command lines. When a command line import failed none of the following command lines in the Import Package were processed, even ones with valid Owner names.

The old SID was replaced in the dbo.security.trustee table with a SID of a new, dummy, user."

But why would the same export package import successfully on another 7.1 server?

and one fails it may stop the import of all remaining data in that class.

But if you just import one package it might be a "good" one and suceed on it's own because there hasn't been a faulty one before to stop the process.

The same exported(6.x) package(#1) imported all 160+ packages successfully to my "CMS7-DEV" 7.1 server. I tried to import just 1 sw package from the same exported(6.x) package(#1) but it will not display the command line properties when I try to promote to the sw library to the new production 7.1 server.

Last night I left my NS6 server running a new export job #2 with the MigWiz. Today I tested the import of the #2 package to another dev server "SMS7-DEV", and again it it imported the couple of SW packages I selcted successfully.

But #2 again displayed the same problem as before when I tried to promote the package to the production server "SMP-Altiris".

So there has to be something wrong with the new designated production 7.1 server.

Very frustrating!

Maybe use Detailed Export.

Detailed export? Do you mean select everything when exporting?

> Detailed Export. 

I imported over 500 packages using the Migration Wizard. The command line options are not displayed.

Any ideas ?

I can't image creating all packages manually in a new enviroment.

After speaking with Tech Support, they said that happens sometimes. I had to enter the command lines for each package. It took me a couple of days but I got em now.