Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010 Migration Manual page 70

Feature
Disconnectable
Display folder list
Drive mappings
Fault tolerance
Force run as user when
workstation associated
Force run wait
Granular install file control This feature allowed the administrator to control which files were copied
Granular uninstall file
control
Granular install registry
control
Granular uninstall registry
control
Granular install.INI
control
Granular uninstall.INI
control
70 ZENworks 10 Configuration Management ZENworks Migration Guide
Comment
This feature allowed the administrator to not show the application on the
desktop if the workstation was disconnected. Use the equivalent system
requirement in Configuration Management.
This feature allowed the administrator to put the shortcut for the application in
multiple display folders. Configuration Management only allows the
placement of the shortcut in one folder. Therefore, Configuration
Management migrates only the first folder.
This can now be done in a launch script. You can unmap the drive in a
termination script.
The new content system does this automatically on a whole zone basis.
Not supported in Configuration Management.
This feature is replaced by application chaining.
during an installation, based on how they were marked in ConsoleOne
example, you could tell Novell Application Launcher to only copy files marked
"Request Confirm.". Because MSI does not allow a granular (file-by-file)
setting, this feature cannot be migrated if the application is migrated as a
bundle with Install MSI action.
This feature allowed the administrator to control which files were removed
during an uninstallation, based on how they were marked in ConsoleOne.
For example, you could tell Novell Application Launcher to only uninstall files
marked "Request Confirm." Because MSIs do not allow a granular (file-by-
file) setting, this feature cannot be migrated.
This feature allowed the administrator to control which registry settings were
created during an installation, based on how they were marked in
ConsoleOne. For example, you could tell Novell Application Launcher to only
create registry settings marked "Registry Append." Because MSIs do not
allow a granular (registry-setting-by-registry-setting) control, this feature
cannot be migrated.
This feature allowed the administrator to control which registry settings were
removed during an uninstallation, based on how they were marked in
ConsoleOne. For example, you could tell Novell Application Launcher to only
uninstall registry settings marked "Registry Append." Because MSIs do not
allow a granular (registry-setting-by-registry-setting) control, this feature
cannot be migrated.
This feature allowed the administrator to control which INI file entries were
crated during an installation, based on how they were marked in
ConsoleOne. For example, you could tell Novell Application Launcher to
create INI entries marked "create add to section." Because MSIs do not allow
a granular (INI-entry-by-INI-entry) control, this feature cannot be migrated.
This feature allowed the administrator to control which INI file entries were
removed during an uninstallation, based on how they were marked in
ConsoleOne. For example, you could tell Novell Application Launcher to only
uninstall INI entries marked "create add to section." Because MSIs do not
allow a granular (INI-entry-by-INI-entry) control, this feature cannot be
migrated.
®
. For