Applications are migrated to ZENworks Configuration Management as bundles with specific actions. For example, an application having Registry changes is migrated as a bundle with Registry Edit action.
Some features are migrated, some are not, and some are replaced by new features. Table A-1 lists the features that are not migrated. The Comment column explains why not and whether an alternative to the traditional feature exists in Configuration Management.
For Novell Application Launcher Configuration settings that are not migrated, see Section A.3, Policies.
Table A-1 Application Features Not Migrated to Configuration Management
Feature |
Comment |
---|---|
ACL |
Configuration Management uses a new security model for access control. |
Auto Start feature |
This feature caused Novell Application Launcher to add itself to the start menu so that it could automatically start when the user logged in. This is now handled by the ZENworks Adaptive Agent. |
Availability schedule |
This is migrated when associations are migrated. In other words, for every schedule on an application, there is now a specific schedule for every direct association to that application. |
BITS support |
BITS is not supported in Configuration Management. Administrators can manually turn on throttling. |
Capturing printer ports |
This can be done in a launch script. You can uncapture the port in a termination script. |
Copy directory |
You must manually create this action in ZENworks Control Center by using the Copy Directory category in a File bundle. |
Deframe Settings |
Configuration Management supports only simple RDP and ICA sessions. |
Disconnectable |
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. |
Display folder list |
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. |
Drive mappings |
This can now be done in a launch script. You can unmap the drive in a termination script. |
Fault tolerance |
The new content system does this automatically on a whole zone basis. |
Force run as user when workstation associated |
Not supported in Configuration Management. |
Force run wait |
This feature is replaced by application chaining. |
Granular install file control |
This feature allowed the administrator to control which files were copied during an installation, based on how they were marked in ConsoleOne. For 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. |
Granular uninstall file control |
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. |
Granular install registry control |
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. |
Granular uninstall registry control |
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. |
Granular install.INI control |
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. |
Granular uninstall.INI control |
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. |
Icon order |
Configuration Management does not control the order in which icons are displayed. Use application chaining to control the order of application installation. |
Load balancing |
The new content system does this automatically on a whole zone basis. By default, all the Primary Servers in the Management Zone replicate their content among each other. |
MSI admin path |
Because MSI package information is no longer stored in the metadata, you longer need access to the actual MSI file in ZENworks Control Center. Also, most MSIs are uploaded into the content system. |
MSI option install paths random |
Replaced by the new content system that does load balancing automatically. |
MSI package description |
MSI Package information is no longer stored in the metadata. This makes it easier to update MSI packages without touching the MSI bundle itself. |
MSI package identifier |
MSI package information is no longer stored in the metadata. This makes it easier to update MSI packages without touching the MSI bundle itself. |
MSI package size |
MSI package information is no longer stored in the metadata. This makes it easier to update MSI packages without touching the MSI bundle itself. |
Novell Licensing Service (NLS) |
Configuration Management does not supports NLS. |
On Demand |
Configuration Management supports only simple RDP and ICA sessions. |
RDP color depth |
Color depth must be 256, 32768, 65536, or 16777216. |
Remote alternate application |
The ZENworks Adaptive Agent runs the same inside or outside the firewall. It doesn't make a distinction, so this feature is no longer supported. |
Reporting |
Configuration Management has a global reporting system, so reporting is no longer configured on an application-by-application basis. |
Run 16-bit applications in a separate session |
Configuration Management does not support 16-bit operating systems. |
Site List |
This feature allowed users to use the closest matching applications source path to install the application to their workstation. The new content system does this automatically. |
Thin client settings |
Configuration Management only supports a subset of the features Novell Application Launcher used to support. The following attributes have been dropped:
|
Uninstall prompt for reboot |
This feature is no longer supported. Msiexec.exe now handles rebooting for each uninstallation. Most of this functionality is handled by adding parameters to the MSIExec command line. |
Volume file system rights |
Configuration Management does not automatically assign rights to any file system. |