Enterprise. Enterprise. Administrator Guide MN-PCMVENTPR-EN-04 (REV. 02/09)

Transcription

1 h t t p : / / w w w. l a p l i n k. c o m / b u s i n e s s _ s o l u t i o n s Tel (USA): +1 (425) Fax (USA): +1 (425) us at CorpSales@laplink.com Tel (UK): +44 (0) Fax (UK): +44 (0) Copyright / Trademark Notice Copyright 2009 Laplink Software, Inc. All rights reserved. Laplink, the Laplink logo, Connect Your World, and PCmover are registered trademarks or trademarks of Laplink Software, Inc. in the United States and/or other countries. Other trademarks, product names, company names, and logos are the property of their respective holder(s). MN-PCMVENTPR-EN-04 (REV. 02/09)

2 2 Installation Contents System Requirements Installing PCmover (Policy Manager and Client) PCmover Introduction Introduction to Policy Manager PCmover Client Migration Checklist Modifying Policy Files (Tabs) Start Page Access Identification Authorization Configuration Commands Connections Migration Items Migration Modifications User Map Drive Map Directory Filter File Filter Applications Custom Information Registration Reports Additional Support Feedback & Assistance

3 1 PCmover is a powerful business-class migration engine that allows organizations to automate the PC replacement process. IT s are able to enforce migration policy compliance in the transfer process and self-configure the migration experience, resulting in a well-managed migration outcome. Advanced reporting capabilities are also available, allowing visibility into the PC migration process. PCmover Policy Manager: The module used to configure and customize migrations through creating and editing policy files. In a policy file, the IT can specify what programs, files, and settings they want transferred, which PC and/or user is allowed to do the migration, and to which PC the data will be transferred. A license can also be pre-activated for an offline migration. PCmover Client: The migration application that will transfer the programs, files, and settings from the user s source (old) PC to the target (new) PC, depending on the customized settings and configurations set up by the IT in the policy file. PCmover Client can be installed and run from the user s old and new PCs, or directly from a corporate network or removable storage device. System Requirements PCmover Policy Manager (IT s PC) Windows 2000/Server 2003/XP, including Windows XP Media Center and XP Tablet PC/Vista. Installing PCmover (Policy Manager and Client) Note: In most cases, the Policy Manager should be installed on an IT s PC and the Client installed on a network shared drive accessible by all users who need to complete a PCmover migration. IMPORTANT: If you choose to install Policy Manager and PCmover Client using two separate install processes, you will need to manually set the PCmover Client root folder file path in Policy Manager. See Introduction to Policy Manager - First Time Use (page 3) for more information. 1. Save PCmover_.exe to the IT s PC from the FTP server. 2. Run PCmover_.exe. Before the PCmover InstallShield Wizard opens, the.net 2.0 Framework Setup will launch. The.Net 2.0 Framework is needed to run PCmover Policy Manager. 3. Once the PCmover InstallShield Wizard opens, follow the on-screen prompts until you reach the Custom Setup screen. 4. On the Custom Setup screen, you have the option to change the installation location for PCmover. PCmover Client Windows 2000/Server 2003/XP, including Windows XP Media Center and XP Tablet PC/Vista. The operating system on the user s new PC must be the same as or newer than the operating system on the user s old PC. All Microsoft high-priority updates should be applied to the new PC before migration:

4 2 Policy Manager: Accept the default installation of the Policy Manager to the local IT s PC. Client: Installation location should be changed to the network shared drive or other location, depending on your corporate needs. Select Client and click Change. In the dialog box that appears, enter network path in the Folder Name text field. See screen below for further help with the Custom Setup screen User Interface. Note: We recommend that you always install Microsoft Redistributable Files when installing PCmover Client. The Microsoft Redistributable Files are included because PCmover does not migrate these files from the source computer, and some applications migrated to the target computer may require these files to run properly. If you install PCmover Client on a network shared drive as recommended, the Microsoft Redistributable Files will be available for the applications on the Target computer that require these files. 5. Once the InstallShield Wizard finishes, PCmover installation is complete. Before using PCmover Policy Manager for the first time, please see the following section for important information about the application.

5 3 Introduction to Policy Manager 1. First Time Use: When running Policy Manager for the first time, click No in the dialog box that appears. Before running the Define New Migration Wizard, a policy file should be created and used in the migration setup. Note: Once you are ready to run the Define New Migration Wizard, this can be accessed from within the Policy Manager in the File menu. IMPORTANT: If you installed Policy Manager and PCmover Client using two separate install processes, you will need to manually set the PCmover Client root folder file path. Go to the Tools menu, choose Options, and enter the file path. 2. Policy Files: Control and automate PCmover migrations. Using policy files, the IT can place restrictions on PCmover migrations (Ex. No music files). The user s choices in the PCmover screens can also be limited (Ex. Only migration method allowed is a network migration). If all choices are made in the policy file by the IT, then the migration can run completely automated, with no decisions needed by the user. Master Policy File: Overriding file that applies to and controls all migrations. Usually, this file will have few migration restrictions, as any choices made in this file will apply globally. For example, if your corporation has a policy of no game applications on company PCs, the Master Policy File can be set to allow all applications to be transferred except for game applications. Note: A Master Policy File is automatically created during installation of the Policy Manager. It is saved in the same root directory as PCmover Client. Only one Master Policy File can be used at one time, and the Master Policy File must be named MasterPolicy.pol. The first time you make changes to the Master Policy File, choose to Save As and make sure the file is saved to the PCmover Client root folder. Session Policy File: Secondary file that can be set up to apply to a group of PCs (ex. Accounting) or to a specific pairing for a migration between two PCs. Note: When doing a large number of migrations, it may be useful to create a Session Policy File with restrictions and choices broad enough that it can apply to a group of PCs. Then, when setting up a migration for a PC from within this group, the general Session Policy File can be applied to this specific migration. The Policy Manager will leverage the general Session Policy file and the other selections that you make in the Define New Migration Wizard to create a new Session Policy File for that specific migration. See Setting Up a Specific Migration below for more information. 3. User Interface: Through the Policy Manager, you can edit the Master Policy File, and also create and edit Session Policy Files. Note: Laplink recommends that you save all Policy Files in paths relative to the PCmover Client root folder. See below and the Location of PCmover Components section on page 5 for specific details. MasterPolicy.pol: Each time Policy Manager is started, MasterPolicy.pol is automatically opened. Session Policy Files: To create and edit a Session Policy File, choose New Session Policy File in the File menu. Note: These Session Policy Files will by default be saved to the Documents folder on the local (IT s) PC. Laplink recommends that you don t take the default, but instead create a new folder within the PCmover Client root folder and save the Session Policy Files here. Each Session Policy File will open in a new window. Left Tabs: For both the Master Policy File and Session Policy Files, edits can be made by making choices and selections in these tabs. Many of the tabs directly correspond to a screen that the user will see

6 4 in PCmover Client. Once you have made the desired edits, remember to click Save. Note: For more information on the options available on each tab, see Modifying Policy Files on page 7. ii. Continue to follow the Wizard prompts. At the Style of Migration screen, select the Session Policy File that you want to use. Help Image: For those tabs that directly correspond to a screen in PCmover Client, this image in the lower right will show an example of that screen. Setting Up a Specific Migration: Once you have made the desired edits to MasterPolicy.pol and created a Session Policy File, a migration can be easily set up by choosing Define New Migration in the File menu. i. Follow the prompts in the Wizard. In the Choose Computers screen, select the name of the source ( old ) and target ( new ) computers. iii. Note the file path given on the last screen of the Wizard, as this path is the location from which the user will run PCmover Client. Note: For more detailed information on steps that should be completed before and after PCmover Client migrations, see PCmover Client Migration Checklist on page 6. Migration Cleanup: Once a migration has been set up with the Define New Migration Wizard, you have the option to delete files and records associated with the migration. Note: All PCs on your local subnet will show up in the dropdown lists. Alternately, you can manually enter the computer names for the source and target PCs. To access the Migration Cleanup Wizard, choose Migration Cleanup from the File menu. Follow the on-screen prompts until you reach the Cleanup screen.

