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

Also see for ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3 30-03-2010: Upgrade guide Reference guide Command reference guide Deployment guide Getting started guide

Contents

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

80 ZENworks 10 Configuration Management ZENworks Migration Guidenovdocx (en) 16 April 2010B.1.1 GeneralWhen you are migrating an object that already exists in ZENworks Configuration Management, youcan use the Overwrite objects that already exist option to cause the latest object being migrated to beused instead. The existing object is overwritten with the new migration object in the ZENworks®Configuration Management database.NOTE: If you choose to remigrate an application to ZENworks Configuration Management withthe Overwrite objects that already exist option enabled, you must ensure that the version of theapplication you want to remigrate is higher by one than the version of the existing ZENworksConfiguration Management bundle. This is required to avoid inconsistent results on the manageddevice when the bundle is assigned to it.The Skip saving/loading history option allows you to dramatically improve performance on largemigrations by not storing the local history.B.1.2 ApplicationsThe Migrate failed MSI builds option forces application migration when the utility fails to migrateone or more attributes to the MSI.An MSI bundle is considered to be failed when a warning is produced while converting an AOTApplication object to an MSI. These bundles can often be migrated successfully in spite of thewarning. For example, the warning might be produced because a Windows shortcut link containedin the AOT is no longer valid.If you enable this option, the warning messages are not presented. You can review the migration logfor information on what attributes were not migrated.The Preserve Created MSI and Temporary Files option means the application is created andmigrated, but the directory holding the temporary files and new MSI file is not automaticallydeleted. This allows you to have access to the newly created MSI before it is incorporated into thecontent service in Configuration Management.The Upload applications to content server option lets you upload content to the content server. Thisoption is selected by default.The applications are migrated as Install MSI action to the ZENworks Configuration Managementserver and also uploaded to the content server if the Upload applications to content server option isselected and the source path of the file is resolved to a local path or UNC path at the time ofmigration.The applications are migrated as Install Network MSI action to the ZENworks ConfigurationManagement server and are not uploaded to the content server in the following scenarios: The Upload applications to content server option is deselected. The Upload applications to content server option is selected but the source path of the file isnot resolved to a local path or UNC path at the time of migration, or the file is not found.The Migrate distribution options as individual actions option lets you migrate the distributionoptions in applications as individual actions such as Edit INI action, Registry Edit action, or RunScript action that can be edited. By default, it is selected. Deselect the Migrate distribution optionsas individual actions option to migrate the distribution options in applications as MSI.