Incase anyone's having issues with the software, there is a new release (601) for DL that updates alot of things. You can call Symantec or log in to their corporate site and DL the patch.



Resolved migration issues
Package Analyzer creates a useless variable
If a package contains multiple drive entries, for example, "C: D: E: F:", within the [restrictions] section, Package Analyzer created the useless variable "DRV=c:d:e:f:". The enhanced Package Analyzer utility now resolves this issue.

Package Analyzer automatically removes duplicate admin param values
The Package Analyzer program automatically removed duplicate parameter values found in the [admin param] section of the Package Configuration File (config.swp). This action could result in the removal of a default value.

The Package Analyzer program has been modified to include a column in the List pane labeled "Repeated Parameter Values". You can do one of the following:

Accept the default action in the Package Analyzer, which will remove the duplicate parameter values.
Change the package data manually and rerun the Package Analyzer.
Delete the package.
For more information on using the Package Analyzer, see the Symantec LiveState Delivery 6.0 Migration Guide.

Package Analyzer does not print to file
The Package Analyzer program now lets you print the results of the analysis to a file.

Cannot upgrade packages with invalid package IDs
When upgrading a Symantec ON iCommand 3.x package to a Symantec LiveState Delivery 6.0 package, the package cannot be upgraded unless the package ID conforms to the Symantec LiveState Delivery 6.0 package ID rules.

A command line utility, ChangePackageId, converts invalid 3.x package IDs to valid 6.0 package IDs, including any invalid IDs located in the DEPOTDIR, dependencies, and substitute entries. Also, there is an additional command line parameter (-idmap) for the TwoDirToPak and ServerToPak utilities.

For more information about the ChangePackageId utility, see the Supplemental Documentation section at the end of this document.

TwoDirToPak utility cannot migrate packages with duplicate response values for admin params
There was an issue migrating packages from Symantec ON iCommand 3.x to Symantec LiveState Delivery 6.0 if you had duplicate response values for a parameter in the [admin param] section of a package’s config.swp file. This issue has been fixed. Now, if the TwoDirToPak utility encounters duplicate response values, it accepts the first parameter value in the list as the default value and ignores all other duplicate values.

TwoDirToPak utility does not correctly evaluate the destination folder's UNC path
The TwoDirToPak utility now correctly evaluates UNC paths, including the dollar sign character "$".

RAWMODE value is always set to "FALSE"
The TwoDirToPak utility reset the package parameter RAWMODE to "FALSE". The enhanced SwpParser used by the TwoDirToPak utility now resolves this issue.

Package migration process may hang if one of the packages contains a dependency to a package ID
The Symantec LiveState Configuration Database Service has been enhanced to manage dependencies during package migration. In addition, the job scheduler of this service is now disabled during the package migration.

Package Info files are not generated during package upgrade
During the upgrade of a Symantec ON iCommand 3.x package to a Symantec LiveState Delivery 6.0 package, if the 3.x package had a blank Package Info File, then the 6.0 package's Package Info File (info.html) would be blank also. This becomes apparent in the Symantec LiveState Delivery 6.0 Command Center, because you can view the Package Info File in the Result pane.

During the 3.x package upgrade process, a Description fileset and a Package Info File (info.html) now have been added to the 6.0 package. The information in the Package Info File is created in one of the following three ways and in the following order:

If there is a readme.htm file in the %SME_ROOT%\sw directory, then the content of the readme.htm file is copied into the info.html file.
If there is a readme.txt file in the %SME_ROOT%\sw directory, then the content of the readme.txt is copied into the info.html file.
The content of the [info] section of the config.swp file is copied into the info.html file.
For information about viewing Package Info files in the Command Center, see the Symantec LiveState Delivery 6.0 Command Center Help.

Packages are unassignable due to missing vendor files
After migration most packages were unassignable. The error was "missing vendor files: PAKDESCRIPTION". This issue has now been fixed.

Packages cannot be deleted from a computer profile that has been migrated from Symantec ON iCommand 3.x
Packages can now be deleted from a migrated computer profile.

Symantec LiveState Configuration Database Service deadlock
Managed computers were connecting to the Configuration Server and requesting the job list while running the package migration in the Symantec LiveState Delivery 6.0 Server Setup program. This could trigger an update of the package order, which resulted in a database deadlock. This issue has been fixed.

Embedded database service for Symantec LiveState exits during migration
The embedded database service for Symantec LiveState exits during the package migration process. The Symantec LiveState Configuration Database Service has been enhanced to correct this issue.


0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
There is also a patch to the 6.1.1 update(Which also acts as a standalone install). You can check by making sure the version of your Livestate Agent is 7.1.3(7.1.2 before this patch)
Answered 09/11/2006 by: Timanator
Third Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity