System Migration Assistant Deployment Guide V6

System Migration Assistant Deployment Guide Version 6.
0
Updated: September 29, 2009
Note Before using this information and the product it supports, read the general information in Appendix D, Notices, on page 141.
Maintenance Edition (October 2009) Copyright Lenovo 2008, 2009. LENOVO products, data, computer software, and services have been developed exclusively at private expense and are sold to governmental entities as commercial items as defined by 48 C.F.R. 2.101 with limited and restricted rights to use, reproduction and disclosure. LIMITED AND RESTRICTED RIGHTS NOTICE: If products, data, computer software, or services are delivered pursuant a General Services Administration GSA contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No. GS-35F-05925.
Contents
Preface . . . . . . . . . . . . . . . v Chapter 1. Introducing System Migration Assistant . . . . . . . . . . . . . . 1
How SMA works . . . . . . Typical migration . . . . . Custom Migration . . . . SMA components . . . . . . System requirements. . . . . Hardware requirements. . . Operating systems supported . New features in SMA 6.0 . . . Upgrading from previous releases User account requirements. . . Migrating multiuser profiles . . Migration methods . . . . . PC to PC migration . . . . File transfer migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 2 2 3 3 3 5 5 6 7 8 8 9 SMABAT return codes . . . . . . . . . . . 41
Chapter 5. Best practices . . . . . . . 43

Scenario 1: Migrating a single user . . . . . Example of a config.ini file . . . . . . . Example of a GUI_default_commands.xml file . Example of a Capture.bat file . . . . . . Example of an Apply.bat file. . . . . . . Scenario 2: Migrating a single domain user . . . Example of the capture CD contents . . . . Example of the apply CD contents. . . . . Scenario 3: Migrating multiple users in batch mode Example of a commands.xml file . . . . . Examples of .bat files . . . . . . . . . Scenario 4: Migrating multiple users in batch mode Example of the capture CD contents . . . . Example of the apply CD contents. . . . . Scenario 5: Migrating multiple users . . . . . Example of a config.ini file . . . . . . . Example of a GUI_default_commands .xml file Examples of .bat files . . . . . . . . . Scenario 6: Migrating multiple users . . . . . Example of a commands .xml file . . . . . Example of a Capture.bat file . . . . . . Example of a config.ini file . . . . . . . Example of a GUI_default_commands .xml file Example of an Apply.bat file. . . . . . . . . . . . . . . . . . . . . . . . . . . 43 45 48 50 50 50 52 54 56 58 61 61 64 67 73 75 78 80 81 83 85 85 88 90
Chapter 2. Firewall management . . . . 11

Disabling Disabling Disabling Disabling Disabling the Windows Firewall . . . BlackICE PC Protection . . . McAfee Personal Firewall Plus Norton Personal Firewall . . Check Point Integrity Client . . . . . . . . . . . . . . . . . . . . . 11 12 12 12 13
Chapter 3. System Migration Assistant Customization . . . . . . . . . . . 15

Customizing the standard migration Global options . . . . . . Show Page Options. . . . . Window Title Options . . . . Guidance Text Options . . . Splash Page . . . . . . . Begin Page . . . . . . . TopOptions Page . . . . . Install Method Page . . . . Choice options . . . . . . Other options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 16 17 17 18 18 18 19 19 20
Chapter 6. Application settings available for migration . . . . . . . . 91

Migrating general application settings . . . . . 91 Migrating additional application settings . . . . 108 Creating an application file . . . . . . . . 114 Example of an application.XML file for Adobe Reader. . . . . . . . . . . . . . . 119
Appendix A. File and registry exclusions . . . . . . . . . . . . 129

File and directory exclusions . Registry exclusions . . . . . . . . . . . . . . . . . 129 . 129
Chapter 4. Performing a migration in batch mode. . . . . . . . . . . . . 21

Compatibility with SMA 4.x . . . . . . . . . Syntax of the smabat command. . . . . . . . Creating a command file . . . . . . . . . . Commands that can be used in the command file File-migration commands. . . . . . . . . Printer migration . . . . . . . . . . . Examples of file-migration commands . . . . Creating a command file template . . . . . . Applying a migration file in batch mode . . . . Migrating background local users in batch mode . . Migrating background domain users in batch mode 21 21 23 23 30 34 36 38 39 39 40
Appendix B. Migration of user profiles supported in SMA 6.0 . . . . . . . . 131 Appendix C. Compatibility with earlier versions . . . . . . . . . . . . . 135
Command file . . . . . . Application file . . . . . . Translation of application file . . . . . . . . . . . . . . . . . . . . 135 . 138 . 139
Appendix D. Notices . . . . . . . . 141

Trademarks . . . . . . . . . . . . . . 142
Copyright Lenovo 2008, 2009
iii
iv
System Migration Assistant Deployment Guide Version 6.0
Preface
Information presented in this guide supports ThinkVantage programs and does not support Lenovo 3000 technology. For information regarding Lenovo 3000 technology, refer to the Lenovo Web site located at:
http://www.lenovo.com/thinkvantage
This book provides information about installing and using ThinkVantage System Migration Assistant (SMA) 6.0. This guide is intended for IT administrators, or those responsible for deploying new computers throughout their organizations. SMA is a software tool system that administrators can use to migrate a users work environment from one computer to another. There are two types of migration: custom and typical. A custom migration can be run either from the GUI or from a command line prompt. It requires advanced knowledge of the SMA, and is recommended for such users as IT administrators. A typical migration can be run from the graphic user interface (GUI). It is hidden by default, and IT administrators can reveal the typical migration for all users by changing the SMA configurations. This deployment guide mainly describes the command line interface, and presents useful migration scenarios that are good examples for IT administrators in large organizations. This deployment guide is developed for IT professionals and the unique challenges that they encounter. If you have suggestions or comments, communicate with your Lenovo authorized representative. Periodically, these guides are updated, so check the following Web site for future publications:
http://www.lenovo.com/thinkvantage
vi
Chapter 1. Introducing System Migration Assistant

System Migration Assistant (SMA) is a software tool with which you can migrate a work environment such as the following: v Operating system preferences, such as desktop and network connectivity settings v Files and folders v Customized application settings, such as bookmarks in a Web browser or editing preferences in Microsoft Word v User accounts System administrators can use SMA either to set up a standard work environment for a company or to upgrade an individual users computer. Individual users can use SMA to either back up a computer or to migrate settings and files from one computer system to anotherfor example, from a desktop computer to a mobile computer.
How SMA works

SMA begins by taking a snapshot of the work environment of a computer. It then uses the snapshot as a blueprint and duplicates the work environment on another computer. The computer that SMA takes a snapshot of is the source computer. The computer on which the snapshot is duplicated is the target computer. The source and target computers can be in different physical locations and even in different time zones. SMA migrates the work environment of one computer to another computer in three phases: the capture phase for all users, the apply phase for the user logged on to the computer as a local administrator, and the delayed apply phase for local or domain users who are not logged on during the initial apply phase. There are two possible migration methods: custom and typical migration. The typical migration automatically selects recommended settings and files for migration. The custom migration provides a user interface for selecting or deselecting migration settings. Custom migration is recommended for advanced users. All migration options are available including the creation of a migration file and the ability to begin the migration from the source computer. By default, the typical migration is hidden on the SMA GUI, and can be activated by configuring the config.ini file. For more information on configuring config.ini file, see Table 3 on page 15.
Typical migration
In the capture phase of a typical migration for a single user, the following items are copied from the source computer: v Desktop settings v Printer settings v Network settings v Application settings v Files and folders
These settings and files are transferred directly to the target computer during a PC-to-PC migration. During the apply phase, SMA applies captured settings and files to the target computer.
Custom Migration
In the capture phase of a custom migration for a user logged on as an administrator and other background users not logged at the time of migration, the following items can be selected and copied from the source computer: v v v v v v Desktop settings Printer settings Network settings Application settings Files and directories User profiles for background users
These settings and files are either stored in an SMA migration file or transferred directly to the target computer during a PC-to-PC migration. During the apply phase of a custom migration for a user logged on as an administrator and other background users not logged at the time of migration, SMA performs two tasks: v The migration file is applied to the administrator user of the target computer. You can apply the entire migration file, or you can specify the components of the migration file that you want to apply. v The delayed apply tasks are prepared for other users. When other background users log on to the computer for the first time, the settings for their profiles are applied automatically.
SMA components
SMA has the following components: 1. Executable components: sma.exe A GUI executable file that captures settings and files from a source computer and copies them to a migration file. This executable file also applies the migration file to a target computer. smabat.exe An executable file that provides a command-line interface for use in batch mode. 2. DLL libraries: v SMA 5 DLL v System plug-in DLLs v Capture/Apply plug-in DLLs 3. Control files: GUI_default_commands.XML A command file used to drive the capture and apply process.
config.ini A configuration file used to customize SMA.EXE. <Application name>.xml An application file used to define how to capture and apply a application by SMA.
System requirements
This section presents information about the requirements for hardware and user accounts, and the operating systems supported. It also presents scenarios for migrations.
Hardware requirements
The source computer must meet the following conditions: v The hard disk drive must have 60 MB of free space for the SMA installation files. v There must be free hard disk space required for the temporary files that are created during the capture phase. The size of the temporary files depends on the size of the files that are being migrated. The target computer must meet the following conditions: v The hard disk drive must have 60 MB of free space for the SMA installation files. v There must be free hard disk space required for the temporary files that are created during the apply phase. The size of the temporary files depends on the size of the files that are being migrated. v The target computer must be able to access the SMA migration files. You can use a local area network (LAN), a removable medium (such as a USB removable storage device), or an Ethernet crossover cable. v For a PC-to-PC migration, the target computer must have free space on the hard disk equal to the total size of the migration files.
Operating systems supported

You can install SMA 6.0 on any of the following operating systems: v Microsoft Windows 2000 Professional v Windows XP Home v v v v v v v v Windows Windows Windows Windows Windows Windows Windows Windows XP Professional XP Tablet PC Edition 2005 Vista Home Basic 32-bit and 64-bit Vista Home Premium 32-bit and 64-bit Vista Business 32-bit and 64-bit Vista Ultimate 32-bit and 64-bit 7 Home Basic 32-bit 7 Home Premium 32-bit and 64-bit
v Windows 7 Professional 32-bit and 64-bit v Windows 7 Enterprise 32-bit and 64-bit v Windows 7 Ultimate 32-bit and 64-bit Windows XP Professional, Windows XP Home, and Windows XP Tablet PC Edition 2005 are all sometimes referred to as Windows XP; all versions of Windows Vista
are referred to as Windows Vista; all versions of Windows 7 are referred to as Windows 7 unless a distinction must be made. Note: Migration of user profiles is supported on Windows 2000 Professional, Windows XP, Windows Vista, and Windows 7.
Supported migration scenarios

SMA can migrate a users work environment within and across operating systems. Table 1 shows valid migration scenarios for each operating system. Yes indicates valid migration scenarios; No indicates invalid migration scenarios.
Table 1. Introducing SMA: Supported migration scenarios Operating system running on the target computer Windows XP Tablet PC Edition 2005 Windows XP Home
Windows Vista Home Premium
Windows 7 Home Premium
Windows Vista Home Basic
Windows Vista Business
Windows Vista Ultimate
Windows 2000 Professional
Windows XP Professional
Operating system running on the source computer Windows 2000 Professional Windows XP Home Windows XP Professional Windows XP Tablet PC Edition 2005 Windows Vista Home Basic Windows Vista Home Premium Windows Vista Business Windows Vista Ultimate Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Enterprise
Windows 7 Home Basic
Windows 7 Enterprise Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
No
No
Yes
Yes
No
No
No
No
No
No
No
Yes
No
No
No
Yes
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
Yes
Yes
Yes
No No
No No
No No
No No
No No
No No
No No
No No
No No
No No
Yes No
Yes Yes
Windows 7 Ultimate
Table 1. Introducing SMA: Supported migration scenarios (continued) Operating system running on the target computer Windows XP Tablet PC Edition 2005 Windows XP Home
Windows Vista Home Premium
Windows 7 Home Premium
Windows Vista Home Basic
Windows Vista Business
Windows Vista Ultimate
Windows XP Professional
Operating system running on the source computer Windows 7 Ultimate
Windows 7 Home Basic
Windows 7 Enterprise No
No
No
No
No
No
No
No
No
No
No
No
Yes
Notes: 1. You can migrate your work environment from a 32-bit operating system to a 64-bit operating system. However, you cannot migrate your work environment from a 64-bit operating system to a 32-bit operating system. 2. The source and target computers must run the same language version of Windows.
New features in SMA 6.0

SMA 6.0 has the following new features and improvements: v Supports the Microsoft Windows 7 operating systems: Windows 7 Home Basic 32-bit Windows 7 Home Premium 32-bit and 64-bit Windows 7 Professional 32-bit and 64-bit Windows 7 Enterprise 32-bit and 64-bit Windows 7 Ultimate 32-bit and 64-bit v Supports the following applications: Adobe Illustrator CS4 Adobe Photoshop CS4 AOL Instant Messenger 7.0 Apple iTunes 8.1 Firefox 3.5 Google Picasa 3.1 Internet Explorer 8 Lotus Notes 8.5 Microsoft Windows Media Player 12
Skype 4.0 v Supports new versions of the ThinkVantage Technologies applications: Access Connections 5.4 Password Manager for Client Security Solution 8.3 Rescue and Recovery 4.3
Upgrading from previous releases

You can upgrade to SMA 6.0 from SMA 5.x. You do not have to uninstall the earlier version of SMA before installing SMA 6.0.
Windows 7 Ultimate
The data format of an SMA 6.0 or 5.x migration file is not compatible with SMA 4.x or earlier versions. An SMA profile that is captured by SMA 4.x cannot be applied by SMA 6.0 or 5.x, and vice versa. An SMA 5.x migration file can be applied by SMA 6.0; however, an SMA 6.0 migration file can not be applied by SMA 5.x.
User account requirements

To migrate all settings supported by SMA, log on to an account with administrative privileges on both source and target computers. For more information on user account requirements, see Appendix B, Migration of user profiles supported in SMA 6.0, on page 131. Table 2 shows the types of migration possible and the settings that can be migrated for each type of user accounts.
Table 2. Valid types of migration and settings to be migrated for each type of user accounts Type of user account on both source and target computers Administrator Power user Standard User Limited user
1
Type of migration Multiuser migration Yes No No No PC to PC migration Yes Yes Yes No
Settings System settings Yes Yes

1
Personal settings Yes Yes Yes Yes
No No
The following Network settings cannot be migrated by a user logged on to a power user account: v TCP/IP Configuration v Network Identification v Shared Folders and Drives A user logged on as power user in Windows Vista or Windows 7 cannot migrate the file in the user profile folder and the HKLM registration file. To migrate profiles of multiple users simultaneously or system settings, log on to an account with administrative privileges on both source and target computers. For the detailed description of multiuser migration, see Migrating multiuser profiles on page 7. To perform PC to PC migration you may log on to an account with either administrative or power users privileges.
To migrate personal settings, such as Desktop settings, or files in the user profile pathfor example, C:\Documents and Settings\username, you can log on to an account with limited user privileges. At the delayed apply phase, the user whose profile is being migrated may be logged on to the target computer using a local administrator account, a local limited user account, or a domain client user account.
Migrating multiuser profiles

Three kinds of user accounts are involved in multiuser migration: 1. Foreground logon user A user who is logged on to the computer during the migration. This user must have administrative privileges. SMA must be launched from this user account. This user name appears as one of the Local Users in the GUI User Profiles panel; its check box is always selected and cannot be cleared. 2. Background local users User accounts in the local computer, which are not currently logged on to the local computer. They can be generic user privilege accounts. These users are listed as Local Users in the GUI User Profiles panel. 3. Background domain users User accounts in the network domain, which are not currently logged on to the domain. The domain controller controls their account information, and the local client PC owns their profile information. These users are listed as Network Users in the GUI User Profiles panel of the local computer and as Local Users in the GUI User Profiles panel in the domain controller, if the local policy of the controller PC allows users to log on to the controller PC locally. For information on how to migrate a foreground logon user who is logged on to both source and target computers, see the ThinkVantage System Migration Assistant 6.0 Users Guide. For information on how to migrate background local users in batch mode, see Migrating background local users in batch mode on page 39. For information on how to migrate background domain users in batch mode, see Migrating background domain users in batch mode on page 40. The following restrictions apply to the migration of multiuser profiles: v If the logon user names of on the source computer and target computers do not match, the settings for the background user are not migrated. Only the settings for the logon user are migrated. v To apply the settings, the domain controller must be visible over the network. For a lookup, a domain user must be found in the PDC. v Crossover cable can be used for PC to PC migration of local users, but not for migration of domain users. v To apply domain user profiles, you must first migrate the network domain settings. For more information about migrating network domain settings, see ThinkVantage System Migration Assistant 6.0 Users Guide. v If you are migrating some but not all settings of a domain user profile, you should not select a roaming user profile. If you do, all settings will be migrated by default, and your selections will be overridden. v If you are migrating background users whose account names use Double Byte Character Set (DBCS) characters, the logon passwords for the newly created user accounts at the target computer are set to Passw0rd and are case-sensitive. Note: The migration file must be placed on the local hard disk drive of the target computer. Otherwise the settings for the background local users or the background domain users cannot be applied successfully in the delayed apply phase. If the
migration file is on the network drive or on a removable media drive, SMA may be unable to find it, because such drives may not be ready to use right after the user logs on to the computer.
Migration methods
You can migrate by directly connecting source and target computers over a LAN or by an Ethernet cable, or by use of a removable storage device.
PC to PC migration
You can use a PC-to-PC migration to migrate a work environment directly from the source computer to the target computer. PC-to-PC migration is useful when the source computer does not have enough disk drive space to save the SMA migration file.
Setting up a PC to PC connection
To perform a PC to PC migration, both the source computer and the target computer must have a network interface card (NIC). The TCP/IP protocol must be enabled, and both computers must be nodes in the same LAN. An Ethernet cable enables you to establish a network connection between the source and target computers by the following means: Directly: v Directly using a crossover cable: A crossover cable creates a network connection between two computers by enabling the network interface card (NIC) adapters to connect together in such a manner that the transmit pair from one adapter transmits to the receive pair of the other adapter. This necessary crossover is accomplished through the cable. v Directly using straight-through cable: Some computer models are able to create a network connection using a normal Ethernet cable because the necessary crossover can be accomplished through an updated network interface card (NIC) adapter that supports internal crossovers. This internal crossover enables the computers to establish a direct connection without the need of a network or a crossover cable. Make sure that the IP addresses of both computers specify the same network. On Windows 2000, Windows XP, Windows Vista, and Windows 7, the IP addresses are issued automatically. Indirectly: v Indirectly using a Local Area Network (LAN): A LAN creates a network connection by acting as the bridge between the various computers. The network enables the computers to establish a direct connection without the need of a crossover cable. You can use an Ethernet connection to migrate your data and settings directly to the target computer. However, a small removable memory device, such as a memory key, might still be needed to install the System Migration Assistant application onto the source computer.
Determining connectivity
Complete the following procedure to determine whether a connection is possible between the source and target computers using the current configuration: 1. On the source computer, complete the following procedure: a. Click Start Run, and type cmd.
2. 3. 4. 5.
b. At the command prompt, type IPCONFIG and press Enter. This displays the current IP address of the computer. c. Record the IP address of the computer. Repeat the above procedure on the target computer. At the command prompt on the source computer, type PING xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the IP address of the target computer). Verify that the source computer receives a reply from the target computer and not a Request timed out. At the command prompt on the target computer, type PING xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the IP address of the source computer).
6. Verify that the target computer receives a reply from the source computer and not a Request timed out. If the above procedure is successful, then the two computers can communicate successfully over the network. If the procedure is unsuccessful, verify that all firewalls have been temporarily turned off or configured to allow SMA to make a network connection. For information about managing the firewall, see Chapter 2, Firewall management, on page 11.
File transfer migration

File transfer migration enables you to perform a migration without establishing the network connection. You will need a removable media, such as USB hard disk drive with enough free space on it to save a migration file. File transfer migration is useful when the source computer and the target computer are in different locations and a network connection between them cannot be established.
10
Chapter 2. Firewall management

When the System Migration Assistant (SMA) attempts to perform a PC-to-PC migration, a network connection must be established between the source and target computers. Firewall applications are security systems that regulate network connections between computers. In order for SMA to establish a connection, any firewall software on the computers must be either disabled or configured to allow SMA network access. Important: 1. If you are experiencing problems establishing a PC-to-PC connection, a firewall application might be blocking the connections. Disabling firewalls might solve the issue. Read this section for information about disabling firewall applications. 2. If you are using VPN connections (such as AT&T Network Client, etc), failing to disable the firewalls on both source and target computers may disable the delay migration function. Perform one of the following actions to allow the source and target computers to establish a network connection: Disable the firewall By turning off the firewall, the computers can accept a network connection. Typically, the firewall can be turned off by opening the firewalls utility panel and selecting either Off or Disabled. Both computers must have their firewalls disabled. Configure the firewall to allow SMA access A firewall application keeps a list of approved applications for which the firewall will accept an incoming network connection. By adding SMA to this list, the computer can accept the network connection from the other computer. Both the source and target computers must have SMA added to their approved application list. Refer to the specific firewall applications documentation for instructions about adding applications to the approved application list. For information about configuring Windows Firewall, refer to the Microsoft Windows Help. The following procedures are examples of how to disable some popular firewall applications. Note: These procedures are only examples of how to disable the firewall applications. For complete instructions, refer to the documentation of your firewall application.
Disabling the Windows Firewall

The following procedure is an example of how to disable the Windows firewall application. Actual procedures might vary. For more specific procedures, refer to the Microsoft Windows documentation. 1. Log on to Windows using a user that is a member of the Administrators group. 2. Open the Network Connections folder, right-click the desired connection, and select Properties.
11
3. Select the Advanced tab. 4. Click Settings for Windows Firewall. 5. Click Off (not recommended).
Disabling BlackICE PC Protection

The following procedure is an example of how to disable the BlackICE(TM) PC Protection firewall application. Actual procedures might vary based on the version of the application installed on your computer. For more specific procedures, refer to the BlackICE(TM) PC Protection documentation. 1. Right-click the BlackICE icon in the system tray. 2. Select Stop BlackICE Engine. BlackICE stops monitoring incoming traffic and a red diagonal line appears over the BlackICE icon. 3. Right-click the BlackICE icon again. 4. Select Stop BlackICE Application Protection. BlackICE stops monitoring the system for unauthorized applications and applications connecting to the network.
Disabling McAfee Personal Firewall Plus

The following procedure is an example of how to disable the McAfee Personal Firewall Plus firewall application. Actual procedures might vary based on the version of the application installed on your computer. For more specific procedures, refer to the McAfee Personal Firewall Plus documentation. 1. Double-click the McAfee SecurityCenter icon in the system tray. The McAfee SecurityCenter opens. 2. On the left side of the window, click Personal firewall plus. 3. On the top-right side of the window, click Disable personal firewall plus. An alert window opens 4. Click Yes. Note: You can also disable the McAfee Personal Firewall Plus application by right-clicking on the McAfee SecurityCenter icon in the system tray and selecting Personal Firewall > Disable.
Disabling Norton Personal Firewall

The following procedure is an example of how to disable the Norton Personal Firewall application. Actual procedures might vary based on the version of the application installed on your computer. For more specific procedures, refer to the Norton Personal Firewall documentation. 1. Double-click the Norton Internet Security icon in the system tray. 2. On the left side of the window, click Norton Internet Security and click Status & Settings. 3. On the right side of the window, click Personal Firewall, then Turn Off. The Protection Alert window opens. 4. Click OK. Note: You can also disable the Norton Personal Firewall application by right-clicking on the Norton Internet Security icon in the system tray and selecting Disable Norton Internet Security.
12
Disabling Check Point Integrity Client

The following procedure is an example of how to disable the Check Point Integrity Client firewall application. Actual procedures might vary based on the version of the application installed on your computer. For more specific procedures, refer to the Check Point Integrity Client documentation. 1. Double-click the Check Point Integrity Client icon in the system tray. 2. On the left side of the screen, click Firewall. 3. On the right side of the window, set Internet Zone Security to Low.
Chapter 2. Firewall management
13
14
Chapter 3. System Migration Assistant Customization

This chapter describes the customization options available for the System Migration Assistant Graphical User Interface (GUI).
Customizing the standard migration Global options

Table 3 presents information about the settings of the Global options.
Table 3. Config.ini file: Global options settings Variable Import_Command_File Values Fully qualified file name What it does Specifies the name and path of the command file used for capture. All the default selections in the source computer, except the password protection setting, can be customized in the command file. To protect the migration file with a password by default, set Enable_Password_protection to Yes. Specifies the name and path of the command file used for apply. All the default selections, except the password protection setting, can be customized in the command file. Specifies the name and path of the command file to be generated. It is set to (install directory)\commands.xml Specifies whether a migration file is to be created. To create a command file template without creating a migration file, set Just_Create_Command_File to Yes. The command file will then be generated as specified by Export_Command_File. To warn the user that a migration file cannot be written to a FAT32 partition if the migration file is larger than 4 GB, set this variable to Yes. Specifies the name and path of the executable file with options. The executable can be run as preprocess before SMA starts. To reveal the page for selecting from typical migration and custom migration, set this variable to Yes. To prompt the user to pick up a previously selected file, set this variable to Yes. To prompt the user to type the P2P keyword on source computer, set this variable to Yes. To prompt user to specify the migration file location, set this variable to Yes To prompt the user to start the process of creating or applying the settings from the SMA migration file, set this variable to Yes.
Import_Command_File_For_Apply
Fully qualified file name
Export_Command_File
Fully qualified file name Yes or No
Just_Create_Command_File
Enable_4GFat32_warning
Yes or No
Preprocess_Executable
Fully qualified file name Yes or No
Begin_Page_Show_Page
Show_Previous_File_Selection_Dialog Show_P2P_Messagebox Show_File_Dialog Show_Start_Processing_Dialog
Yes or No Yes or No Yes or No Yes or No
15
Table 3. Config.ini file: Global options settings (continued) Variable Show_Reboot_Dialog Show_All_Progressbar_Dialogs Show_All_Warning_Dialogs Enable_Password_Protection Values Yes or No Yes or No Yes or No Yes or No What it does To prompt the user to restart the machine, set this variable to Yes. To display dialogs to user during processing in progress, set this variable to Yes. To show all warning messages to the user, set this variable to Yes. To make the check box for password option active, set this variable to Yes. This option applies only to the source computer. To disable the AT&T Net firewall automatically, set this variable to Yes.
ATTFW_Auto_Disabled
Yes or No
Show Page Options

The Show/Not Show Window Options section contains the following variable:
SpecificPage_Page_Show_Page
where SpecificPage is one of the following: v Splash v v v v v Welcome Begin TopOptions MigOptions Profiles
v Desktop v Applications v v v v v v Network Printers Selection AutoManual P2P_Logon P2P_Auto_SRC
v P2P_Manual_TGT v P2P_Manual_SRC v v v v v P2P_SourceIni P2P_Keyword Receive_Data Log SummaryTypical
Note: The Begin page is the Which computer are you using? window. The TopOptions page is the Select a migration type window. The AutoManual page is the Install System Migration Assistant window. The pages with P2P_ are the Establishing a connection windows.
16
If you dont want the window to open when you run SMA, set this variable to No. Otherwise, set it to Yes or leave it unspecified. When a window is not displayed, SMA captures or applies the default settings specified in the imported command file.
Window Title Options

The Window Title Options section contains the following variable:
SpecificPage_Page__Title
where SpecificPage is one of the following: v Welcome v Begin v TopOptions v MigOptions v v v v v v Profiles Desktop Applications Network Printers Selection
v AutoManual v P2P_Logon v v v v v P2P_Auto_SRC P2P_Manual_TGT P2P_Manual_SRC P2P_SourceIni P2P_Keyword
v Receive_Data v Log v SummaryTypical Note: The Begin page is the Which computer are you using? window. The TopOptions page is the Select a migration type window. The AutoManual page is the Install System Migration Assistant window. The pages with P2P_ is the Establishing a connection windows. This variable specifies the alternative text that will be displayed as a page title.
Guidance Text Options

The Guidance Text Options section contains the following variable:
SpecificPagePage_Guidance_Text
where SpecificPage is one of the following: v v v v v Welcome Begin TopOptions MigOptions Profiles
17
v v v v v v v v v v v v
Desktop Applications Network Printers Selection AutoManual P2P_Logon P2P_Auto_SRC P2P_Manual_TGT P2P_Manual_SRC P2P_SourceIni P2P_Keyword
v Receive_Data v Log v SummaryTypical Note: The Begin page is the Which computer are you using? window. The TopOptions page is the Select a migration type window. The AutoManual page is the Install System Migration Assistant window. The pages with P2P_ is the Establishing a connection windows. This variable specifies the alternative text that will be displayed as the guidance text.
Splash Page
Splash Page section contains the following variable: v Splash_Page_Display_Time This variable specifies the length of time, in seconds, that the splash screen is displayed. By default, Splash_Page_Display_Time is set to 2.
Begin Page
The Begin Page section contains the following variable:
Begine_Page_Choice_Type
This variable specifies the migration type, either Typical or Custom.
TopOptions Page
TopOptions Page section contains the following variables: v TopOptions_Page_Choice_Mode v TopOptions_Page_Choice_TransferMode v TopOptions_Page_Target_Initiated_Migration TopOptions_Page_Choice_Mode specifies the migration mode. If this is the PC you want to move to, set Target. If this is the PC you want to move from, set Source.
18
TopOptions_Page_Choice_TransferMode specifies the way to migrate. To send captured files and settings directly to the target computer, set it to P2P. To copy files and settings by use of a removable storage device, set it to FileTransfer. TopOptions_Page_Target_Initiated_Migration specifies the Target Initiated migration. This variable is effective only when TopOptions_Page_Choice_Mode is Target and TopOptions_Page_Choice_TransferMode is P2P. If you set this variable to Yes, you can choose target initiated migration.
Install Method Page

The Install Method Page section contains the following variable:
InstallMethod_Page_Choice_Method
Select Auto for network installation or Manual to copy the install to removable media.
Choice options
This section provides information about variables that contain the following string:
_Choice
These variables are in the Migration Options Page, Desktop Page, and Network Page sections of the config.ini file. They control whether check boxes are displayed or hidden, active or not available, or selected by default.
Values
Each such variable takes the following value:
OptionDisplay, OptionActive, OptionSelected
where v OptionDisplay is one of the following values: HIDE hides the check box. DISPLAY displays the check box. v OptionActive is one of the following values: ENABLED specifies that the check box is active. DISABLED specifies that the check box is not available. If OptionDisplay is set to HIDE, SMA ignores this variable. v OptionSelected is one of the following values: CHECKED specifies that the radio button or the check box is selected by default. UNCHECKED specifies that the radio button or check box is cleared by default. OptionSelected is available only for the Migration Options page section.
Examples
Consider the following examples: v The Colors check box on the Desktop Settings page is displayed, but the user cannot clear the check box.
Desktop_Page_Choice_Colors = Display, Disabled
v The Files and Folders check box on the Migration Options page is displayed, and the check box is cleared but cannot be selected.
Options_Page_Choice_Files = Display, Disabled, Unchecked
19
v The Task Bar check box is not displayed on the Desktop settings page. However, if the task bar settings are selected by default, they are selected and captured automatically .
Desktop_Page_Choice_ Task_Bar = Hide, Checked.
v The Printers check box is not displayed on the Options page. However, it is selected and captured automatically.
Options_Page_Choice_Printers = Hide, Checked.
Other options
Table 4 presents information about additional variables in the config.ini file.
Table 4. Config.ini file: Other options Variable Applications_Page_Show_Registry_Button Value Yes or No What it does Specifies whether the registry button is to be displayed on the Application Settings window. The default is No. To prompt the user to set a new password for all user profiles to migrate, set this variable to Yes. The default value is No. This option applies only to the target computer. Specifies the maximum amount of uncompressed data (in MB) that can be captured. Specifies an alternative warning message that is displayed when the user selects files with certain extensions. Specifies file extensions that will cause a warning message to be issued when the user selects files with such extensions. You must specify each extension on a separate linefor example: [Selection_Page_Warning_Extensions_Start] exe com dll [Selection_Page_Warning_Extensions_End]
Profiles_Page_Show_GlobalPassword_Dialog Yes or No
Selection_Page_File_Quota
Number (MB)
Selection_Page_File_Warning_Message
A text string
Selection_Page_Warning_Extensions
File extensions
20
Chapter 4. Performing a migration in batch mode

This chapter presents information about performing a migration in batch mode.
Important Be sure to close all applications before you start the migration. You can use GUI or batch mode migration interchangeably. File migration functions the same in both modes; the difference is that in batch mode you select files and folders by including and excluding characteristics. The migration files produced in the GUI and batch mode are the same. If you create a migration file in batch mode, you can open it and examine the contents by use of the user interface. You can also use the GUI to create a command-file template, although you must add file migration criteria manually. Notes: 1. The following migration files will be created at the specified directory v *.sma : Base migration file v *.sma.DriveC : Migration files for Drive C: v *.sma.DriveX : Migration files for Drive X: (in case user selects migrating files in drive X) 2. Do not select the d:\_SMA directory, where d: is the drive on which SMA has been installed. This directory is a temporary folder used by SMA.
Compatibility with SMA 4.x

SMA 6.0 and SMA 5.x use XML technology to describe the data captured for migration. The command file has been changed to the XML file format. However, for compatibility with version 4.2, SMA 6.0 and 5.x have been designed to handle earlier command file formats as well. For detailed information about the compatibility of the two versions, refer to Appendix C, Compatibility with earlier versions, on page 135.
Syntax of the smabat command

The SMA executable file is smabat.exe. It is started from the command prompt. If you installed SMA in the default location, it is in the d:\Program Files\ThinkVantage\SMA directory, where d is the drive letter of the hard disk drive. The syntax of the smabat command is as follows:
smabat /c :cmdfile [/n smafile] | /a [cmdfile] /n smafile [options]
Notes: 1. If a fully qualified file name includes any spaces, as in c:\Program Files\ThinkVantage\SMA\Commandfile.xml, you must enclose the file name in quotation marks, as follows: "c:\Program Files\ThinkVantage\SMA\ Commandfile.xml"
21
2. Specified smabat commands override the settings in the command file. For example, if you specify the location of a log file in the command file, that specification is always overridden by the command /o logfile. 3. In order to show the smabat command syntax help on Windows Vista, you need to open the command prompt with the Run as Administrator option.
The primary parameters of the SMABAT command are described in Table 5.

Table 5. Primary SMABAT parameters Function Capture Syntax /c cmdfile /n smafile where v cmdfile is the fully qualified file name of the command file. v /n smafile is an optional parameter that specifies an alternative migration file, and smafile is the fully qualified name of the migration file. What it does Captures the files and settings specified in the command file, and creates a migration file. By default, the migration file is written to the directory that is specified in the command file. If you wish, you can write the migration file to some other directory. Applies the files and settings specified in the migration file. You can also choose to run a command file against the migration file before it is applied to the target computer. Specifies the location of the log file.
Apply
/a cmdfile /n smafile where v cmdfile is an optional parameter that specifies a command file. v smafile is the fully qualified name of the migration file.
Log file
/o logfile where logfile is the fully qualified file name of the log file.
Temporary directory
/t tmpdir where tmpdir is the fully qualified name of the temporary SMA directory. /p smapwd where smapwd is one of the following values: v The password used to password-protect a migration file during the capture phase v The password used to access a password-protected migration file during the apply phase Each password must meet the following criteria: v It must contain from 6 characters to 16 characters. v Neither the first nor the last one may be a numeral. v It must have no two consecutive identical characters.
Specifies the location of the temporary SMA directory.
Password
Specifies the password for an SMA migration file.
Apply by PC to PC migration
/a /p2p keyword /n smafile where v keyword is used to establish PC-to-PC connection. v smafile is used to specify the migration file to be saved; it is the fully qualified name of the migration file.
Optional command used to apply the files and settings by PC-to-PC migration. smafile is used to save the received migration file.
22
Creating a command file

During the capture phase, smabat.exe reads the contents of the command file and creates a migration file. This section explains command files and the statements they can contain. SMA provides an example of a command file, GUI_default_commands.xml, that you can use as a template to create a customized command file. If you installed SMA in the default location, this file is in the d:\Program Files\ThinkVantage\ SMA directory, where d is the drive letter of the hard disk drive. Note: SMA 6.0 uses XML technology to describe the commands in the command file. SMA 6.0 is designed to handle the command files of version 4.2. If you want to use an older command file, and need detailed information about the compatibility of versions 6.0 and 5.2, see Appendix C, Compatibility with earlier versions, on page 135. Consider the following points concerning SMA 6.0 command files: v They use the syntax of XML version 1.0. v The command file is case-sensitive. v Each command and parameter section must start with <TagName> and end with </TagName>, and its value must be specified between those tags. v Syntax errors might cause an error when you run SMA. If SMA encounters an error, it writes an error message to the log file and continues the operation. If the error is severe, the end results might be flawed.
Commands that can be used in the command file

Table 6 presents information about the commands that can be used in a command file, except for those related to file migration or the registry. Windows Environment Variables can be used to specify a specific folder and its subfolders for the current logon user, such as %windir%, %USERPROFILE%, or %ProgramFiles%.
Table 6. Commands that can be used in the command file Command <Password> Parameters <PlainPassword> Parameter values and examples To encrypt the migration file with a password, set <PlainPassword> to an alphanumeric string, containing from 6 to 16 characters. If you issue the /p parameter from the command line prompt with smabat.exe, the password you specify overwrites any password set in the command file. In a PC-to-PC migration, a password option will work only if you set it to create the SMA migration file.
23
Table 6. Commands that can be used in the command file (continued) Command <TransferMode> Parameters <mode> Parameter values and examples To perform a PC-to-PC migration, set the parameter to P2P. Otherwise, leave it unspecified. For example: To migrate via a PC-to-PC connection <TransferMode> <mode>P2P</mode> </TransferMode> To migrate by migration file: <TransferMode> <mode></mode> </TransferMode> <P2P> <connection_id> To establish a PC-to-PC connection between the source computer and the target computer, specify an alphanumeric string. For example: <P2P> <connection_id>mykeyword</connection_id> </P2P> <FilesAndFolders> <run> To enable File-migration commands, set this parameter to True. Otherwise set it to False or leave it unspecified. To specify the path and file name of the migration file, set <filename> to the path and file name of the migration file. For example: <ArchiveFile> <filename>C:\SMA5\MyData.sma></filename> </ArchiveFile> You can also specify the location of the migration file by using the following notation: \\my computer\temp\MyData.sma In default, the migration files include the following files: v *.sma : Base migration file v *.sma.DriveC : Migration files for Drive C: v *.sma.DriveX : Migration files for Drive X: (in the event that the user selects some migrating files in drive X) To have the same migration file format as SMA5.0 or SMA5.1, refer to the quick_zip_mode option in the MISC section in this table.
<ArchiveFile>
<filename>
24
Table 6. Commands that can be used in the command file (continued) Command <Desktop> Parameters v <desktop_settings> v <accessibility> v <active_desktop> v <colors> v <desktop_icons> v <display> v <icon_metrics> v <keyboard> v <mouse> v <pattern> v <screen_saver> v <sendto_menu> v <shell> v <sound> v <start_menu> v <taskbar> v <time.zone> v <wallpaper> v <window_metrics> <Network> v <ip_subnet_gateway_configura tion> v <dns_configuration> v <wins_configuration> v <computer_name> v <computer_description> v <domain_workgroup> v <mapped_drives> v <dialup_networking> v <microsoft_networking> v <odbc_datasources> <Applications> <Application> For a list of the applications supported, see Chapter 6, Application settings available for migration, on page 91. To capture or apply the application settings supported, specify the application name as a parameter in the command file. For example: <Applications> <Application>Lotus Notes</Application> <Application>Microsoft Office</Application> </Applications> or <Applications> <Application>$(all)</Application> </Applications> To select a network setting, set this parameter to True. Otherwise set it to False or leave it unspecified. For example: <Network> <computer_name>true</computer_name> <mapped_drives>false</mapped_drives> </Network> Parameter values and examples To select a desktop setting, set this parameter to True. Otherwise set it to False or leave it unspecified. For example: <Desktop> <colors>true</colors> <desktop_icons>true</desktop_icons> <screen_saver>true</screen_saver> <start_menu>false</start_menu> <time_zone>true</time_zone> </Desktop>
25
Table 6. Commands that can be used in the command file (continued) Command <IncUsers> Parameters <UserName> Parameter values and examples To capture all user profiles, set (all) or use * as a wildcard for all users. Otherwise specify users individually. The following wildcards are available: v * for a variable-length wildcard v % for a fixed-length wildcard (1 character) For example: <IncUsers> <UserName>administrator</UserName> <UserName>Domain\Jim</UserName> <IncUsers> <ExcUsers> <UserName> To exclude a user from the migration process, specify the domain and user name of that user. The following wildcards are available: v * for a variable-length wildcard v % for a fixed-length wildcard (1 character)
26
Table 6. Commands that can be used in the command file (continued) Command <Printers> Parameters <Printer> <PrinterName> <AddPrinter> <PrinterType> <PrinterName> <PortName> <DriverName> <InstallExePath> <InfFilePath> Parameter values and examples This control statement is effective for both source and target computers. To capture all printers, set the parameter to $(all). Otherwise specify each printer individually. To capture the default printer only, set the parameter to $(DefaultPrinter). For example, <Printers> <Printer>$(all)</Printer> </Printers> <Printers> <Printer> <PrinterName>IBM 5589-L36</PrinterName> <Printer> </Printers> <Printers> <Printer>$(DefaultPrinter)</Printer> </Printers> You can capture either All, Default, or you can specify an individual printer by name. If you specify multiple printers, only the first one you specify will be processed; the rest will be ignored, and a warning message will be issued. For more information about migrating printer settings, see Printer migration on page 34.To add new printers, use the <AddPrinter> tag. This control statement is effective only for the target computer. For example,  <Printers> <AddPrinter> <PrinterType>OS built-in</PrinterType> <PrinterName>IBM 4029 LaserPrinter</Printer Name> <PortName>LPT1:</PortName> <DriverName>Parallel</DriverName> <InstallExePath /> <InfFilePath /> </AddPrinter> </Printers>
27
Table 6. Commands that can be used in the command file (continued) Command <Printers> (continued) Parameters Parameter values and examples  <Printers> <AddPrinter> <PrinterType>Network</PrinterType> <PrinterName>\\Server\IBM 5589-L36 </PrinterName> <PortName /> <DriverName /> <InstallExePath /> <InfFilePath /> </AddPrinter> </Printers>  <Printers> <AddPrinter> <PrinterType>UserProvided</PrinterType> <PrinterName>My Private Printer </PrinterName> <PortName /> <DriverName /> <InstallExePath>c:\SMA5\temp\printer\ install.exe</InstallExePath> <InfFilePath /> </AddPrinter> </Printers>  <Printers> <AddPrinter> <PrinterType>UserProvided</PrinterType> <PrinterName>My Canon Printer</PrinterName> <PortName>USB</PortName> <DriverName>Canon i320</DriverName> <InstallExePath /> <InfFilePath>c:\myprinter\i320.inf</InfFile Path> </AddPrinter> </Printers>  <Printers> <AddPrinter> <PrinterType>UserProvided</PrinterType> <PrinterName>My HP Printer</PrinterName> <PortName>USB</PortName> <DriverName>hp deskjet 995c series </DriverName> <InstallExePath /> <InfFilePath>c:\HP995C\hpf995k.inf</InfFile Path> </AddPrinter> </Printers> For more information about migrating printer settings, see Printer migration on page 34.
28
Table 6. Commands that can be used in the command file (continued) Command <MISC> Parameters <bypass_registry> Parameter values and examples To deselect all registry settings, set this parameter to true. Otherwise set it to False or leave it unspecified. To overwrite existing files, set this parameter to true. Otherwise, set it to False or leave it unspecified. To copy only icons that have active links, set this parameter to true. Otherwise, set it to False or leave it unspecified. To restart the computer automatically after a target-side migration is completed, set this parameter to 1. To display a pop-up window asking whether the user wants to reboot the computer, set it to 2. Otherwise set it to 0 or leave it unspecified. To display the dialog message that SMA is migrating user data at the delayed apply phase, set this parameter to True. Otherwise set it to False or leave it unspecified. To specify the maximum amount of uncompressed data (in MB) that can be captured, set this parameter to a valid value. To specify the directory to which SMA writes log files, enter a fully qualified directory name. You can specify a shared directory on another computer. If you do not set this parameter, SMA writes log files to d:\SMA_Installed_Directory, where d is the drive letter of the hard disk drive, and \SMA_Installed_Directory is the directory in which SMA is installed. <file_span_size> <user_exit_after_apply> Specify a size in KB. When a migration file reaches this size, it will be spanned. To launch an application after migration is completed, set this parameter to the fully qualified name of an executable file. To launch an application after create migration files, set this parameter to the fully qualified name of an executable file. In order not to apply the source PC logon user settings to the target PC logon user, set this parameter to True. Otherwise, set it to False or unspecified. To save the migration file at target computer via a PC to PC connection, set this parameter to True. Otherwise set it to False or leave it unspecified. To compress the migration file, set this parameter to 1. Otherwise, set it to 0 or leave it unspecified.
<overwrite existing files>
<resolve_icon_links>
<autoreboot>
<PromptBeforeDelayedApply>
<quota/>
<log_file_location>
<user_exit_after_capture>
<cancel_logon_user>
<P2PArchiveFile >
<compression_level>
29
Table 6. Commands that can be used in the command file (continued) Command <MISC> (continued) Parameters <quick_zip_mode> Parameter values and examples To create migration files in faster mode, set this parameter to True or leave it unspecified. Otherwise, set it to False. In default, the migration files include the following files: v *.sma : Base migration file v *.sma.DriveC : Migration files for Drive C: v *.sma.DriveX : Migration files for Drive X: (in the event that the user selects some migrating files in drive X) To get the same migration file format as SMA5.0/5.1, set this parameter to false <temp_file_location> To specify the directory to which SMA writes temporary files, enter a fully qualified directory name. You can specify a shared directory on another computer. If you do not set this parameter, SMA writes temporary files to d:\SMA_Installed_Directory\etc\ data, where d is the drive letter of the hard disk drive, and \SMA_Installed_Directory is the directory in which SMA is installed. <Registries> <Registry> <hive> <keyname> <value> To capture or apply the registry settings, specify the hive, keyname, and value as the parameters in the command file. For example, <Registry> <hive>HKCU</hive> <keyname>Software\Lenovo\SMA</keyname> <value></value>
File-migration commands
When SMA processes file-migration commands, it processes the file inclusion commands first, and then the file exclusion commands for the inclusion files. You no longer have to specify the order in which inclusion and exclusion commands are to be processed, as was necessary in SMA 4.2. SMA selects and deselects files on the basis of the original location of files and folders on the source computer. File redirection statements are stored in the migration file and are interpreted during the apply phase. The processing of file and directory names is not case-sensitive. Table 7 on page 31 presents descriptions of the file-migration commands. All file-migration commands are optional.
30
Table 7. File-migration commands Command <FilesAndFolders> Parameter <run> What it does To capture or apply file migration, set this parameter to True. Otherwise set it to False or leave it unspecified. For example: <FilesAndFolders> <run>true</run> </FilesAndFolders> <ExcludeDrives> <Drive> Specify the drive letter of each drive you want to exclude from being scanned. For example: <ExcludeDrives> <Drive>D</Drive> <Drive>E</Drive> </ExcludeDrives>
31
Table 7. File-migration commands (continued) Command <Inclusions> Parameter <IncDescription> <Description> <DateCompare> <Operand> <Date> <SizeCompare> <Operand> <Size> <Dest> <Operation> where <Description> is the fully qualified filename. You can use wildcard characters for both the file name and the folder name. <DateCompare> is an optional parameter that specifies files according to the date when they were created. <Operand> is either NEWER or OLDER. <Date> is the baseline date, in mm/dd/yyyy format. <SizeCompare> is an optional parameter that can be used to select files by size. <Operand> is either LARGER or SMALLER. <Size> is the file size in MB. <Dest> is an optional parameter that specifies the name of the destination folder on the target computer in which the files will be written. Note: To specify the folder name, add \ at the end of the description Example 2 <IncDescription> <Description>C:\MyWorkFolder\*.*</Description> <DateCompare> <Operand>NEWER</Operand> <Date>07/31/2005</Date> </DateCompare> </IncDescription> Example 3 <IncDescription> <Description>C:\MyWorkFolder\*.*</Description> <SizeCompare> <Operand>SMALLER</Operand> <Size>200</Size> </SizeCompare> </IncDescription> Example 4 <IncDescription> <Description>C:\MyWorkFolder\*.*</Description> <Dest>D:\MyNewWorkFolder</Dest> <Operation>P</Operation> <IncDescription> What it does Searches for all matching files in the directories specified. Example 1 <IncDescription> <Description>c:\MyWorkFolder\ /s</Description> </IncDescription>
32
Table 7. File-migration commands (continued) Command <Inclusions> (continued) Parameter v <Operation> is an optional parameter that specifies how the file path is to be handled. Specify either of the following: P preserves the path of the file and recreates the file on the target computer, starting at the location specified by the <Dest> parameter. R removes the path of the file and places the file directly in the location specified by the <Dest> parameter. <Exclusions> <ExcDescription> <Description> <DateCompare> <Operand> <Date> <SizeCompare> <Operand> <Size> where Deselects all matching files in a specified directory. Example 1 <ExcDescription> <Description>C:\YourWorkFolder\</Description> </ExcDescription> Example 2 <ExcDescription> <Description>C:\YourWorkFolder\</Description> <DateCompare> <Operand>OLDER</Operand> <Date>07/31/2005</Date> </DateCompare> </ExcDescription> What it does
v <Description> is a fully qualified file name or folder name. It can contain wildcard characters for both the file Example 3 name and the folder name. <ExcDescription> v <DateCompare> is an <Description>C:\YourWorkFolder\</Description> optional command that you <SizeCompare> can use to select files by the <Operand>LARGER</Operand> date when they were created: <Size>200</Size> </SizeCompare> <Operand> is either </ExcDescription> NEWER or OLDER. <Date> is the baseline date, in mm/dd/yyyy format. v <SizeCompare> Optional parameter to select files by size. <Operand> is either LARGER or SMALLER. <Size> is the file size in MB.
33
Note: In the file-migration command XML file, all the <IncDescription> </IncDescription> and <ExcDescription></ExcDescription> tags in the <Inclusions></Inclusions> and <Exclusions></Exclusions> sections should have the same sub-tag structure even though there are no real values for the sub-tags. For example:
<IncDescription> <Description>E:\TempBox\src\test.fm</Description> <Dest></Dest> <Operation></Operation> </IncDescription> <IncDescription> <Description>E:\TempBox\src\test.fm</Description> <Dest>E:\TempBox\tar</Dest> <Operation>r</Operation> </IncDescription> <IncDescription> <Description>E:\TempBox\src\test.fm</Description> <Dest></Dest> <Operation></Operation> </IncDescription>
Printer migration
There are two ways to specify printer settings for the target computer. You can migrate printer settings from the source computer by use of the <Printer> tag, or install new printers by use of the <AddPrinter> tag. A printer can be any of the following: OS built-in printer The printer name is in the ntprint.inf file. Network printer The printer name is in the list of visible network printers. User-provided printer Any printer other than the two mentioned above. Notes: 1. Printers that can not be migrated by SMA are not displayed in the printer list on the SMA GUI. 2. All printers must be visible over the network from both source and target computers. 3. To migrate an LPR port printer, Printer Services must be installed on the target PC: v For Windows 2000 or XP: Click Start, select Control Panel. Double-click Add or Remove Programs, then select Add/Remove Windows components. Select the Other Network File and Print Services checkbox, and click Properties then select the Print Services for UNIX checkbox and click OK.. v For Windows Vista or Windows 7: Open Control Panel, select Programs. Click Turn Windows Features on or off, expand Printer Services, select the LPR Port Monitor checkbox and click OK. Table 8 on page 35 presents the tag combinations for printer migration.
34
Table 8. Tag combinations for printer migration <AddPrinter> tag OS built-in printer * O O O User-provided printer Network printer O O Setup install O O Inf install * O O O O
Tag name <PrinterName> <PrinterType> <InstallExePath> <InfFilePath> <PortName> <DriveName>
<Printer> tag O X X X X X
where O * X must be specified. is optional. If no value is specified, a null tag, such as <PrinterName />, must be added. is not necessary for migration, but there must be a null tag. Even if a value is specified, it will be ignored during the migration. must not be specified.
If the captured printer is set as the default printer on the source PC, it should be set as the default printer for the target PC as well. If the default printer for the source PC is not migrated to the target PC, the OS will determine which of the printers will be set as the default printer. Only common printer settings can be migrated by use of SMA. Settings unique to a printer vendor cannot be migrated. If you have manually installed a revised version of a printer driver built into the OS on the source computer, the original version of that driver will be installed on the target PC. To install the revised version of the OS built-in printer driver on the target PC, specify it by use of the <AddPrinter> tag.
Migration of a printer provided by the user

If the printer you specify is not one of those built into the OS, SMA will install it by use of the install package you provide. The function is then available only on the target PC. Information captured from the source PC will be ignored. You must provide the installation package, specifying the full path to the package on the target computer, and also you must specify the installer program in the package. The following example illustrates how to specify a user-provided printer in the commands.xml file:
<Printers>  <AddPrinter> <PrinterType>UserProvided</PrinterType> <PrinterName>My Private Printer</PrinterName> <InstallExePath>c:\SMA5\temp\printer\install.exe</InstallExePath> <InfFilePath /> <PortName /> <DriverName /> </AddPrinter>
35
 <AddPrinter> <PrinterType>UserProvided</PrinterType> <PrinterName>My Private Printer</PrinterName> <InstallExePath /> <InfFilePath>c:\Windows\inf\myprinter.inf</InfFilePath> <PortName>USB</PortName> <DriverName>IBM Generic USB Printer</DriverName> </AddPrinter> </Printers>
Migration of the network printer

To identify network printers, the following key information is captured: v The printer name v The server name During the capture phase, if the printer whose name is enclosed by the <PrinterName> tags in the <Printer> section is found in the list of network printers, it will be captured. If you specify $(all), all listed printers are captured. During the apply phase, if the printer whose name is enclosed by the <PrinterName> tags in the <Printer> section is found in the network printer list of the migration file, it will be installed. If you specify $(all), all captured printers are installed. Only a printer that is visible over the network can be installed as a network printer on the target PC.
Migration of the OS built-in printer

To identify OS built-in printers, the following key information is captured: v The printer name v Monitor settings v The port name v Driver settings During the capture phase, if the printer whose name is enclosed by the <PrinterName> tags in the <Printer> section is found on the OS built-in printer list of the ntprint.inf file, it will be captured. If you specify $(all), all listed printers are captured. During the apply phase, if the printer whose name is enclosed by the <PrinterName> tags in the <Printer> section is listed in the ntprint.inf file as one of the OS built-in printers, it will be installed.
Examples of file-migration commands

This section presents examples of file-migration commands. These examples demonstrate how to combine file-inclusion and file-exclusion commands to refine your file selection. Only the file-handling sections of the command file are shown.
Selecting files during the capture phase

This section presents four examples of code used to select files during the capture phase.
36
Example 1: The following code selects all files with extension .doc (Microsoft Word documents) and moves them into the d:\My Documents directory. It then excludes all files that are in the d:\No_Longer_Used directory.
<Inclusions> <IncDescription> <Description>*:\*.doc /s</Description> <Dest>d:\My Documents</Dest> <Operation>r</Operation> <IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>d:\No_Longer_Used\</Description> </ExcDescription> </Exclusions>
Example 2: The following code selects the contents of the d drive, excluding all files that are in the root of the d drive and all files that have extension .tmp.
<Inclusions> <IncDescription> <Description<d:\*.* /s</Description> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>d:\*.*</Description> </ExcDescription> <ExcDescription> <Description>*:\*.tmp /s</Description> </ExcDescription> </Exclusions>
Example 3: The following code selects the entire contents of the c: drive, excluding all files that are under %windir%, which specifies a Windows directory.
<Inclusions> <IncDescription> <Description>C:\*.* /s</Description> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%windir%\</Description> </ExcDescription> </Exclusions>
Example 4: The following code selects the entire contents of the %USERPROFILE% folder that is the User Profile Path of the current logon user, excluding all files that have extension .dat and are in the Local Settings subfolder.
<Inclusions> <IncDescription> <Description>%USERPROFILE%\</Description> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%USERPROFILE%\*.dat</Description> </EcxDescription> <ExcDesctription> <Description>%USREPROFILE%\Local Settings\</Description> </ExcDescription> </Exclusions>
37
Note: When describing files or subfolders, be sure to add a backslash \ immediately after each environment variable.
Auto Reboot
This option is specified in the Commands.xml file by use of the autorebootkeyword in the <MISC></MISC> section. Possible values are as follows: 0 (default) At the end of the batch apply process, do not reboot the computer automatically. In order for the settings to take effect, you must later reboot the computer manually. 1 2 At the end of the batch apply process, the computer restarts automatically. SMA prompts you to choose whether to reboot immediately or not. A pop-up window appears, even in a batch process. You always have to intervene.
<MISC> <autoreboot>2</autoreboot> </MISC>
Creating a command file template

You can use the GUI to create a command file template. Then, instead of creating an actual migration file, SMA captures the types of settings that you want to capture. This information is written to a command file, which you can use to capture a migration file in batch mode. Note: Because file migration is handled differently in the two modes, you cannot use the GUI to add file-migration commands to the command file template. To create a command file template, do as follows: 1. Open the config.ini file in an ASCII text editor. If you installed SMA in the default location, this file is in the d:\Program Files\ThinkVantage\SMA directory, where d is the drive letter of the hard disk drive. 2. To ensure that SMA does not create a migration file, change the Just_Create_Command_File option to the following string:
Just_Create_Command_File = Yes
3. Change the Export_Command_File option to specify the name and path of the template file. By default, the Export_Command_File is set to d:\Program FIles\ThinkVantage\SMA\etc\data\commands.xml file, where d is the drive letter of the hard disk drive. 4. Start SMA and run the capture phase. The Migration file Location window is used to capture the location and name of the migration file in the template file, although no actual migration file will be created. 5. (Optional) If you want to add file migration commands, edit the template file and make the appropriate changes. For more information, see File-migration commands on page 30. 6. Reopen the config.ini file in an ASCII text editor, and change the Command_File and the Just_Create_Command_File options back to the default settings.
38
Applying a migration file in batch mode

During the apply phase, the smabat.exe file copies the contents of the migration file to the target computer. You can modify the migration file before it is applied. The following two examples demonstrate the use of smabat command to apply a migration file. In the first example, the selected migration file (receptionist.sma) is applied to the target computer:
smabat /a /n "c:\sma_migration files\receptionist.sma"
In the second example, the selected migration file is modified before it is applied to the target computer. The modifications are specified in the EntryLevel.xml command file:
smabat /a c:\EntryLevel.xml /n "c:\sma_migration files\receptionist.sma"
When you apply a migration file in batch mode, bear the following points in mind: v You cannot add settings or files to a specified migration file. v When SMA processes file exclusion commands during the apply phase, it uses the original location of the files and folders on the source computer, not the redirected location specified during the capture phase. v The <ExcludeDrives> command is ignored. If a file is moved to a directory that already contains a file that has the same name, and if the <overwrite_existing_files> parameter in the command file is set to zero or left unspecified, a numeric string is appended to the name of the relocated file. For example, if the target directory already contains a readme.txt file, the relocated file is renamed readme_01.txt. If additional files named readme.txt are moved to the directory, the appended numeric string is incremented, so that the renamed files have names such as readme_02.txt and readme_03.txt.
Migrating background local users in batch mode

To migrate background local users in batch mode, do as follows: 1. Log on to the source computer, using a local administrator account. 2. Launch SMABAT.EXE with option /c, where local users to be migrated are specified in the commands.xml file as follows:
<IncUsers> <UserName>localuser1</UserName> <UserName>localuser2</UserName> <UserName>localuser3</UserName> </IncUsers>
When specifying users, you can use a wildcard. To migrate all local users, use an asterisk (*) as follows:
<IncUsers> <UserName>*</UserName> </IncUsers>
3. Log on to the target computer, using a local administrator account. 4. Launch the SMABAT.EXE file with option /a, where the SMA migration file is specified. 5. Restart the computer.
39
SMA will apply the settings to the local user account on the target computer. The process will be launched automatically when the local user logs on to the target computer. 6. The local user logs on. 7. The SMA delayed apply task starts automatically. Note: When migrating local user account(s) at step 4, if you save the SMA migration file to a network drive or a removable drive, after reboot SMA may not be able to get access to it for the delayed apply task. If you have to use a shared network drive, add the following statement to the commands.xml file:
<PromptBeforeDelayedApply>true</PromptBeforeDelayedApply>
If you do this, a prompt will appear before the start of a delayed apply phase; while the prompt is displayed, you can establish a network connection.
Migrating background domain users in batch mode

To migrate background domain users in batch mode, do as follows: 1. Make sure that the domain controller is visible from the migration source computer via a network (there is no need to log on to the domain controller). 2. Log on to the source computer, using a local administrator account. 3. Launch SMABAT.EXE with option /c, where the domain users to be migrated are specified in the commands.xml file as follows:
<IncUsers> <UserName>ourdomain\domainuser1</UserName> <UserName>ourdomain\domainuser2</UserName> <UserName>ourdomain\domainuser3</UserName> </IncUsers>
When specifying users, you can use a wildcard. To migrate all domain users, use an asterisk (*) as follows:
<IncUsers> <UserName>*\*</UserName> </IncUsers>
4. Make sure that the domain controller is visible from the target computer via a network (there is no need to log on to the domain controller). 5. Make sure that the target computer is a member of the domain. To confirm that it is, open the Computer Name tab of System Properties, and check the Domain: settings on the panel. If the domain name is displayed, the target computer is the member of the domain. If the domain name is not displayed, press the Change button and follow the directions in the Computer Name Changes panel to enter the computer as a member of the domain. 6. Log on to the target computer, using a local administrator account (there is no need to log on to the domain controller). 7. Launch SMABAT.EXE with option /a, where the SMA Migration file is specified. 8. Restart the computer. SMA will apply the settings to the domain user account on the target computer. The process will be launched automatically when the domain user logs on to the target computer. 9. The domain user logs on. If this is the first time the domain user has logged on, the Windows operating system automatically creates a new user profile. It may take a few minutes.
40
10. The SMA delayed apply task starts running automatically. Note: When migrating one or more domain user accounts in step 8 on page 40, if you save the SMA migration file to a network drive or a removable drive, SMA may not be able to get access to the network or the removable drive for the delayed apply task immediately after restart. If you have to use a shared network drive, add the following statement to the commands.xml file:
<PromptBeforeDelayedApply>true</PromptBeforeDelayedApply>
If you do this, a prompt will appear before the start of a delayed apply phase; while the prompt is displayed, you can establish a network connection.
SMABAT return codes

Table 9. SMABAT return codes Return Code 0 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 Description Success. Error is found in loading the lang.dll file. No parameter is specified. Display the on-line help file. Profile is missing. Password is required. More than one migration mode is specified. Invalid command file is specified. Invalid user name is specified. Invalid profile file is specified. Temp file location is required. Log file location is required. TSM password is required. Domain User Account Name is required. Domain User Account Password is required. Domain User Account Password is specified. The input parameters are invalid. Required disk size is larger than free disk space. Fail to import command file. Its not IBM machine. Fail to initialize Framework. Error is found in Expand Environment strings of P2P keyword. P2P setup fails. Error is found in TSM mode. Another smabat.exe is running. Extract command only. Fail to extract the archived file. Error is found in getting the user list.
41
Table 9. SMABAT return codes (continued) Return Code 928 929 931 932 933 934 999 Description Error is found in getting the application list. Error is found in getting the printer list. Fail to create CSmaBat framework. Fail to create CSmaLangResource. Check the BIOS settings to identify the hardware failure. Fail to create CArrayPrinterGuiInfo. The causes of returning an error code 999 can be: v A failure of creating SMA batch occurs. v An unknown error in the language resource of SMA batch occurs. v The current machine is not an IBM or Lenovo machine. v An unknown error in the printer occurs. v A failure of executing (using Capture or Apply button) one or more plug-ins. For example, when the desktop icon plug-in fails, the failure will not influence the other plug-ins. However, if the FileAndFolder plug-in fails, the detail serverity can be decided by viewing detail log. v Any unhandled exception occurs.
42
Chapter 5. Best practices

This chapter presents scenarios to illustrate the best practices of System Migration Assistant. The scenarios are: v Migrating a single user v Migrating a single domain user v Migrating multiple users in batch mode v Migrating multiple users in batch mode v Migrating multiple users v Migrating multiple users
Scenario 1: Migrating a single user

Operation overview To start automatic SMA installation, the end user double-clicks the batch command file on the shared drive. After the installation is complete, the migration in GUI mode starts automatically. To start the capture operation, the end user selects Source PC on the source PC when prompted. When SMA completes its capture operation on the source PC, the migration file is created on the shared folder of the server. Next, the end user on the target PC starts the apply phase by selecting Target PC when prompted. SMA finds and reads the migration file on the shared folder, and starts applying the profile. Migration conditions The conditions for migrating a single user are summarized in Table 10.
Table 10. Conditions for migrating a single user Item Operator Windows OS version Source PC End user Windows 2000 Professional Target PC End user Windows XP, Windows Vista, or Windows 7 (When the Target OS is Windows Vista or Windows 7, System Migration Assistant can only migrate files and folders.) Local administrators SMA
Type of the logon users account Tool (SMABAT or SMA) Connectivity (File or PC-to-PC)
(Default) SMA X:/FileName
File located on the mapped drive,
43
Table 10. Conditions for migrating a single user (continued) Item Settings to be migrated Desktop settings Source PC Desktop icons Taskbar Wallpaper Mapped drives ODBC data source Microsoft Access Microsoft Word Microsoft Excel Microsoft PowerPoint Microsoft Internet Explorer Microsoft Outlook Target PC
Network settings Application settings
Printer settings Files and folders to be migrated Files and folders to be excluded from migration C:/My Documents *.mp3 IE Cookies IE Temp Files IE History
Actions required of the administrator before the migration 1. Prepare the following two shared folders on the server: SMA_Inst for SMA setup SMA_Files to place SMA migration files 2. Prepare the following files in the SMA_Inst folder. config.ini to customize SMA GUI. GUI_default_commands.xml to customize migration commands. SMASetup.exe to install SMA Capture.bat and Apply.bat to set up the above files Actions required of the end user before the migration Map the SMA_Inst shared folder as the Y: drive from both the source and the target PCs. Map the SMA_Files shared folder as the X: drive from both the source and the target PCs. Actions required of the administrator during the migration None Actions required of the end user during the migration On the source PC 1. Start the SMA setup by double-clicking the Capture.bat file on the Y: drive. 2. When the migration in the GUI mode starts, select the applications for which the settings will be migrated; then select the files and folders to be migrated. 3. When the Save As dialog window opens, specify the migration file name on the X: drive. 4. When the capture operation is finished, the migration file will be created on the X:\ drive. 5. Go to the target PC.
44
On the target PC 1. Start the SMA setup by double-clicking the Apply.bat file on the Y: drive. When the OS is Windows Vista or Windows 7 and logged on to an Administrators account, start the SMA setup using Apply.bat with the runas administrator option. 2. When the migration in the GUI mode starts, select Custom, Target, Migration File when prompted. 3. When the Open dialog window opens, select the migration file on the X:\ drive. Then confirm that the settings for all desired applications, files, and folders have been captured. 4. When the migration is completed, reboot the computer and confirm that all the selected settings have been migrated properly.
Example of a config.ini file

;****************************************************************************** ; ; CONFIG.INI ; ; This file is intended for use with SMA version 6.0. It is used to override ; default settings within SMA. ; ; Important: Any text that appears after a semicolon ";" will be treated as a ; comment. The semicolon must appear at the beginning of the text ; and must not be preceded by other characters. Also, the text ; in this file is not case sensitive. ; For example: C:\COMMANDS.XML is treated exactly the same as ; c:\commands.xml. ; ;****************************************************************************** ;-----------------------------------------------------------------------------; GLOBAL OPTIONS ;-----------------------------------------------------------------------------Configuration_File_Show_Configuration_Messages = no Import_Command_File = GUI_default_commands.xml Import_Command_File_For_Apply = GUI_default_commands_apply.xml Export_Command_File = Just_Create_Command_File = Verbose_Logging = yes Enable_4GFat32_warning = yes Preprocess Executable = ; Set YES/NO to display/hide the previous file selection dialog Show_Previous_File_Selection_Dialog = no ; Set YES/NO to display/hide the message for P2P migration Show_P2P_Messagebox = no ; Set YES/NO to display/hide the file dialog to open and save migration file Show_File_Dialog = no ; Set YES/NO to display/hide the start processing message dialog Show_Start_Processing_Dialog = no ; Set YES/NO to display/hide the reboot message dialog Show_Reboot_Dialog = yes ; Set YES/NO to display/hide the progress dialogs Show_All_Progressbar_Dialogs = yes ; Set YES/NO to display/hide the all warning message dialogs Show_All_Warning_Dialogs = yes ; Set YES/NO to enable/disable password protection Enable_Password_Protection = no ;-----------------------------------------------------------------------------; SHOW/NOT SHOW PAGE OPTIONS ;-----------------------------------------------------------------------------Splash_Page_Show_Page = no
45
Welcome_Page_Show_Page = no Begin_Page_Show_Page = no TopOptions_Page_Show_Page = no MigOptions_Page_Show_Page = no Profiles_Page_Show_Page = no Desktop_Page_Show_Page = no Applications_Page_Show_Page = yes Network_Page_Show_Page = no Printers_Page_Show_Page = no Selection_Page_Show_Page = yes AutoManual_Page_Show_Page = no P2P_Logon_Page_Show_Page = no P2P_Auto_SRC_Page_Show_Page = no P2P_Manual_TGT_Page_Show_Page = no P2P_Manual_SRC_Page_Show_Page = no P2P_SourceIni_Page_Show_Page = no P2P_Keyword_Page_Show_Page = no Receive_Data_Page_Show_Page = no Log_Page_Show_Page = yes SummaryTypical_Page_Show_Page = yes ;-----------------------------------------------------------------------------; WINDOW TITLE OPTIONS ;-----------------------------------------------------------------------------Welcome_Page_Title = Begin_Page_Title = TopOptions_Page_Title = MigOptions_Page_Title = Profiles_Page_Title = Desktop_Page_Title = Applications_Page_Title = Network_Page_Title = Printers_Page_Title = Selection_Page_Title = AutoManual_Page_Title = P2P_Logon_Page_Title = P2P_Auto_SRC_Page_Title = P2P_Manual_TGT_Page_Title = P2P_Manual_SRC_Page_Title = P2P_SourceIni_Page_Title = P2P_Keyword_Page_Title = Receive_Data_Page_Title = Log_Page_Title = SummaryTypical_Page_Title = ;-----------------------------------------------------------------------------; GUIDANCE TEXT OPTIONS ;-----------------------------------------------------------------------------Welcome_Page_Guidance_Text = Begin_Page_Guidance_Text = TopOptions_Page_Guidance_Text = MigOptions_Page_Guidance_Text = Profiles_Page_Guidance_Text = Desktop_Page_Guidance_Text = Applications_Page_Guidance_Text = Network_Page_Guidance_Text = Printers_Page_Guidance_Text = Selection_Page_Guidance_Text = AutoManual_Page_Guidance_Text = P2P_Logon_Page_Guidance_Text = P2P_Auto_SRC_Page_Guidance_Text = P2P_Manual_TGT_Page_Guidance_Text = P2P_Manual_SRC_Page_Guidance_Text = P2P_SourceIni_Page_Guidance_Text = P2P_Keyword_Page_Guidance_Text = Receive_Data_Page_Guidance_Text = Log_Page_Guidance_Text = SummaryTypical_Page_Guidance_Text = ;------------------------------------------------------------------------------
46
; SPLASH PAGE ;-----------------------------------------------------------------------------Splash_Page_Display_Time = ;-----------------------------------------------------------------------------; BEGIN PAGE ;-----------------------------------------------------------------------------; Set Typical/Custom to perform a Typical/Custom migration. Begin_Page_Choice_Type = ;-----------------------------------------------------------------------------; TOP OPTIONS PAGE ; Note: When you set Begin_Page_Choice_Type = Typical, ; TopOptions_Page_xxxx options are unavailable. ;-----------------------------------------------------------------------------; If this is the PC you want to move to, set Target. ; If this is the PC you want to move from, set Source. TopOptions_Page_Choice_Mode = ; Choose the type of migration you want to perform below. ; FileTransfer : Copy files and settings using a removable media ; P2P : PCs are directly connected by an ethernet cable TopOptions_Page_Choice_TransferMode = ; Set yes to perform a Target-Initiated migration, ; or set no to perform a standard migration. TopOptions_Page_Target_Initiated_Migration = ;-----------------------------------------------------------------------------; INSTALL METHOD PAGE ;-----------------------------------------------------------------------------; Set Network/Media to perform a Auto/Manual migration. InstallMethod_Page_Choice_Method = ;-----------------------------------------------------------------------------; MIGRATION OPTIONS PAGE ;-----------------------------------------------------------------------------Options_Page_Choice_Profiles = display,enabled,checked Options_Page_Choice_Desktop = display,enabled,checked Options_Page_Choice_Applications = display,enabled,checked Options_Page_Choice_Printers = hide,enabled,unchecked Options_Page_Choice_Network = display,enabled,checked Options_Page_Choice_Files = display,enabled,checked ;-----------------------------------------------------------------------------; DESKTOP PAGE ;-----------------------------------------------------------------------------Desktop_Page_Choice_Desktop_Settings = display,enabled Desktop_Page_Choice_Accessibility = display,enabled Desktop_Page_Choice_Active_Desktop = display,enabled Desktop_Page_Choice_Colors = display,enabled Desktop_Page_Choice_Desktop_Icons = display,enabled Desktop_Page_Choice_Display = display,enabled Desktop_Page_Choice_Icon_Font = display,enabled Desktop_Page_Choice_Keyboard = display,enabled Desktop_Page_Choice_Mouse = display,enabled Desktop_Page_Choice_Pattern = display,enabled Desktop_Page_Choice_Screen_Saver = display,enabled Desktop_Page_Choice_Send_To_Menu = display,enabled Desktop_Page_Choice_Shell = display,enabled Desktop_Page_Choice_Sound = display,enabled Desktop_Page_Choice_Start_Menu = display,enabled Desktop_Page_Choice_Task_Bar = display,enabled Desktop_Page_Choice_Time_Zone = display,enabled Desktop_Page_Choice_Wallpaper = display,enabled Desktop_Page_Choice_Window_Metrics = display,enabled ;-----------------------------------------------------------------------------; APPLICATIONS PAGE ;-----------------------------------------------------------------------------Applications_Page_Show_Registry_Button = no ;-----------------------------------------------------------------------------; NETWORK PAGE ;-----------------------------------------------------------------------------Network_Page_Choice_TCP_IP_Configuration = display
47
Network_Page_Choice_IP_Subnet_Gateway = display,enabled Network_Page_Choice_DNS_Configuration = display,enabled Network_Page_Choice_WINS_Configuration = display,enabled Network_Page_Choice_Network_Identification = display Network_Page_Choice_Computer_Name = display,enabled Network_Page_Choice_Computer_Description = display,enabled Network_Page_Choice_Domain_Workgroup = display,enabled Network_Page_Choice_Other = display Network_Page_Choice_Mapped_Drives = display,enabled Network_Page_Choice_Dial_Up_Networking = display,enabled Network_Page_Choice_Shared_Folders_Drives = display,enabled Network_Page_Choice_ODBC_DataSources = display,enabled ;-----------------------------------------------------------------------------; FILE AND FOLDER SELECTION PAGE ;-----------------------------------------------------------------------------Selection_Page_File_Quota = Selection_Page_File_Warning_Message = ; Warnings [Selection_Page_Warning_Extensions_Start] exe com dll [Selection_Page_Warning_Extensions_End]
Example of a GUI_default_commands.xml file

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#1</comment> <comment>Migration from Win2000 to Win XP by File Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>File</mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>X:\FileName.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell>
48
<sound>false</sound> <start_menu>false</start_menu> <taskbar>true</taskbar> <time_zone>false</time_zone> <wallpaper>true</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>true</odbc_datasources> </Network> <Applications> <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft </Applications> Access</Application> Office Word</Application> Office Excel</Application> Office Power Point</Application> Internet Explorer</Application> Outlook</Application>
<Inclusions> <IncDescription> <Description>C:\My Documents\ /s</Description> <Dest>%USERPROFILE%\My Documents</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.mp3 /s</Description> <Dest>%USERPROFILE%\My Documents</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%WINDIR%\Temporary Internet Files\</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare>
49
<SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers> <UserName></UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> </MISC> </controlcard>
Example of a Capture.bat file

@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" copy config.ini "C:\Program Files\ThinkVantage\SMA\config.ini" /y copy GUI_default_commands.xml "C:\Program Files\ThinkVantage\SMA\GUI_default_commands.xml" /y "C:\Program Files\ThinkVantage\SMA\sma.exe"
Example of an Apply.bat file

@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" copy GUI_default_commands.xml "C:\Program Files\ThinkVantage\SMA\GUI_default_commands.xml" /y "C:\Program Files\ThinkVantage\SMA\sma.exe" "\\ServerName\Folder\FileName.sma"
Scenario 2: Migrating a single domain user

Operation overview SMA is installed automatically by means of a software distribution tool because the user does not have administrator privileges. The end user should save the credentials, and create the user profile on the target PC, which should join the domain. The end user connects the source PC and the target PC using Ethernet, and is given two CDs. One CD is set to run the Capture.bat file on the source PC, and the other is set to run the Apply.bat file on the target PC.
50
Migration conditions The conditions for migrating a single domain user are summarized in Table 11.
Table 11. Conditions for migrating a single domain user Items Operator Windows OS version Type of logon user account Tool (SMABAT or SMA) Connectivity: file or PC-to-PC Settings to be migrated Desktop settings Network settings Application settings Printer settings Files and folders to be migrated Files and folders to be excluded from migration Source PC End user Windows 2000 Professional Domain power user SMABAT Target PC End user Windows XP Professional Domain power user SMABAT
PC to PC (peer-to-peer) via Ethernet Display of desktop icons (the Resolve icons link option is not used in this case) Mapped drives Lotus Sametime Lotus Notes No All files in the users My Documents folder All .mp3 files. Any files migrated by desktop icons cannot be excluded.
Actions required of the administrator before the migration Prepare the migration CDs. capture CD Prepare the following files in the root directory of the capture CD . v Commands.xml to customize migration commands. When the user privilege is limited users (except Administrator), dont add the user name to the <IncUsers> selection of the Commands.xml file. v Capture.bat to start the SMA capture process. v autorun.inf to run Capture.bat automatically. apply CD Prepare the following files in the root directory of the Apply CD. v Apply.bat to start SMA apply process. v autorun.inf to run Apply.bat automatically. Actions required of the end user before the migration None Actions required of the administrator during the migration None Actions required of the end user during the migration On the source PC 1. Log on as the domain user. 2. Confirm that SMA has been installed.
51
3. Insert the capture CD in the source PC. The Capture.bat file is launched automatically, and the capture process starts. On the target PC 1. Log on as the domain user. The logon user name should be the same as on the source PC. 2. Confirm that SMA has been installed. 3. Insert the apply CD in the target PC. The Apply.bat file is launched automatically, and the apply process starts. 4. When the prompt to restart the computer is displayed, the migration is complete. 5. Restart the target PC.
Example of the capture CD contents

@echo off md C:\SMAWORK copy /y commands.xml C:\SMAWORK\ :start set connectionID= set /p connectionID="type connection id >" if /i "%connectionID%"=="" goto start if /i "%connectionID%"=="exit" goto end echo Start Capture operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /c "C:\SMAWORK\commands.xml" /p2p %connectionID% :end set connectionID=
Example of a commands.xml file

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#2</comment> <comment>Migration single domain user from Win2000 to Win XP by PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>P2P</mode> </TransferMode> <P2P> <connection_id>unique_password</connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename></filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors>
52
<desktop_icons>true</desktop_icons> <display>true</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>false</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Lotus Notes</Application> <Application>Lotus Sametime</Application> </Applications> <Inclusions> <IncDescription> <Description>%USERPROFILE%\My Documents\ /s</Description> <Dest></Dest> <Operation></Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>*:\*.mp3 /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers>
53
<UserName></UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>
Example of the apply CD contents

@echo off md C:\SMAWORK copy /y commands.xml C:\SMAWORK\ :start set connectionID= set /p connectionID="type connection id >" if /i "%connectionID%"=="" goto start if /i "%connectionID%"=="exit" goto end echo Start Apply operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /a "C:\SMAWORK\commands.xml" /p2p %connectionID% :end set connectionID=

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#2</comment> <comment>Migration single domain user from Win2000 to Win XP by PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>P2P</mode> </TransferMode> <P2P> <connection_id>unique_password</connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders>
54
<ArchiveFile> <filename></filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>true</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>false</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Lotus Notes</Application> <Application>Lotus Sametime</Application> </Applications> <Inclusions> <IncDescription> <Description>%USERPROFILE%\My Documents\ /s</Description> <Dest></Dest> <Operation></Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>*:\*.mp3 /s</Description> <DateCompare> <Operand></Operand> <Date></Date>
55
</DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers> <UserName></UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>
Scenario 3: Migrating multiple users in batch mode

Operation overview On the source PC, the administrator starts the SMA installation by double-clicking the Capture.bat file, which is in the shared folder. After the installation is finished, migration in batch mode starts automatically. On the target PC, the administrator starts the SMA installation by double-clicking Apply.bat; then the migration enters the apply phase. Migration conditions The conditions for migrating multiple users in the batch mode are summarized in Table 12.
Table 12. Conditions for migrating multiple users in the batch mode Items Operator Windows OS version Source PC Administrator Windows XP Professional Target PC Administrator Windows XP Professional or Windows Vista or Windows 7 Domain administrators SMABAT
Type of the logon user account Tool (SMABAT or SMA) Connectivity: file or PC-to-PC
Domain administrators SMABAT
File on the server \\Server\folder\ FileName
56
Table 12. Conditions for migrating multiple users in the batch mode (continued) Items Settings to be migrated Desktop settings Source PC Target PC
Display of desktop icons (the Resolve icons link option is used in this case) Screen saver Wallpaper Mapped drive Microsoft Access 2000 to 2003 Microsoft Word 2000 to 2003 Microsoft Excel 2000 to 2003 Microsoft PowerPoint 2000 to 2003 Microsoft Outlook 2000 to 2003 No All users files in the My Documents folder (Documents and Settings\*\My Documents) All .doc files on the PC All .ppt files on the PC All .xls files on the PC Documents and Settings\Administrator folder and Documents and Settings\All Users folder
Printer settings Files and folders to be included
Files and folders to be excluded from migration
Actions required of the administrator before the migration 1. Prepare two shared folders on the server: v SMA_Inst for SMA setup v SMA_Files to locate the migration file 2. Prepare the following files in the SMA_Inst folder: v SMASetup.exe to install SMA v Commands.xml to customize migration commands on the source PC v Capture.bat to setup and invoke SMA on the source PC v Apply.bat to setup and invoke SMA on the target PC 3. Ask end users to move or copy migrating files into the My Documents folder. Actions required of the end user before the migration Move or copy migrating files in the My Documents folder. Actions required of the administrator during the migration On the source PC 1. Log on to the computer, using the domain administrator account. 2. Map the SMA_Inst shared folder as the Y:\ drive. 3. Double-click the Capture.bat file to start the SMA installation. 4. When the SMABAT operation has been completed, confirm that the migration file will be created at
\\Server\Folder
where \\Server\Folder is the SMA_Files shared folder in UNC format. 5. Shut down the source PC, then go to the target PC. On the target PC 1. Map the SMA_Inst shared folder as the Y: drive.
57
2. Double-click the Apply.bat file to start the application of the migration file. 3. Migration finishes, and the prompt to restart the computer is displayed. 4. Restart the target PC. 5. Ask the migrated users to log on to the target PC to complete the delayed apply process. Actions required of the end user after the migration 1. Log on to the target PC and confirm that the delayed apply process starts. 2. When the delayed apply process has been completed, reboot the computer.

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#3</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via File Migration </comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>File</mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>\\ServerName\Folder\FileName.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>true</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>true</wallpaper> <window_metrics>false</window_metrics>
58
</Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft </Applications> Access</Application> Office Word</Application> Office Excel</Application> Office Power Point</Application> Outlook</Application>
<Inclusions> <IncDescription> <Description>%SystemDrive%\Documents and Settings\*\My Documents\ /s</Description> </IncDescription> <IncDescription> <Description>*:\*.doc /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.xls /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.ppt /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription>
59
</Inclusions> <Exclusions> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\Administrator\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\All Users\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers> <UserName>$(all)</UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> <UserName>Administrator</UserName> <UserName>Guest</UserName> <UserName>SQLDebugger</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>
60
Examples of .bat files

Example 1: Capture.bat
@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" md C:\SMAWORK copy commands.xml "C:\SMAWORK\commands.xml" /y @echo Start Capture operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /c "C:\SMAWORK\commands.xml"
Example 2: Apply.bat
@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" md C:\SMAWORK copy commands.xml "C:\SMAWORK\commands.xml" /y @echo Start Apply operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /a "C:\SMAWORK\commands.xml"
Scenario 4: Migrating multiple users in batch mode

Operation overview: The end user connects the target and the source PC via Ethernet and is given two CDs. One CD launches the Capture.bat file automatically, and the other launches the Apply.bat file. On the source PC, the Capture.bat file starts the installation of SMA, and, when the installation is finished, starts migration in the batch mode. On the target PC, the Apply.bat file installs SMA, and then starts the apply phase in the batch mode. The TCP/IP setting of the source PC should be static IP; the TCP/IP, DNS, WINS settings, the computer name, and the network name must also migrate. For the migration of these settings, the apply process is separated into four steps. Migration conditions The conditions for migrating multiple users in the batch mode are summarized in Table 13. When the target OS is Windows Vista or Windows 7, the DNS configuration setting of the source PC must have the proper value to access the Primary Domain Controller (PDC)
Table 13. Conditions for migrating multiple users in the batch mode Items Operator Windows OS version Source PC Administrator Windows 2000 Professional Target PC Administrator Windows XP Professional or Windows Vista or Windows 7 Local administrators SMABAT
Type of logon user account Tool (SMABAT or SMA) Connectivity: file or PC-to-PC
Local administrators SMABAT
PC to PC (peer-to-peer) via Ethernet
61
Table 13. Conditions for migrating multiple users in the batch mode (continued) Items Settings to be migrated Desktop settings Source PC Target PC
Display of desktop icons (the Resolve icons link option is used in this case) Screen saver Wallpaper IP / Subnet / gateway DNS configuration WINS configuration Computer Name Domain / Workgroup Mapped drives Microsoft Access 2000 to 2003 Microsoft Word 2000 to 2003 Microsoft Excel 2000 to 2003 Microsoft PowerPoint 2000 to 2003 Microsoft Outlook 2000 to 2003 No All users files in the My Documents folder (Documents and Settings\*\My Documents) All .doc files on the PC All .ppt files on the PC All .xls files on the PC Documents and Settings\Administrator folder and Documents and Settings\All Users folder
Network settings
Application settings
Printer settings Files and folders to be migrated
Files and folders to be excluded from migration
Actions required of the administrator before the migration 1. Prepare the migration CDs. capture CD Prepare the following files in the root directory of the capture CD: v Commands.xml to customize the migration commands v Capture.bat to start the capture process v autorun.inf to run Capture.bat automatically v SMASetup.exe to install SMA apply CD Prepare the following files in the root directory of the apply CD: v Step1_Commands.xml to create a migration file on the target PC. v Step2_Commands.xml to apply TCP/IP, DNS, WINS settings, and the computer name. v Step3_Commands.xml to apply network group settings. v Step4_Commands.xml to apply all other settings. v APPLY1.BAT to start the apply process by use of Step1_Commands.xml. v APPLY2.BAT to start the apply process by use of Step2_Commands.xml. v APPLY3.BAT to start the apply process by use of Step3_Commands.xml.
62
v APPLY4.BAT to start the apply process by use of Step4_Commands.xml. v autorun.inf to run APPLY1.BAT automatically. v SMASetup.exe to install SMA. 2. Ask each end user to put the files being migrated into his or her My Documents folder. Actions required of the end user during the migration Move or copy the migrating files to the My Documents folder. Actions required of the administrator during the migration On the source PC 1. Connect to the network using Ethernet. 2. Log on using the local administrator account. 3. Insert the capture CD in the optical drive of the source PC. SMA setup starts automatically, and then the capture process starts. 4. When the SMABAT operation completes, power off the source PC, then go to the target PC. On the target PC 1. Connect to the network using Ethernet. 2. Log on to the computer using the local administrator account. The logon account name should be the same as on the source PC. 3. Insert the apply CD in the optical drive of the target PC. SMA setup and the initial apply process launch automatically. 4. When the SMABAT operation has been completed, confirm that the SMA migration file (.sma) will be created at the C:\SMAWORK folder of the target PC. 5. When the prompt is displayed, restart the target PC. 6. Log on again, using the local administrator account. 7. Double-click the CD_DRIVE:\APPLY2.BAT file to start the second stage of the apply process, when TCP/IP, DNS, WINS, and computer name is migrated. 8. When the prompt is displayed, restart the target PC. 9. Log on again, using the local administrator account. 10. Confirm that TCP/IP, DNS, WINS settings, and the computer name have been migrated. 11. Double-click the CD_DRIVE:\APPLY3.BAT file to start the third stage of the apply process, in which the network group is migrated. 12. When the prompt is displayed, restart the target PC. 13. Log on again, using the local administrator account. 14. Confirm that the network group has been migrated. 15. Double-click the CD_DRIVE:\APPLY4.BAT file to start the fourth stage 16. When the prompt is displayed, restart the target PC. 17. Log on again, using the local administrator account. 18. Ask all the migrated users to log on to the target PC once, to complete the delayed apply process. Actions required of the end user after the migration
63
1. Log on to the target PC to confirm that the delayed apply process starts automatically. 2. When the delayed apply process completes, reboot the computer.
Example of the capture CD contents

@echo off echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" md C:\SMAWORK copy commands.xml "C:\SMAWORK\commands.xml" /y :start set connectionID= set /p connectionID="type connection id >" if /i "%connectionID%"=="" goto start if /i "%connectionID%"=="exit" goto end echo Start Capture operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /c C:\SMAWORK\commands.xml /p2p %connectionID% :end set connectionID=

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#4</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>P2P</mode> </TransferMode> <P2P> <connection_id>unique_data</connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>C:\SMAWORK\Scenario4.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>true</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell>
64
<sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>true</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>true</ip_subnet_gateway_configuration> <dns_configuration>true</dns_configuration> <wins_configuration>true</wins_configuration> <computer_name>true</computer_name> <computer_description>true</computer_description> <domain_workgroup>true</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft </Applications> Access</Application> Office Word</Application> Office Excel</Application> Office Power Point</Application> Outlook</Application>
<Inclusions> <IncDescription> <Description>%SystemDrive%\Documents and Settings\*\My Documents\ /s</Description> <Dest></Dest> <Operation></Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.doc /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.xls /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand>
65
<Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.ppt /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\Administrator\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\All Users\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers> <UserName>$(all)</UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> <UserName>Administrator</UserName> <UserName>Guest</UserName> <UserName>SQLDebugger</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links>
66
<autoreboot>2</autoreboot> </MISC> </controlcard>
Example of the apply CD contents

Example 1: Apply1.bat file
@echo off echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" md C:\SMAWORK copy /y Step1_commands.xml C:\SMAWORK\ :start set connectionID= set /p connectionID="type connection id >" if /i "%connectionID%"=="" goto start if /i "%connectionID%"=="exit" goto end echo Start Migration file creation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /a C:\SMAWORK\Step1_commands.xml /p2p %connectionID% :end set connectionID=

@echo SMA6.0 Installation is in progress... copy Step2_commands.xml "C:\SMAWORK\Step2_commands.xml" /y @echo Start Apply operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /a "C:\SMAWORK\Step2_commands.xml"


Examples of .xml files

Example 1: Step1_commands.xml file
<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#4</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>P2P</mode> </TransferMode> <P2P> <connection_id>unique_data</connection_id>
67
</P2P> <FilesAndFolders> <run>false</run> </FilesAndFolders> <ArchiveFile> <filename>C:\SMAWORK\Scenario4.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>false</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>false</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>false</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application></Application> </Applications> <IncUsers> <UserName></UserName> </IncUsers> <ExcUsers> <UserName></UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC>
68
<bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#4</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode></mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>false</run> </FilesAndFolders> <ArchiveFile> <filename>C:\SMAWORK\Scenario4.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>false</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>false</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>true</ip_subnet_gateway_configuration> <dns_configuration>true</dns_configuration> <wins_configuration>true</wins_configuration> <computer_name>true</computer_name> <computer_description>true</computer_description> <domain_workgroup>false</domain_workgroup>
69
<shared_folders_drives>false</shared_folders_drives> <mapped_drives>false</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application></Application> </Applications> <IncUsers> <UserName></UserName> </IncUsers> <ExcUsers> <UserName></UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#4</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode></mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>false</run> </FilesAndFolders> <ArchiveFile> <filename>C:\SMAWORK\Scenario4.sma</filename> </ArchiveFile> <Desktop>
70
<desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>false</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>false</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>true</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>false</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application></Application> </Applications> <IncUsers> <UserName></UserName> </IncUsers> <ExcUsers> <UserName></UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>
71
<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#4</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via PC to PC Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode></mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>C:\SMAWORK\Scenario4.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>true</desktop_settings> <accessibility>true</accessibility> <active_desktop>true</active_desktop> <colors>true</colors> <desktop_icons>true</desktop_icons> <display>true</display> <icon_metrics>true</icon_metrics> <keyboard>true</keyboard> <mouse>true</mouse> <pattern>true</pattern> <screen_saver>true</screen_saver> <sendto_menu>true</sendto_menu> <shell>true</shell> <sound>true</sound> <start_menu>true</start_menu> <taskbar>true</taskbar> <time_zone>true</time_zone> <wallpaper>true</wallpaper> <window_metrics>true</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>true</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>false</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>$(all)</Application> </Applications>
72
<IncUsers> <UserName>$(all)</UserName> </IncUsers> <ExcUsers> <UserName></UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer>$(all)</Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>
Scenario 5: Migrating multiple users

Operation overview On the source PC, the administrator starts the SMA installation by double-clicking the Capture.bat file on the shared drive. Migration in the GUI mode starts automatically. A migration file is created in the shared folder of the server. On the target PC, the administrator starts the SMA installation by double-clicking the Apply.bat file. Migration in the GUI mode starts, enabling the administrator to reselect the settings being migrated in the GUI selection windows on the target PC. Migration conditions The conditions for migrating multiple users are summarized in Table 14.
Table 14. Conditions for migrating multiple users Items Operator Windows OS version Source PC Administrator Windows 2000 Professional Local administrators SMA Target PC Administrator Windows XP or Windows Vista or Windows 7 Local administrators SMA
File on the shared drive of the server \\Server\folder\FileName
73
Table 14. Conditions for migrating multiple users (continued) Items Settings to be migrated Desktop settings Source PC Desktop icons Screen saver Wallpaper Mapped drives Microsoft Access Microsoft Word Microsoft Excel Microsoft Power Point Microsoft Outlook Target PC
Printer settings Files and folders to be migrated Files and folders to be excluded from migration Other settings All users files in the My Documents folder (Documents and Settings\*\My Documents) Documents and Settings\Administrator Documents and Settings\All Users Resolve_icon_links = YES
Actions required of the administrator before the migration 1. Prepare two shared folders on the server: v SMA_Inst for SMA setup v SMA_Files to locate the migration file 2. Prepare the following files in the SMA_Inst folder: v config.ini to customize the GUI v GUI_default_commands.xml to customize migration commands v SMASetup.exe to install SMA v Capture.bat to setup and invoke SMA on the source PC v Apply.bat to setup and invoke SMA on the target PC 3. Ask end users to place migrating files in the My Documents folder. Actions required of the end user before the migration Move or copy the migrating files to the My Documents folder. Actions required of the administrator during the migration On the source PC 1. Map the SMA_Inst shared folder as the Y:\ drive 2. Double-click Capture.bat to start the installation of SMA. 3. When the capture operation in the GUI mode has been completed, confirm that the SMA migration file will be created at
\\Server\folder
where \\Server\folder is the SMA_Files shared folder in UNC format. 4. Shut down the source PC, and go to the target PC. On the target PC 1. Map the SMA_Inst shared folder as the Y: drive 2. Double-click the Apply.bat file to start SMA. 3. When the User Profile window opens, clear the check boxes for accounts that will not be migrated.
74
4. Proceed according to the instructions on the screen. 5. Ask the migrated users to log on to the target PC to complete the delayed apply process. Actions required of the end user after the migration 1. Log on to the target PC and confirm that the delayed apply process starts. 2. When the delayed apply process has been completed, reboot the computer.

;****************************************************************************** ; CONFIG.INI ; ; This file is intended for use with SMA version 6.0. It is used to override ; default settings within SMA. ; ; Important: Any text that appears after a semicolon ";" will be treated as a ; comment. The semicolon must appear at the beginning of the text ; and must not be preceded by other characters. Also, the text ; in this file is not case sensitive. ; For example: C:\COMMANDS.XML is treated exactly the same as ; c:\commands.xml. ; ;****************************************************************************** ;-----------------------------------------------------------------------------; GLOBAL OPTIONS ;-----------------------------------------------------------------------------Configuration_File_Show_Configuration_Messages = no Import_Command_File = GUI_default_commands.xml Import_Command_File_For_Apply = GUI_default_commands_apply.xml Export_Command_File = Just_Create_Command_File = Verbose_Logging = yes Enable_4GFat32_warning = yes Preprocess_Executable = ; Set YES/NO to display/hide the previous file selection dialog Show_Previous_File_Selection_Dialog = no ; Set YES/NO to display/hide the message for P2P migration Show_P2P_Messagebox = no ; Set YES/NO to display/hide the file dialog to open and save migration file Show_File_Dialog = no Set YES/NO to display/hide the start processing message dialog Show_Start_Processing_Dialog = no ; Set YES/NO to display/hide the reboot message dialog Show_Reboot_Dialog = yes ; Set YES/NO to display/hide the progress dialogs Show_All_Progressbar_Dialogs = yes ; Set YES/NO to display/hide the all warning message dialogs Show_All_Warning_Dialogs = yes ; Set YES/NO to enable/disable password protection Enable_Password_Protection = no ;-----------------------------------------------------------------------------; SHOW/NOT SHOW PAGE OPTIONS ;-----------------------------------------------------------------------------Splash_Page_Show_Page = no Welcome_Page_Show_Page = no Begin_Page_Show_Page = no TopOptions_Page_Show_Page = no MigOptions_Page_Show_Page = no Profiles_Page_Show_Page = no Desktop_Page_Show_Page = no Applications_Page_Show_Page = no Network_Page_Show_Page = no
75
Printers_Page_Show_Page = no Selection_Page_Show_Page = yes ; Show F&F view AutoManual_Page_Show_Page = no P2P_Logon_Page_Show_Page = no P2P_Auto_SRC_Page_Show_Page = no P2P_Manual_TGT_Page_Show_Page = no P2P_Manual_SRC_Page_Show_Page = no P2P_SourceIni_Page_Show_Page = no P2P_Keyword_Page_Show_Page = no Receive_Data_Page_Show_Page = no Log_Page_Show_Page = yes SummaryTypical_Page_Show_Page = yes ;-----------------------------------------------------------------------------; WINDOW TITLE OPTIONS ;-----------------------------------------------------------------------------Welcome_Page_Title = Begin_Page_Title = TopOptions_Page_Title = MigOptions_Page_Title = Profiles_Page_Title = Desktop_Page_Title = Applications_Page_Title = Network_Page_Title = Printers_Page_Title = Selection_Page_Title = AutoManual_Page_Title = P2P_Logon_Page_Title = P2P_Auto_SRC_Page_Title = P2P_Manual_TGT_Page_Title = P2P_Manual_SRC_Page_Title = P2P_SourceIni_Page_Title = P2P_Keyword_Page_Title = Receive_Data_Page_Title = Log_Page_Title = SummaryTypical_Page_Title = ;-----------------------------------------------------------------------------; GUIDANCE TEXT OPTIONS ;-----------------------------------------------------------------------------Welcome_Page_Guidance_Text = Begin_Page_Guidance_Text = TopOptions_Page_Guidance_Text = MigOptions_Page_Guidance_Text = Profiles_Page_Guidance_Text = Desktop_Page_Guidance_Text = Applications_Page_Guidance_Text = Network_Page_Guidance_Text = Printers_Page_Guidance_Text = Selection_Page_Guidance_Text = AutoManual_Page_Guidance_Text = P2P_Logon_Page_Guidance_Text = P2P_Auto_SRC_Page_Guidance_Text = P2P_Manual_TGT_Page_Guidance_Text = P2P_Manual_SRC_Page_Guidance_Text = P2P_SourceIni_Page_Guidance_Text = P2P_Keyword_Page_Guidance_Text = Receive_Data_Page_Guidance_Text = Log_Page_Guidance_Text = SummaryTypical_Page_Guidance_Text = ;-----------------------------------------------------------------------------; SPLASH PAGE ;-----------------------------------------------------------------------------Splash_Page_Display_Time = ;-----------------------------------------------------------------------------; BEGIN PAGE ;-----------------------------------------------------------------------------; Set Typical/Custom to perform a Typical/Custom migration. Begin_Page_Choice_Type =
76
;-----------------------------------------------------------------------------; TOP OPTIONS PAGE ; Note: When you set Begin_Page_Choice_Type = Typical, ; TopOptions_Page_xxxx options are unavailable. ;-----------------------------------------------------------------------------; If this is the PC you want to move to, set Target. ; If this is the PC you want to move from, set Source. TopOptions_Page_Choice_Mode = ; Choose the type of migration you want to perform below. ; FileTransfer : Copy files and settings using a removable media ; P2P : PCs are directly connected by an ethernet cable TopOptions_Page_Choice_TransferMode = ; Set yes to perform a Target-Initiated migration, ; or set no to perform a standard migration. TopOptions_Page_Target_Initiated_Migration = ;-----------------------------------------------------------------------------; INSTALL METHOD PAGE ;-----------------------------------------------------------------------------; Set Network/Media to perform a Auto/Manual migration. InstallMethod_Page_Choice_Method = ;-----------------------------------------------------------------------------; MIGRATION OPTIONS PAGE ;-----------------------------------------------------------------------------Options_Page_Choice_Profiles = display,enabled,checked Options_Page_Choice_Desktop = display,enabled,checked Options_Page_Choice_Applications = display,enabled,checked Options_Page_Choice_Printers = hide,enabled,unchecked Options_Page_Choice_Network = display,enabled,checked Options_Page_Choice_Files = display,enabled,checked ;-----------------------------------------------------------------------------; DESKTOP PAGE ;-----------------------------------------------------------------------------Desktop_Page_Choice_Desktop_Settings = display,enabled Desktop_Page_Choice_Accessibility = display,enabled Desktop_Page_Choice_Active_Desktop = display,enabled Desktop_Page_Choice_Colors = display,enabled Desktop_Page_Choice_Desktop_Icons = display,enabled Desktop_Page_Choice_Display = display,enabled Desktop_Page_Choice_Icon_Font = display,enabled Desktop_Page_Choice_Keyboard = display,enabled Desktop_Page_Choice_Mouse = display,enabled Desktop_Page_Choice_Pattern = display,enabled Desktop_Page_Choice_Screen_Saver = display,enabled Desktop_Page_Choice_Send_To_Menu = display,enabled Desktop_Page_Choice_Shell = display,enabled Desktop_Page_Choice_Sound = display,enabled Desktop_Page_Choice_Start_Menu = display,enabled Desktop_Page_Choice_Task_Bar = display,enabled Desktop_Page_Choice_Time_Zone = display,enabled Desktop_Page_Choice_Wallpaper = display,enabled Desktop_Page_Choice_Window_Metrics = display,enabled ;-----------------------------------------------------------------------------; APPLICATIONS PAGE ;-----------------------------------------------------------------------------Applications_Page_Show_Registry_Button = no ;-----------------------------------------------------------------------------; NETWORK PAGE ;-----------------------------------------------------------------------------Network_Page_Choice_TCP_IP_Configuration = display Network_Page_Choice_IP_Subnet_Gateway = display,enabled Network_Page_Choice_DNS_Configuration = display,enabled Network_Page_Choice_WINS_Configuration = display,enabled Network_Page_Choice_Network_Identification = display Network_Page_Choice_Computer_Name = display,enabled Network_Page_Choice_Computer_Description = display,enabled Network_Page_Choice_Domain_Workgroup = display,enabled Network_Page_Choice_Other = display
77
Network_Page_Choice_Mapped_Drives = display,enabled Network_Page_Choice_Dial_Up_Networking = display,enabled Network_Page_Choice_Shared_Folders_Drives = display,enabled Network_Page_Choice_ODBC_DataSources = display,enabled ;-----------------------------------------------------------------------------; FILE AND FOLDER SELECTION PAGE ;-----------------------------------------------------------------------------Selection_Page_File_Quota = Selection_Page_File_Warning_Message = ; Warnings [Selection_Page_Warning_Extensions_Start] exe com dll [Selection_Page_Warning_Extensions_End]
Example of a GUI_default_commands .xml file

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#5</comment> <comment>MultiUsers Migration from WinXP to Win XP by Domain Administrator via File Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>File</mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>\\ServerName\Folder\FileName</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>true</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>true</wallpaper> <window_metrics>false</window_metrics> </Desktop>
78
<Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft </Applications> Access</Application> Office Word</Application> Office Excel</Application> Office Power Point</Application> Outlook</Application>
<Inclusions> <IncDescription> <Description>%SystemDrive%\Documents and Settings\*\My Documents\ /s</Description> <Dest></Dest> <Operation></Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.doc /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.xls /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> <IncDescription> <Description>*:\*.ppt /s</Description> <Dest>C:\other_office_files</Dest> <Operation>P</Operation>
79
<DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\Administrator\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\All Users\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers> <UserName>$(all)</UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> <UserName>Administrator</UserName> <UserName>Guest</UserName> <UserName>SQLDebugger</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>false</resolve_icon_links> <PromptBeforeDelayedApply>true</PromptBeforeDelayedApply> </MISC> </controlcard>

Example 1: Capture.bat file
80
@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" copy config.ini "C:\Program Files\ThinkVantage\SMA\config.ini" /y copy GUI_default_commands.xml "C:\Program Files\ThinkVantage\SMA\GUI_default_commands.xml" /y @echo Start Capture operation... "C:\Program Files\ThinkVantage\SMA\sma.exe"
Example 2: Apply.bat file

@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" copy GUI_default_commands.xml "C:\Program Files\ThinkVantage\SMA\GUI_default_commands.xml" /y @echo Start Apply operation... "C:\Program Files\ThinkVantage\SMA\sma.exe" "\\ServerName\Folder\FileName.sma"
Scenario 6: Migrating multiple users

Operation overview On the source PC, the administrator starts the installation of SMA by double-clicking the Capture.bat file on the shared drive. When the installation has been completed, migration in the batch mode starts automatically. The migration file is created in the shared folder of the server. On the target PC, the administrator starts the installation of SMA by double-clicking the Apply.bat file located on the shared drive. When the installation has been completed, migration in the GUI mode starts automatically, enabling the administrator to reselect migration settings in the GUI selection views on the target PC. The difference from Scenario 5: Migrating multiple users is that on the source PC migration is executed in the batch mode. Migration conditions The conditions for migrating multiple users in batch mode are summarized in Table 15.
Table 15. Conditions for migrating multiple users in batch mode Item Operator Windows OS version Source PC Administrator Windows 2000 Professional Local administrators SMABAT Target PC Administrator Windows XP or Windows Vista or Windows 7 Local administrators SMA
File at Server \\Server\folder\FileName
81
Table 15. Conditions for migrating multiple users in batch mode (continued) Item Settings to be migrated Desktop settings Source PC Desktop icons Screen saver Wallpaper Mapped drives Microsoft Access Microsoft Word Microsoft Excel Microsoft Power Point Microsoft Outlook Target PC
Printer settings Files and folders to be All users files in the My Documents folder migrated (Documents and Settings\*\My Documents) Files and folders to be Documents and Settings\Administrator excluded from Documents and Settings\All Users migration Other miscellaneous settings Resolve_icon_links = YES
Actions required of the administrator before the migration 1. Prepare two shared folders on the server: v SMA_Inst to setup SMA v SMA_Files to locate SMA migration files 2. Prepare the following files in the SMA_Inst folder: v config.ini to customize the GUI on the target PC v GUI_default_commands.xml to customize migration commands on the target PC v commands.xml to customize migration commands on the source PC v SMASetup.exe to install SMA v Capture.bat to set up and invoke SMA on the source PC v Apply.bat to set up and invoke SMA on the target PC 3. Ask end users to place the files to be migrated into the My Documents folder. Actions required from the end user before the migration Move or copy the migrating files to the My Documents folder. Actions required from the administrator during the migration On the source PC 1. Map the SMA_Inst shared folder as the Y: drive 2. Double-click the Capture.bat file to start the installation of SMA. 3. When SMABAT operation has been completed, confirm that the SMA migration file will be created at
\\Server\folder
where \\Server\folder is the SMA_Files shared folder in UNC format. 4. Shut down the source PC, and go to the target PC. On the target PC
82
1. Map the SMA_Inst shared folder as the Y: drive. 2. Double-click the Apply.bat file to start SMA. 3. When the User Profile window opens, clear the check boxes for the accounts that will not be migrated. 4. Proceed according to the instructions on the screen. 5. Ask the migrated users to log on to the target PC to complete the delayed apply process. Actions required from the end user after the migration 1. Log on to the target PC, and confirm that the delayed apply process starts. 2. When the delayed apply process has been completed, reboot the computer.
Example of a commands .xml file

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#6</comment> <comment>MultiUsers Migration from Win2000 to WinXP by Local Administrator by File Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>File</mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>\\ServerName\Folder\FileName.sma</filename> </ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>true</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>true</wallpaper>
83
<window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft </Applications> Access</Application> Office Word</Application> Office Excel</Application> Office Power Point</Application> Outlook</Application>
<Inclusions> <IncDescription> <Description>%SystemDrive%\Documents and Settings\*\My Documents\ /s</Description> <Dest></Dest> <Operation></Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\Administrator\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\All Users\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers>
84
<UserName>$(all)</UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> <UserName>Guest</UserName> <UserName>SQLDebugger</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>true</resolve_icon_links> <autoreboot>2</autoreboot> </MISC> </controlcard>

@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" md C:\SMAWORK copy commands.xml "C:\SMAWORK\commands.xml" /y @echo Start Capture operation... "C:\Program Files\ThinkVantage\SMA\smabat.exe" /c "C:\SMAWORK\commands.xml"

;****************************************************************************** ; CONFIG.INI ; ; This file is intended for use with SMA version 6.0. It is used to override ; default settings within SMA. ; ; Important: Any text that appears after a semicolon ";" will be treated as a ; comment. The semicolon must appear at the beginning of the text ; and must not be preceded by other characters. Also, the text ; in this file is not case sensitive. ; For example: C:\COMMANDS.XML is treated exactly the same as ; c:\commands.xml. ; ;****************************************************************************** ;-----------------------------------------------------------------------------; GLOBAL OPTIONS ;-----------------------------------------------------------------------------Configuration_File_Show_Configuration_Messages = no Import_Command_File = GUI_default_commands.xml Import_Command_File_For_Apply = GUI_default_commands_apply.xml Export_Command_File = Just_Create_Command_File = Verbose_Logging = yes Enable_4GFat32_warning = yes Preprocess_Executable = ; Set YES/NO to display/hide the previous file selection dialog Show_Previous_File_Selection_Dialog = no ; Set YES/NO to display/hide the message for P2P migration Show_P2P_Messagebox = no ; Set YES/NO to display/hide the file dialog to open and save migration file
85
Show_File_Dialog = no ; Set YES/NO to display/hide the start processing message dialog Show_Start_Processing_Dialog = no ; Set YES/NO to display/hide the reboot message dialog Show_Reboot_Dialog = yes ; Set YES/NO to display/hide the progress dialogs Show_All_Progressbar_Dialogs = yes ; Set YES/NO to display/hide the all warning message dialogs Show_All_Warning_Dialogs = yes ; Set YES/NO to enable/disable password protection Enable_Password_Protection = no ;-----------------------------------------------------------------------------; SHOW/NOT SHOW PAGE OPTIONS ;-----------------------------------------------------------------------------Splash_Page_Show_Page = no Welcome_Page_Show_Page = no Begin_Page_Show_Page = no TopOptions_Page_Show_Page = no MigOptions_Page_Show_Page = no Profiles_Page_Show_Page = no Desktop_Page_Show_Page = no Applications_Page_Show_Page = no Network_Page_Show_Page = no Printers_Page_Show_Page = no Selection_Page_Show_Page = yes ; Show F&F view AutoManual_Page_Show_Page = no P2P_Logon_Page_Show_Page = no P2P_Auto_SRC_Page_Show_Page = no P2P_Manual_TGT_Page_Show_Page = no P2P_Manual_SRC_Page_Show_Page = no P2P_SourceIni_Page_Show_Page = no P2P_Keyword_Page_Show_Page = no Receive_Data_Page_Show_Page = no Log_Page_Show_Page = yes SummaryTypical_Page_Show_Page = yes ;-----------------------------------------------------------------------------; WINDOW TITLE OPTIONS ;-----------------------------------------------------------------------------Welcome_Page_Title = Begin_Page_Title = TopOptions_Page_Title = MigOptions_Page_Title = Profiles_Page_Title = Desktop_Page_Title = Applications_Page_Title = Network_Page_Title = Printers_Page_Title = Selection_Page_Title = AutoManual_Page_Title = P2P_Logon_Page_Title = P2P_Auto_SRC_Page_Title = P2P_Manual_TGT_Page_Title = P2P_Manual_SRC_Page_Title = P2P_SourceIni_Page_Title = P2P_Keyword_Page_Title = Receive_Data_Page_Title = Log_Page_Title = SummaryTypical_Page_Title = ;-----------------------------------------------------------------------------; GUIDANCE TEXT OPTIONS ;-----------------------------------------------------------------------------Welcome_Page_Guidance_Text = Begin_Page_Guidance_Text = TopOptions_Page_Guidance_Text = MigOptions_Page_Guidance_Text = Profiles_Page_Guidance_Text = Desktop_Page_Guidance_Text =
86
Applications_Page_Guidance_Text = Network_Page_Guidance_Text = Printers_Page_Guidance_Text = Selection_Page_Guidance_Text = AutoManual_Page_Guidance_Text = P2P_Logon_Page_Guidance_Text = P2P_Auto_SRC_Page_Guidance_Text = P2P_Manual_TGT_Page_Guidance_Text = P2P_Manual_SRC_Page_Guidance_Text = P2P_SourceIni_Page_Guidance_Text = P2P_Keyword_Page_Guidance_Text = Receive_Data_Page_Guidance_Text = Log_Page_Guidance_Text = SummaryTypical_Page_Guidance_Text = ;-----------------------------------------------------------------------------; SPLASH PAGE ;-----------------------------------------------------------------------------Splash_Page_Display_Time = ;-----------------------------------------------------------------------------; BEGIN PAGE ;-----------------------------------------------------------------------------; Set Typical/Custom to perform a Typical/Custom migration. Begin_Page_Choice_Type = ;-----------------------------------------------------------------------------; TOP OPTIONS PAGE ; Note: When you set Begin_Page_Choice_Type = Typical, ; TopOptions_Page_xxxx options are unavailable. ;-----------------------------------------------------------------------------; If this is the PC you want to move to, set Target. ; If this is the PC you want to move from, set Source. TopOptions_Page_Choice_Mode = ; Choose the type of migration you want to perform below. ; FileTransfer : Copy files and settings using a removable media ; P2P : PCs are directly connected by an ethernet cable TopOptions_Page_Choice_TransferMode = ; Set yes to perform a Target-Initiated migration, ; or set no to perform a standard migration. TopOptions_Page_Target_Initiated_Migration = ;-----------------------------------------------------------------------------; INSTALL METHOD PAGE ;-----------------------------------------------------------------------------; Set Network/Media to perform a Auto/Manual migration. InstallMethod_Page_Choice_Method = ;-----------------------------------------------------------------------------; MIGRATION OPTIONS PAGE ;-----------------------------------------------------------------------------Options_Page_Choice_Profiles = display,enabled,checked Options_Page_Choice_Desktop = display,enabled,checked Options_Page_Choice_Applications = display,enabled,checked Options_Page_Choice_Printers = hide,enabled,unchecked Options_Page_Choice_Network = display,enabled,checked Options_Page_Choice_Files = display,enabled,checked ;-----------------------------------------------------------------------------; DESKTOP PAGE ;-----------------------------------------------------------------------------Desktop_Page_Choice_Desktop_Settings = display,enabled Desktop_Page_Choice_Accessibility = display,enabled Desktop_Page_Choice_Active_Desktop = display,enabled Desktop_Page_Choice_Colors = display,enabled Desktop_Page_Choice_Desktop_Icons = display,enabled Desktop_Page_Choice_Display = display,enabled Desktop_Page_Choice_Icon_Font = display,enabled Desktop_Page_Choice_Keyboard = display,enabled Desktop_Page_Choice_Mouse = display,enabled Desktop_Page_Choice_Pattern = display,enabled Desktop_Page_Choice_Screen_Saver = display,enabled Desktop_Page_Choice_Send_To_Menu = display,enabled
87
Desktop_Page_Choice_Shell = display,enabled Desktop_Page_Choice_Sound = display,enabled Desktop_Page_Choice_Start_Menu = display,enabled Desktop_Page_Choice_Task_Bar = display,enabled Desktop_Page_Choice_Time_Zone = display,enabled Desktop_Page_Choice_Wallpaper = display,enabled Desktop_Page_Choice_Window_Metrics = display,enabled ;-----------------------------------------------------------------------------; APPLICATIONS PAGE ;-----------------------------------------------------------------------------Applications_Page_Show_Registry_Button = no ;-----------------------------------------------------------------------------; NETWORK PAGE ;-----------------------------------------------------------------------------Network_Page_Choice_TCP_IP_Configuration = display Network_Page_Choice_IP_Subnet_Gateway = display,enabled Network_Page_Choice_DNS_Configuration = display,enabled Network_Page_Choice_WINS_Configuration = display,enabled Network_Page_Choice_Network_Identification = display Network_Page_Choice_Computer_Name = display,enabled Network_Page_Choice_Computer_Description = display,enabled Network_Page_Choice_Domain_Workgroup = display, enabled Network_Page_Choice_Other = display Network_Page_Choice_Mapped_Drives = display,enabled Network_Page_Choice_Dial_Up_Networking = display,enabled Network_Page_Choice_Shared_Folders_Drives = display,enabled Network_Page_Choice_ODBC_DataSources = display,enabled ;-----------------------------------------------------------------------------; FILE AND FOLDER SELECTION PAGE ;-----------------------------------------------------------------------------Selection_Page_File_Quota = Selection_Page_File_Warning_Message = ; Warnings [Selection_Page_Warning_Extensions_Start] exe com dll [Selection_Page_Warning_Extensions_End]
Example of a GUI_default_commands .xml file

<?xml version="1.0" ?> <?sma version="6.0" ?> <controlcard> <!-<comment>SMA6.0 Deployment Guide Sample Senario#6</comment> <comment>MultiUsers Migration from Win2000 to WinXP by Local Administrator by File Migration</comment> --> <Password> <PlainPassword></PlainPassword> </Password> <TransferMode> <mode>File</mode> </TransferMode> <P2P> <connection_id></connection_id> </P2P> <FilesAndFolders> <run>true</run> </FilesAndFolders> <ArchiveFile> <filename>\\ServerName\Folder\FileName.sma</filename>
88
</ArchiveFile> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>true</desktop_icons> <display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>true</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>true</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft <Application>Microsoft </Applications> Access</Application> Office Word</Application> Office Excel</Application> Office Power Point</Application> Outlook</Application>
<Inclusions> <IncDescription> <Description>%SystemDrive%\Documents and Settings\*\My Documents\ /s</Description> <Dest></Dest> <Operation></Operation> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </IncDescription> </Inclusions> <Exclusions> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\Administrator\ /s</Description> <DateCompare> <Operand></Operand>
89
<Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> <ExcDescription> <Description>%SystemDrive%\Documents and Settings\All Users\ /s</Description> <DateCompare> <Operand></Operand> <Date></Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription> </Exclusions> <IncUsers> <UserName>$(all)</UserName> </IncUsers> <ExcUsers> <UserName>ASPNET</UserName> <UserName>Guest</UserName> <UserName>SQLDebugger</UserName> </ExcUsers> <MigrationNote> <Note></Note> </MigrationNote> <Printers> <Printer></Printer> </Printers> <MISC> <bypass_registry>false</bypass_registry> <overwrite_existing_files>true</overwrite_existing_files> <resolve_icon_links>true</resolve_icon_links> <PromptBeforeDelayedApply>true</PromptBeforeDelayedApply> </MISC> </controlcard>

@echo SMA6.0 Installation is in progress... start /WAIT SMAsetup.exe /s /v"/qn" copy GUI_default_commands.xml "C:\Program Files\ThinkVantage\SMA\GUI_default_commands.xml" /y @echo Start Apply operation... "C:\Program Files\ThinkVantage\SMA\sma.exe" "\\ServerName\Folder\FileName"
90
Chapter 6. Application settings available for migration

This appendix lists the applications and settings that SMA can migrate. Results might differ depending on the operating system, the migration scenario, and any differences between the application versions on the source machine and the target machine. If the file that contains user settings is saved anywhere other than in the default folder, the application settings might not migrate properly. In this case, first edit the application file according to your environment, and then migrate the application settings. If different versions of an application are installed on the source PC and the target PC, the target PC should contain the newer version.
Migrating general application settings

The following table provides information on migrating general application settings.
Table 16. Application settings available for migration Application ThinkVantage Access Connections version 3.x, 4.x, 5.12 and 5.2 ThinkVantage Client Security Solution version 7.0, 8.0, 8.2, 8.21, and 8.3 Settings Location profile Note
v security policy settings v authentication mode v passphrase
Only Private Disk files of the system drive can migrate. Migration by use of SMA cannot be performed if the Private Disk has been mounted. Before you begin migration, unmount all Private Disks. For information about how to unmount a Private Disk, see the Help for ThinkVantage Client Security Solution. If the user name used to log on to the target computer differs from the one used to log on to the source computer, the Private Disk does not migrate correctly.
ThinkVantage Fingerprint Software (UPEK) version 5.5, 5.6, 5.6.1, 5.8, and 5.9
v Passport Data v General v Logon v Security Mode v Sound v Bio (version 5.6 or later) v Power-on security (version 5.6 or later)
In order to utilize the migrated Fingerprint Software data appropriately, Windows logon password should be reset to be the same as the Windows logon password on the source computer.
ThinkVantage Fingerprint Software (Authentec) 3.2
v Authentication v Additional Security v User Privileges
91
Table 16. Application settings available for migration (continued) Application Settings Note
ThinkVantage v Preferences Password Manager setting for Client Security Solution 7.0, 8.0, 8.1, 8.21, and 8.3 ThinkVantage Presentation Director version 2, 3, and 4.01 v Profiles v Immediately apply this display scheme: v Show Presentation Director icon in task bar system tray v Options... v Fn + F7 Settings ThinkVantage Rescue and Recovery version 1.0, 2.0, 3.0, 3.1, 4.0, 4.1, 4.2, 4.21, and 4.3 v Including and excluding the list of files in backups v Backup preferences Support migrating settings of version 4.1 and 4.2 which settings are same with version 4.0.
92
Table 16. Application settings available for migration (continued) Application Adobe Acrobat Reader version 5.x, 6.x, 7.x and 8.x Settings v Accessibility v Comments v Identity v Full screen v Update v Web buy Note Support migrating most common settings form version 6, 7 to 8. Following common settings can not be migrated from 7 to 8: v Edit / Preferences / Forms / General / Automatically calculate field values v Edit / Preferences / Forms / General / Keep forms data temporarily available on disk v Edit / Preferences / Full Screen / Full Screen Appearance / Default transaction: v Edit / Preferences / Full Screen / Full Screen Appearance / Mouse cursor v Edit / Preferences / Identity v Edit / Preferences / Internet / Web Options / Display PDF in browser v Edit / Preferences / Multimedia / v Edit / Preferences / Spelling / underline color v Edit / Preferences / Spelling / Dictionaries Following common settings can not be migrated from 6 to 8: v Edit / Preferences / Forms / General / Automatically calculate field values v Edit / Preferences / Forms / General / Keep forms data temporarily available on disk v Edit / Preferences / Full Screen / Full Screen Appearance / Default transaction v Edit / Preferences / Identity v Edit / Preferences / Internet / Web Options / Display PDF in browser v Edit / Preferences / Multimedia v Edit / Preferences / Reading / Reading order v Edit / Preferences / Reading / Dictionaries v Edit / Preferences / Startup / display splash screen
93
Table 16. Application settings available for migration (continued) Application Adobe Illustrator 12.0 and CS4 Settings v Color Settings v Envelope Distort / Envelope Options v Keyboard shortcuts v Live Paint / Gap Options v Live Trace / Tracing Options v SWF Presets v Preferences / Appearance of Black v Preferences / File Handling and Clipboard v Preferences / General v Preferences / Guides and Grid v Preferences / Hyphenation v Preferences / Plug-ins and Scratch Disks v Preferences / Section & Anchor Display v Preferences / Slices v Preferences / Smart Guide v Preferences / Type v Preferences / Units and Display Performance v Preferences / User Interface v Text Wrap / Text Wrap Options v Tools / Options... / Network v Tracing presets v Transparency flattener presets v Workspace / Manage Workspaces Adobe Pagemaker v Document setup 7.0 v Preferences v Polygon settings v Rounded corners v Link options Adobe Photoshop v Color Settings 8.0 and CS4 v Keyboard Shortcuts and Menus v Preferences v Proof Setup v Show / Show Extra Options Note
94
Table 16. Application settings available for migration (continued) Application AOL Instant Messenger 6.0 and 7.0 Settings v Edit / Away Messages v View / Buddy List Window Always On Top v Edit / My Buddy Info v Edit / Settings / Buddy List v Edit / Settings / Connection v Edit / Settings / Enhanced IM v Edit / Settings / Expressions v Edit / Settings / General IM v Edit / Settings / IM Logging v Edit / Settings / Notifications v Edit / Settings / Offline IM v Edit / Settings / Privacy v Edit / Settings / Sounds v Edit / Settings / Sign In / Sign Out v Edit / Settings / Style v View / Offline Buddies v View / Plugins v View / Show in Buddy List v View / Sort Buddy List By Note
95
Table 16. Application settings available for migration (continued) Application Apple iTunes 7 and 8.1 Settings v Edit / Preferences / General v Edit / Preferences / Device (excluding Warning when more than...of the data on this computer will be changed) v Edit / Preferences / Podcasts v Edit / Preferences / Playback v Edit / Preferences / Sharing v Edit / Preferences / Apple TV v Edit / Preferences / Store v Edit / Preferences / Advanced v Edit / Preferences / Parental Control v Controls / Shuffle v Controls / Repeat mode v View / Visualizer Options v View / List View v View / Album View v View / Cover Flow View v View / View Options v View / Visualizer v View / Show/Hide Browser v View / Show/Hide Artwork Column v View / Show Equalizer v View / Switch to Mini Player AT&T Network Client 5.0 AT&T Global Network Client 7.6 Avaya IP Softphone 6.0 v General v Advanced phone settings v Login Properties v Default profiles and user setup profiles v View v Tools / Program Options v Settings / Audio / Options v Audio / Options v Settings / Font Corel v Workspace Manager Presentations 12.0 v Settings Corel Quattro Pro v Workspace Manager 12.0 v Customize v Settings Corel WordPerfect v Workspace Manager 12.0 v Settings When the user selects View / Call Bar Style / Generic Phone, the Audio Options menu shows under the Settings menu, and the Audio menu does not display; if the user selects View / Call Bar Style / Classic, the Audio Options menu shows under the Audio menu and no Audio Options submenu shows under the Setting menu. Note
96
Table 16. Application settings available for migration (continued) Application Google Desktop 4.2 Settings v Desktop Use Habit/Local Index v Desktop Use Habit/Display v Desktop Use Habit/Others Google Earth 4.0 v PlaceMark v Options v Windows position Google Picasa 2.2 and 3.1 v Tools / Configure Buttons v View / Folder View v View / Hidden Pictures v Tools / Network v Tools / Options / E-mails v Tools / Options / File Types v Tools / Options / General v Tools / Options / Printing v Tools / Options / Slideshow v View / Small Pictures v View / Small Thumbnails / Normal Thumbnails v View / Thumbnail Caption v Tools / Web Albums Google Talk 1.0 v Account v View v Setting / General / Friends list v Setting / General / Change font v Setting / Notification v Setting / Audio v Setting / Appearance IBM Global Network Dialer 4.0 Supports target computers running on Windows 2000 Professional or Windows 2000 Server only.
Note
v Access v Appearance v Programs v Browser v Mail v News v Servers
97
Table 16. Application settings available for migration (continued) Application Intuit Quicken 2007 Settings v Edit / Costomize Account Bar v Edit / Customize Toolbar v Edit / Preferences / Quicken Program (exclude: Register, Reminders) v Edit / Preferences / Customize Online Updates (exclude: Connection) v Tools / Edit Personal Information v Account List v Category List (exclude: Display tax information) v Scheduled Transaction List v Memorized Payee List v Class List v Currency List v Calendar v Show All Alerts v Set Up Alerts v Address Book v Cash Flow / Reconcile v Cash Flow / Write Checks v Cash Flow / Budget v Cash Flow / Calendar v Investing / Portfolio v Investing / Security Detail View v Investing / Portfolio Analyzer v Investing / Security List v Investing / Security Type List v Investing / Investing Goal List v Property & Debt / Loan v Planning / Saving Goals v Tax / Tax Planner Note SMA only migrates the Quicken data and setting files in the default directory set by Quicken. After applying on the target computer, Quicken can not automatically open the data file, which was last opened on the source computer. Therefore, the user needs to manually open the Quicken data file to access the data and setting files.
98
Table 16. Application settings available for migration (continued) Application Settings Note SMA only migrates the QuickBooks company data files in the default directory set by QuickBooks.
Intuit QuickBooks v Edit / Preferences 2007 v View / Open Window List v View / Navigation Bar v View / Icon Bar v View / One Window / Multiple Windows v Company / Company Information v Company / Set Up Users v Company / Planning & Budgeting / Set Up Budgets v Company / Planning & Budgeting / Set Up Forecast v Company / To Do List v Company / Alerts Manager v Customers / Customer Center v Vendors / Vendor Center v Vendors / Item List v Employees / Employee Center Lotus Notes, versions 4.x, 5.x, 6.x, 7.x, and 8.5 v Home v File / Database / Access Control v File / Replication / Settings v File / Preferences v View v Mail v ID files v INI files v Address book Lotus Organizer , v To-do preferences version 6.0 v Contacts v Calls v Planner v Anniversary
In a migration between different versions, some application settings cannot be migrated.
A Lotus application can be migrated only if all applications are installed in the same directory. Lotus Notes is an exception. Good example: v C:\Lotus\123\ v C:\Lotus\Wordpro\ v C:\Lotus\Organizer\ Bad example: v C:\Lotus\123\ v C:\Program files\Wordpro\ v D:\Lotus\Organizer\
99
Table 16. Application settings available for migration (continued) Application Lotus SmartSuite for Windows, version 9.8
Settings v Approach Show Grid Show in design Maintain default sort for Database Show Navigation Data v Freelance Graphics Grid Preferences View v Lotus 1-2-3 General New workbook defaults Recalculation Classic keys View General Security Show / Hide v Word Pro General Location Personal General usage Performance View Preferences v SmartCenter Folder options (color and icon)
Note A Lotus application can be migrated only if all applications are installed in the same directory. Lotus Notes is an exception. Good example: v C:\Lotus\123\ v C:\Lotus\Wordpro\ v C:\Lotus\Organizer\ Bad example: v C:\Lotus\123\ v C:\Program files\Wordpro\ v D:\Lotus\Organizer\ The Locations settings in Preferences does not migrate.
McAfee VirusScan v System scan / Action versions 7.0 and v System scan / Report 8.0 v System scan / Exclusion v E-mail scan / Detection v E-mail scan / Action v E-mail scan / Alert v E-mail scan / Report v Script stopper
Migration from McAfee VirusScan version 7.0 to version 8.0 is not supported.
100
Table 16. Application settings available for migration (continued) Application
Settings
Note
Microsoft Access , v Toolbars versions 2000, v Options 2003, XP and 2007 v View v General v Find v Keyboard v Data sheet v Reporting v Advanced v Queries Microsoft Internet v Favorites Explorer, versions v Tools / Compatibility View Settings 5.0, 5.5, 6.0, 7.0, v View / Encoding and 8.0 v View / Full Screen v View / Explorer Bars v Tools / InPrivate Filtering Settings v Tools / Internet Options v View / Text Size v View / Toolbars Microsoft Money 2007 v Tools / Settings / Account settings v Tools / Settings / Backup Settings v Tools / Settings / Bill Settings v Tools / Settings / Browser Settings v Tools / Settings / Category Settings v Tools / Settings / Home page display settings v Tools / Settings / Investment settings v Tools / Settings / Online service settings v Tools / Settings / Planner settings v Tools / Settings / Print checks v Tools / Settings / Program settings Microsoft NetMeeting, versions 2.x and 3.x v View v General v Call v Advanced calling options v Security Microsoft Office, versions 97, 2000, 2003, XP, and 2007 (Excel, PowerPoint and Word) v Toolbars v Options v Templates v Save options v User info (under Tools options) If the version of Microsoft Office on the source computer is different from that on the target computer, the Toolbars and Templates settings of the Word and PowerPoint applications do not migrate. Compatibility in the Options settings does not migrate. SMA only support migrating Microsoft Money files and Microsoft Money Backup files which in the default directory set by Microsoft Money. If users change the directory to save the Microsoft Money files and Microsoft Money Backup files, SMA will not capture those files which are not in the default directory. After applying on target computer, Microsoft Money can not automatically open Microsoft Money file which was last opened on source computer, so users need to open Money file manually.
101
Table 16. Application settings available for migration (continued) Application Microsoft Office 2003 Publisher 11.0, Microsoft Office 2007 Publisher 12.0 Settings v Windows position v Privacy options v Printer and paper / pager settings Microsoft Outlook and Internet Explorer are migrated simultaneously. Microsoft Outlook and Microsoft Outlook Express cannot be migrated simultaneously. If the user name used to log on to the target computer differs from the one used to log on to the source computer, do as follows before starting Microsoft Outlook on the target computer: 1. Open the Control Panel. 2. Double-click Folder Options. 3. Select the View tab. 4. Select Show hidden files and folders. 5. Click OK, then close the Folder Options window. 6. In the Control Panel, double-click Mail. 7. Click Data Files. 8. Click Settings. 9. When the Outlook.pst is not valid message appears, click OK. 10. Go to the following directory: C:\Documents and Settings\%USERNAME%\ Local Settings\Application Data\Microsoft\Outlook and select Outlook.pst (%USERNAME% is the user account name you are using to log on.) 11. Close Mail Setup. 12. Start Microsoft Outlook. If you fail to go through this procedure before starting Microsoft Outlook on the target computer, you will need to migrate Microsoft Outlook again and go through the procedure. Note
Microsoft v Toolbars Outlook, v View versions 98, 2000, 2003, XP and 2007 v Customize options v Address book v Accounts v Preferences / E-mail options v Tracking options v Calendar options v Mail delivery v Resource scheduling
102
Table 16. Application settings available for migration (continued) Application Microsoft Outlook Express, versions 5.x, and 6.x / Microsoft Windows Mail Settings v General v Mail-sending format v News-sending format v Send v Read v Security v Advanced v Address book Note Microsoft Outlook Express and Internet Explorer are migrated simultaneously. Microsoft Outlook and Microsoft Outlook Express cannot be migrated simultaneously. If Address Book has not migrated, do as follows: 1. Open the Control Panel. 2. Double-click Folder Options. 3. Select the View tab. 4. Select Show hidden files and folders. 5. Click OK; then close the Folder Options window. 6. Start Microsoft Outlook Express 5.x/6.x. 7. On the menu bar, select File. 8. Select Import; then select Address Book. 9. Specify the Address book file (*.wab) as follows: C:\Documents and Settings\%USERNAME%\ Application Data\Microsoft\address book\%SOURCEUSERNAME%.wab (%SOURCEUSERNAME% is the user account name you are using to log on to the source computer.) 10. Close the Message Import window. The folder in Address Book does not migrate. This is a restriction of Outlook Express. For more information, see http://support.microsoft.com/default.aspx?scid=kb;enus;268716 Microsoft Project, versions 98, 2000 and 2002 v Toolbars v Preferences v Save options v File locations v Most recent documents Microsoft Visio , v View versions 2000 and v Toolbars 2002 v Customize / Options v General v Drawing v Settings v Advanced
103
Table 16. Application settings available for migration (continued) Application Microsoft Windows Media Player 9, 10, 11, and 12 Settings v File / Work Offline v v v v v Note
All settings that can be migrated from version 9 are included in version 10, 11, and 12, but not all settings Play / Audio and Language Tracks are the same with version 10, 11, and 12. Therefore, Play / Lyric, captions, and subtitles when SMA migrates the settings from version 10 to 11 and 12, only common settings are migrated, and the Tools / Options... / Burn settings under Tools/Options.../Performance/ Tools / Options... / Devices Advanced... will not be migrated from 10 to 11 and 12. Tools / Options... / DVD
v Tools / Options... / Library v Tools / Options... / Network v Tools / Options... / Performance v Tools / Options... / Player v Tools / Options... / Plug-ins / Properties of Battery v Tools / Options... / Privacy v Tools / Options... / Rip Music v Tools / Options... / Security v Tools / Plug-ins / Options... v View / Full Mode v View / Plug-ins / Options v View / Skin Chooser v View / Skin v View / Show Menu Bar v View / Video Size Microsoft Windows Live Messenger 7.5, 8.1, 8.5, and 2009 v Tools / Options / Alerts v Tools / Options / Connection (excluding Advanced Settings / username, password) v Tools / Options / File Transfer v Tools / Options / Layout v Tools / Options / Messages (excluding Message History) v Tools / Options / Personal v Tools / Options / Phone v Tools / Options / Privacy v Tools / Options / Security v Tools / Options / Sign In (excluding Automatically run Windows Live Messenger when I log on to Windows) v Tools / Options / Sounds Microsoft Windows MSN Messenger 5.0 v Personal v Messages v Privacy v General v Accounts v Connection SMA does not support migrating version 5 to 7.5, 8.1, 8.5, and 2009. Also, SMA does not support migrating the following common settings from 7.5 to 8.1, 8.5, and 2009: v Contacts / view contact by v Tools / change display picture / dont show a picture v Tools / options / tab v Tools / connection / advanced settings / Save a log of my server connections to help troubleshoot connection problems v Tools / personal / Show song information from Windows Media Player as a personal message SMA only supports migrating received files in the default directory set by Live Messenger. If users change the received files location, SMA will not capture those files, which are not in the default received files directory.
104
Table 16. Application settings available for migration (continued) Application Microsoft Works Suite 2006 Settings v Home / Calendar v Home / Contacts v Projects / Saved Projects Mozilla Firefox 1.5, 2.0, 3.0, and 3.5 Note SMA does not support migrating the settings of Works Suite from Windows XP or Windows 2000 to Windows Vista or Windows 7, because Works Suite uses different setting files between Windows XP, Windows 2000, and Windows Vista, Windows 7.
v Tools / Clear Recent History... v Tools / Options... v View / Character Encoding v View / Page Style v View / Sidebar v View / Status Bar v View / Toolbars v View / Zoom / Zoom Test Only
105
Table 16. Application settings available for migration (continued) Application Netscape Navigator, versions 6.x and 7.x (continued) Settings Note If the user name used to log on to the target computer differs from the one used to log on to the source computer, do as follows before starting the migration: 1. Open the Control Panel. 2. Double-click Folder Options. 3. Select the View tab. 4. Select Show hidden files and folders. 5. Click OK; then close the Folder Options window. 6. Before the migration, find the Profiles folder of Mozilla on the target computer; it is in C:\Documents and Settings\%USERNAME% Application Data\ . (Here %USERNAME% represents the user account name you are using to log on). Change the name of the folder to SMABACK. 7. Migrate Netscape. 8. Reboot the target computer. 9. Open C:\Documents and Settings\ %USERNAME% Application Data\Mozilla\ Profiles\defaults\ xxxxx.slt. (For xxxxx, choose the same name as on the source side). 10. On the Menu bar, select Edit. 11. Select Preferences. 12. Select Advanced from Category. 13. Select Cash. 14. Change Disk Cache Folder to C:\Documents and Settings\%USERNAME%\Application Data\Mozilla\Profiles\defaults\ xxxxx.slt. (For xxxxx, choose the same name as on the source side). 15. Right-click the prefs.js file, and select Edit. 16. Search C:\Documents and Settings\ %SOURCEUSER%\\ and replace all %SOURCEUSER% with %USERNAME% (where %SOURCEUSER% is the user account name you are using to log on to the source computer, and %USERNAME% is the user account name you are using to log on to the target computer). 17. Start Netscape. Norton Antivirus, v Frequency version 7.x and v When updates v Advanced v Random options Palm Desktop 4.1 v Window position v Address book v ToDo v Memo v Expense In Windows Vista or Windows 7, only window position can be migrated.
106
Table 16. Application settings available for migration (continued) Application Skype 3.2 and 4.0 Settings v Skype / online Status v Skype / Profile v Tools / Change Language v Tools / Options / Advanced / Advanced settings v Tools / Options / Advanced / Connection v Tools / Options / Advanced / Hotkeys v Tools / Options / Calls / Call Settings v Tools / Options / General / AudioSettings v Tools / Options / General / General Settings v Tools / Options / General / Sounds v Tools / Options / General / Video settings / Automatically receive video from v Tools / Options / General / Video settings / Show that I have video to v Tools / Options / IM & SMS / IM Appearance v Tools / Options / IM & SMS / IM Settings v Tools / Options / Privacy / Privacy Settings v Tools / Options / Notifications / Notifications Settings v Tools / Options / Notifications / Alerts & Messages v Tools / Options / Notifications / Sounds v View / Character Encoding v View / Default View or Compact View Symantec Antivirus 9.x v Updates v Frequency v When v Advanced v Random options Tablet OS settings v Tablet Input window settings v Tablet Pen settings Note
107
Table 16. Application settings available for migration (continued) Application WinZip, version 8.x and 11 Settings v Columns v General v Section v Buttons v System default folder v Explorer enhancements v Context menu commands v Miscellaneous Note Support migrating most common settings form version 8 to 11, but some common settings can not be migrated as following: v Options / Configuration / System / Associate Winzip with archives v Options / Configuration / System / include winzip in start menu v Options / Configuration / System / include winzip on desktop v Options / Configuration / Explorer enhancements / Display context menu items in a submenu v Options / Configuration / Miscellaneous / v Options / Configuration / Other / Show comments when opening ZIP files Yahoo Messenger 8.1 v Messenger / Preferences / General (exclude: Edit Mobile Device) v Messenger / Preferences / Alert & Sounds v Messenger / Preferences / Appearance v Messenger / Preferences / Archive v Messenger / Preferences / Chat v Messenger / Preferences / Connection v Messenger / Preferences / Display Image v Messenger / Preferences / Ignore List v Messenger / Preferences / Yahoo! Music v Messenger / Preferences / LiveWords v Messenger / Preferences / Messages v Messenger / Preferences / Privacy v Messenger / Preferences / Webcam v Messenger / Preferences / Super Webcam v Contacts / Show Offline Contracts v Contacts / Show Empty Groups v Contacts / Show Messenger List v Contacts / Show Address Book
Migrating additional application settings

Note: To create custom application files, you must have a thorough knowledge of the applications, including the locations at which customized settings are stored.
108
By default, SMA is preconfigured to migrate settings for several applications. You can also create a custom application file to migrate settings for additional applications. This file must be named application.xml or application.smaapp, and must be placed in the d:\Program Files\ThinkVantage\SMA\Apps directory, where application specifies the application and d is the drive letter of the hard disk drive. If both application.smaapp and application.xml custom application files of the same application exist, priority is given to the application.smaapp file. To support a new application, you can copy an existing application file and modify it. Bear in mind the following characteristics of application files: v application.xml The tag enclosed with  is treated as a comment. For example,

Each command must be described in a separate section. Each section begins with a command enclosed by tags; for example, <AppInfo> or <Install_Directories>. You can enter one or more fields in a section; each field must be on a separate line. If the application file contains syntax errors, SMA continues the operation and writes error messages in the log file. The application file is case-sensitive. v application.smaapp For details about using the application.smaapp file, refer to Appendix C, Compatibility with earlier versions, on page 135. Table 17 on page 110 presents information about application files.
109
Table 17. Migrating additional application settings: Application files Setting <Applications> Parameter <Family> Description A text string that specifies the non-version-specific name of the application. When you run SMA in batch mode, you use this string in the applications section of the command file. Leading spaces are ignored; do not enclose the text string in quotation marks. For example: <Family>Adobe Acrobat Reader</Family> <SMA_Version> A text string. that specifies the SMA version number. For example: <SMA_Version>SMA 6.0</SMA_Version> <App> ShortName where ShortName is a version-specific short name for one or more applications. For example: <APP>Acrobat_Reader_50</APP> <Application ShortName=ShortName> <Name> <Version> <Detects> <Detect> A text string that specifies the name of the application. A numeric version that specifies the version of the application. Specifies a registry key. SMA detects an application by searching for the specified registry key. For example: <Name>ThinkVantage Technology - Client Security Solution</Name> <Version>7.0</Version> <Detects> <Detect> <hive>HKLM</hive> <keyname>Software\Lenovo Client Security Solution\</keyname> <value>Version</value> </Detect> </Detects> It the <value> tag exists, the specified registry value is used to compare the <version> description to detect the specific version of the application
110
Table 17. Migrating additional application settings: Application files (continued) Setting <Install_Directories.> For example: <Install_Directories> <Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\InstallPath</keyname> <value>(Default)</value> </Registry> <Registry> </Install_Directory> <Install_Directory> <OS>Win2000</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader \5.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> </Install_Directories> Parameter <OS> Description A text string that specifies the operating system and can be any one of the following: v Windows 7 v Windows Vista v Windows XP v Windows 2000
Specifies the installation directory as it is listed in the registry. hive is either HKLM or HKCU. keyname is the keyname. value is an optional command that specifies the registry value being migrated.
111
Table 17. Migrating additional application settings: Application files (continued) Setting <Files_From_Folders> Parameter SMAvariable\Location\[File] [/s] where v SMAvariable is one of the following variables that specify the location of the customization files: %Windows Directory% (location of operating-system files) Description Specifies the customization files that you want to migrate. This setting is optional. For example: <Files_From_Folder>%AppData Directory% \Adobe\Acrobat\Wh api\</Files_From_Folder> SMA captures the files in the %AppData Directory%\Adobe\Acrobat\Whapi folder. The files in the subdirectories are not included.
%Install Directory% <Files_From_Folder>%AppData Directory% (location of the \Adobe\Acrobat\Wh application as defined in api\ /s</Files_From_Folder> the Install_Directories SMA captures the files in the %AppData section) Directory%\Adobe\Acrobat\Whapi folder. The files in the subdirectories are %Appdata Directory% included. (the Application Data directory, a subdirectory <Files_From_Folder>%AppData Directory% of the user profile \Adobe\Acrobat\Wh directory) api\*.*</Files_From_Folder> SMA captures the files in the %AppData %LocalAppdata Directory%\Adobe\Acrobat\Whapi Directory% (the folder. The files in the subdirectories are Application Data not included. directory in the Local Settings folder, a <Files_From_Folder>%AppData Directory% subdirectory of the user \Adobe\Acrobat\Wh api\*.* /s</Files_From_Folder> profile directory) SMA captures the files in the %AppData %Cookies Directory%, a Directory%\Adobe\Acrobat\Whapi subdirectory of the user folder. The files in the subdirectories are profile directory included. %Favorites Directory% , <Files_From_Folder>%AppData Directory% a subdirectory of the \Adobe\Acrobat\Wh user profile directory api</Files_From_Folder> %Personal Directory% , If \ does not follow Whapi, SMA a subdirectory (My treats Whapi not as a folder but as a Documents) of the user file. profile. This environment variable cannot be used by Windows NT4.) %UserProfile Directory%, the User Profile directory.
112
Table 17. Migrating additional application settings: Application files (continued) Setting <Files_From_Folders> (continued) Parameter v Location\ specifies a fully qualified directory. You can use wildcard characters in the path. If you specify a directory, all files are copied. v [File] is an optional parameter that can be used only if Location specifies a directory, and File is the file to be copied. You can use wildcard characters in the file name. v [/s] is an optional parameter. If you use [/s], all files in all subdirectories are copied. If you are using SMA 6.0, you can use a Windows environment variable. The environment variable of the user who started SMA is used as the value of the Windows environment variable. <Registries> hive is either HKLM or HKCU. keyname is the keyname. value is an optional command that specifies the registry value being migrated. Specifies the registry entries to be migrated. For example, <Registries> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat </keyname> <value></value> </Registry> </Registries> Specifies the registry keys and values to be excluded from the selected registry entries. For example, <Registry_Excludes> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader \5.0\AdobeViewer </keyname> <value>xRes</value> </Registry> </Registry_Excludes> Description
<Registry_Excludes>
hive is either HKLM or HKCU. keyname is the keyname. value is an optional command that specifies the registry value being migrated.
113
Table 17. Migrating additional application settings: Application files (continued) Setting <Files_Through_Registries> Parameter <OS> Description Specifies the customization files to be migrated.
specifies the operating system For example, and is one of the following values: <Files_Through_Registries> v Win7 <Files_Through_Registry> v WinVista <OS>WinXP</OS> v WinXP <Registry> <hive>HKCU</hive> v Win2000 <keyname>Software\Lotus\Organizer \99.0\Paths</keyname> <Registry> specifies the <value>Backup</value> registry entry and is in the </Registry> format hive,keyname,value, <File>*.*/s</File> where: </Files_Through_Registry> v hive is either HKLM or </Files_Through_Registries> HKCU. v keyname is the keyname. v value is an optional command that specifies the registry value being migrated. File is the file name. You can use wildcard characters. <SourceBatchProcessing> <SourceBatchProcessing> <!CDATA[batch commands]] </SourceBatchProcessing> <SourceBatchProcessing> performs batch processing before <Files_From_Folders> is processed by Capture. For example, <SourceBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3]] </SourceBatchProcessing> <PreTargetBatchProcessing> <PreTargetBatchProcessing> <PreTargetBatchProcessing> performs batch <!CDATA[batch commands]] processing before <Registries> is processed </PreTargetBatchProcessing> by Apply. For example, <PreTargetBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3]] </PreTargetBatchProcessing> <TargetBatchProcessing> <TargetBatchProcessing> <!CDATA[batch commands]] </TargetBatchProcessing> <TargetBatchProcessing> performs batch processing after <Registries> is processed by Apply. For example, <TargetBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3]] </TargetBatchProcessing>
Creating an application file

To determine which application settings must be migrated for custom application files, you must carefully test the applications.
114
To create an application file, do the following: 1. Use an ASCII text editor to open an existing application.XML file. If you installed SMA in the default location, the application.XML files are in the d:\Program Files\ThinkVantage\SMA\Apps directory, where d is the drive letter of the hard disk drive. 2. Modify this application.XML file for the application and application settings that you want to migrate. 3. Modify the information in the <Applications> section. 4. Modify the <Name> and <Version> commands in the <Application ShortName=ShortName> section. 5. Determine which registry keys must be migrated: a. Click Start Run. The Run window opens. In the Open field, type regedit and click OK. The Registry Editor window opens.
Figure 1. Advanced administrative topics: The Registry Editor window
b. c. d. e.
In the left pane, expand the HKEY_LOCAL_MACHINE node. Expand the Software node. Expand the vendor-specific node; for example, Adobe. Continue navigating until you find the registry key for the application. In this example, the registry key is SOFTWARE\Adobe\Acrobat Reader\6.0.
115
Figure 2. Advanced administrative topics: The Registry Editor windowFinding a registry key
f. Set the value of the Detect field. For example:

<Detects> <Detect> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0</keyname> </Detect> <Detects>
6. Modify the <Install_Directories> section. 7. Determine the path to the directory where the application will be installed. a. From the Registry Editor window, navigate to the HKLM\SOFTWARE\ Adobe\Acrobat Reader\6.0\InstallPath node.
116
Figure 3. Advanced administrative topics: Registry Editor window: Finding the installation path
b. Add the appropriate command to the <Install_Directories> section of the application file. For example:
<Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory>
Note: If you do not find an application-specific directory in the HKLM\Software\Microsoft\Windows\CurrentVersion\AppPaths directory, you must find a directory that contains the installation path elsewhere in the HKLM\Software tree. Then use that key in the <Install_Directories> section. 8. In the <Files_From Folders> section, specify the customization files you want to migrate. a. Since many applications, by default, save files in the Documents and settings subdirectory, check the Application data directory for directories that pertain to the application. If there is one, you can use the following command to migrate the directory and files:
<Files_From_Folder>SMAvariable\Location\[File] [/s] </Files_From_Folder>
where Location/ is a fully qualified file or directory, and [File] is an optional parameter that can be used only if Location/ specifies a directory. In the Adobe Reader example, the customization files are in the Preferences directory.
117
Figure 4. Advanced administrative topics: Customization files in the Documents and settings folder
b. Check all related directories for personal settings that might be stored there. c. Check the Local Settings directory. 9. Determine registry entries that you want to migrate. They will be in HKCU (HKEY_CURRENT_USER). In the <Registries> section of the application file, add the appropriate commands. 10. Save the application.XML file in the d:\Program Files\ThinkVantage\SMA\ Apps directory, where d is the drive letter of the hard disk drive. 11. Test the new application file.
118
Example of an application.XML file for Adobe Reader

This section presents an application file for the Adobe Reader program.
<?xml version="1.0"?> <Applications> <Family>Adobe Acrobat Reader</Family> <SMA_Version>SMA 6.0</SMA_Version> <APP>Acrobat_Reader_80</APP> <APP>Acrobat_Reader_70</APP> <APP>Acrobat_Reader_60</APP> <APP>Acrobat_Reader_50</APP> <Application ShortName="Acrobat_Reader_50"> <AppInfo> <Name>Acrobat_Reader_5.0</Name> <Version>5.0</Version> <Detects> <Detect> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0</keyname> </Detect> </Detects> </AppInfo> <Install_Directories> <Install_Directory> <OS>WinVista</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>Win2000</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\InstallPath<keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>Win98</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinNT</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> </Install_Directories>
119
<Files_From_Folders> <Files_From_Folder>%AppData Directory%\Adobe\Acrobat\Whapi\*.* /s</Files_From_Folder> <Files_From_Folder>%Personal Directory%\*.pdf</Files_From_Folder> <Files_From_Folders> <Files_Through_Registries></Files_Through_Registries> <Registries> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat</keyname> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader</keyname> </Registry> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Persistent Data</keyname> </Registry> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\AdobeViewer</keyname> <value></value> </Registry> </Registries> <Registry_Excludes> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\AdobeViewer</keyname> <value>xRes</value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\Adobe\Viewer</keyname> <value>yRes</value> </Registry> <Registry_Excludes> <SourceBatchProcessing></SourceBatchProcessing> <PreTargetBatchProcessing> <![CDATA[ if /i "%SourceUserName%" == "SYSTEM" goto Done if /i "%SourceApp%" == "Acrobat_Reader_50" goto Update50 goto Done :Update50 regfix /delete "HKCU\Software\Adobe\Acrobat Reader\5.0\AdobeViewer" regfix /delete "HKLM\Software\Adobe\Acrobat Reader\5.0\AdobeViewer" :Done ]] </PreTargetBatchProcessing> <TargetBatchProcessing></TargetBatchProcessing> </Application> <Application ShortName="Acrobat_Reader_6.0"> <AppInfo> <Name>Adobe Acrobat Reader 6.0<\Name> <Version>6.0</Version> <Detects> <Detect> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0</keyname> </Detect> </Detects> <\AppInfo> <Install_Directories> <Install_Directory> <OS>WinVista</OS> <Registry>
120
<hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>Win2000</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>Win98</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinNT</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> </Install_Directories> <Files_From_Folders> <Files_From_Folder>%AppData Directory%\Adobe\Acrobat\6.0\*.* /s</Files_From_Folder> <Files_From_Folder>%Personal Directory%\*.pdf</Files_From_Folder> </Files_From_Folders> <Files_Through_Registries></Files_Through_Registries> <Registries> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat</keyname> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader</keyname> </Registry> </Registries> <Registry_Excludes> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\AdobeViewer</keyname> <value>xRes</value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\6.0\Adobe\Viewer</keyname> <value>yRes</value> </Registry> <Registry_Excludes> <SourceBatchProcessing></SourceBatchProcessing>
121
<PreTargetBatchProcessing></PreTargetBatchProcessing> <TargetBatchProcessing> <![CDATA[ if /i "%SourceApp%" == "Acrobat_Reader_50" goto Update50 goto Done :Update50 regfix "HKCU\Software\Adobe\Acrobat Reader\5.0" "HKCU\Software\Adobe\Acrobat Reader\6.0" regfix "HKLM\Software\Adobe\Acrobat Reader\5.0\AdobeViewer" "HKLM\Software\Adobe\Acrobat Reader\6.0\AdobeViewer" :Done ]] </TargetBatchProcessing> </Application> <Application ShortName="Acrobat_Reader_7.0"> <AppInfo> <Name>Adobe Acrobat Reader 7.0<\Name> <Version>6.0</Version> <Detects> <Detect> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\7.0</keyname> </Detect> </Detects> <\AppInfo> <Install_Directories> <Install_Directory> <OS>WinVista</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>Win2000</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>Win98</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinNT</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory>
122
</Install_Directories> <Files_From_Folders> <Files_From_Folder>%AppData Directory%\Adobe\Acrobat\7.0\*.* /s</Files_From_Folder> <Files_From_Folder>%Personal Directory%\*.pdf</Files_From_Folder> </Files_From_Folders> <Files_Through_Registries></Files_Through_Registries> <Registries> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat</keyname> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader</keyname> </Registry> </Registries> <Registry_Excludes> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\AdobeViewer</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\AdobeViewer</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\AdobeViewer</keyname> <value>xRes</value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\7.0\AdobeViewer</keyname> <value>yRes</value> </Registry> <Registry_Excludes> <SourceBatchProcessing></SourceBatchProcessing> <PreTargetBatchProcessing></PreTargetBatchProcessing> <TargetBatchProcessing> <![CDATA[ if /i "%SourceApp%" == "Acrobat_Reader_50" goto Update50 if /i "%SourceApp%" == "Acrobat_Reader_60" goto Update60 goto Done :Update50 regfix "HKCU\Software\Adobe\Acrobat Reader\5.0" "HKCU\Software\Adobe\Acrobat Reader\7.0" regfix "HKLM\Software\Adobe\Acrobat Reader\5.0\AdobeViewer" "HKLM\Software\Adobe\Acrobat Reader\7.0\AdobeViewer" goto Done :Update60 regfix "HKCU\Software\Adobe\Acrobat Reader\6.0" "HKCU\Software\Adobe\Acrobat Reader\7.0" regfix "HKLM\Software\Adobe\Acrobat Reader\6.0\AdobeViewer" "HKLM\Software\Adobe\Acrobat Reader\7.0\AdobeViewer" :Done ]] </TargetBatchProcessing> </Application> <Application ShortName="Adobe Acrobat Reader 80"> <AppInfo> <Name>Adobe Acrobat Reader 8.0</Name> <Version>8.0</Version> <Detects> <Detect>
123
<hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\8.0</keyname> </Detect> </Detects> </AppInfo> <Install_Directories> <Install_Directory> <OS>Win7</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinVista</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> <Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\InstallPath</keyname> <value>(Default)</value> </Registry> </Install_Directory> </Install_Directories> <Files_From_Folders> <Files_From_Folder>%AppData Directory%\Adobe\*.* /s</Files_From_Folder> <Files_From_Folder>%LocalAppData Directory%\Adobe\Updater5\AdobeUpdaterPrefs.dat</Files_From_Folder> </Files_From_Folders> <Files_Through_Registries></Files_Through_Registries> <Registries> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\3D\</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Access</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Accessibility</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Annots\cPrefs</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Appearance</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\AVDisplay</keyname> <value></value>
124
</Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value>
Reader\8.0\AVGeneral</keyname>
Reader\8.0\AVGenaral\cDockables\cOCGs</keyname>
Reader\8.0\AVGenaral\cToolbars</keyname>
Reader\8.0\AVTracker</keyname>
Reader\8.0\AutoSaveDocs</keyname>
Reader\8.0\AutoScroll</keyname>
Reader\8.0\FullScreen</keyname>
Reader\8.0\FormsPrefs</keyname>
Reader\8.0\HandTool</keyname>
Reader\8.0\HostedServices\cProtectPDF</keyname>
Reader\8.0\HostedServices\cMeeting</keyname>
Reader\8.0\HostedServices\cMeetingInfo</keyname>
Reader\8.0\Identity</keyname>
125
</Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Intl</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat <value></value>
Reader\8.0\JSPrefs</keyname>
Reader\8.0\Language</keyname>
Reader\8.0\Measuring</keyname>
Reader\8.0\Measuring3D</keyname>
Reader\8.0\multimedia</keyname>
Reader\8.0\multimediaLanguage</keyname>
Reader\8.0\Originals</keyname>
Reader\8.0\OptionalContent</keyname>
Reader\8.0\PICommonPrefs</keyname>
Reader\8.0\PrefsDialog</keyname>
Reader\8.0\ReadAloud</keyname>
Reader\8.0\RememberedViews</keyname>
126
</Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Search\cOptions</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Security</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Selection</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\SDI</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Spelling</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Tracker</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\TrustManager</keyname> <value></value> </Registry> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\8.0\Window</keyname> <value></value> </Registry> </Registries> <Registry_Excludes></Registry_Excludes> <SourceBatchProcessing></SourceBatchProcessing> <PreTargetBatchProcessing> <![CDATA[ if /i "%SourceUserName%" == "SYSTEM" goto Done regfix /delete "HKCU\Software\Adobe\Acrobat Reader\8.0\Originals" goto Done :Done ]] </PreTargetBatchProcessing> <TargetBatchProcessing> <![CDATA[ if /i "%SourceUserName%" == "SYSTEM" goto Done if /i "%SourceApp%" == "Acrobat_Reader_50" goto Done if /i "%SourceApp%" == "Acrobat_Reader_60" goto Update60 if /i "%SourceApp%" == "Acrobat_Reader_70" goto Update70 goto Done :Update60 regfix "HKCU\Software\Adobe\Acrobat Reader\6.0" "HKCU\Software\Adobe\Acrobat Reader\7.0" regfix "HKLM\Software\Adobe\Acrobat Reader\6.0\AdobeViewer" "HKLM\Software\Adobe\Acrobat Reader\7.0\AdobeViewer"
127
goto Update70 :Update70 regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete regfix /delete "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat "HKCU\Software\Adobe\Acrobat Reader\7.0\AdslnReader" Reader\7.0\Annots\cAnnots\cAnnot\\tauthor" Reader\7.0\DocumentStatus" Reader\7.0\EBookPlugin" Reader\7.0\FindSearch" Reader\7.0\Installer" Reader\7.0\Identity" Reader\7.0\InstallPath" Reader\7.0\Multimedia" Reader\7.0\TaskButtons" Reader\7.0\Updater" Reader\7.0\Settings" Reader\7.0\Highlight" Reader\7.0\FocusRect"
regfix /rename "HKCU\Software\Adobe\Acrobat Reader\7.0\3D" "b3DShowToolbar" "i3DShowToolbar" regfix "HKCU\Software\Adobe\Acrobat Reader\7.0\DiskCabs" "HKCU\Software \Adobe\Adobe Acrobat\8.0\DiskCabs" regfix /delete "HKCU\Software\Adobe\Acrobat Reader\7.0\DiskCabs" regfix /delete "HKCU\Software\Adobe\Acrobat Reader\8.0\Originals" regfix "HKCU\Software\Adobe\Acrobat Reader\7.0" "HKCU\Software\Adobe\Acrobat Reader\8.0" regfix /delete "HKCU\Software\Adobe\Acrobat Reader\6.0" regfix /delete "HKCU\Software\Adobe\Adobe Acrobat\6.0" regfix /delete "HKCU\Software\Adobe\Acrobat Reader\7.0" goto Done :Done ]] </TargetBatchProcessing> </Application> </Applications>
128
Appendix A. File and registry exclusions