7 5 Choose your desired option(s) on the Cleanup screen: 4. Location of PCmover Components: Based on application defaults and also on selections you made in the Custom Setup screen of the InstallShield Wizard. Locations of components with a typical PCmover installation. Note: Laplink recommends that you save all Policy Files, logs and reports in paths relative to the PCmover Client root folder. See below for specific details on each PCmover component. Policy Manager: IT s (local PC) program files folder. PCmover Client: If installed in the recommended location, it is in the root folder of the network shared drive. MasterPolicy.pol : PCmover Client root folder. Remove from list of defined migrations: Selecting this option removes the migration from the list of current migrations on the Identification tab in the Master Policy File. If you set up a large number of migrations, it may be useful to periodically delete migrations from this list. Note: Choosing this option does not delete the Session Policy File, but only the reference to that file. See next option for information on deleting a Session Policy File. Delete Session Policy File: Choose this option to delete a Session Policy File that is no longer needed. Delete logs, reports and remove migration directory: If the migration has already been completed and you no longer need the migration records, select this option to remove the records. Session Policy Files (for a migration pairing): Session Policy Files created by the Define New Migration Wizard are located in the SPF folder within the PCmover Client root folder. Session Policy Files (for a group of PCs): If saved in the recommended location, the Session Policy Files will be in a new folder within the PCmover Client root folder. Settings.xml File: Policy Manager root folder. Note: The Settings.xml file documents where certain components are installed and saved, such as PCmover Client and the Session Policy Files. Logs and Reports: Location depends on how the migration is set up and if the default save location is accepted. Migrations Folder: If the Define New Migration Wizard is used to set up a migration, then PCmover will create a Migrations folder within the PCmover Client root folder. Each migration pairing is given its own folder, with naming scheme of [source PC] to [target PC], to hold the logs and reports generated from that migration.

8 6 Folder specified by IT : If you chose New Session Policy File from the File menu, and you specify a folder in the Log File Directory field under the Configuration tab in that Session Policy File, the logs and reports will be saved in the specified folder. Note: Laplink recommends that you specify a folder path relative to the PCmover Client root folder. If just the name of a folder is entered in the Log File Directory field, PCmover Client reads this as a path relative to the PCmover Client root folder. If no folder with the specified name exists in the PCmover Client root folder, then PCmover Client will create a folder with this name. Default Folder Accepted: If you chose New Session Policy File on the File menu, but didn t specify a folder under the Configuration tab, the default save location will be used. The default folder is the PCmover Application Data folder on the user s migrated PC: Documents and Settings/All Users/Application Data/ Laplink/PCmover PCmover Client Migration Checklist 1. Verify your PCmover licensing is sufficient for the desired number of migrations. Note: For any questions regarding licensing, please see your Laplink Account Representative. 2. Install PCmover on your (IT s) PC. 3. Install PCmover Client on a network shared drive that is accessible by all users who will be doing a migration. 4. Verify all users have read and execute permissions for the network shared drive. 5. Enable write access for all users to the logs and reports directory on the network shared drive. 6. Run Policy Manager and edit MasterPolicy.pol to specify restrictions or choices for all migrations as needed. 7. Create and edit a Session Policy File to apply to a group of PCs. Note: For more information about editing Master Policy and Session Policy files, see Modifying Policy Files on page 7. Specifying the Session Policy File: The Session Policy File to be used for a specific migration can be specified using one of three methods. i. Auto-Identification: In the Identification tab in the Master Policy File, specify machine names and/or user names for both the source (old) and target (new) PCs, in relation to a specific Session Policy File. Using this method, only PCs and/or users identified in this section can run PCmover Client using that specific Session Policy File. When the user runs PCmover Client, the application will automatically identify the correct Session Policy File to use. Note: To make sure that users do not bypass use of a Session Policy File, choose Require a Policy File when running PCmover under the Access tab in the Master Policy File. General Session Policy File: If you need a general Session Policy File that can be used to migrate any machine or user, do not specify any machines or users in the Identification tab in the Session Policy File or in the corresponding rule in the Identification tab in the Master Policy File. IMPORTANT: If you choose to set up a general rule on the Master Policy s Identification tab to apply a Session Policy File to all PCs, Laplink recommends that you set up this general rule last.

9 7 PCmover will check the list from top to bottom for a Session Policy File that it is allowed to use for a specific migration. If the general rule is set up first, it will be at the top of the list and the application will always use that rule for migrations (even if there is a more specific rule further down the list that you designated to have used for a certain migration). You may also choose to use the Session Policy File Name ( PolicyFile ) or Session Policy ID ( PolicyID ) methods of specifying a Session Policy File (below) to avoid unintentionally using the general rule for a migration. 9. Verify that the test migration worked as expected and that logs and reports were uploaded to the network shared drive. 10. Set up migration for end user with the Define New Migration Wizard. 11. Send migration to the end user with file path link to PCmover Client. 12. Monitor status of the end user s migration with the uploaded logs and reports. ii. iii. Specific Session Policy File Name ( PolicyFile ): To specify what Session Policy File to use by its file name, run PCmover using a command line parameter as in the example listed below. (Note the space after PCmover.exe and PolicyFile ): [File path to PCmover.exe]\PCmover.exe /PolicyFile \\[File path to Policy File]\[Policy File name] Session Policy ID ( PolicyID ): To specify what Session Policy File to use by its Policy ID, run PCmover using a command line parameter as in the example listed below. (Note the space after PCmover.exe ): [File path to PCmover.exe]\PCmover.exe /PolicyID [ID Name] The Policy ID can be found in the Master Policy File s Identification tab. To change the Policy ID from the default, click on the desired Policy File rule and click Edit. Important: If settings are not made correctly in the applicable Master Policy File tabs (ex. Identification), the specific computer and/or user may be restricted from running PCmover Client with the designated policy file (even if the Session Policy File is identified through a command line parameter). 8. Test the Master Policy and Session Policy File by running PCmover Client on a virtual machine (i.e. Microsoft Virtual PC, VMware, etc). Modifying Policy Files Edits can be made to the Master Policy and Session Policy Files by making changes to the options in the tabs on the left side of the Policy Manager window. If all PCs within a department, group, or other team all need similar Session Policy configurations for executing migrations, the same Session Policy File can be used for all machines within that team. In this manner, Session Policy Files act as templates to be leveraged through the Define New Migration wizard. For more information on the Define New MIgration wizard, see Setting Up a Specific Migration on page 4. Note: Session Policy Files should be saved in a location that is accessible to all users who will be running PCmover Client. Although Session Policy Files are by default saved to the Documents folder on the local (IT s) PC, Laplink recommends that you don t take the default. Instead, create a new folder within the PCmover Client root folder and save the Session Policy Files here. The first time you make changes to the Master Policy File, choose to Save As and make sure the file is saved to the PCmover Client root folder. IMPORTANT: Unless noted otherwise, the following tabs are present in both the Master Policy and Session Policy Files. If you make conflicting edits to the same tab in both the Master Policy and Session Policy File, the changes made to the Session Policy File will take precedence in a migration.

10 8 Policy Manager Tabs: Some of the tabs correspond directly to a screen in PCmover Client. For these tabs, if you set the Interactive option to No, then PCmover Client will skip that screen. Choosing this option ensures that the user will not make changes to the settings you have pre-configured on that screen. All tabs in the Policy file (with the exception of the Start Page) give you an option to Include this page in the Policy File. If this option is unchecked, the changes you have made to the Policy File on this tab will not be incorporated into the migration. Instead, the default action will be taken by PCmover Client. Note: The option to Include this page in the Policy File is automatically checked when you make a change to the corresponding tab. Start Page Tab: The Start Page presents the with a central location for managing policy files, editing policy file descriptions, and accessing Getting Started links for additional information about PCmover. s can also launch the Define New Migration and Migration Cleanup wizards from the Start Page. Note: The Policy Manager can create two types of Policy Files: Master Policy Files and Session Policy Files. The tabs on the left hand side of the window are slightly different, depending on whether you are working within a Master Policy or Session Policy. The title bar on the Policy Manager window will indicate whether you are working within a Master Policy or Session Policy File. Access Tab (Master Policy File only): The Access Tab gives the control over how PCmover Client can be accessed, ensuring that only the migrations that have been configured by Policy Manager take place. PolicyFile / PolicyID Command Line Parameters: Disallowed - If use of the PolicyFile (File Name) and PolicyID command line parameters is disallowed, then the Session Policy Files will only be available as set up in the Identification section. Allowed - If command line parameters are allowed, users can run PCmover in a more automated fashion, eliminating the need to set up auto-identification of the Session Policy File. Session Policy File: Required - If a Session Policy File is required when running the PCmover Client, then the policy file will prevent migrations from machines for which you have not yet set up the migration policy. Not Required - If you do not require a Session Policy File, you have the flexibility of allowing direct, non-policy migrations. Note: Requiring a Session Policy File will not prevent a migration if you have set up a general rule in the Identification section that doesn t specify any machines or users for a Session Policy File. In this case, a migration from any PC will be allowed, even for those PCs that are not specified in the Session Policy File. See the Identification section for more information. Identification Tab (Master Policy File only): When PCmover Client starts running with no policy-related command-line parameter, itdetermines which Session Policy File to use by matching the machine and user against the rules defined in the Identification section. Identifying the Session Policy File: PCmover Client will check the list of rules from top to bottom and use the first rule and corresponding Session Policy FIle that it is allowed to use for a specific migration. If no match is found, PCmover Client runs with no policy file (if allowed in the Access section). If a PolicyID parameter will be defined for a Session Policy File (for use with a command line driven migration) the ID should be unique so that the Session Policy File isn t inadvertently used for the wrong PC or group of PCs (Ex: use AccountantA for an individual accountant s PC or Accounting for all PCs in the Accounting department). The Add option in this tab allows the administrator to determine which PCs or users are allowed access to the policy file when processing a migration. If the user or machine name is not added to

11 9 the identification list, then the migration will not be allowed. IMPORTANT: If you set up a rule that doesn t specify any machines or users for a Session Policy File, then all machines and users are allowed to use this Session Policy File to perform a migration. Note: If you choose to set up a general rule on the Master Policy s Identification tab to apply a Session Policy File to all PCs, Laplink recommends that you set up this general rule last. If the general rule is set up first, it will be at the top of the list, and the application will always use that rule for migrations (even if there is a more specific rule further down the list that you designated to have used for a certain migration). You may also choose to use the Session Policy File Name ( PolicyFile ) or Session Policy ID ( PolicyID ) methods of specifying a Session Policy File to avoid unintentionally using the general rule for a migration. See previous section for more information about these options on the Access tab. Authorization Tab (Session Policy Files only): A Session Policy File may be customized for use in a particular migration or for a specific machine involved in a migration. Preventing Unauthorized Migrations: Since PCmover Client accepts a command-line parameter to specify what Session Policy File to use, someone might inadvertently try to use a Session Policy File that has not been customized for their computer. To prevent this, the Authorization section lists what computers or users are authorized to use this file. If PCmover Client tries to use the Session Policy File for a machine or user not listed here, the migration won t be allowed to continue. This Authorization process still takes place even if the Session Policy File is run using the PolicyFile or PolicyID command-line parameter. Therefore, you need to make sure that machines or users involved in a migration are listed in the Identification section for this Session Policy File. IMPORTANT: If you do not specify any machines or users in either a rule in the Master Policy File or directly on the Authorization tab in the Session Policy File, this File is open for all machines and users to use for PCmover Client migrations. Configuration Tab: In the Policy File, you can specify what directories the PCmover Client will use for creating, using, and storing log files, application profiles, and rules. You also have the flexibility to provide different sets of rules or application profiles for different migrations. Relative Paths: Since PCmover Client will need to access the data in these directories, you should not use local drives or mapped drive letters that will not be correct when the client is running. The easiest way to avoid this problem is to use paths relative to the PCmover Client directory. If just the name of a folder is entered in the Log File Directory field, PCmover Client reads this as a path relative to the PCmover Client root folder. If no folder with the specified name exists in the PCmover Client root folder, then PCmover Client will create a folder with this name. Note: If you don t specify the directories, the default save location for storing log files, application profiles, and rules is the PCmover Application Data folder on the user s migrated PC: Documents and Settings/All Users/Application Data/Laplink/PCmover The default save location may not be accessible to PCmover Client, so in most cases you should override the default and save as detailed above. Be aware that PCmover Client will store files in the Log Files directory, and so you need to make sure that the users have Write access to this directory.

12 10 Commands Tab: In this tab, you can specify the particular action for the PCmover Client to perform automatically, eliminating the need for the user to select whether they are on the source or target PC. The choices are: Send - Designates that the specified computer will be the source ( old ) PC that will migrate to the target ( new ) PC. Receive - Designates that the specified computer will be the target PC that will receive a migration from the source PC. Undo - Designates that the specified computer is the target ( new ) PC and PCmover will undo a previous migration. Snapshot - Designates that PCmover Client is to create a snapshot of the specified computer. The snapshot, usually created from the target PC, is an inventory of the PC s programs, files, and settings. PCmover uses this information to ensure that anything that already exists on the target computer will not be migrated from the source computer. The snapshot is the first step of a file-based migration. Disallow - Designates that PCmover should not do anything on the specified computer. It can be used instead of the Authorization section to prevent actions on PCs that are not configured for this policy file. Migration Items Tab: PCmover Client will normally migrate all files, settings, and applications that do not already exist on the target computer. However, the user is allowed to restrict the items that are migrated, through a screen in PCmover Client. If you desire to pre-set these restrictions for the user, you may do so on this tab. If you are want the user to only migratie files, for example, select Files Only here. Note: If you choose to migrate Files and Settings only or Files only, the user will be restricted from migrating applications and/or settings, regardless of choices you make in other tabs in the Policy Manager. Corresponds to the PCmover Client screen Choose Migration Items. Migration Modifications Tab: In some cases you may need to configure some of the more advanced modification options for a migration such as Not moving the Outlook Express Identity and Address Book. If you choose to not pre-set the Advanced Migration Modification settings, the default action will be taken for each option. Note: Corresponds to the PCmover Client screen Select Migration Modifications. Note: Corresponds to the PCmover Client screen Preparing Your Computers for Migration. Connections Tab: PCmover allows multiple methods of connecting the source computer to the target computer. On this tab you can predefine which methods are presented to the user during the migration. Note: Selecting only one option will cause this screen to be bypassed entirely when PCmover Client is run. Corresponds to the PCmover Client screen Method of Migration. User map Tab: During a migration, PCmover Client matches login users on each computer, and it creates any users as necessary on the target computer to correspond to migrated users from the source computer. Through a screen in PCmover Client, the user can view and modify these mappings. Using the options on this tab, you have control over the mappings and over a user s ability to change them. Options for Mapping Users: Map a particular user from the source computer to a particular user on the target computer.

13 11 Prevent a particular user from being migrated at all. Prevent the PCmover Client user from modifying the pre-configured mappings. Prevent PCmover Client from creating any new users on the target computer. Set PCmover Client to transfer only the current user. Note: Corresponds to the PCmover Client screen Select User Accounts to Migrate. Directory Filter Tab: PCmover Client will normally transfer all files from all directories (other than temporary directories) to the corresponding location on the target computer (Of course, PCmover never overwrites files that already exist on the new computer). Through a screen in PCmover Client, the user is allowed to choose directories to exclude from migration. On this tab, you can specify the full absolute directory path of each directory that you don t want to migrate, eliminating the need for the user to make this choice. Directories that you may not want to migrate could include: Backup storage locations Data directories for applications you are not migrating Drive Map Tab: During a migration, PCmover Client matches hard drives on the source and target computers. If a source drive letter does not exist on the target computer, it creates a sub-directory off of drive C for the migrated data. Through a screen in PCmover Client, the user can view and modify these mappings. Using the options on this tab, you have control over the mappings and over a user s ability to change them. Options for Mapping Drives: Map a particular drive from the source computer to a particular drive or sub-directory on the target computer. Prevent a particular drive from being migrated at all. Prevent the PCmover Client user from modifying the pre-configured mappings. Note: Corresponds to the PCmover Client screen Select the Drives to Migrate. Note: Corresponds to the PCmover Client screen Deselect any folders that you do not want to migrate. File Filter Tab: PCmover Client will normally transfer all files that do not already exist on the target computer. In PCmover Client, the user is allowed to choose files, as specified by a wildcard pattern, which should not migrate. On this tab, you can pre-set which files should not migrate by specifying masks. Files that you may not want to migrate could include: Temporary files (e.g. *.tmp) Backup files (e.g. *.bak) Obsolete data files (e.g. OldProg.mdb) Note: Corresponds to the PCmover Client screen Exclude Specific File Types.

