The Advanced Options table lists the advanced options that can be set for CA DMM. Boolean values are specified as either 1 (true) or 0 (false).
|
Name |
Explanation |
Comment |
Valid Values |
Dependency |
|---|---|---|---|---|
|
Critical file list |
What files do you want identified as critical files? |
Defines the list of files that you want identified as critical files. |
Defaults to: io.sys|boot.ini|msdos.sys| |
None. |
|
Don't warn if critical file or folder is selected |
Do you want the user warned if a critical file is selected for migration? |
If true, a warning message will not be displayed to the user if a file critical to the operating system is selected for migration. |
1 = True 0 = False Defaults to False |
None. |
|
Don't migrate broken desktop shortcuts |
Do you want to exclude migrating any broken desktop shortcuts? |
If true, any shortcuts on the users' desktop that cannot be resolved during the migration are not migrated. |
1 = True 0 = False Defaults to False |
None. |
|
Don't migrate broken quick launch shortcuts |
Do you want to exclude migrating any broken quick launch shortcuts? |
If true, any shortcuts in the quick launch that cannot be resolved during the migration will not be migrated. |
1 = True 0 = False Defaults to False |
None. |
|
Don't migrate broken start menu shortcuts |
Do you want to exclude migrating any broken start menu shortcuts? |
If true, any shortcuts in the start menu that cannot be resolved during startup are not migrated. |
1 = True 0 = False Defaults to False |
None. |
|
Don't migrate broken startup shortcuts |
Do you want to migrate any broken startup shortcuts? |
If true, any shortcuts in the startup that cannot be resolved are not migrated. |
1 = True 0 = False Defaults to False |
None. |
|
Don't migrate any broken shortcuts |
Do you want to exclude migrating any broken shortcuts? |
If true, any shortcuts that cannot be resolved during the migration are not migrated. |
1 = True 0 = False Defaults to False |
None. |
|
Move broken desktop shortcuts into a folder |
Do you want to move broken shortcuts on your desktop to a folder? |
If true, any shortcuts that cannot be resolved during migration are moved into a Broken Shortcuts directory on the desktop. |
1 = True 0 = False Defaults to True |
None. |
|
File IO buffer size (bytes) |
What should the size of the buffer be when working with DNA files? |
Larger IO buffer values may increase performance and memory usage. |
Defaults to 1048576 |
None. |
|
Free disk space margin (Kb) |
How much free disk space will you require to create your DNA file? |
Defines the disk space margin necessary to create a DNA file. The DNA file size plus this margin will not be exceeded when creating a DNA file. |
Defaults to 64 KB |
None. |
|
Free removable-disk space margin (Kb) |
How much free removable disk space is required to store your DNA file? |
Defines the disk space margin required to create a DNA file on removable media. The DNA file plus the margin is not exceeded when creating the DNA file. The margin is automatically set to 1 KB if the specified margin leaves less than the minimum required spanning size. |
Defaults to 1 KB. |
None. |
|
Path for Name and Location filters |
What is the path to look for specific files or folders to create a Name and Location filter? |
This option contains the path to look for specific files and folders when using a Name and Location filter. |
Blank |
None. |
|
File names for Name and Location Filters |
What are the names of the files or folders to create a Name and Location filter? |
This option contains the names of files or folders that will be migrated when a Name and Location filter is created. |
Blank |
None. |
|
Maximum FAT32 file size (MB) |
What is the maximum FAT32 file size allowed? |
Defines the maximum DNA file size that can be created on FAT32 systems. |
Defaults to 4096 MB |
None. |
|
Maximum NTFS file size (Mb) |
What is the maximum NTFS file size allowed? |
Defines the maximum DNA files size that can be created on NTFS systems. |
Defaults to 0 (no limit) |
None. |
|
Maximum FAT file size (MB) |
What is the maximum FAT file size allowed? |
Defines the maximum DNA file size that can be created on a FAT file system. |
Defaults to 2048 |
None. |
|
Maximum registry value size (KB) |
What is the maximum registry value size allowed? |
Defines the maximum registry value size that can be created. |
Defaults to 64 (KB) |
None. |
|
Maximum mapped file size (Kb) |
What is the maximum file size for mapped files? |
This option only limits the mapping of files exceeding the maximum value. Files exceeding the maximum file size are migrated to the destination machine but not mapped. When large files are mapped, it can affect performance and memory use. |
Defaults to 10 KB. |
None. |
|
Maximum VSS Timeout (ms) |
What is the maximum time in milliseconds after which VSS must time-out? |
This option is used to configure the time-out limit for VSS in milliseconds. |
Defaults to 120,000 ms |
None. |
|
Uncompressible file list |
What types of files should not be compressed during the creation of a DNA file. |
The uncompressible file list contains file extensions that should not be compressed when creating a DNA file. |
File names separated by a pipe '|'.
Defaults to: Z|ZIP|RAR|ARJ|ACE|LZH| |
This option is only valid if Compression is turned on. |
|
Path for registry exclusion list |
What is the path to the registry exclusion list file? |
The registry exclusion list file contains a list of registry items to be excluded from a migration. |
Valid path and file name. Defaults to CA DMM reg exclude.dnax. |
This option should not be changed unless you have modified the location of the default exclusion list. |
|
Path for non-register exclusion list |
What is the path to the non-registry exclusion list file? |
The non-registry exclusion list file contains a list of files not to be registered during a migration. |
Valid path and file name. Defaults to CA DMM Non Register exclude.dnax |
This option should not be changed unless you have modified the location of the default non-registry exclusion list file. |
|
Path for DMM memory map |
What is the path to save a DMM memory map log? |
During the creation of a DNA file, certain file corruptions are detected and a Debug log is written to this location. |
Valid path and file name. File name defaults to DNAMemoryMap.log |
None. |
|
Path for file exclusion list |
What is the path to the exclusion list file? |
The file exclusion list contains a list of files to be excluded during a migration. |
Valid path and file name. File name defaults to Desktop DNA exclude.dnax |
This option should not be changed unless you have modified the location of the default exclusion list file. |
|
Path for NTFS stream exclusion list |
What is the path to the NTFS stream exclusion list file? |
The NTFS stream exclusion list contains a list of NTFS stream names to be excluded during a migration. |
Valid path and file name. File name defaults to Desktop DNA NTFS stream exclude.dnax.
|
None. |
|
Verify DNA file |
Do you want to add the checksum and verify the DNA file? |
If true, when a DNA file is created, a checksum is calculated and saved in the file. Upon opening a DNA file, a verification takes place ensuring the file matches the checksum. |
1 = True 0 = False Defaults to False This will slow the creation and opening of a DNA file. |
None. |
|
Virtual memory (Mb) |
How much disk space should be available for virtual memory? |
CA DMM will not run unless there is at least this much disk space (MB) available on the drive which contains the virtual memory swap file. |
Defaults to 100 MB |
None. |
|
Don't warn of virtual memory |
Do you want the user to be warned if virtual memory runs low during a migration? |
If true, a message displays, warning the user that virtual memory space is running low. |
1 = True 0 = False Defaults to True |
None. |
|
Non-fatal migration errors |
What are the Win32 error numbers that if encountered should not abort a migration? |
The entered list of Win32 error numbers, if encountered, will not abort a migration. |
Valid Win32 error numbers Defaults to 0,2,3,5,30,32,183,206,1005 |
None. |
|
Use date for script compare |
Do you want an error message to display if the script dates are different between the source and destination systems? |
If true, when performing a real time migration, a message displays to the user if the source and destination have scripts with different dates. |
1 = True 0 = False Defaults to False |
None. |
|
Open DNA file with no items selected |
Do you want to open a DNA file with none of the items selected? |
If true, the DNA file is loaded with no items selected to migrate. This lets you open a template and apply only what is selected in the template (selective apply). |
1 = True 0 = False Defaults to False. |
Must be used on the destination machine when opening a DNA file. |
|
Detect scripts as every selected user |
Do you want to detect system and application scripts based on settings for all selected users or only on the currently selected user? |
If false, detection for multiuser migration finishes faster on slow systems with the potential of not detecting some user-specific settings in rare cases. Use true to guarantee that all possible settings are displayed. Note: Some older scripts might require multiuser detection to function properly. |
1 = True 0 = False Defaults to true. |
None. |
|
Don't stop Windows Explorer |
Do you want to prevent CA DMM from stopping Windows Explorer during migration? |
If true, Windows Explorer will not be stopped during the migration. |
1 = True 0 = False Defaults to False
|
None. |
|
Don't restart Windows Explorer |
CA DMM may stop Windows Explorer during migration. Do you want to prevent CA DMM from restarting Windows Explorer after the migration is complete? |
If true, Windows Explorer will not be restarted after the migration has completed. |
1 = True 0 = False Defaults to False
|
None. |
|
Copyright © 2013 CA.
All rights reserved.
|
|