This appendix presents information about files and registry entries that cannot be migrated by use of SMA.
File and directory exclusions

The following files and directories are excluded from the scan process and so cannot be captured: v pagefile.sys v hal.dll v ntuser.dat v ntuser.dat.log v ntuser.dat.ini v system.dat v user.dat v v v v v v v v v v v bootsect.dos io.sys msdos.sys ntdetect.com ntldr $ldr$ hiberfil.sys boot.ini system.ini msdos.--command.com
v win386.swp
v system.ini v system.1st v config.sys v autoexec.bat v systemdir\config, where systemdir is the operating-system directory v SMA temporary directory Also, the system volume information is not scanned and so cannot be captured.
Registry exclusions
SMA cannot capture the following registry entries: v HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer v HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion v HKLM\\Hardware v HKLM\\sam v HKLM\\security
129
v v v v v v v v v v v v v v v v v v
HKLM\\system\\ControlSet00N HKLM\\system\\currentcontrolset\\enum HKLM\\system\\currentcontrolset\\services\\Tcpip HKLM\\system\\currentcontrolset\\hardware profiles HKLM\\SOFTWARE\\Microsoft\\Cryptography HKLM\\SOFTWARE\\Policies HKLM\\System\\CurrentControlSet\\Control\\Class HKLM\\System\\CurrentControlSet\\Control\\Network HKLM\\System\\CurrentControlSet\\Control\\DeviceClasses HKLM\\Software\\Microsoft\\RPC HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Syncmgr HKLM\\Software\\Classes\\CID HKLM\\System\\CurrentControlSet\\Services\\Class\\Net HKCU\\AppEvents HKCU\\Control Panel HKCU\\Identities HKCU\\InstallLocationsMRU
v HKCU\\Keyboard layout v HKCU\\Network v HKLM\\Config v v v v HKLM\\Driver HKLM\\Enum HKLM\\Network HKLM\\Hardware
v HKLM\\Security In addition, registry keys are excluded when the final node is one of the following text strings: v StreamMRU v Cache v Enum
130
Appendix B. Migration of user profiles supported in SMA 6.0

SMA 6.0 supports two kinds of migration: v A foreground single-user profile v A multiuser profile You can migrate a single-user profile as follows: v To a different user name v From local account to domain account v From domain account to local account The following tables show valid migration scenarios: Table 18 for a single-user migration, Table 19 for a multiuser migration.
Table 18. Migration of a single-user profile User account on the target computer Source and target accounts have the same user name Local account Yes Yes Domain account Yes Yes Source and target accounts have different user names Local account Yes Yes Domain account Yes Yes
User account on the source computer Local account Domain account
Table 19. Multiuser migration User account on the target computer (migration by delayed apply) Foreground source and target accounts have the same user name Local account Yes Yes Domain account Yes Yes Foreground source and target accounts have different user names Local account No
1
User account on the source computer Local account Domain account
Domain account No1 No1
No1
Migration to a different user name account is supported for foreground user migration only. Table 20 and Table 21 on page 132 show which users of the source computer will be migrated to the target computer.
Table 20. Case 1: Same user names on the source and target computers User name User A (logon) User B User C User A Yes
1
User B Yes2
User C
Yes3
The settings for the foreground user, user A, are correctly migrated to the target computer. 2 The settings for the background user, user B, are correctly migrated to the target computer if user Bs password is the same as the user namethat is, user B. If the
131
password is different from the user name, user B will not be migrated. 3 User C is created on the target computer, and the settings for user C are copied from the source computer.
Table 21. Case 2: Different user names on the source and target computers User name User A (logon) User B User C User D User A No
4
User B (logon) Yes

5
User C
User D
No6 No7 No8
The settings for user A of the source computer will not be migrated to user A of the target computer. If the logon user names on the source and the target computers are different, only the settings of the logon user are migrated. 5 The settings for user A will be migrated to user B, because user B is currently logged on to the target computer. 6 The settings for user B on the source PC will not be migrated, because the settings for user A of the source PC are applied to user B on the target PC. 7 User C will not be created on the target PC. If the logon user names on the source and the target computers are different, only the settings of the logon user are migrated. 8 User D will not be migrated to the target PC. If the logon user names on the source and the target computers are different, only the settings of the logon user are migrated. In order to identify user profiles available for migration, do the following: 1. Logon to the source PC with administrative privilege. 2. Create USRCHK.BAT and USRCHK_CMD.XML files at the SMA installation directory. 3. Run USRCHK.BAT from the command prompt; user accounts available for migration will be listed. 4. If the desired domain user profile is not listed, the users cached credentials may have expired. To update the cached credentials, log on to this account. Example of a USRECHK.BAT
@echo off "%sma%smabat" /c "%sma%USRCHK_CMD.XML" /n "%sma%usrchk.sma" find "I1200" "%sma%sma.log" del /q "%sma%*.log" del /q "%sma%usrchk.sma" pause
Example of a USERCHK_CMD.xml
<?xml version="1.0" ?> <?sma version="5.0" ?> <controlcard> <FilesAndFolders> <run>false</run> </FilesAndFolders> <Desktop> <desktop_settings>false</desktop_settings> <accessibility>false</accessibility> <active_desktop>false</active_desktop> <colors>false</colors> <desktop_icons>false</desktop_icons>
132
<display>false</display> <icon_metrics>false</icon_metrics> <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>false</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>false</taskbar> <time_zone>false</time_zone> <wallpaper>false</wallpaper> <window_metrics>false</window_metrics> </Desktop> <Network> <ip_subnet_gateway_configuration>false</ip_subnet_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drives>false</shared_folders_drives> <mapped_drives>false</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <IncUsers> <UserName>$(all)</UserName> </IncUsers> </controlcard>
Appendix B. Migration of user profiles supported in SMA 6.0
133
134
Appendix C. Compatibility with earlier versions

This appendix presents information about the compatibility of SMA 6.0 or earlier versions. The architecture of SMA 6.0 and SMA 5.2 have been redesigned compared to SMA 4.2 or earlier versions. Therefore an SMA profile (migration file) created by use of SMA 4.2 or an earlier version cannot be used by SMA 6.0 or SMA 5.2. Because SMA 6.0 and 5.2 use the XML file format for its command file and application files, command files and application files created by use of SMA 4.2 can be used with SMA 5.2. If you specify an old SMA 4.2 version command file or application files instead of SMA 6.0 or 5.2 XML files, SMA automatically translates those files to SMA 6.0 or 5.2 data. The following commands from SMA 4.2 have become obsolete: v capture_ntfs_attribute in [MISC] section v removable_media in [MISC] section v createselfextractingexe in [MISC] section
The following commands have been added for SMA 5.x and SMA 6.0: v time_zone in the <Desktop> section v desktop_settings (Desktop theme/Color scheme/Visual effect) in the <Desktop> section
Command file
The SMA 4.2 commands that can be handled as SMA 5.2 or SMA 6.0 commands are briefly described in the Table 22.
Table 22. Commands in the command file Commands Password SMA 4.2 [password_start] plain_password = xxxx [password_end] [profile_path_and_name_start] output_profile = c:\migrate.sma [profile_path_and_name_end] [misc_settings_end] using_peer_to_peer_migration = 1 [misc_settings_end] SMA 5.2 and SMA 6.0 <Password> <PlainPassword>xxxx</PlainPassword> </Password> <ArchiveFile> <filename>c:\migrate.sma</filename> </ArchiveFile> <TransferMode> <mode>P2P</mode> </TransferMode> <P2P> <connection_id>xxxx<connection_id> </P2P>
Migration File PC to PC migration
135
Table 22. Commands in the command file (continued) Commands Desktop Settings SMA 4.2 [desktop_start] accessibility = 0 active_desktop = 1 colors = 1 desktop_icons = 1 display = 1 icon_font = 0 keyboard = 0 mouse = 0 pattern = 0 screen_saver = 1 sendto_menu = 0 shell = 0 sound = 0 start_menu = 0 taskbar = 1 wallpaper = 1 window_metrics = 0 [desktop_end] SMA 5.2 and SMA 6.0 <Desktop> <accessibility<false</accessibility> <active_desktop>true</active_desktop> <colors>true</colors> <desktop_icons>true</desktop_icons> <display>true</display> <icon_metrics>false</icon metrics) <keyboard>false</keyboard> <mouse>false</mouse> <pattern>false</pattern> <screen_saver>true</screen_saver> <sendto_menu>false</sendto_menu> <shell>false</shell> <sound>false</sound> <start_menu>false</start_menu> <taskbar>true</taskbar> <wallpaper>true</wallpaper> <window_metrics>false</window_metrics> <time_zone>true</time_zone> <desktop_settings>true</desktop_settings> </Desktop> Note: Unlike earlier versions, SMA 5.2 and SMA 6.0 support the migration of time_zone and desktop_settings (Desktop theme/Color scheme/Visual effect). Network Settings [network_start] ip_subnet_gateway_configuration = 0 dns_configuration = 0 wins_configuration = 0 computer_name = 0 computer_description = 0 domain_workgroup = 0 shared_folders_drives = 1 mapped_drives = 1 dialup_networking = 0 microsoft_networking = 0 odbc_datasources = 0 [network_end] <Network> <ip_subnet_gateway_configuration>false</ip_subn et_gateway_configuration> <dns_configuration>false</dns_configuration> <wins_configuration>false</wins_configuration> <computer_name>false</computer_name> <computer_description>false</computer_description> <domain_workgroup>false</domain_workgroup> <shared_folders_drivers>true</shared_folders_driv es> <mapped_drives>true</mapped_drives> <dialup_networking>false</dialup_networking> <microsoft_networking>false</microsoft_networking> <odbc_datasources>false</odbc_datasources> </Network> <Applications> <Application>Adobe Acrobat Reader</Application> <Application>Lotus Notes</Application> <Application>Microsoft Internet Explorer</Applica tion> </Applications> <Registry> <hive>HKLM</hive> <keyname>sofware\microsoft\currentversion</key name> <value>value</value> </Registry> <ExcludeDrives> <Drive>d</Drive> </ExcludeDrives>
Application
[applications_start] Adobe Acrobat Reader Lotus Notes Microsoft Internet Explorer [applications_end] [registry_start] HKLM,"software\microsoft\currentversi on", "value"[registry_end]
Registry
Exclude Drive
[exclude_drive_start] d: [exclude_drive_end]
136
Table 22. Commands in the command file (continued) Commands SMA 4.2 SMA 5.2 and SMA 6.0 <IncDescription> <Description>c:\data\*.cpp /s</Description> <DataCompare> <Operand>NEWER</Operand> <Date>05/01/2005</Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> <Dest>c:\NewData</Dest> <Operation>P/Operation> </IncDescription> <ExcDescription> <Description>c:\data\*.cpp /s</Description> <DataCompare> <Operand>OLDER</Operand> <Date>05/01/2005</Date> </DateCompare> <SizeCompare> <Operand></Operand> <Size></Size> </SizeCompare> </ExcDescription>
File Inclusion [includefile_start] c:\data\*.cpp [includefile_end] [includepath_start] c:\data [includepath_end] [includefiledescription_start] *.cpp,c:\data,c:\NewData,P,NEWER, 05/01/2005 [includefiledescription_end] File Exclusion [excludefile_start] c:\data\*.cpp [excludefile_end] [excludepath_start] c:\data [excludepath_end] [excludefiledescription_start] *.cpp,c:\data,c:\NewData,OLDER, 05/01/2005 [excludefiledescription_end] [excludefilesandfolders_start] %:\data\text%\*.cpp [excludefilesandfolders_end] User Inclusion [userprofiles_start] GetAllUserProfiles = 1 Administrator [userprofiles_end] [excludeuserprofiles_start] localuser2 SMADOM1\domainuser2 [excludeuserprofiles_end] [misc_settings_start] printers = 0 defaultprinteronly = [misc_settings_end] [misc_settings_start] bypass_registry = quota=0 stop_if_quota_exceeded = 0 capture_ntfs_attribute = user_exit = C:\EXIT.EXE overwrite_existing_files = 1 temp_file_location = c:\templog_fi le_location = c:\log removable_media = 0 AutoReboot = 2 resolve_icon_links = 1 createselfextractingexe = 0using_peer_to_peer_migration = 1 [misc_settings_end]
<IncUsers> <UserName>$(all)</UserName> <UserName>Administrator</UserName> </IncUsers> <ExcUsers> <UserName>localuser2</UserName> <UserName>SMADOM1\domainuser2</UserName> </ExcUsers> <Printer> <PrinterName>IBM Network Printer</PrinterName> </Printer> <MISC> <bypass_registry>true</bypass_registry> <quota></quota> <user_exit_after_apply>c:\EXIT.EXE</user_exit_af ter_apply> <overwrite_existing_files>true</overwrite_existi ng_files> <temp_file_location>c:\temp</temp_file_location> <log_file_location>c:\log</log_file_location> <AutoReboot>2</AutoReboot> <resolve_icon_links>true</resolve_icon_links> <span_size>124</span_size> </MISC> Note: capture_ntfs_attribute, removable_media, and createselfextractingexe are obsolete in SMA 5.1.
User Exclusion
Printer
Misc
137
Application file
To use SMA 4.2 application files with SMA 6.0, copy those files to the SMA6.0_Install_Directory/apps folder (where SMA6.0_Install_Directory is the directory in which SMA 6.0 is installed). Table 23 provides the application file commands and the descriptions on how they are handled in SMA4.2, SMA5.2, and SMA6.0.
Table 23. Appendix: Application file commands Commands Application Information SMA 4.2 [General] Family= Application Name SMA_Version= 4.2 APP1= Application_1 (=shortname) APP2= Application_2 SMA 5.2 and SMA 6.0 <Applications> <Family>Application name</Family> <SMA_Version>5.0</SMA_Version> <APP>Application_1</APP> <APP>Application_2</APP>
[App_Info.shortname] <Application ShortName="Application_1"> Name= Application Name <AppInfo> Version= 5.0 <Name>Application Name</Name> Detect_1= hive, "Registry keyname" <Version>5.0</Version> <Detects> <Detect> <hive>hive</hive> <keyname>Registry keyname</keyname> </Detect> <Detects> </AppInfo> Set %Install Directory% SMAvariable [Install_Directories.shortname] WinXP= HKLM, "SOFTWARE\SMA ", "INSTALLDIR" <Install_Directories> <Install_Directory> <OS>WinXP</OS> <Registry> <hive>HKLM</hive> <keyname>SOFTWARE\SMA</keyname> <value>INSTALLDIR</value> </Registry> </Install_Directory> </Install_Directories> <Files_From_Folders> <Files_From_Folder>%InstallDirectory%\D ata\*.txt</Files_From_Folder> </Files_From_Folders> <Registries> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat</key name> <value>(Default)</value> </Registry> </Registries> <Registry_Excludes> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat</key name> <value>(Default)</value> <Registry> </Registry_Excludes>
File inclusion
[Files_From_Folders.shortname] %Install Directory%, Data, *.txt
Registry inclusion
[Registry.shortname] HKCU, "Software\Adobe\Acrobat", (Default)
Registry exclusion
[Registry.shortname] HKCU, "Software\Adobe\Acrobat", (Default)
138
Table 23. Appendix: Application file commands (continued) Commands SourceBatchProcessing SMA 4.2 SMA 4.2 does not support SourceBatchProcessing SMA 5.2 and SMA 6.0 <SourceBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migra tion del c:\migration\*.mp3]] </SourceBatchProcessing> <PreTargetBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migra tion del c:\migration\*.mp3]] </PreTargetBatchProcessing> <TargetBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migra tion del c:\migration\*.mp3]] </TargetBatchProcessing>
PreTargetBatchProcessing
[PreTargetBatchProcessing] copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3]] [/PreTargetBatchProcessing] [TargetBatchProcessing] copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3]] </TargetBatchProcessing>
TargetBatchProcessing
Translation of application file

SMA includes a tool that translates an application file of SMA 4.2 into an application file of SMA 5.2 or SMA 6.0. If you installed SMA in the default location, AppFileTransfer.exe is in the d:\Program Files\ThinkVantage\SMA directory, where d is the drive letter of the hard disk drive. The AppFileTransfer.exe command uses the following syntax:
AppFileTransfer "SMA42ApplicationFile" "SMA51ApplicationFile"
For example, to translate Lotus_Notes.smaapp of SMA 4.2 into Lotus_Notes.xml of SMA 5.2 or SMA 6.0, type the following string in the command prompt:
d:\Program Files\ThinkVantage\SMA\AppFileTransfer C:\Apps\Lotus_Notes.smaapp C:\Ap ps\Converted\Lotus_Notes.xml
Lotus_Notes.xml is created in the C:\Apps\Converted folder.
139
140
Appendix D. Notices
Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult your local Lenovo representative for information on the products and services currently available in your area. Any reference to an Lenovo product, program, or service is not intended to state or imply that only that Lenovo product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any Lenovo intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any other product, program, or service. Lenovo may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: Lenovo (United States), Inc 1009 Think Place Building One Morrisville, NC 27560 USA Attention: Lenovo Director of Licensing LENOVO GROUP LTD. PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. The products described in this document are not intended for use in implantation or other life support applications where malfunction may result in injury or death to persons. The information contained in this document does not affect or change Lenovo product specifications or warranties. Nothing in this document shall operate as an express or implied license or indemnity under the intellectual property rights of Lenovo or third parties. All information contained in this document was obtained in specific environments and is presented as an illustration. The result obtained in other operating environments may vary. Lenovo may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any references in this publication to non-Lenovo Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this Lenovo product, and use of those Web sites is at your own risk
141
Any performance data contained herein was determined in a controlled environment. Therefore, the result in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Trademarks
The following terms are trademarks of Lenovo in the United States, other countries, or both: Lenovo Rescue and Recovery ThinkVantage The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM (used under license) Approach Lotus Lotus Notes Lotus Organizer Freelance Graphics Sametime SmartSuite Word Pro 1-2-3 The following terms are trademarks of the Microsoft group of companies: Microsoft Access Internet Explorer Media Player MSN Outlook Visio Windows Windows NT Windows Vista Other company, product, or service names may be trademarks or service marks of others.
142

System Migration Assistant Deployment Guide V6

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

System Migration Assistant Deployment Guide V6

Încărcat de

Drepturi de autor:

Formate disponibile

System Migration Assistant Deployment Guide Version 6.

Chapter 5. Best practices . . . . . . . 43

Chapter 2. Firewall management . . . . 11

Chapter 3. System Migration Assistant Customization . . . . . . . . . . . 15

Chapter 6. Application settings available for migration . . . . . . . . 91

Appendix A. File and registry exclusions . . . . . . . . . . . . 129

Chapter 4. Performing a migration in batch mode. . . . . . . . . . . . . 21

Appendix D. Notices . . . . . . . . 141

Copyright Lenovo 2008, 2009

System Migration Assistant Deployment Guide Version 6.0

Copyright Lenovo 2008, 2009

System Migration Assistant Deployment Guide Version 6.0

Chapter 1. Introducing System Migration Assistant

How SMA works

Copyright Lenovo 2008, 2009

System Migration Assistant Deployment Guide Version 6.0

Operating systems supported

Supported migration scenarios

Windows Vista Home Premium

Windows 7 Home Premium

Windows Vista Home Basic

Windows Vista Business

Windows Vista Ultimate

Windows 2000 Professional

Windows 7 Home Basic

System Migration Assistant Deployment Guide Version 6.0

Windows Vista Home Premium

Windows 7 Home Premium

Windows Vista Home Basic

Windows Vista Business

Windows Vista Ultimate

Windows 2000 Professional

Operating system running on the source computer Windows 7 Ultimate

Windows 7 Home Basic

New features in SMA 6.0

Upgrading from previous releases

User account requirements

Type of migration Multiuser migration Yes No No No PC to PC migration Yes Yes Yes No

Settings System settings Yes Yes

Personal settings Yes Yes Yes Yes

System Migration Assistant Deployment Guide Version 6.0

Migrating multiuser profiles

System Migration Assistant Deployment Guide Version 6.0

File transfer migration

Chapter 1. Introducing System Migration Assistant

System Migration Assistant Deployment Guide Version 6.0

Chapter 2. Firewall management

Disabling the Windows Firewall

Disabling BlackICE PC Protection

Disabling McAfee Personal Firewall Plus

Disabling Norton Personal Firewall

System Migration Assistant Deployment Guide Version 6.0

Disabling Check Point Integrity Client

Chapter 2. Firewall management

System Migration Assistant Deployment Guide Version 6.0

Chapter 3. System Migration Assistant Customization

Customizing the standard migration Global options

Fully qualified file name

Fully qualified file name Yes or No

Fully qualified file name Yes or No

Show_Previous_File_Selection_Dialog Show_P2P_Messagebox Show_File_Dialog Show_Start_Processing_Dialog

Yes or No Yes or No Yes or No Yes or No

Copyright Lenovo 2008, 2009