The conversion tool itself supports running on Windows Vista. Migrated packages may not be able to run under Vista on managed clients. General rule is that if package did not run under Vista previously with LiveState Delivery, then it will not run under Vista after migration.
Known issues are recognized problems that are not listed in the documentation. They include problems that may be resolved in future and problems for which a workaround exists. Design limitations are documented in the individual functional specifications.
It is possible that some programs may not be compatible with running in a hidden desktop (the "hidden" mode of execution using the RunHidden.exe tool). This may be occur in cases where the program is written in a manner that relies on access to a visible user desktop.
One known case involves install programs that use shell dialogs like the common File Open or File Save As dialogs. Since these dialogs cannot be displayed on a hidden desktop, the package execution will hang. This is an unusual case though, because it is not appropriate to use Transcript Recorder to browse through File Save/Open (as it may be different on each machine), and it is better to use a variable to set the filename text box instead.
There may also be occasions in which the selected user security context (in the Notification Server program execution options) may result in unexpected behavior when
the package is executed in "hidden desktop" mode. One such case involving the Nero installer was identified in the lab. When running under a specific
user context in a hidden desktop, the Nero installer halted. This was solved by changing the user context to run as SYSTEM user.
If a migrated package script refers to an absolute path like "C:\_integra" or "\\depot", then it is most likely will not run straight away when migrated to Notification Server. After migration, the scripts (which will be on the Notification Server share) should be reviewed to verify that any specified paths are valid for execution in the Notification Server context.
If a migrated package script refers to a tool outside of the package files, (e.g. tools distributed with the LSD agent like "smecp"), those tools will not be available in Notification Server environment. The workaround is to include the tool in the package depot (or development) files.
Note: "awk" will be included if used. Also, wininter.exe is not affected by this limitation, because it is always included in package development files.
This is as designed. Custom GINA DLL is necessary for autologon to work and will be installed on the client.
This should not really happen. As part of the migration process, the old LiveState Delivery agent should be removed from clients and replaced by the appropriate Altiris agents. Failure to remove the LiveState Delivery agent could result in a conflict between the custom GINA DLL prerequisite package and the old LiveState Delivery agent.
Version 1.1 of .NET is required for the client-side components of the Altiris Administrator SDK. The installation of the Altiris Administrator SDK may fail and generate a 1721 error in cases where .NET 1.1 is not installed on the target computer. This is true even if .NET 2.0 is installed on the target machine. Version 1.1 of .NET 1.1 must be installed on the target computer before installing components from the Altiris Administrator SDK.
The product's uninstall does not verify whether any of its tools are currently running before proceeding with the uninstall process. In cases where some of the tools are running at the time that the uninstall process is begun, the uninstall may fail to remove some files. Please close all running instances of the tools before uninstalling.
When reporting a problem or defect with the product, please provide detailed information about the environment, the actions required to replicate the problem, and any applicable debug and log files.
Please provide the following:
Depending on the problem, the development team may request the package being used at the time. This will help resolve the problem, but is left to your discretion, as some packages may contain sensitive data.
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.