The option forces application migration when the utility fails to migrate one or more attributes to the MSI.
An MSI bundle is considered to be failed when a warning is produced while converting an AOT Application object to an MSI. These bundles can often be migrated successfully in spite of the warning. For example, the warning might be produced because a Windows shortcut link contained in the AOT is no longer valid.
If you enable this option, the warning messages are not presented. You can review the migration log for information on what attributes were not migrated.
The option means the application is created and migrated, but the directory holding the temporary files and new MSI file is not automatically deleted. This allows you to have access to the newly created MSI before it is incorporated into the content service in Configuration Management.
The option lets you upload content to the content server. This option is selected by default.
The applications are migrated as Install MSI action to the ZENworks Configuration Management server and also uploaded to the content server if the option is selected and the source path of the file is resolved to a local path or UNC path at the time of migration.
The applications are migrated as Install Network MSI action to the ZENworks Configuration Management server and are not uploaded to the content server in the following scenarios:
The option is deselected.
The option is selected but the source path of the file is not resolved to a local path or UNC path at the time of migration, or the file is not found.
The option lets you migrate the distribution options in applications as individual actions such as Edit INI action, Registry Edit action, or Run Script action that can be edited. By default, it is selected. Deselect the option to migrate the distribution options in applications as MSI.
If the option is enabled, then the applications are migrated as specific actions:
An application having registry changes is migrated as a bundle with Registry Edit action.
An application having INI settings is migrated as a bundle with an Edit INI File action.
An application having text file changes is migrated as a bundle with an Edit Text File action.
An application having icons or shortcuts is migrated as a Windows bundle with a Run Script action or File Removal action.
An application having application files changes is migrated as follows:
Files as Copy Files or Install Files action.
Directory as a Copy Directory, Install Directory, or Create/Delete Directory action.
Deletion of files as a File Removal action
Deletion of directory as a Create/ Delete Directory action.
If the option is disabled, then the application is migrated as an Install MSI action. But, the Edit Text File action, Copy Directory, Install Directory, File Removal are not a part of this Install MSI action.
The option allows you to place the temporary migration files in a different location than the default users %TEMP% directory. If you migrate an application with a very long path (longer than 256 characters), this option enables you to make the temporary path short, such as c:\temp.