14 12 Applications Tab: PCmover Client will normally migrate all applications that are not already installed on the target computer. Through a screen in PCmover Client, the user can choose applications to migrate. Using the options on this tab, you can restrict the user s choices, presetting specific applications to migrate or to not migrate. You can also specify that no applications should migrate other than specified ones. Applications that you may not want to migrate could include: Forbidden applications, such as certain games. Old versions of applications that have a newer version already installed on the target computer. Obsolete applications that are no longer being used. Note: Corresponds to the PCmover Client screen Application List. Prompt: Give a name to the interactive text field to help the user understand what information to enter (Ex: If you want the user to enter their name, put Name here). Default Text: Initial text that will display in the text field until the user enters their own text. Report Header: If you want the user-obtained information recorded in the migration report, enter an identifying title for this information. You may also enter information here that you want directly written to the migration report, but never displayed on a screen to the user. Make sure to choose No from the Interactive drop-down menu for information to be written to the report without being displayed. Note: If you are not obtaining information from the user and only want to communicate information to the user about the migration, be sure to leave this blank. Custom Information Tab: PCmover Client can display a screen with your own information as entered on this tab. The screen will appear after the Introduction screen in PCmover Client. Using this customizable screen, you can communicate information about the migration to the user and obtain information interactively from the user for the report. After clicking Add, you can specify this information: Title: Appears on the screen displayed to the user. Interactive (drop-down menu): Choose Yes if you want the customizable screen to be displayed to the user. Registration Tab: If you enter the name, address, and serial number information on this page, PCmover will automatically activate itself without prompting the user for information. Be aware that anyone using this policy file will then be able to migrate using your multiple license serial number, and so be careful about the distribution of this file. Pre-Registration: If the source computer will not have Internet access, you can pre-register the migration here. Policy Manager will then validate the serial number and use one of the licenses on it, storing a Validation Code in the policy file. Note: Pre-registration will use up a license even if the user doesn t perform the migration, so be cautious when using this feature. Explanation: Communicate information about the migration to the user or explain what information that you need the user to enter into the interactive text field.

15 13 Reports Tab: PCmover can generate several types of reports at the end of a migration. These reports are saved in a Comma-Separated-Values (CSV) format that can easily be imported into a spreadsheet or database. Report Options Length: Each report is available in a shorter, exceptions only, version. This would include, in some cases, only the errors that were encountered by PCmover Client during the migration. A condensed report is less complete but will usually contain those specific items that are of the greatest interest for troubleshooting. Feedback & Assistance For PCmover or enquiries about our other products, please contact us by: Telephone: +44 (0) sales@pillar-solutions.com Append to Existing vs. Create New: Each report can be appended together in one file with other existing reports. You also have the option to save each report in a separate file. We recommend that you append single line summary reports together, but store each detail report separately. If you don t append summary reports, each time a new summary report is created from a migration, the new report will overwrite any older report existing in that directory location. File Name: If the text {Machine} appears in the file name, that is replaced with the network name of the computer that generated the report. This way, you can have multiple computers store reports in the same location and easily keep track of them. For example, if you enter the file name {Machine}Report and the report is generated by a computer with the network name Accounting1, the resulting file name is Accounting1Report.