pc transplant ref

Altiris PC Transplant™ 6.8 SP4 fromSymantecReference Guide

Administrator

Placed Image

Copyright © 2008 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Altiris and any Altiris or Symantec trademarks used in the product are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION, INCLUDING WITHOUT LIMITATION ITS AFFILIATES AND SUBSIDIARIES, SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation," as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display, or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation

20330 Stevens Creek Blvd.

Cupertino, CA 95014

http://www.symantec.com

Document Date: August 22, 2008

Altirs PC Transplant™ Reference Guide 2

Contents

Chapter 1: Introducing Altiris PC Transplant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Easy to Use PC Transplant Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Personality Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Real-time Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8PC Transplant Real-time Destination Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Application Install Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Application to Information (.A2i) Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8A2i Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Personality Template Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9PC Transplant Package Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Sending Events to Notification Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Settings You Can Transplant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Desktop Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

New Features in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13PC Transplant Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2: Transplanting Computer Settings and Data . . . . . . . . . . . . . . . . . . . . . . . . . 15Using and Editing a Personality Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Personality Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16User Account Settings and Files Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Orphan Accounts and Disconnected Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18User Map File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Security Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Personality Build Template Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20PC Transplant Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Template Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Text Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

PC Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Application Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Files, Folders, and File Types Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Password Encryption Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Using the PC Transplant Wizard with Command-line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

user: Command-line Option Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Groups and Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Include/Exclude Users Using Wildcard Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Orphan User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Real-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Viewing, Printing, or Changing Personality Package Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Viewing and Printing a Package’s Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Changing a Personality Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

PC Transplant Exit Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


Chapter 3: Personality Package Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Installing Personality Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Personality Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

User Accounts Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Orphan Accounts and Disconnected users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47User Map File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Migrating the Computer Name and Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48PC Settings and Data Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Migration Support for Non-standard Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Complete Installation Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Installing Personality Packages Using Command-line Options. . . . . . . . . . . . . . . . . . . . . . . . . 49Personality Package -user Command-line Option Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Windows NTx to Windows NTx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Orphan User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

PC Transplant Package Exit Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 4: Using the Application Install Administrator . . . . . . . . . . . . . . . . . . . . . . . . . 63Defining the Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Authenticating Installation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Providing a Path for the Install File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Command-line Options in the Definition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 5: Using the Template Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Template Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

PC Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Desktop Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 6: Using the PC Transplant Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70PC Transplant Package Editor Menu Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 7: Using the A2i Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72A2i Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Submit A2i Files to Altiris Test Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 8: Using the A2i Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75A2i Editor Menu Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 9: Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77PC Transplant File Types and Executables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Desktop and Network Settings File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Desktop Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Setting Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Basic Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Advanced Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90<%REG:%> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90


<%REG:%> Nesting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91<%MULTIREG:%> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91<%STRIPTAILSLASHESn:path%> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92<%STRIPHEADSLASHESn:path%>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93<%all%> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93<%allvalues%> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95<%INI:%> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Comma “ , ”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Wildcards “ ? ” and “ * ” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Pipe “ | ” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Question Mark “?”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Settings and Item Setting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101LogError . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Exclude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102DestOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103DestVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107DeleteKeyBeforeMigrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

DeleteKeyBeforeMigrating=Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108DeleteKeyBeforeMigrating=RetainSpecified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

ExcludeFilePaths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Retain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109NewDestination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Application to Information (.A2i) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Application Executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Application Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

INI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Variable Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Template File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123General File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Personality Build Template Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Desktop, Network, and Applications Settings Sections. . . . . . . . . . . . . . . . . . . . . . . . . . 124Files Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132


Chapter 1Introducing Altiris PC Transplant

Altiris PC Transplant has a wizard-driven interface that captures a computer’s personality—user accounts; desktop, network, and application settings; files; folders; and personal data—and transplants that personality to another computer. You can transplant a personality through a self-extracting executable file called a Personality Package or you can perform a real-time migration from one computer to another.

PC Transplant can evaluate what application versions were installed on the source computer. The application can be installed for the same or higher version on the destination computer.

PC Transplant simplifies the deployment and migration of new computers or Windows operating systems by facilitating the migration of data and settings. It supports existing desktop management tools, meeting an easily identified need that none of these tools currently addresses. With PC Transplant, you can not only migrate to a new computer quickly and efficiently, but also transfer key aspects of a computer’s personality between multiple computers on an on-going basis. PC Transplant is an ideal solution for IT administrators, consultants, VARs, resellers, computer vendors, and configuration centers.

PC Transplant offers the following primary functions:

Upgrade to a new computer Run the PC Transplant Wizard on the old computer to capture the user profiles and the required settings and data. You can perform a real-time migration or save the Personality Package, copy that file onto the new computer, double-click and the upgrade process is complete.

Upgrade to a new OS PC Transplant includes a Migration Wizard that captures the existing personality, deploys, and restores the personality. PC Transplant even creates the user accounts automatically.

Deploy a new OS organization-wide PC Transplant lets you create Personality Build Templates, ensuring that the settings and data you want to capture are included in the Personality Package. These templates can be run from the command-line to automate OS migrations organization-wide.

Manage the migration of applications PC Transplant lets you install applications prior to migration. You can install applications of the same or higher version with a new PC Transplant tool called Application Install Administrator.

Execute the departmental PC shuffle more easily Users have to run PC Transplant and back up their computer personalities to the network. To move all computers at once, have your users reapply their personalities and the process is complete.

Perform Remote Migration Use a remote management agent, such as Altiris® Deployment Server® software or


Microsoft SMS, to capture a computer’s personality and push it to the same upgraded computer or to a new computer.
Back up and restore computer personalities Most disaster recovery solutions restore data. PC Transplant also restores desktop, network, printer, application settings (such as templates, favorites, and contacts), and entire directory structures, so users can use their computers.

Share resources You can share computer resources (such as a departmental travel laptop or a teacher’s console in a multi-teacher computer training lab) by having each user create a Personality Package with the settings and data they need on the shared computer. Users can double-click on their Personality Package before their class or presentation and then double-click the undo icon to uninstall it after they have completed their session to return the computer to its original state.

Synchronize multiple computers Create a Personality Build Template including only the folders, documents, and settings you use most, then build a new Personality Package any time you need to move between computers to capture your most recent changes.

Share settings and establish department profiles Create a small Personality Package containing only the settings you want to share, or create a “marketing” or “accounting” personality with the templates, style sheets, forms, and contacts you want to share with all computers within the department.

Features and BenefitsPC Transplant provides many features. This section lists and describes these features. For a complete list of PC Transplant files and executables, see PC Transplant File Types and Executables (page 77).

Easy to Use PC Transplant WizardThe PC Transplant Wizard helps you easily identify and transplant users, files, folders, and desktop, network, and application settings. You can migrate the data over a network connection or build the data into a compressed, self-extracting Personality Package.

For a list of settings you can transplant, see Settings You Can Transplant (page 9).

The wizard lets you establish rules for including and excluding files and prioritizing those rules. The wizard also lets you define the behavior of a Personality Package when it runs on the target computer. Example: You can configure the Personality Package to restart after the migration is complete, set up passwords to prevent unauthorized editing or running of the Personality Package, define the process of handling file replacements, and create an Undo file which, when run, reverses the changes made by the Personality Package. You can create a Cleanup package which helps in removing any private or personal files in the source computer after creating the Personality Package. You can also create customized splash screens and descriptions to enhance the end user’s experience.


Personality Package
A Personality Package is a self-extracting executable file created by the PC Transplant Wizard. Because a Personality Package is a self-contained executable file, you can distribute it any way you want: floppy disk, e-mail, network share, CD, Web download,

or removable media such as Iomega JazTM, ZipTM, or PeerlessTM drives.

Personality Packages can also be deployed using services, such as Windows Task Manager, Microsoft SMS, and Altiris® Deployment Solution™ for servers, a total computer management and deployment solution. When the Personality Package runs on the target computer, the settings you captured are applied to the computer.

Real-time MigrationThrough a network connection, you can transplant a computer’s settings and files directly and in real time to another computer, eliminating the need for creating Personality Packages. Real-time migration includes the following features: user mapping, user properties, user account creation, application installation, and destination computer application information.

PC Transplant Real-time Destination AgentThe PC Transplant Real-Time Destination Agent lets you perform real-time migrations. This agent is run on the computer to which you want to transplant a personality. The PC Transplant Wizard is loaded on the source computer and can communicate with the agent on the destination computer through a network connection. Real-time migrations allow you to select and transfer the same elements of a Personality Package without the need of creating Personality Package files.

Application Install AdministratorPC Transplant can evaluate what application versions were installed on the source computer with the Application Install Administrator tool. You can install applications on the destination computer before migrating the settings. The tool reads all the .A2i files and finds the supported versions. The application can be installed for the same or higher version on the destination computer.

It helps you create an application installation file containing all information required for the installation. The installation file created using this tool can be used later during the migration process for providing the application installation information. You can thus manage the migration of applications. For more information, see Using the Application Install Administrator (page 63).

Application to Information (.A2i) FilesThe .A2i files are used to describe all the components that are needed to transfer an application’s settings and data files. Each .A2i file is specific to a certain application and is used by the PC Transplant Wizard to show the user which application settings can be migrated and how to collect this information. For more information, see Application Settings (page 11).


A2i Builder
The A2i Builder is included in PC Transplant and helps you create customized .A2i files for an application. For more information, see Using the A2i Builder (page 72).

Personality Template BuilderThe PC Transplant Wizard supports the use of templates to define specific settings, files, and options that are used to create a Personality Package. For more information, see Viewing, Printing, or Changing Personality Package Contents (page 42).

The Template Builder allows users to build and edit templates without being on the source computer. The tool has a similar interface as the PC Transplant Wizard.

For more information on using the Template Builder, see Using the Template Builder (page 66).

PC Transplant Package EditorAfter you have created a Personality Package, you can open the package in the PC Transplant Package Editor to view, add, edit, and delete individual files and registry values. For more information, see Using the PC Transplant Package Editor (page 70).

Sending Events to Notification ServerIf PC Transplant finds the Altiris client agent installed on a computer, PC Transplant components send event status information to the Notification Server.

Online HelpHelp is at your fingertips no matter where you are in the migration process. By clicking the question mark (?) in the upper right hand corner of any dialog, you can click any item displayed in PC Transplant to get additional information. PC Transplant also has updated and enhanced the online help to context-sensitive Microsoft HTML help. Click Help from any page in the wizard to view the HTML help.

Settings You Can TransplantYou can transplant the following three categories of settings:

Desktop Settings (page 9)

Network Settings (page 11)

Application Settings (page 11)

Desktop SettingsPC Transplant can migrate the following desktop settings:

Control Panel

Accessibility

Keyboard Settings

Mouse Settings


Power Settings
Printer Settings including TCP/IP printer ports

Regional Settings

Sound

Display Properties

Active Desktop

Appearance

Background

Display Settings

Effects (Plus! Settings)

Screen Saver

Windows Shell

Desktop Icons

Explorer Settings

TaskBar


Network Settings
PC Transplant can migrate the following network settings:

Computer Name

Domain Name

Dial-Up/RAS connections

Window drive Mappings

Folder/Drive share assignments

NetWare Windows Client (Client 32) settings

TCP/IP

Name Resolution Files (lmhosts, hosts)

Settings

Application SettingsPC Transplant migrates settings for more than 100 application versions of the most commonly used business applications. With a few exceptions, PC Transplant does not migrate complete applications but migrates application settings. To see the specific


application settings, open any .A2i file (contained in the PC Transplant installation folder) in a text editor.
Here are some of the applications that PC Transplant supports:

Company Application

Adobe Acrobat, PageMaker, Photoshop

Altiris Carbon Copy® Solution

AOL AOL Client, Instant Messenger

AT&T AT&T Global Network

Cisco Vpn Client

Corel WordPerfect, Quattro Pro, Presentation, Paradox

FileMaker, Inc. FileMaker Pro

GlobalScape CuteFTP

ICQ, Inc. ICQ

Jasc Software Paint Shop Pro

Lotus Notes, Smart Center, WordPro, 1-2-3, Organizer, Approach, FastSite, Freelance, ScreenCam

Microsoft Microsoft Word, Excel, PowerPoint, Access, Outlook, Outlook Express, Exchange Client, Internet Explorer, NetMeeting, MSN Messenger, Publisher, FrontPage, Visual C++, Visual Basic, Visual InterDev, Visual FoxPro, Visual Source Safe, ActiveSync, Project, Visio

Netscape Navigator

Network Associates McAffee Virus Scan

Novell GroupWise

Nullsoft Winamp

Palm Computing Palm Desktop

Pumatech Intellisync for Palm Computing

Qualcomm Eudora Pro

RealAudio RealPlayer, RealJukebox

Symantec ACT!, Norton AntiVirus, PC Anywhere, WinFax Pro

WinZip WinZip

Yahoo Yahoo! Messenger


Altiris continues to add support for additional applications. The .A2i files, which support these applications, are available as a free download from Altiris’ Web site at ftp://support.altiris.com/pct/ver6.x/EN. You can also update your list of .A2i files from within the PC Transplant Package Editor by clicking Help > Application Updates.

Your computer connects to the Altiris Web site, searches for new or updated .A2i files, and presents them for automatic download. You can also update your setting files from within the PC Transplant Wizard and the Template Builder by running the application and clicking the system menu, then Update Application Support. The original files are placed in the Backup folder before updating the .A2i files.

If you are using applications for which no A2i files exists, PC Transplant ships a utility with the A2i Builder that lets you build your own customized .A2i files. For more information, see Using the A2i Builder (page 72).

New Features in this releaseFor a list of what is new, seethe PC Transplant Release Notes.


ftp://support.altiris.com/pct/ver6.x/EN

ftp://support.altiris.com/pct/ver6.x/EN

PC Transplant Documentation
The PC Transplant documentation is available in context-sensitive HTML help format and PC Transplant Reference Guide is available in .PDF format.

You can access the PC Transplant documentation in the following ways:

On a computer where PC Transplant is installed, click Start > Programs > Altiris > PC Transplant > Documentation.

By clicking Help when running PC Transplant programs, you can access the Online help.

From the PC Transplant program folder on a computer where PC Transplant is installed, open pctransplantref.pdf or pctransplant.chm.

From the Docs folder of the Altiris product CD, open pctransplantref.pdf or pctransplant.chm.

The most current versions of documentation are available from the Altiris documentation Web page at www.altiris.com/support/documentation.

To access the What’s This? Help, click ? in the top right corner of the PC Transplant program screen and then click the item you want to learn more about.


http://www.altiris.com/support/documentation

Chapter 2Transplanting Computer Settings and Data

There are two ways to transplant a computer’s personality (settings and data) to another computer:

Creation and installation of Personality Packages

Real-time Migrations

You can create a Personality Package or perform a real-time migration using PC Transplant’s easy-to-use wizard. The PC Transplant Wizard lets you pick and choose the settings you want to transplant to another computer.

You can also automate a personality transplant by running the PC Transplant Wizard with command-line options. This feature lets you initiate migrations through batch files, login scripts, and so on.

When you create a Personality Package, the computer’s settings and files are captured in a single self-extracting executable file. In addition, you can define options that affect the way the Personality Package behaves when it installs itself on the target computer.

When you perform a real-time migration, a source computer’s settings and files are migrated “real-time” through a network connection to a destination computer, eliminating the need of any stored files.

To run PC Transplant successfully on your source and destination computers, we recommend an account that has access to all users on the source computer and has the rights to create users on the destination computer. We recommend that you use a domain user account with local administrative rights as the minimum rights level. If the user account does not have administrative rights on a domain, then local administrative rights is sufficient. If you use an account that is not a local administrator or has lesser rights than a standard administrator account, you will not be able to create users and migrate certain settings. You will be forced into a limited migration. Example: if you are migrating a printer and the printer’s drivers need to be installed, a group policy that prevents users or power users from installing those drivers would prevent the migration of the printer.

We also recommend that you always preface your user account name with a domain name applicable to the migration.

When migrating domain user accounts on the same domain, you need different rights based on the situation

For migrating domain user accounts, you need a domain user with rights to the local computers that are being migrated. Local administrative rights are preferred because of possible limitations without them.

For computer and domain name migration, you need administrative rights on the local computers and rights on the domain to manage computer accounts.

For any multiple user migration you must be a local administrator on both machines.

When migrating domain user accounts from different domains (example: Domain A to Domain B), you need different account rights based on the situation.


For package migration, you need a Domain A account for the source package and a Domain B account for the destination. You can also use an account that traverses both domains using domain trusts.
For real time migration, you must have an account with rights to both domains and both local computers.

For any multiple user migration you must be a local administrator on both computers.

NoteWhen pushing from the Deployment Server, you can only use the Pre Windows 2000 User Name.

This chapter provides information on:

Viewing, Printing, or Changing Personality Package Contents (page 42)

Using and Editing a Personality Package (page 16)

Using the PC Transplant Wizard with Command-line Options (page 25)

PC Transplant Exit Values (page 42)

Using and Editing a Personality PackageWhen a Personality Package is created, you can run the package on another computer to install the personality.

You can view or edit the contents of a personality package. See Viewing, Printing, or Changing Personality Package Contents (page 42).

Personality Settings OptionsThis section discusses about the additional information on settings you can configure for transplanting personalities. These settings can be easily configured in the PC Transplant Wizard and Template Builder. For more information, refer to the online help.

User Account Settings and Files Options (page 16)

Personality Build Template Options (page 20)

PC Settings Options (page 21)

Application Install Options (page 24)

Files, Folders, and File Types Options (page 24)

User Account Settings and Files Options

PC Transplant supports the capturing and migrating of files and settings for a single user,

multiple users, or all users. For information on how file permissions are transplanted, see Security Options (page 19).

Real-time migration includes the following features:

Migration on Same Computer with Loop Back Functionality

Real-time migration lets you do migration on the same computer. The -multiple command line option can be used while performing real-time migration on the same


computer to allow the execution of PC Transplant Wizard and the PC Transplant real-time destination agent. For more information, see Using the PC Transplant Wizard with Command-line Options (page 25). With the loop back functionality, you can give the same computer name and the IP address for the target computer. You can also provide the loop back IP address, that is, 127.0.0.1 instead of the same IP address. The loop back functionality can be used for the following:
Migrate settings from one user to another user on the same computer

Import settings of an orphan account to some active user account on the same computer

Migrate data from one directory to another on the same computer

User Mapping

When selecting the user accounts to migrate, you are shown the user accounts that exist on both the source and destination computers. You can map the settings of one user account on the source computer to any account name on the destination computer.

User has administrative rights on both the source and destination computers

All the accounts on both the computers are listed. You can map any of the accounts on the source computer to any of the accounts on the destination computer.

User has administrative rights only on the source computer

All the accounts on the source computer and your account on the destination computer are listed. You can map any of the accounts on the source computer to your account on the destination computer.

User has administrative rights only on the destination computer

All the accounts on the destination computer and your account on the source computer are listed. You can map your account on the source computer to any of the accounts on the destination computer.

User does not have administrative rights on both the computers

Your account on both the computers is listed. You can only map your account on the source computer to your account with the same name on the destination computer.

User Properties

The User Properties feature displays the users that exist on both the source and destination computers, and the groups to which those users belong.

Only users with administrative rights have the ability to view and migrate multiple users. If the current user running the Wizard does not have administrative or system rights, only the current logged on user will be presented for migration.

User Creation

You can also create new accounts on the destination computer to match accounts on the source computer. Example: If an account named Bob exists on the source computer but not on the destination computer, and you want to migrate that account and maintain the name, you can create an account named Bob on the destination computer from the Wizard, and then select that account to be migrated.


PC Transplant attempts to set an empty password for the new account. If your computer is a member of a domain that restricts a password to a minimum length or complexity, PC Transplant creates the password using the following syntax:
PasswordMMYYYY

The syntax is case-sensitive, where MM represents the number of the month, and YYYY represents the year the account was created (that is, Password012002). The password is logged in the migrate.log file.

You can override the password defined by PC Transplant by using the New User Password option provided in the PC Transplant Wizard or through the -newuserpassword command-line option. The new password must satisfy the password policy on the local computer. Only one password can be set for all the local users, that is, you cannot change this password for the other new users you want to create. For more information, see Using the PC Transplant Wizard with Command-line Options (page 25).

When accounts have been validated, you are provided with a user map to link user accounts from the source computer with accounts on the destination computer. The user mapping can be done with the -user and -usermap command-line options also.

While creating new user accounts and adding them to a particular group on the destination computer, you need to check whether the user account is already a member of the group. If the user account is not an existing member of the group, then the user account is added to the group. Example: If a domain user, Altirs\Joe, exists on the source computer and is a member of the administrator group on the source computer, then Altirs\Joe should be made a member of the administrator group on the destination computer too.

Consider the scenario where Altirs\Joe is an administrator on the source computer and a member of Altiris\domain users group, and Altiris\domain users is a member of the administrator group on the destination computer. When Altiris\Joe is migrated to the destination computer, this user account becomes a member of the administrator group in two methods; one is through the Altiris\domain users group and the other is by being directly added to the administrator group. Additionally, if Altirs\Joe has been removed from the administrator group, this user account will still be a member because it is a member of the Altiris\domain users group. PC Transplant first checks if a user account is a member of a group before creating the user account and adding it to a particular group on the destination computer.

Orphan Accounts and Disconnected UsersOrphan accounts are accounts that cannot be resolved by the local computer or domains available under Windows NT\2000\XP. The accounts are considered lost and can only be identified from the original users Security ID (SID), and remaining profile folder. PC Transplant has the ability of migrating the settings and the files associated with these accounts. Additional functionality allows a user to transfer these settings to a new account, same account, or another existing account.

Disconnected users are user accounts that cannot be resolved due to the unavailability of their domain. Disconnected users can be easily identified because their icon is different from the icons used for other users. If the domain name of the disconnected user can be retrieved, then the user account is displayed with its domain name preceding it in this format - DomainName\UserName (example: TestDomain\Joe). If the domain name of the disconnected user cannot be retrieved, then the user account is displayed with a question mark preceding it. Example: ?\Joe.


By including this additional functionality for disconnected users, PC Transplant no longer requires a network connection to migrate domain user accounts. This opens up the added flexibility of using a network cross-over cable to migrate users from one computer to another.
While deploying this user, the user account is created as a network user if its domain is not available. The settings of the user account are migrated to the newly created disconnected user. While deploying the package, disconnected users can be mapped to a new account, same account, or another existing account.

User Map FileThe user map file is an initialization (.ini) file that has the list of the accounts that need to be captured and migrated. This can be passed from the command-line option -usermap. See Using the PC Transplant Wizard with Command-line Options (page 25).

Here is the sample usermap.ini file:

;Sample Usermap.ini file

[Users]

user1=

domain1\user2=

domain1\user3=domain2\user1


It is mandatory that the mapped user or unmapped user should have ‘=’

Example: for an unmapped user, it has to be as:

user1=

NoteFor an unmapped user, it has to be as: user1=

Security OptionsThis section describes how PC Transplant migrates file permissions. This feature is only available on Microsoft Windows using an NTFS file store.

Example Description

user1= Captures User1 in capture mode and maps User1 to User1 during real-time migration and deploying the package

User2=User2 Captures User2 in capture mode and maps User2 to User2 during real-time migration and deploying the package



Users and administrators of these systems can manage the access of their files and folders at a group or user level. PC Transplant can migrate these permissions, allowing you to keep your files and folders secure.
PermissionsWhen migrating the permissions of a file, all security elements assigned to the file will be transferred to the destination computer. A security element may be a user group or individual user account. If an element does not exist on the destination computer, it will be added and will remain unresolved. The security element must already exist on the destination computer for the transfer to be successful. If a user uses Explorer to view the security of a migrated file (Properties, Security), any user or group that does not exist on the destination computer will be shown as an unresolved SID (user security identifier). In some cases, a domain user’s FSID will migrate, but remains unresolved until that user accesses that account either locally or across the network on the respective computer.

There are potential problems with accessing files migrated along with their security permissions if the user accounts assigned to the file are local accounts or you are moving to a different domain. In these two cases, PC Transplant will turn off the migration of security permissions. You may choose to override the functionality when prompted during migration or if running in quiet mode using the -security option. If moving to a new domain, trust must be established between the old domain and the new one for the SID to be accepted or SID history must exist for the old SID.

Personality Build Template Options

PC Transplant’s Wizard uses template files (.PBT) to define the settings, files, and

options that are selected during run time. You can use predefined templates or a template that you create.

The following predefined templates are available:

Default – Comprises of Desktop settings and a few Network settings such as the Folder/Driver share assignments, Dial-Up/RAS, and Windows drive mapping. No application, file, or data settings are captured by the Default.pbt.

DNA - Comprises all Desktop, Network, and Application settings

DNMail - Comprises all Desktop, Network, Microsoft Outlook, and Microsoft Outlook Express mail settings

DNOffice - Comprises all Desktop and Network settings, and all Microsoft Office applications settings

DNMSApplication - Comprises all Desktop and Network settings, and all Microsoft applications settings

DNLotus – Comprises all Desktop, Network, and Lotus application settings

A template file can be selected from within the Wizard or can be passed as a command line switch to the program using the –p switch. The -at: <template name> command line option allows you to specify the admin template file name when building a Personality Package. For a complete listing of what command line options can be used to automate the creation of a Personality Package, see Using the PC Transplant Wizard with Command-line Options (page 25).


By creating build templates, you can reuse settings when transplanting other personalities. PC Transplant provides three ways to create a Personality Build Template:
PC Transplant Wizard

Template Builder

Manually through a text editor

PC Transplant Wizard A template created using the PC Transplant Wizard is system dependant. It requires that all desktop, network, and application settings, files, and folders be present on the executing computer to define the template. To create a system independent template, see Template Builder (page 21).

Template Builder The Template Builder allows users to build and edit templates outside the PC Transplant Wizard. This tool allows a user to define a template without being on the source computer. The tool has a similar interface as the PC Transplant Wizard.

Text EditorTemplate files can also be manually created using any text editor or program capable of creating text files. For more information, see Template File Format (page 123).

PC Settings Options

The settings listed in the Desktop and Network tabs come from the information in the

Dsktp*.ini and Ntwrk*.ini files. All these files can be edited using a text editor. See Desktop and Network Settings File Format (page 79).

The details and the warnings of the settings that you selected can be viewed.

If you select Create a new Package or Edit an existing package in the wizard, then the warnings for the application settings are displayed with respect to the source version to all the possible versions.

If you select Real Time Migration, then the warnings for the application settings are displayed with respect to the source version and the destination version.

For the Template Builder, the warnings for the application settings are displayed for all the supported versions to all the possible versions.

Desktop SettingsThe settings listed in the Desktop tab come from the information in the Dsktp*.ini file. This file can be edited using a text editor. See Desktop and Network Settings File Format (page 79).

Network SettingsThe settings listed in the Network tab come from the information in the Ntwrk*.ini file. This file can be edited using a text editor. See Desktop and Network Settings File Format (page 79).


Multiple NIC Support
When using multiple network cards in one computer, the user has the option of selecting the network card whose TCP/IP settings will be captured. This information is provided in the UI under TCP/IP for Network settings. On a destination computer, you also can remap one NIC to another.

NoteWith the Template Builder, you cannot select multiple NIC. If you select to migrate TCP/IP, then all the NICs are migrated.

Computer and Domain Names

You can migrate the computer and domain name through a Personality Package.

NoteTo avoid conflicts, this option is not enabled during a real-time migration.

Before installing a Personality Package with a computer name and/or domain name on a destination computer, it is important that the source computer be disconnected from the network. If the source computer is still connected to the domain, PC Transplant will not be able to establish a trust relationship with the domain for the destination computer. Two computers using the same computer and domain names are not allowed by Microsoft. If PC Transplant cannot establish this trust, the destination computer is added to the ‘tmpwork’ Workgroup. You are then forced to manually connect the destination computer to the domain to continue.

Computer Name. A computer name migration requires that you be an administrator on both the source and destination computers. In the event that you are migrating a computer that is already added to a domain, you must also provide the user name and password of an account that has rights to change and create a computer account in that domain. When a package with just the computer name is run on a destination computer, a dialog box asks you for this information. The dialog box appears only if the computer is currently a member of a domain. This is necessary because of the trust relationship that exists between the domain and that computer. PC Transplant associates the computer that is being migrated with the computer account on the domain. If the account is not correctly associated with the computer account on the domain, you cannot log on to any domain user accounts on that computer.

Domain Name. A domain name migration requires you to be an administrator on both the source and destination computers. Because of the nature of domain name migration, PC Transplant requires that you provide the user name and password of an account that has rights to change and create a computer account in that domain. You are prompted for this at the end of the PC Transplant Wizard when you click the OK button or the Schedule button.

You may also pass in a -dau and -dap switch to specify this from the command line. In quiet mode the -dau and -dap switches are required for a domain migration to take place. For more information, see Using the PC Transplant Wizard with Command-line Options (page 25). User authentication for a domain is not stored in the template. The user name provided may need to be preceded by the domain name depending on the authentication model of your domain server. You can also pass an encrypted password in the command line. See Using the PC Transplant Wizard with Command-line Options (page 25).


Application Settings
The settings listed in the Applications tab come from .A2i files you have and the applications that are registered in the Windows registry as installed applications.

Migration Support for Non-standard Applications

The list of applications in the Applications tab depends on what .A2i files you have and which applications are registered in the Windows registry as installed applications. If the application is not registered in the registry, the application is still displayed if you had specified the complete path of the .exe or complete or partial path with Type=Scan in the .A2i file.

The .A2i files are created for non-standard applications, that is, the applications that do not store their installation information with the registry. To see the specific application settings, open any .A2i file (contained in the PC Transplant installation folder) in a text editor or the A2i Builder. The applications section of these A2i files has a new attribute, Type=Scan. This attribute tells the PC Transplant Wizard that it has to scan the hard disk to locate this application. The search path is given in the A2i file using the ScanPath tag.

For the applications which do not contain information in the registry, Flag=Scan is provided in the Applications section of the .A2i files. See Application to Information (.A2i) Format (page 110).

For the PC Transplant Wizard, the applications that do not contain information in the registry are considered as if they are not installed. These applications are not selected in the list. A magnifying glass icon is displayed with such applications. You can select such an application and when you click Finish to create a personality package, the A2i files are scanned. The icon and the description are changed for the application. If there is no information found for the applications, then they are deleted during the scan.

During real-time migration, all the applications are selected. A warning message is displayed for the applications that might not be migrated to the destination computer. The actual scanning of the applications takes place when you click the Finish button to start the migration. If the application is found on both the source computer and the destination computer, then the application is migrated.

For the Template Builder, the applications are not searched.

A2i File Updates

Altiris continues to add support for additional applications. The Application to Information (.A2i) files which support these applications are available as a free download from Altiris’ Web site at ftp://ftp.altiris.com/pct/.

Select the folder for the version of PCT that you are using. For example, for version 6.8 use the ver6.8 folder. The ver6.x folder is for 6.x versions previous to 6.8.

A2i Builder

If you are using applications for which no A2i files exist, PC Transplant ships with A2i Builder, a utility that lets you build your own custom .A2i files.

Application Install Options

You can use the Transplant Install Application page to select the application to be installed

on the destination computer. You can select to install the same or higher version of the applications.


ftp://ftp.altiris.com/pct/

During real-time migration, some applications would require you to restart the computer after installation. In such cases, the Application Installer tool gets launched to install other applications that you selected from the list, if only you log on using the same user name.
When doing a real-time migration, you are shown information about the applications that are installed on both the source and destination computers. Applications that are installed on the source computer but not on the destination computer are designated so that you do not transplant settings for an application that does not exist on the destination computer. You are also shown information about the applications that are installed on each computer but are of different versions.

Example: If Microsoft ActiveSync is installed on the source computer, but not on the destination computer, ActiveSync will be displayed in the application list, but it will be denoted as not being installed, and you will not be able to select settings for that application.

Note:For a real-time migration on the same computer, this feature is not available.

For the Template Builder, this page is displayed if any applications are selected for migration. All the applications selected for migration are disabled initially. If the application installer definition file that you provided contains the install information and the install server information for the applications selected for migration, then the application list is enabled. The applications that are listed can be installed using the information defined in the Application Install Administrator.

Installing Applications prior to MigrationYou can select the application to be installed and specify an installation file for the information on the installation. You can also create or edit the installation file using the Application Install Administrator tool.

Files, Folders, and File Types OptionsYou can include or exclude files to be migrated. You can select to include or exclude files based on criteria such as file names, folders, file type extension, drives, file size, and file date.

Password Encryption UtilityYou can pass any string to the Password Encryption tool to get it converted to an encrypted string.

The encrypted string can be passed with the command-line options that accept passwords. A new switch -DecryptPwd is also included. -DecryptPwd must be passed when using encrypted passwords from the command line. This switch decrypts all the encrypted passwords provided from the command line. You cannot use encrypted and unencrypted passwords together with a command-line option. See also -DecryptPwd (page 27).


Using the PC Transplant Wizard with Command-line Options
The following command-line options can be added to PCTWiz.exe to automate the PC Transplant Wizard tasks when creating a Personality Package or performing a real-time migration.

NoteSome of these options are only used when performing a real-time migration.

CautionIf there is any path or password with spaces, then type the entire path or password within double quotes. Example: See -p:<template filename> (page 31) command-line option.

PC Transplant Wizard Command-line Options

Option [option] Details

-advcrossconfig:

<IPaddress>,<Subnet Mask>

Function. Provides a customized IP address and subnet mask to configure the source and destination computer for crossover migration.

This switch can be used in the PC Transplant Wizard and in the PCTCrossConfig utility. When you use this switch in the PC Transplant Wizard, you have to specify the IP address of the source computer. When you use this switch in the PCTCrossConfig utility, you have to specify the IP address of the destination computer.

-alp:<password> This option is applicable only for real-time migration.

Function. Specify the password required for auto-logon for application installation and CNDN migration. The password cannot be blank.

-alu:<Domain name\user name>

This option is applicable only for real-time migration.

Function. Specify the domain name and the user name required for auto-logon for application installation and CNDN migration. This command-line option helps in continuing migration after a reboot has occurred.


-at:<template name> Function. Use the -at: option to pass an admin template on the command line when building a Personality Package. This command can be used in conjunction with the -p:<template file name>. The -at: option lets an administrator define a template that works in conjunction with a user’s selection. This gives administrators the ability of defining default settings for each user, but the flexibility to allow users to add in additional settings, folders, and files they want migrated. This option also accepts environment variables.

Example

The administrator uses the wizard to create a template that will be used to migrate all users’ common settings, and saves the template to the network under the path - x:\pct\admin.pbt. The administrator also understands that some users have personal folders and files on their systems that the administrator is not aware of. The users will need to provide this information. So a link to TEMPLATE.EXE is sent to the users. The users are instructed to execute the shortcut, select any personal settings, files, and folders, and to save the template at the end to network as \\server\pct\templates\%username%.pbt. Now the administrator has two templates that will not only pick up their corporate settings, but the user’s personal settings, too. The administrator then launches the wizard on the user’s computer using the following command and creates a complete package:

PCTWIZ.EXE -at:\\<server>\pct\admin.pbt -p:\\<server>\pct\templates\%username%.pbt -f:\\<server>\pct\packages\%username%.exe -q

-bandwidth:<xx> or <xxKB>

Function. Allows static bandwidth handling during real-time migration across a network or through a crossover cable. You can set the bandwidth once (example: -bandwith:100KB) or based on the percentage of available bandwidth. Example: -bandwidth:10.

-clean:1 Function. After migrating a PC personality from a source computer to a target computer, you might want to remove any private or personal files on the source computer. Use this option on the source computer to create a cleanup package based on the Personality Package created. A cleanup package will remove files that were captured during the process of creating a Personality Package. You can create the Cleanup Package in two ways: By selecting the Cleanup option through the wizard or by using the command-line option -clean:1.

Example

PCTWIZ -clean:1

PC Transplant Wizard Command-line Options (Continued)



-cmdverify Function. Validates the command-line options passed to the application. Paths and file names are validated for the types of options and the syntax of the commands. A dialog is displayed for errors encountered for the non-quiet mode. The errors are logged for the quiet mode and the execution is aborted.

-dap:<password> Function. Password defines the password of the domain administrator and is used in conjunction with the -dau option to migrate computer and domain names in quiet mode.

NoteIf you use multiple passwords, all the passwords must be either plain-text or encrypted.

-dau:<username> Function. Username defines the name of the domain administrator. This option is required to migrate computer and domain names in quiet mode. You need to specify the credentials of a user who is an administrator on that domain.

Example

-dau:<domain\username> -dap: <password>

-DecryptPwd Function. Decrypts all the passwords provided from the command line. The passwords used with this switch must be encrypted using the Altiris Password Encryption tool.

You cannot include any unencrypted passwords on the command line if this command-line option is used.

-DriveMap: <SourceDrive>$<DestinationDrive>

Function. By default, a file or folder is migrated to the same drive on the destination computer. You can specify a new drive to migrate the files or folders by using the -DriveMap option.

-ep Function. Adds an edit password to the package. This is especially useful when used with -q.

Syntax

PCTWIZ -ep:password

Example

PCTWIZ -ep:editrip

-errorlevel:<level> Function. Provides more information about the errors that occur during capture. The information depends on the error level.

-errorlevel:1 logs generic information about the errors.

-errorlevel:2 logs errors and warnings.

-errorlevel:3 logs detailed information about the errors and warnings.

By default, the error level is 1.




-errorlog:<pathname> Function. Lets users define the path and file name to the error.log file, which is created if any errors or warning occur during the creation of a package. This option accepts environment variables.

Example

PCTWIZ -errorlog:p:\pct\blderrors\%username%.log

-f:<filename> Function. Sets the name of the Personality Package executable.

Example

If you want to use the PC Transplant Wizard (PCTWiz.EXE) from the command line and you want to save the Personality Package to a file called ‘mysettings.exe’, type:

PCTWIZ -f:mysettings.exe

This option also accepts environment variables.

Example

PCTWIZ -f:%username%.exe

If no default name is specified, the default package name will be the computer name.

You can also save Personality Packages to a Web server.

For Windows Vista, you can provide the option to create .EXE and .PKG files or only .EXE file. To create .EXE and .PKG files type:

-f:<filename>;1

To create a .EXE file, type:

-f:<filename>;0

See -pkg:<package name.pkg> (page 31) command-line option.




-keepprofilepaths Function. This option lets you set the profile path of the folders of the destination computer as the profile path of the source computer. You can specify this command line for a package.

Example

<filename>.exe -keepprofilepaths

Example

PCTWiz.exe -keepprofilepaths

You can also use this command line to copy the existing data-My Document, My Music, My Pictures, and My Video folders in the profile folder of the destination computer to the new location. You can use the following command-line option to copy the existing folders.

-keepprofilepaths:1

OR

-keepprofilepaths

You can use the following command-line if you do not want to copy the existing folders to the new location.

-keepprofilepaths:0

You can use this command line to set the profile path of the folders of the source computer as the profile path of the destination computer also during a real-time migration. During a real-time migration, you have to use this command-line option only with the -rt:network=<machinename> command-line option.

See -rt:network= (page 35) command-line option.

Example

-rt:network=<machinename> -keepprofilepaths

-migratelog: <pathname> This option is only applicable for real-time migration.

Function. Lets users define the path and file name for the migrate.log file, which is created when migrating the personality. It contains any errors or warnings that occurred. This option accepts environment variables.

Example

mypkge.exe -migratelog:p:\pct\runerrors\%username%.log




-multiple Function. Allows the execution of two or more instances of the PC Transplant Wizard, Personality Migration Wizard, and the PC Transplant real-time destination agent. If you do not use this command-line option, PC Transplant does not allow any two instances of the mentioned combined applications to run simultaneously on the same computer.

-netdrives This option is applicable only for real-time migration.

Function. Allows the migration of files to network drives.

-newuserpassword: <password>


Function. Use this command-line option to define a password for all new local user accounts created by PC Transplant. If this command is not used, PC Transplant will attempt to set an empty password for all new accounts. If your computer is a member of a domain that restricts a password to a minimum length or complexity, PC Transplant will create the password using the following syntax:

PasswordMMYYYY

The syntax is case-sensitive, where MM represents the number of the month, and YYYY represents the year the account was created (that is, Password012002).


-nonetworkfiles Function. Do not migrate any network files, even if explicitly defined as a file or folder or as part of a setting.

-noundoshortcut This option is applicable only for real-time migration.

Function. Do not create a shortcut link on the desktop for the undo file.




-p:<template filename> Function. The PC Transplant Wizard and the Template Builder support the creation of personality build template (.pbt) files. These files contain all settings, files, and options that can be used to create a Personality Package. This option allows you to specify the template file name on the command line that can be used to automate the collection process.

If there is any path with spaces, then type the entire path within double quotes.

Example

If the file name is mysettings.pbt and the path has spaces then type:

PCTWiz -p:”\\Mycomp\My Templates\mysettings.pbt”

Example

If the file name is mysettings.pbt then type:

PCTWIZ -p:mysettings.pbt

This option also accepts environment variables.

Example

PCTWIZ -p:%username%.pbt

For more information, see Environment Variables (page 97).

-password:<password> Function. The password specified will be used with the -usercontext option to connect to the destination computer to push and run the PC Transplant Destination agent, if not running.

When you store Personality Package on a Web server, the password specified is used to authenticate to a IIS Server.


-pkg:<package name.pkg> Function. Used to specify .PKG file that is run by a personality package. A .PKG file includes settings, files, folders, and registry information. The .PKG file is created in a Windows Vista computer when you specify the option to create a .PKG file in the -f command line. See -f:<filename> (page 28) command-line option.

-printer:<Name of Printer>$<Path of inf file>


Function. Specifies the path of .inf file for each printer in case of cross platform printer migration.

Syntax

PCTWIZ -printer:<Name of Printer>$<Path of inf file>




-printer:+printerserver= <Names of printers to be migrated>

This option is applicable only for real-time migration, and can be used with network printers only.

Function. Searches for the print server associated with the source computer and migrates all the specified printers.

Syntax

PCTWIZ -printer:+printerserver=<Names of printers to be migrated>

Example

-printer:+printerserver=wing??;hp*

This command migrates all printers whose names match with wild card wing?? and hp*, such as wing2a, wing2b, hp laser 2000, hp 2000 series, and so on to the destination computer.

Example

-printer:+printerserver!=wing??;hp*

This command does not migrate all printers whose names match with wild card wing?? and hp*, such as wing2a, wing2b, hp laser 2000, hp 2000 series, and so on to the destination computer.

-printer:<Names of printers to be migrated>+printerserver=<Names of printer server>

This option is applicable only for real-time migration, and can be used with network printers only.

Function. Migrates the specified printer only if it belongs to the specified print server.

Syntax

PCTWIZ -printer:-printer:<Names of printers to be migrated>+printerserver=<Names of printer server>

Example

-printer:Wing-2A$c:\drivers\print\hp.ini+printerserver=voy*;john;

This command migrates the printer Wing-2A only if it belongs to a print server whose name starts with voy or if the print server name is john.

Example

-printer:Wing-2A$c:\drivers\print\hp.ini+printerserver!=voy*;john;

This command does not migrate the printer Wing-2A if it belongs to a print server whose name starts with voy or if print server name is john.




-q Function. Builds a Personality Package that requires no user interaction (quiet mode). When the wizard is run in a quiet mode, the user will be provided with a progress dialog that can be used to monitor the overall progress of the migration. The user will not be able to stop the migration from this dialog.

Example

If you want to build a Personality Package without viewing the PC Transplant Wizard interface, and PCTWiz.exe is located on the drive G and in the ‘pct’ folder, and you want to save the Personality Package as ‘mysettings.exe’, type:

g:\pct\pctwiz.exe -q -f:u:\user\MySettings.exe

NoteThe -f option must accompany the -q option to store the package in specified path (see -f:<filename> on page 28). If -f is not specified, the package is stored in the default path where PCTWiz.exe is stored.

When you use this command-line option on a Microsoft Windows Vista computer, the User Account Control (UAC) dialog appears. The UAC dialog cannot be handled programmatically. Therefore, you have to disable the UAC dialog from the control panel. However, this option is not recommended. So, you can run the package in the quiet mode from the administrative command mode by running the command prompt as the administrator.

You can also add a -p: option to specify templates (see -p:<template filename> on page 31).




-qm Function. Allows a user to run the PC Transplant Wizard in a quiet minimized mode. The package is shown running in the system tray in minimized mode. When running in quiet mode, the user must also provide a file name for the package (see -f:<filename> on page 28).

To use the feature, run the wizard (PCTWiz.EXE) using the -qm option.

Note

When you use this command-line option on a Microsoft Windows Vista computer, the User Account Control (UAC) dialog is displayed. The UAC dialog cannot be handled programmatically. Therefore, you have to disable the UAC dialog from the control paned. However, this option is not recommended. So, you can run the Package in the quiet mode from the administrative command mode by running the command prompt as the administrator.

Example

PCTWIZ -qm -f:c:\user\package.exe

-r:<filename> This option is applicable only for real-time migration.

Function. Sets the file name given to an undo or rollback file.

-redirect:<pathname> This option is applicable only for real-time migration.

Function. Defines the path where the unmapped drives’ data or unavailable drives’ data is to be sent. By default, PC Transplant places unavailable drives under c:\migrate.

-RedirectPaths: <SourcePath>$<DestinationPath>;<SourcePath>$<DestinationPath>

Function. Redirects the location to which the specified files, folders, and drives will be migrated. You can specify multiple paths for redirection, seperated by semi-colons.

-reset Function. Lets you reset the status and settings of the source computer after the migration is complete or if the migration is interrupted before completion.

-rp Function. Adds a run password to the package. This is especially useful when used with -q.


Syntax

PCTWIZ -rp:password

Example

PCTWIZ -rp:runrip




-rt:network=

<machinename>

This option is only applicable for real-time migration.

Function. Specify the destination computer name in place of <machinename>. If administrative rights are needed to authenticate to the destination computer, use -usercontext and -password options.

This option can also be used to search the computers on which the Destination agent is running. The first computer that is found to run the Destination agent is selected in the non-quiet mode. The search continues in the quiet mode.

Syntax

PCTWIZ -rt:network=<machinename>

Example

PCTWIZ -rt:network=devlaptop

This example attempts to connect to the PC Transplant Destination Agent on devlaptop and start a real-time migration using the other command-line options provided. If the destination agent is not running, it will attempt to push the PC Transplant Destination Agent to the computer and launch it (only available when migrating from Windows NTx to NTx).

PCTWIZ -rt:network=*

This example searches across the network for the computers on which the Destination agent is running.

-Security:

<Security options: no, object, parent>

This option is only applicable for real-time migration.

Function. This defines the security permission migration option.

-security:no means security permission will not get migrated.

-security:object means security permission will be migrated for the file or folder only and will not propagate to its parent.

-security:parent means security permission will be migrated to the file and read-only permission will get propagated to its ancestors.

NoteThis command-line option can be used only if the Migrate Security Permissions in the Security area of Run tab on Options page was selected in the template that you use for migration.

Syntax PCTWIZ -Security: <Security options: no, object, parent>




-settingsfiles:<path> Function. Path defines the location of your desktop (dsktp*.ini), network (ntwrk*.ini), and application (*.a2I) setting files. The default location of these files is the program folder.

-splash:<value> Function. Defines if the splash screen should be displayed or not. The value can be 0 or 1. Use 0 to turn the splash screen off or 1 to turn it on. If you do not provide the option, the splash screen is displayed by default.

-summary:<pathname> Function. Lets the user define the path and filename of the summary.log file. This file is created during the creation of a Personality Package and includes information about the settings stored within the package.

Example

PCTWIZ -summary:p:\pct\summary.log

-user: Function Defines a list of users to migrate. For more information on how to use this option, see user: Command-line Option Usage (page 37).

-usercontext:

<username>

Function. The user name specified will be used to connect to the destination computer to push and run the PC Transplant Destination Agent, if not running.

When you store Personality Package on a Web server, the user name specified is used to authenticate to an IIS Server.

-usermap:<filename> Function. Provides a method to redirect users to different domains or different user account names from a single file. Replace <filename> with the usermap.ini file path. The ini file contains the Users section where you can give the user accounts mappings switch.

Example

[Users]

domain\user1$domain\*

domain\user1+Created=12days$domain\user2

When using the -usermap switch in the quiet mode, ensure that your usermap.ini file is in the correct format. A sample format of a usermap.ini file is given below:

[Users]

;This will capture user1 in capture mode, and migrate user1's settings to user2 when deploying the package on the destination computer. In the RTM mode, it maps user1 to user2.

domain\user1= domain\user2




user: Command-line Option UsageThe -user command-line option can be used to define specific users, domains, groups, and dates of any user accounts you want to migrate.

UsersTo specify multiple users, separate each name with a semicolon.

Example -user:mary;bob;greg

To distinguish between local domain or network domain accounts, add the domain name before the user account.

Syntax -user:domain\user

-uweb Function. Update setting files with the most recent definitions stored on the Altiris Web site (ftp://support.altiris.com/pct/ver6.x/EN). Altiris is continually adding support for migrating settings and files for new application versions and adding functionality to existing ones. It is recommended that you update your settings files to ensure that you are using the latest files.

Syntax

PCTWIZ -uweb

You can specify whether you want to update from the Web, regardless of what mode you are running in and allow it to turn on or off. The switch can accept any one of the three parameters: 0, 1, or 2. Specify Zero to turn off updating from the Web, 1 to turn it on and display the dialog box, and 2 to update the files silently, whether in UI or quiet mode.

-Unresolved:<options> Function. Allows the unresolved shortcut links from the indicated area to remain visible even though the shortcut is not presently valid.

Path, such as c:\ has shortcuts located there.

Start Menu option refers to the start menu items selected within the package.

Desktop option refers to the Desktop items selected within the packages.

Example

-unresolved:c:\temp;Start Menu;Desktop

Retrieves the shortcut from C:\temp, the Start Menu, and from the Desktop folder and migrates them to the destination computer irrespective of whether the links are pointing to the referenced programs.




Example -user:jimspc\jim;altiris\joe

To captures settings for all the accounts present on the computer, wildcard characters, such as * and ? can be used. * is used to represent any number of characters, whereas ? is used to represent a single character. Additionally, you can exclude certain accounts using !=.

NoteThis is the default behavior in quiet mode. Syntax -user:*

The following table provides some examples of the usage of wildcard characters and

excluding accounts.

To capture settings for all accounts on a specific domain, include the domain name followed by an asterisk.

Syntax -user:domain\*

To capture setting for all domain accounts for a given user, include an asterisk followed by the user name.

Syntax -user:*\usernameOn Windows 2000, and XP computers, the domain is only required if you want specific domain accounts.

Groups and DatesUser accounts can also be dynamically defined using groups and dates. Examples of different group types include Administrator, Power User, User, and so on. By using dates,

Example Function

-user:*\*+users=a* Includes all user names starting with “a”.

-user:*\*+users=???? Includes all user names that contain 4 characters.

-user:*\*+users!=a* Excludes all user names starting with “a”.

-user:*\*+users!=???? Excludes all user names that contain 4 characters.

-user:*\*+users=??ge* Includes all user names that contain two characters before “ge” and any number of characters after “ge”, as in Tiger.

-user:*\*+users!=??ge* Excludes all user names that contain two characters before “ge” and any number of characters after “ge”, as in Tiger.


you can distinguish between accounts that were created or last accessed based on a specific date or within a specific date range.
Syntax

-user:domain\username+Groups=Group Type,Group Type,…+Date Type=date range or date;domain\username+Groups=Group Type,Group Type,…+Date Type=date range or date;…

Examples:

Example Function

-user:altiris\*+Groups=Users+Created=6Days Captures all Altiris domain user accounts that were created in the last 6 days.

-user:”%MI_COMPUTERNAME%\*+Groups=Power Users,Users+Accessed=6Monts;Altiris\*+Groups=Users+Accessed=6Months”

Captures all local domain accounts that are power users or user accounts that have been accessed over the last 6 months. It will also grab all domain user accounts that have also been accessed over the last 6 months.

-user:*+Groups=Administrators+Created=01-01-2001

Captures all users that are part of the administrator group that have been created since January 1, 2001.

NoteThe asterisk was included to indicate all accounts but is not required.

-user:work\*+Created!=6months Captures all the accounts that belong to work domain and those that were not created in the last six months.

-user:work\*+Accessed!=12-6-2002 Captures all the accounts that belong to work domain which were not accessed since 6 December 2002.

-user:*+domains=work+groups!=Administrators Captures all the users from work domain and excludes the users from the administrator group.

-user:*+domains!=work,work1+groups=Users, administrators

Includes all the users that are not a part of work and work1 domain during capture. It captures the users that are a part of either user group or admin group.

-user:*+Users=user1,user2+domains=work+ groups =Administrators

Captures the user1 and user2 users from the work domain and administrator group.


NoteYou can use the Groups and the Created or Accessed options alone and in combination with others types. The Created and Accessed options that are available are: accounts Created, accounts Not Created, accounts Last Accessed, and accounts Not Accessed. However, you cannot use both the Created and Accessed types together.
Include/Exclude Users Using Wildcard CharactersWildcard characters such as * and ? can be used with the -user switch to include and exclude user names that follow a particular name pattern. Some examples are given below:

Orphan User AccountsDuring the life cycle of a computer, there may exist old accounts that are no longer valid. The accounts may have been members of an old domain, or deleted from the operating system’s user list. These types of accounts cannot be resolved by PC Transplant, and are labeled orphan accounts. You can use a special user tag called “orphanusers” to support the migration of these accounts. To make use of the option use the following syntax:

Syntax -user:user definition;+orphanusers

Example -user:*\*+Groups=administrators;+orphanusers;

The example captures all users belonging to the administrators group and includes all orphan user accounts.

Real-timeWhen migrating users during a real-time migration, support for mapping user accounts settings to a different user is needed. The -user switch that controls the mapping of user accounts is similar to the syntax provided for personality packages.

Note

For domain users, if your mapping is -user:domain1\user1, then it is mapped as -user:domain1\user1$domain1\user1. The migration is successful as the domain and user names on both the source and destination computers match.

For local users, if you choose to migrate -user:computer1\user1 without providing any mapping, then the migration does not take place. PC Transplant does not convert it to -user:computer1\user1$computer2\user1 automatically.

Example Description

-user:*\*+users=a* Includes all user names starting with “a”.

-user:*\*+users=???? Includes all user names that contain 4 characters.

-user:*\*+users!=a* Excludes all user names starting with “a”.

-user:*\*+users!=???? Excludes all user names that contain 4 characters.

-user:*\*+users=??ge* Includes all user names that contain two characters before “ge” and any number of characters after “ge” as in Tiger.

-user:*\*+users!=??ge* Excludes all user names that contain two characters before “ge” and any number of characters after “ge” as in Tiger.


nt in same

in same

nt of

tination

tination

But if you explicitly give -user:computer1\user1$computer2\user1, then the mapping is done.

User Priority

Install first looks for the account in the domain to which the source computer’s current or last logged on user belongs.

If failed, it goes for the account in the same domain to which the destination computer’s current or last logged on user belongs.

After this, it looks for the account in the destination computer’s local domain.

NoteThe -user option is not available for a rollback file.

Windows NTx to Windows NTx

User to User. To migrate settings from one user to another (such as from account Domain1\user1 to account Domain2\user2):

Syntax

-user:SourceUser$DestinationUser

-user:Domain1\user1$Domain2\user2

Example -user:Altiris\Mary$Test\Jack

NoteIf account Domain2\user2 is not present on the destination computer, the account will be created and the settings will be migrated to that account.

Wildcard Support. The -user option allows wildcard characters to be used for user names. This allows an administrator to migrate a specific set of users, including remapping users to new domains. The following table provides examples:

Orphan User Accounts. Orphan accounts during real-time migration are identified using a question mark (?). Since PC Transplant is unable to resolve the part of SID that defines its computer or domain origin, it temporarily replaces it with a question mark. The name of the user’s profile folder is used to help provide a user name (example: an

Example Function

-user:domain1\*$domain2\* Maps all users’ settings in domain1 to domain2

-user:*\user1$*\* Maps user1 account in all domains to the user1 accoudomain

-user:*\user1$*\user2 Maps user1 account in any domain to user2 account domain

-user:domain1\*$*\* Maps all users of domain1 to same account

-user:*\*$domain2\* Maps all the source accounts to the same user accoudomain2

-user:*\*$*\* Maps all the source accounts to same account on des

-user:* Maps all the source accounts to same account on des


unresolved profile folder named jimb would be identified as ?\jimb). To manage the migration of orphan accounts, PC Transplant adds the question mark to the list of available source tags.
The following syntax shows how to migrate settings from all orphan user accounts to local computer accounts.

Syntax -user:?\*$Computer\*

Example -user:?\*$Computer2\*

This example captures all orphan accounts and migrates their settings to their new Computer2 accounts

Viewing, Printing, or Changing Personality Package Contents

PC Transplant includes tools that let you view, print, or change the contents of a Personality Package.

Viewing and Printing a Package’s ContentsThe Package Contents tool outputs the contents of a Personality Package to a file that can be viewed and printed. The file includes information such as the package version, title, description, computer it was built on and it’s domain, who built the package, a summary of it’s contents, and detailed information regarding files and registry values.

You can start the Package Contents tool (Pkgcntnt.exe) on a shared network device.

Changing a Personality PackageYou can change a Personality Package by using the PC Transplant Package Editor to delete, add, and edit individual files or registry values.

You can also use the PC Transplant Wizard to add, delete, or modify package settings. Simply start the PC Transplant Wizard, select Edit an existing package, and make your changes in the wizard as if you were creating a new package.

PC Transplant Exit ValuesIf you are using a batch file or a third party application to execute the PC Transplant Wizard, you can use the value returned by the application to determine the script’s flow. The exit codes defined in the following table provide details regarding the success of the running application.

-1 Application cancelled by user

0 Success

1 Undefined error

2 Restart needed to complete the migration

3 Administrative rights required

4 Unable to obtain the rights needed

5 Not enough disk space


6 Evaluation time for using the product has expired
7 Invalid run password provided

8 Run password prompt cancelled by user

9 Run password required

10 The target operating system is not supported by PC Transplant

16 The specified users cannot be found

17 Errors logged. Please refer to the error log file for more information.

18 Waiting for user to log on to complete the migration

19 Unable to create user account

21 Missing settings files (dsktp*.ini and ntwrk*.ini)

22 There appears to be problems with this package. Please rebuild.

23 Unable to obtain a connection

24 Could not write the package to the specified path

25 Required file InstPCT.bin missing

26 The specified template file does not exist

27 Connection speed does not meet minimum requirements

28 Unable to locate the PCT Web service

29 Package expired on PCTWeb server

30 Attempting to resume the migration.

31 Cannot execute while an instance of PCTPackage or PCTRTDestAgent is running

32 The request from client contains bad syntax or cannot be fulfilled

33 PCT Real-time destination agent could not be found

34 Failed to authenticate to Web server. User name or password typed is wrong

35 PCTWeb server may not be installed properly

36 User would not have sufficient rights on destination machine

37 Username and/or password provided for destination machine was wrong

38 Destination machine does not have sufficient disk space

39 Error occurred while transferring PCTRTDestAgent to destination machine

40 Failed to open file PCTResource.dll at Web server

41 Language of personality build template did not match with language of current locale


42 Tried to Migrate to different locale destination machine
that is not allowed

43 Failed to connect to the destination machine

44 Invalid computer name was provided for destination machine

45 Invalid IP address was provided for destination machine

46 Error occurred while loading user hive

9000 Expired or Invalid License

9001 Operating System not supported

9002 Setting files (dsktp*.ini and ntwrk*.ini) could not be found

10022

Package built appears to be corrupt or invalid


Chapter 3Personality Package Installation

The Personality Package is a wizard-based self-extracting executable file. You can distribute a Personality Package by floppy disk, e-mail, network share, CD, Web

download, or Iomega JazTM, ZipTM, or PeerlessTM drives. Personality Packages can also be deployed using Altiris® Deployment Solution™ software, a total PC management and deployment solution.

NoteFor Windows Vista, the executable file is not self-extracting.

A personality package is created by selecting the option to create a self-extracting package in PCTWiz. By default, on the Capture Options page in the PC Transplant Wizard, the Create a self-extracting package (not recommended for Windows Vista) check box is selected for non-Vista computers. If you select this check box for a Windows Vista computer, a .EXE file is created as the self-extracting package. If you do not select this check box for a Windows Vista computer, .EXE and .PKG files are created as the self-extracting package. A .PKG file includes settings, files, folders, and registry information. A .EXE file is the capture logic that is copied to the path specified by the user and is renamed to the name provided by the user. The .PKG file is not associated with PC Transplant. You have to use the .EXE file to run the .PKG file.

You can save the personality package online and run it. If you save the personality package on Webstore, you can run the .EXE file from Webstore on the destination computer. But you need to download the .PKG file and then run it on the destination computer.

This chapter provides information on:

Installing Personality Packages (page 45)

Personality Settings Options (page 46)

PC Transplant Package Exit Values (page 61)

Installing Personality Packages Using Command-line Options (page 49)

Installing Personality PackagesPersonality Package is a self-contained executable file. So you do not need any special client application to extract its contents. All you need to do is run it on the target computer and it takes care of everything else. When the Personality Package runs on the target computer, the settings and files you captured are migrated to fit the new Windows operating system and its applications. See Installing Personality Packages Using Command-line Options (page 49).

During a package installation, the user is provided with information about the contents of the package and how it affects the destination. Example: Values are given for the space required for the currently selected settings to install to a drive and the amount of free disk space available on the drive. You need to free up additional space on an existing drive to make room for the migration. When the files have been removed, click


the ‘Free Space’ column to recalculate the amount of free space available. The user also has the opportunity to redirect drives and folders.
Personality Settings OptionsYou can modify the settings that were captured while creating the personality package. These settings can be easily configured in the Personality Migration Wizard. For more information on how to configure the settings, refer to the online help.

User Accounts Settings Options (page 46)

PC Settings and Data Options (page 49)

User Accounts Settings OptionsThe Personality Package can transplant files and settings for a single user, multiple users, or all users. For information on how file permissions are transplanted, see Security Options (page 19).

The wizard displays all user accounts available on the destination computer. From this page, select the destination user.

User Mapping

When selecting the user accounts to migrate, you are shown the user accounts that exist on both the source and destination computers. You can map the settings of one user account on the source computer to any account name on the destination computer. You can use the -usermap command-line option to perform the same action. For more information, see User Map File (page 47) and Installing Personality Packages Using Command-line Options (page 49).

User Creation

You can also create new accounts on the destination computer to match accounts on the source computer. Example: if an account named Bob exists on the source computer but not on the destination computer, and you want to migrate that account and maintain the name, you can create an account named Bob on the destination computer from the wizard, and then select that account to be migrated.

Only users with administrative rights have the ability to view and migrate multiple users. If the current user running the wizard does not have administrative or system rights, then the user can migrate the settings to the current user’s computer if only the user is listed in the source user’s list.

The package determines if the user executing the package has administrative rights. If the user is not an administrator, then it checks if the user’s settings are included in the package. The user is not allowed to proceed unless the user’s settings are found and the user is only allowed to migrate the user’s settings.

If the user has administrative rights, the package checks the accounts in the package with the accounts on the destination computer. The user can create accounts in the package that do not exist on the local domain. The user is also given the option of creating any additional user accounts. The accounts can also be created if the user has mapped them through the command line or with the help of the user map file. The user mapping can be done with the -user and -usermap command-line options also. For more information, see Installing Personality Packages Using Command-line Options (page 49).


Orphan Accounts and Disconnected usersOrphan accounts are accounts that cannot be resolved by the local computer or domains available under Windows. The accounts are considered lost and can only be identified from the original users Security ID (SID), and remaining profile folder. PC Transplant has the ability of migrating the files associated with these accounts. Additional functionality allows users to transfer these settings to a new account, same account, or another existing account.
Disconnected users are user accounts that cannot be resolved due to the unavailability of their domain. Disconnected users can be easily identified because their icon is different from the icons used for other users. If the domain name of the disconnected user can be retrieved, then the user account is displayed with its domain name preceding it in this format - DomainName\UserName (example: TestDomain\Joe). If the domain name of the disconnected user cannot be retrieved, then the user account is displayed with a question mark preceding it. Example: ?\Joe.

By including this additional functionality for disconnected users, PC Transplant no longer requires a network connection to migrate domain user accounts. This opens up the added flexibility of using a network crossover cable to migrate users from one computer to another.

While deploying this user, the user account is created as a network user if its domain is not available. The settings of the user account are migrated to the newly created disconnected user. While deploying the package, disconnected users can be mapped to a new account, same account, or another existing account.

User Map FileThe user map file is an initialization (.INI) file that has the list of the accounts that need to be captured and migrated. This can be passed from the command-line option -usermap. For more information, see Using the PC Transplant Wizard with Command-line Options (page 25).

Here is the sample usermap.ini file:

;Sample Usermap.ini file

[Users]

user1=

domain1\user2=



It is mandatory that the mapped user or unmapped user should have ‘=’

Example: for an unmapped user, it has to be as:

user1=


NoteFor an unmapped user, it has to be as: user1=
Migrating the Computer Name and Domain NameYou can migrate the computer and domain name through a Personality Package.

Before installing a Personality Package with a computer name and domain name on a destination computer, it is important that the source computer be disconnected from the network. If the source computer is still connected to the domain, PC Transplant will not be able to establish a trust relationship with the domain for the destination computer. Two computers using the same computer and domain names are not allowed by Microsoft. If PC Transplant cannot establish this trust, the destination computer is added to the ‘tmpwork’ Workgroup. You will then be forced to manually connect the destination computer to the domain to continue.

The computer name and domain name migration requires you to restart the computer. The migration of the other settings take place after the computer is restarted. Windows NTx computers have auto-logon support.

Computer Name. A computer name migration requires that you be an administrator on both the source and destination computers. In the event that you are migrating a computer that is already added to a domain, you must also provide the user name and password of an account that has rights to change and create a computer account in that domain. When a package with just the computer name is run on a destination computer, a dialog box asks you for this information. The dialog box appears only if the computer is currently a member of a domain. This is necessary because of the trust relationship that exists between the domain and that computer. PC Transplant associates the computer that is being migrated with the computer account on the domain. If the account is not correctly associated with the computer account on the domain, you cannot log on to any domain user accounts on that computer.

Domain Name. A domain name migration requires you to be an administrator on both the source and destination computers. Because of the nature of domain name migration, PC Transplant requires that you provide the user name and password of an account that has rights to change and create a computer account in that domain.

You may also pass in a -dau and -dap switch to specify this from the command line. In quiet mode the -dau and -dap switches are required for a domain migration to take place. See Installing Personality Packages Using Command-line Options (page 49). User

Example Description

user1= Captures User1 in capture mode and maps User1 to User1 during real-time migration and deploying the package




authentication for a domain is not stored in the template. The user name and password provided may need to be preceded by the domain name depending on the authentication model of your domain server.
PC Settings and Data OptionsYou can transplant the desktop, network, and application settings. You can also transplant the files, folders, and file types that were captured during the Personality Package creation. The values are given for the space required to install settings and data to a drive and the amount of free disk space available on the drive. You need to free up additional space on an existing drive to make room for the migration. When the files have been removed, click the Free Space column to recalculate the amount of free space available.

The details and the warnings of the settings that you selected can be viewed. The warnings for the application settings are displayed with respect to the source version and the destination version.

Migration Support for Non-standard ApplicationsThe applications that do not contain information in the registry are considered as if they are not installed. These applications are not selected in the list. A magnifying glass icon is displayed with such applications. You can select such an application and when you click Begin to install a personality package, the A2i files are scanned. The icon and the description are changed for the application if information for the application is found. If no information is found for the applications, they are deleted during the scan.

Complete Installation SupportIf you capture certain applications that support complete installation, then even if the application is not installed on the destination computer, the settings are migrated with the application. The applications that support complete installation presently are:

AOL Instant Messenger

AT & T Global Network

Palm Desktop Application

WinZip

Installing Personality Packages Using Command-line OptionsThese options can be added to the Personality Package file name to automate tasks when installing (running) the self-extracting executable Personality Package files.

CautionIf there is any path or password with spaces, then type the entire path or password within double quotes.


Personality Package Installation Command-line Options


-alp:<password> Function. Specify the password required for auto-logon for application installation and CNDN migration. The password cannot be blank.

-alu:<Domain name\user name>

Function. Specify the domain name and the user name required for auto-logon for application installation and CNDN migration. This command-line option helps in continuing migration after a reboot has occurred.

-apps:<settings>

-desktop:<settings>

-network:<settings>

Function. These options let you define the application, desktop, and network settings are selected for migration. Using these options, you can override any default selections the Personality Package makes. This could be useful if you are running the package in quiet mode (see -q on page 56).

Settings

Each option must be followed by a colon and can contain one or more of the following definitions:

All=1 turns all settings on

All=0 turns all settings off

<setting name>=1 turns a general setting on

<setting name>=0 turns a general setting off

<setting path>=1 turns a specific setting on

<setting path>=0 turns a specific setting off

NoteMultiple setting definitions can be used with each startup option, but they must be separated by a semicolon. Setting names and paths are not case-sensitive. If a setting name or path includes a space, include it after the colon in quotes. Partial setting names and paths are supported.


Examples

1. Selects all desktop settings, but no applications settings:

install -desktop:All=1 -apps:All=0

2. Selects any desktop setting with a category name of “settings”; un-selects the custom dictionary setting of all the applications that have this setting captured.

install -desktop:settings=1 -apps:”custom dictionary=0”

3. Selects only Microsoft applications:

install -desktop:all=0 -network:all=0 -apps:all=0;ms=1

4. Selects only network printers and not the local printers:

-desktop:“Local Printers”=0;“Network Printers”=1

5. Selects only TCP/IP settings and Microsoft Word 2000’s Auto correct file:

install -network:all=0;tcp/ip\settings=1 -apps:”all=0;ms word 2000\auto correct file=1”

-cmdverify Function. Validates the command-line options passed to the application. Paths and file names are validated for the types of options and the syntax of the commands. A dialog is displayed for errors encountered for the non-quiet mode. The errors are logged for the quiet mode and the execution is aborted.

-ConnectAs: <DomainName>$<UserName>$<Password>

Function. Used to run the package with the specified user credentials. To run a package, the logged on user should possess administrator rights on the destination computer. If the logged on user does not possess administrator rights, then you can run the package by specifying a valid user with administrator rights using the -ConnectAs option. The user’s password is encrypted using the Password Encryption utility, and specified as a command-line argument.

Personality Package Installation Command-line Options (Continued)



-d Function. Logs detailed information to the migrate.log file. This file can be found in the temp folder or in the folder specified using the migratelog option. This file contains more information than the standard migrate log, such as name of source file in which error occurred, line number at which the error occurred, and a description of the error.

Example c:\user\MySettings -d

-dap:<password> Function. Password defines the password of the domain administrator, and is used in conjunction with the -dau option to migrate computer and domain names in quiet mode.

-dau:<username> Function. Domain administrator user name. Used to migrate computer and domain names.

When migrating a domain name, the PC Transplant Wizard requires that the domain administrator’s name and password be provided. You are prompted for these at the time you begin building a Personality Package. If you are running in quiet mode (-q on page 56 or -qm on page 57), you can pass this information into PCTWiz.exe using the -dau and -dap options. This information gets encrypted and stored in the package.

When the Personality Package is run on the destination computer, the administrative data will be used to connect the computer to the new domain.

If you are using the undo feature of PC Transplant to create a rollback file, you will be prompted for the administrator’s name and password for the old domain at the time you run the Personality Package.

If you are running in quiet mode, you must pass this information to the package using the -dau and -dap options. The information will be encrypted and stored in the undo package. This information is used by the undo package to set the destination computer back to its original domain.

When migrating only the computer name, the PC Transplant Wizard does not request the domain administrator’s name and password at the time a Personality Package is built. When the Personality Package is run on the destination computer. PC Transplant will determine if domain administrative rights are required to connect the new computer name to the domain. If it is needed, you are prompted for the required administrator information. If you are running in quiet mode, you must pass this information to the Personality Package using the -dau and -dap options.




-DecryptPwd Function. Decrypts all the passwords provided from the command line. The passwords used with this switch must be encrypted using the Altiris Password Encryption tool.

See also Using the PC Transplant Wizard with Command-line Options (page 25).

-DriveMap: <SourceDrive>$<DestinationDrive>

Function. By default, a file or folder is migrated to the same drive on the destination computer. You can specify a new drive to migrate the files or folders by using the -DriveMap option.

-errorlevel:<level> Function. Provides more information about the errors that occur during capture. The information depends on the error level.

-errorlevel:1 logs generic information about the errors.

-errorlevel:2 logs errors and warnings.

-errorlevel:3 logs detailed information about the errors and warnings.

By default, the error level is 1.

-GetNetworkData Function. Captures data from the My Documents folder that points to a UNC path or a mapped network drive.

-I: <File Path of Ini File> Function. Gets the .INI file path for application installation information.

-installapps Function. Provides the options to select the applications to be installed. It is similar to -apps switch.

Note-apps switch has a high priority over -installapps.

Example

1. Selects only Microsoft applications

-installapps:all=0;ms=1

2. Selects all except Adobe acrobat

-installapps:“all=1;Adobe Acrobat=0”

-migratelog: <pathname>

Function. Lets users define the path and file name for the migrate.log file, which is created when running a package. It contains any errors or warnings that occurred when the package was executed. This option accepts environment variables also.

Example

c:\user\mypkge.exe -migratelog:p:\pct\runerrors\%username%.log




-multiple Function. Allows the execution of two or more instances of the PC Transplant Wizard, Personality Migration Wizard, and the PC Transplant real-time destination agent. If you do not use this command-line option, PC Transplant does not allow any two instances of the mentioned combined applications to run simultaneously on the same computer.

-netdrives Function. This option allows you to redirect files, file types, and folders to a network drive while running a package.

Example w:\user\chngstuf.exe -netdrives

-newuserpassword: <password>

Function. Use this command to define a password for all new local user accounts created by PC Transplant. If this command is not used, PC Transplant attempts to set an empty password for all new accounts. If your computer is a member of a domain that restricts a password to a minimum length or complexity, PC Transplant will create the password using the following syntax:

PasswordMMYYYY

The syntax is case-sensitive, where MM represents the number of the month, and YYYY represents the year the account was created (Example: Password012002).

-nocn Function. Turns off the migration of the computer name.

-nodn Function. Turns off the migration of the domain name.

-notcpip Function. Turns off the migration of TCP/IP settings.

-noundoshortcut Function. Use this option if you do not want an undo shortcut to be placed on the user’s desktop after the package has completed.

-nr Function. Do not reboot when finished.

-nu Function. Use this option if you do not want an undo of the migration.

-p:<password> Function. Includes a password that may be required to run a Personality Package.

Example c:\user\MySettings -p:mypassword




-printer Function. PC Transplant has the ability of migrating printers across all operating systems. If you are migrating to the same Windows operating system version, PC Transplant uses the printer drivers from the source computer, to install the printer on the destination computer. If you are migrating the printer to a different operating system type, PC Transplant prompts you for the location of the printer’s .INF file.

The .INF file is used by PC Transplant to install the drivers needed for that printer. If you are running in quiet mode (see -q on page 56 or -qm on page 57), prompting for the printer’s .INF file is not possible. To work around this problem, PC Transplant has included a -printer command-line option that will allow the path to the .INF file to be passed through a command.

If either name of printer or path of .INF file contains spaces, the name or path must be enclosed in the double quotes (“ ”).

For more than one printer, separate each printer with a semicolon.

NoteThis command-line option will not install a printer unless the printer information was migrated from the source computer, the .INF file is found, and the .INF file descriptions match the printer description contained in the PC Transplant Package.

Syntax -printer:Name of Printer$path of inf file

Example

mypackage -printer:“BDC 1\HP Laser Jet PCL 6”$“H:\HP\ English\Drivers\PCL 6\HP2100.inf”;“HP Laser Jet PS”$“H:\HP\ English\Drivers\PCL 6\HPPS.inf”




-q Function. Runs the Personality Package with no user interaction (Quiet Mode). The user will be provided with a progress dialog that can be used to monitor the overall progress of the migration, but the user will not be able to stop the migration from this dialog.

Example

u:\user\MySettings.exe -q

NoteIf running in Quiet Mode, any folders and files that cannot be written to because of a non-existing or a non-writable drive are appended to the C:\Migrate folder on the target computer. If a package redirects files to a network drive and you want the network redirects to be observed, you must use the -netdrives option in conjunction with the -q or -qm option.

When you use this command-line option on a Windows Vista computer, the User Account Control (UAC) dialog is displayed. The UAC dialog cannot be handled programmatically. Therefore, you have to disable the UAC dialog from the control paned. However, this option is not recommended. So, you can run the package in the quiet mode from the administrative command mode by running the command prompt as the administrator.

Example If the Personality Package contains information about drives E and D, but the target computer does not have a drive E or a drive D, the files that would normally be copied to those drives are copied to new folders under C:\Migrate on the target computer.

CautionIf Quiet Mode is used, some settings transferred to the destination PC might not be completed successfully. Because PC Transplant is operating without user interaction, you will not know about the failures. Possible problems include mapped drives that may require user logon, file transfers that may require a new drive destination, and printer installations that require input regarding the location of the printer’s .INF file.




-qm Function. This option (Quiet Minimized Mode) allows the user to run a personality package without any user interaction. The package is shown running on the taskbar in a minimized mode.

Note

When you use this command-line option on a Windows Vista computer, the User Account Control (UAC) dialog is displayed. The UAC dialog cannot be handled programmatically. Therefore, you have to disable the UAC dialog from the control paned. However, this option is not recommended. So, you can run the package in the quiet mode from the administrative command mode by running the command prompt as the administrator.

Example

If you have a Personality Package called chngstuff.exe and you want to run it in “Quiet Minimized Mode”, type:

u:\user\chngstuff.exe -qm

-r:<filename> Function. Determines the file name given to an undo or rollback file.

Example

To save a rollback file to ‘mysettings-rb.exe’, type:

MySettings -r:MySettings-rb.exe

NoteThis option is only valid if the Personality Package was built with Enable Undo selected.

You can substitute the <filename> option with environment variables.

Example

MySettings -r:%username%-rb.exe

-redirect Function. Use this command to redirect a non-existent drive’s files to a different folder. If a drive captured in a package does not exist on the destination computer, the user is prompted for a folder in which to redirect these files. In quiet mode, they are placed in c:\migrate.

Syntax

-redirect:full path.

Example

mypackage -redirect:c:\




-RedirectPaths: <SourcePath>$<DestinationPath>;<SourcePath>$<DestinationPath>

Function. Redirects the location to which the specified files, folders, and drives will be migrated. You can specify multiple paths for redirection, seperated by semi-colons.

-security:<Security options: no, object, parent>-Security: <Security options:no, object, parent>

Function. This defines the security permission migration option.

-security:no means security permission does not get migrated.

-security:object means security permission is migrated for the file or folder only and does not propagate to its parent.

-security:parent means security permission is migrated to the file and read-only permission gets propagated to its ancestors.

NoteTo use this command-line option, the Migrate Security Permissions in the Security area of Run tab on Options page in the PC Transplant Wizard must be selected during capture.

-simulate Function. Simulates a package migration without making modifications to any user’s files or registry values. Potential problems found during simulation mode are logged to the simulate.log file. The location of this file can be found in the user’s temp folder or using the path specified by the -simulatelog (page 58) command-line option.

-simulatelog Function. Defines the location for the simulation log file. This option is only used in conjunction with the -simulate (page 58) option.

-successlog:<filename> Function. This option lets a user create a log file of all successful writes made to the registry and all files copied to a file store when a Personality Package runs. If you use -SuccessLog without the <filename> option, a file called success.log will be created and stored at <Install Directory>\Local Settings\Application Data\Altiris\PC Transplant\6.0. If you include the <filename> option, you must include a full path and file name.

Example

mypcpers.exe -SuccessLog:c:\install.log

You can also substitute the <filename> option with environment variables.

Example

mypcpers.exe -SuccessLog:w:\logfiles\%username%.log




Personality Package -user Command-line Option Usage

Windows NTx to Windows NTx

User to User

To migrate settings from one user to another (such as from account Domain1\user1 to account Domain2\user2):

Syntax

-user:SourceUser$DestinationUser

-user Function. Migrates a specific user in a package to the same or different user. You can specify multiple users by separating them with a semicolon.

Syntax

-user:SourceUser$DestinationUser;

SourceUser$DestinationUser;…

For more information on how to use this option, see Personality Package -user Command-line Option Usage (page 59).

-usermap:<filename> Function. Provides a method to redirect users to different domains or different user account names from a single file. Replace <filename> with the usermap.ini file path. The .INF file contains the Users section where you can give the user accounts mappings switch.

Example

[Users]

domain\user1$domain\*

domain\user1+Created=12days$domain\user2

When using the -usermap switch in the quiet mode, ensure that your usermap.ini file is in the correct format. A sample format of a usermap.ini file is given below:

[Users]

;This will capture user1 in capture mode, and migrate user1's settings to user2 when deploying the package on the destination computer. In the RTM mode, it maps user1 to user2.

domain\user1= domain\user2

-noundoprintershortcut Function. Removes printer shortcuts from user desktop of the printers that were not migrated successfully.




-user:Domain1\user1$Domain2\user2
Example

-user:Altiris\Mary$Test\Jack

NoteIf account Domain2\User2 is not present at the destination computer, the account is created and the settings are migrated to that account.

Wildcard Support

The -user option lets you use wildcard characters to be used for user names. This lets an administrator migrate a specific set of users, including remapping the users to new domains.

If profiles for destination users do not exist on the local computer, they are created. Also if due to use of wildcard, a situation arises where more than one source accounts get mapped to one account, the first available source account will be mapped and for the rest of the accounts an error is output to the migratelog file.

Orphan User Accounts Orphan accounts when transferred from a personality package are identified using a question mark (?). Because PC Transplant is unable to resolve the part of SID that defines its computer or domain origin, it temporarily replaces it with a question mark. The name of the user’s profile folder is used to help provide a user name. Example: an unresolved profile folder named jimb would be identified as ?\jimb. To manage the migration of orphan accounts, PC Transplant adds the question mark to the list of available source tags.

The following syntax shows how to migrate settings from all orphan user accounts to local computer accounts.

Example Function

-user:domain1\*$domain2\* Maps all users settings in domain1 to domain2

-user:*\user1$*\* Maps user1 account in all domains to the user1 account in same domain

-user:*\user1$*\user2 Maps user1 account in any domain to user2 account in same domain

-user:domain1\*$*\* Maps all users of domain1 to same account

-user:*\*$domain2\* Maps all the source accounts to the same user account of domain2

-user:*\*$*\* Maps all the source accounts to same account on destination computer

-user:* Maps all the source accounts to same account on destination computer


Syntax -user: ?\*$Computer\*
Example -user:?\*$Computer2\*

This example captures all orphan accounts and migrates their settings to their new Computer2 accounts.

Notes

For domain users, if your mapping is -user:domain1\user1, then it is mapped as -user:domain1\user1$domain1\user1. The migration is successful as the domain and user names on both the source and destination computers match.

For local users, if you choose to migrate -user:computer1\user1 without providing any mapping, then the migration does not take place. PC Transplant does not convert it to -user:computer1\user1$computer2\user1 automatically. But if you explicitly give -user:computer1\user1$computer2\user1, then the mapping is done.

PC Transplant Package Exit ValuesIf you are using a batch file or a third party application to execute the PC Transplant Package, you can use the value returned by the application to determine the script’s flow. The exit codes defined in the following table provide details regarding the success of the running application.

-1 Application cancelled by user

0 Success

1 Undefined Error

2 Restart required to complete migration

3 This package requires administrative rights to run

4 Cannot obtain rights needed to run this package

5 Not enough disk space to run this package

6 Evaluation period is over

7 Incorrect password supplied

8 Package cancelled at password dialog

9 Password required to run this package

10 The target operating system is not supported by PC Transplant

16 The specified user cannot be found in the package

17 Multiple errors encountered. Refer to the migrate.log file on the destination computer for more information.

18 Waiting for the user to log on to the computer

19 User account does not exist in the computer

20 Missing span file


22 There appears to be problems with this package. Please
rebuild.

31 Cannot execute a package while another instance is running

42 Migration to different local machine is not allowed

46 Error occurred while loading user hive

52 Failed to open resource file: PCTResource.dll


Chapter 4Using the Application Install Administrator

The Application Install Administrator is a new tool for creating application installation .INI file. This tool reads all the .A2i files and finds out all the versions of the applications. It reads the description for each version from .A2i files. The Application Install Administrator shows a list of applications for which there is an entry in the .INF file. The user can install only one version, either the same version or the upgraded version.

The information is stored in the .INF file in the following format:

[APP INI INFO]

Version=1.0

[EN > ACT! for Windows > 4.x]

InstallPath=d

InstallOptions=d

UnInstallOptions=d

Description=ACT! for Windows 4.0

InstallFiles=

WaitForChildProcess=0

[EN > ActiveSync Application > 3.x]

InstallPath=3

InstallOptions=3

UnInstallOptions=3

Description=ActiveSync Application 3

InstallFiles=


There are two tools supported by the Application Install Administrator: Installation Server and Install File Location. For more information on how to use Application Install Administrator, refer to the online help.

The following actions can be performed using the Application Install Administrator:

Defining the Application Installation (page 64)

Authenticating Installation Servers (page 64)

Providing a Path for the Install File Location (page 64)


Defining the Application Installation
You can define a list of properties required for the installation of the application that you have selected.

You can also set the values for InstallFiles= and WaitForChildProcess= keys in the .INF file. If the application’s installer launches any other executable files during the installation, you can specify if the utility must wait or continue with the installation of other applications. See also Command-line Options in the Definition File (page 64)

The installer’s path is validated for existence. If you did not provide a UNC path, then a warning message is displayed with the potential problems that might occur if you use drive mapped paths. If the path is valid, then the new version is added to the particular application node. See also Command-line Options in the Definition File (page 64).

Authenticating Installation ServersThe Installation Server helps in authenticating the servers that are used for installation purposes.

The Installation Server information is stored in the .INF file as:

[Installation Server]

ServerName1 > User Name1 > Encrypted Password1



Providing a Path for the Install File LocationIf the files mentioned in the command-line options refer to the standard files present with this installation, then you must copy these files to some other location.

In the Install File Path box, browse or enter the path to copy all the installation files.

See also Command-line Options in the Definition File (page 64).

Command-line Options in the Definition FileThe PctAppInstall.ini file is shipped with the product which has the command-line options and MST/ISS file names for all the applications supported by the PC Transplant. The format of this file is the same as that of the install.ini file.

Example:

[APP INI INFO]

Version=1.0

[EN > ACT! for Windows > 4.x]

InstallPath=<Optional>

InstallOptions= -S –F1ICQ.iss TRANSFORMS= “MyFile.mst”

UnInstallOptions=d


InstallFiles= -F1”<ICQ.iss>” | TRANSFORMS=”<MyFile.mst>”
//<FileName1>|<File Name 2> It will be “|” separated list of mst/iss files.


When you click Define from the Application Install Administrator page, the PctAppInstall.ini file is read if there is no information available on the application. This information is used in the Install Properties page.

There is another section called “Install File Location” in the install.ini file.

[INSTALL FILE LOCATION]

Path=<Path of location where user will store the MST / ISS files>

When you save the information, PC Transplant checks if any application “InstallFiles= ” value is set or not.

NoteThe InstallFiles value is set only if the command-line options contain any of the “ | ” separated values of InstallFiles read from the PCTAppInstall.ini file.

If “InstallFiles= ” value is set and the value of “Path” in “Install File Location” section is not set, then you are asked to provide a location where all the installation files referred to in the current install.ini must be saved to be used from target computer while installing the applications.

The installer’s path is validated for existence. If you did not provide a UNC path, then a warning message is displayed with the potential problems that occur if you use drive mapped paths. If the path is valid, PC Transplant sets the value of “Path” to that location.

Then PC Transplant checks “InstallFiles= ” for all the applications and copies the installation files to the path provided by you. If a file is already present in that location, you are given an option to replace the file.

If the copying of the files fails due to some reason, you are given another chance to copy the files to some other location. If you do not want to copy the files, PC Transplant checks the earlier “Install File Location” section and sees which files were already present at that location. Only those applications for which files are present at the destination computer are treated as valid applications. All the other applications (having entries in InstallFiles) are considered to be invalid and are removed from the Installs.ini.

You can change the location of the install files from Tools > Install File Location menu. If you use this option, PC Transplant modifies this value in install.ini file and copies all the referred installation file in install.ini to a new location. See Providing a Path for the Install File Location (page 64).


Chapter 5Using the Template Builder

The Template Builder lets users build and edit templates outside the PC Transplant Wizard. For information about what templates are and how to use them, see Personality Build Template Options (page 20).

The Template Builder lets a user define a template without being on the source computer. The tool has an interface similar to the PC Transplant Wizard. Because the tool is generic, a user cannot select a specific user’s settings to migrate.

The tool provides a list of all Desktop and Network settings. It does not include any system specific options like the listing of a specific printer.

The tool displays a list of all applications supported by PC Transplant. The list is built using the current applications defined in the A2i files. No application versions are presented to the user, keeping the template generic. It also includes all the applications for the .A2i files created by the user. The Template Builder displays a list of applications that it finds defined as the .A2i files in a particular language’s folder. Example: EN folder.

Files, folders, and file types are also flexible. A user can add a file or a folder that may or may not exist on the source computer. This same flexibility is included with Filters.

All templates built by the Template Builder are compatible with the PC Transplant Wizard and all the PC Transplant Wizard templates are compatible with the Template Builder. However it is important to note that templates created in the PC Transplant Wizard are not computer independent. Definitions defined in a template built by the PC Transplant Wizard may include items specific to a computer. Example: specific folders, printers, mapped drives, and so on.

Template Settings OptionsThis section provides details about the settings you can configure for a migration that are stored in the Personality Build Template. For information on how to configure the settings, refer to online help.

PC Settings OptionsThe settings listed in the Desktop and Network tabs come from the information in the Dsktp*.ini and Ntwrk*.ini files. All these files can be edited using a text editor. See Desktop and Network Settings File Format (page 79).

The details and the warnings of the settings that you selected can be viewed.

If you select Create a new Package or Edit an existing package in the wizard, then the warnings for the application settings are displayed with respect to the source version to all the possible versions.

If you select Real Time Migration, then the warnings for the application settings are displayed with respect to the source version and the destination version.

For the Template Builder, the warnings for the application settings are displayed for all the supported versions to all the possible versions.


Desktop SettingsThe settings listed in the Desktop tab come from the information in the Dsktp*.ini file. This file can be edited using a text editor. See Desktop and Network Settings File Format (page 79).
You can also use the command-line option -desktop with the Personality Package. See Installing Personality Packages Using Command-line Options (page 49).

Network SettingsThe settings listed in the Network tab come from the information in the Ntwrk*.ini file. This file can be edited using a text editor. See Desktop and Network Settings File Format (page 79).

Multiple NIC Support

When using multiple network cards in one computer, the user has the option of selecting the network card whose TCP/IP settings will be captured. This information is provided in the UI under TCP/IP for Network settings. On a destination computer, you also have the ability of remapping one NIC to another.

NoteWith the Template Builder, you cannot select multiple NICs. If you select to migrate TCP/IP, then all the NICs are migrated.

Computer and Domain Names

You can migrate the computer and domain name through a Personality Package.

NoteTo avoid conflicts, this option is disabled during a real-time migration.

Before installing a Personality Package with a computer name and/or domain name on a destination computer, it is important that the source computer be disconnected from the network. If the source computer is still connected to the domain, PC Transplant will not be able to establish a trust relationship with the domain for the destination computer. Two computers using the same computer and domain names are not allowed by Microsoft. If PC Transplant cannot establish this trust, the destination computer is added to the ‘tmpwork’ Workgroup. You are then forced to manually connect the destination computer to the domain to continue.

Computer Name. A computer name migration requires that you be an administrator on both the source and destination computers. In the event that you are migrating a computer that is already added to a domain, you must also provide the user name and password of an account that has the rights to change and create a computer account in that domain. When a package with just the computer name is run on a destination computer, a dialog box asks you for this information. The dialog box appears only if the computer is currently a member of a domain. This is necessary because of the trust relationship that exists between the domain and that computer. PC Transplant associates the computer that is being migrated with the computer account on the domain. If the account is not correctly associated with the computer account on the domain, you cannot log on to any domain user accounts on that computer.

Domain Name. A domain name migration requires you to be an administrator on both the source and destination computers. Because of the nature of domain name migration,


PC Transplant requires that you provide the user name and password of an account that has the rights to change and create a computer account in that domain. You are prompted for this at the end of the PC Transplant Wizard when you click the OK button or the Schedule button.
You may also pass in a -dau and -dap switch to specify this from the command line. In quiet mode, the -dau and -dap switches are required for a domain migration to take place. See Using the PC Transplant Wizard with Command-line Options (page 25). User authentication for a domain is not stored in the template. The user name provided may need to be preceded by the domain name depending on the authentication model of your domain server. You can also pass an encrypted password in the command line.

Application Settings

Migration Support for Non-standard Applications

The list of applications in the Applications tab depends on the .A2i files you have and which applications are registered in the Windows registry as installed applications. If the application is not registered in the registry, the application is still displayed if you had specified the complete path of the .exe or the complete or partial path with Type=Scan in the .A2i file.

The .A2i files are created for non-standard applications, that is, the applications that do not store their installation information with the registry. To see the specific application settings, open any .A2i file (contained in the PC Transplant installation folder) in a text editor or the A2i Builder. The applications section of these A2i files has a new attribute, Type=Scan. This attribute tells the PC Transplant Wizard that it has to scan the hard disk to locate this application. The search path is given in the A2i file using the ScanPath tag.

For the applications which do not contain information in the registry, Flag=Scan is provided in the Applications section of the .A2i files. See Application to Information (.A2i) Format (page 110).

For the PC Transplant Wizard, the applications that do not contain information in the registry are considered as if they are not installed. These applications are not selected in the list. A magnifying glass icon is displayed with such applications. You can select such an application and when you click Finish to create a personality package, the A2i files are scanned. The icon and the description are changed for the application. If there is no information found for the applications, then they are deleted during the scan.

During real-time migration, all the applications are selected. A warning message is displayed for the applications that might not be migrated to the destination computer. The actual scanning of the applications takes place when you click the Finish button to start the migration. If the application is found on both the source computer and the destination computer, then the application is migrated.

For the Template Builder, the applications are not searched.

A2i File Updates

Altiris continues to add support for additional applications. The Application to Information (.A2i) files which support these applications are available as a free download from Altiris’ Web site at ftp://ftp.altiris.com/pct/.

Select the folder for the version of PCT that you are using. For example, for version 6.8 use the ver6.8 folder. The ver6.x folder is for 6.x versions previous to 6.8.


ftp://ftp.altiris.com/pct/

A2i Builder
If you are using applications for which no A2i files exist, PC Transplant ships a utility with A2i Builder that lets you build your own custom .A2i files.


Chapter 6Using the PC Transplant Package Editor

The PC Transplant Package Editor lets you easily view and change an existing Personality Package. You can also launch PC Transplant tools and update .A2i files.

The PC Transplant Package Editor displays the title, description, created date, created version, total number of files and folders, and the total size of files and folders of the Personality Package.

PC Transplant Package Editor Menu FeaturesThe PC Transplant Package Editor provides the following features to view and change an existing Personality Package.

Feature Description Button Access

Open Opens a window from which you can browse and open a Personality Package.

Ctrl+O

Click File > Open.

Close Closes the Personality Package without saving it.

Click File > Close.

Save Saves the Personality Package. Ctrl+S

Click File > Save.

Save As Saves the Personality Package with a different name and path if required.

Click File > Save As.

Undelete Retrieves the last deleted item. Ctrl+Z

Find Searches for items within the selected structure (registry or file folder).

You can match the whole word only and case. You can also include folders and items.

Ctrl+F

Click Edit > Find.

Add Item Adds an item to the selected structure. Right-click an item and select Add Item.

Delete Deletes the selected item. Right-click an item and select Delete.

Copy Copies the selected item. Right-click an item and select Copy.

Paste Pastes the copied item to the selected structure.

Right-click an item and select Paste.

Properties Opens the Properties window for the selected item.

Right-click an item and select Properties.

Options Opens the Options page where you can change the Run and Display options.

Click Edit > Options.


Migrate User Settings

Opens the PC Transplant Wizard. See Transplanting Computer Settings and Data (page 15).

Click Tools > Migration Wizard.

Create Report Opens the Package Content utility. See Viewing, Printing, or Changing Personality Package Contents (page 42).

Click Tools > Package Report.

A2i Builder Opens the A2i Builder utility. See Using the A2i Builder (page 72).

Click Tools > Custom A2i Builder.

Build PCT Templates

Opens the Template Builder utility. See Using the Template Builder (page 66).

Click Tools > Template Builder.

Application Updates

Updates existing A2i files or adds new A2i files to your list of supported applications.

Click Help > Application Updates.

Online Help Opens the online help. Click Help > Contents and Index.

Feature Description Button Access


Chapter 7Using the A2i Builder

The .A2i files are used to describe all the components that are needed to transfer an application’s settings and data files. This file is used by the PC Transplant Wizard to show the user which application settings can be migrated and how to gather and lay down this information.

Applications Supported

You can find the .A2i files in the <System Drive>:\Program Files\Altiris\PCT\<Language Folder>. The following are few of the applications for which the .A2i files have been created:

Adobe PageMaker

Adobe Illustrator

Altiris Carbon Copy client

AT&T Global Network

Cisco VPN Client

Corel Paradox

Microsoft ActiveSync 3.1/3.5

Microsoft Visual Basic

Microsoft Visual C++

Microsoft FoxPro

Microsoft Visual Interdev

Microsoft Visual Source Safe

Symantec WinFax Pro

Adobe Acrobat 5.0

Adobe Photoshop 6.0

AOL 6.0/7.0

Corel Presentations 11

Corel Quattro Pro 11

Corel WordPerfect 11

Eudora 5.1

FileMaker Pro 5.5

ICQ 4.x/5.x

McAfee Virus 6.0

Microsoft FrontPage2002

Microsoft Messenger 4.5


Microsoft Publisher 2002
Microsoft Visio 2002

Microsoft Word

Microsoft Excel

Microsoft Access

Microsoft PowerPoint

Microsoft Internet Explorer

Microsoft Outlook Express

Microsoft Outlook

Microsoft Project

Microsoft Exchange

Microsoft NetMeeting

Microsoft Office Shortcut Bar

Paint Shop Pro 7.0

PC Anywhere 10.0

QuarkXpress

RIM BlackBerry

Update to the Latest A2i Files from the Web

Altiris is continually adding support for migrating settings and files for new application versions and adding functionality to existing ones. When you start the PC Transplant Wizard, a dialog box gives you the opportunity to update A2i files from the Altiris Web site. You can also set an interval of days for you to be reminded to check for updates again or you can choose not to be reminded again. The original files are placed in the Backup folder before updating the .A2i files.

A2i BuilderThe A2i Builder Wizard helps you create customized .A2i files for a particular application by monitoring the changes made by a user to that application. When applications contain settings that go beyond the capabilities of the A2i Builder, you will be required to manually modify these files using a text editor. For more information on how to use A2i Builder, refer to online help.

CautionBefore using the A2i Builder, read Application to Information (.A2i) Format (page 110), which describes the contents of an .A2i file, and how to build or edit an .A2i file manually using a text editor. This knowledge will help you understand the functionality and limitations that you may find when using the A2i Builder. Any Windows user can use the A2i Builder, but to utilize some of the more advanced capabilities found in an .A2i file, you need advanced knowledge of Windows registries, folders, and files.


Submit A2i Files to Altiris Test Site
A user can now submit .A2i files to the Altiris Web site for approval. The .A2i files can be submitted to the following URL:

ftp://ftp.altiris.com/pct/ver6.x/waitingapproval


ftp://ftp.altiris.com/pct/ver6.x/waitingapproval

Chapter 8Using the A2i Editor

The Altiris A2i Editor lets you easily view and change an existing .A2i file. It provides an easy to use GUI interface, and provides the drag and drop functionality to copy settings from one version to another version. The A2i Editor enables you to enter settings for applications whose settings cannot be captured when A2i builder launches the application.

You can also launch the PC Transplant Wizard from the A2i Editor to create a personality package that contains the edited A2i file. The A2i Editor displays the versions, sections, and variables of the A2i file.

A2i Editor Menu FeaturesThe A2i Editor provides the following features to view and change an existing .A2i file.

Feature Description Toolbar Icon

Access

Open Opens a window from which you can browse and open an A2i file.

Ctrl+O

Click File > Open.

Save Saves the A2i file. Ctrl+S

Click File > Save.

Save As Saves the A2i file with a different name and path if required.

Click File > Save As.

A2i Builder Opens the A2i Builder utility. Click Tools > Launch A2i Builder.

Migrate User Settings

Opens the PC Transplant Wizard. Click Tools > Launch Try Now.

Edit Warnings Opens the Edit Warnings dialog that allows you to add, delete, and modify warnings for each version in the A2i file.

Click Edit > Edit Warnings.

Edit Details Opens the Edit Details dialog that allows you to edit the Details section of the A2i file.

Click Edit > Edit Details.

Add Version Adds a version to the A2i file. Click Insert > New Version.

Add Section Adds a section to the A2i file. Click Insert > Section.

Add Variables Adds a variable to the A2i file. Click Insert > Variables.


Add Registry Adds a registry key to the A2i file. Click Insert > Registry Item.

Add File Adds a file to the A2i file. Click Insert > Files.

Add Folder Adds a folder to the A2i file. Click Insert > Folders.

Add File Types

Adds file types to the A2i file. Click Insert > File Types.

Online Help Opens the online help. Click Help > Contents and Index.

Feature Description Toolbar Icon

Access


Chapter 9Technical Reference

This section includes the following topics:

PC Transplant File Types and Executables (page 77)

Desktop and Network Settings File Format (page 79)

Setting Tags (page 81)

Settings and Item Setting Properties (page 101)

Application to Information (.A2i) Format (page 110)

Template File Format (page 123)

Troubleshooting (page 130)

PC Transplant File Types and Executables

File Type Description

personality.exe Self-executing Personality Package. Personality Packages can be viewed and edited in the PC Transplant Editor (PCTEdit.exe). The package can also be updated using the PC Transplant Wizard.

Application.ini Current list of templates used when building a Personality Package. It maintains a list of 5 recently used templates either by the PC Transplant Wizard or Template Builder.

*.A2i Application to Information file that defines the settings and files required to migrate an application.

Dsktp*.ini Desktop settings file

Ntwrk*.ini Network settings file

Default.pbt Default personality build template. Technicians can create their own custom personality build templates that record what settings are included in the Personality Package during the scan and build process. These templates can be accessed using the command line to automate the build process and bypass the wizard.

*.pbt User-created personality build template. Template files can be created using the PC Transplant Wizard or using the Template Builder.

*.chm PC Transplant HTML help files

*.pdf PC Transplant documentation provided in Adobe Acrobat format.


AltShellExt.dll Microsoft Explorer Shell Extension that allows you to edit or view the properties of a PC Transplant Personality Package from within Windows Explorer.

AltShellExt.reg Registry setup for the Microsoft Explorer Shell Extension.

instpct.bin Personality Package binary logic file. All Personality Packages are built starting with this binary file.

default.bmp Default splash screen added to a new Personality Package

Regsys.sys Device driver for A2ibuild.exe

Regvxd.vxd Device driver for A2ibuild.exe

Aclient.bat Used by the aclient.exe during computer and domain name configuration.

Aclient.cfg Configuration file used by aclient.exe during computer and domain configuration.

Executable Description

Aclient.exe Sets the computer name and domain name on the destination computer. If the domain name is changed, it establishes trust back with the domain.

PCTPackageLauncher.exe

Continues the migration of a Personality Package after the computer and domain name has been configured.

Hhupd.exe Microsoft’s HTML help file install.

License.exe Tool used to license PC Transplant.

Applic.dll License tool supporting file.

Pctedit.exe PC Transplant Package Editor. Used to view, add, modify, and delete individual registry items, files, and folders in a Personality Package.

PCTRTDestAgent.exe

PC Transplant Real-time Destination Agent.

Pctwiz.exe PC Transplant Wizard. Used to build or update Personality Packages to include desktop, network, and application settings and files requested by a user or template. Used to migrate the personality in real-time mode.

PCTNet16.dll

PCTNet32.dll

Used by PCTWiz.exe to authenticate a user name and password.

RemoteInstall.dll

Used by PCTWiz.exe to push the installation of the PCTRTDestAgent.exe to a Windows NTx system.

Pkgcntnt.exe Program that lets you view and print the files and registry values contained in a Personality Package.

Regsys.sys Device driver for A2ibuild.exe

Regvxd.vxd Device driver for A2ibuild.exe

File Type Description


Desktop and Network Settings File FormatA desktop settings or network settings file is used to describe all the components that are needed to transfer Windows desktop or network settings and any data associated with them from one Windows computer back to the same or other Windows computer. These setting files are used by the PC Transplant Wizard to show the user which settings can be migrated, and how to gather this information. These files are named DsktpOSVersion.ini and NtwrkOSVersion.ini, where OSVersion describes the Windows Operating System version type. The settings file names for the different supported operating systems are named like the following:

DsktpXP.ini

NtwrkXP.ini

A setting file follows .ini file syntax, with the exception that duplicate value names are allowed within a section. An .ini file definition is broken down into three parts: Section Name, Key Name, and Value. A typical .ini definition could look like the following:

[My Section]

MyFirstValueName=Value

MySecondValueName=Value

[Another Section]



MyThirdValueName=Value

A desktop or network setting can be a registry value, INI file, a file, or a file type. To define a setting requires the use of three value names: Flag, Base, and Values. These items can be repeated for each registry and file item you wanted to associate with that setting. The use of Flag, Base, and Values for desktop and network setting files are the same as those defined in an .A2i file. For a detailed explanation of the use of these tags, refer to Application to Information (.A2i) Format (page 110) and Setting Tags (page 81).

Desktop SettingsEach setting you define in a desktop settings file starts with a short section name describing the setting. Example: [Display Properties], [Control Panel], or [This one is mine].

Template.exe Template Builder. Tool to create personality build template that is used to select settings in the PC Transplant Wizard.

A2ibuild.exe A2i Builder. Program to build your own custom .A2i files.

Sidgen.exe Program that regenerates a new, unique Security ID (SID).

Executable Description


These settings define the primary setting groups that will be displayed in the Desktop settings area of the PC Transplant Wizard. Each main setting can include sub-settings. A sub-setting is defined by providing the main setting name followed by a space, followed by a “>” character, followed by a space, and then followed by the name for the sub-setting:
[Main Setting > Sub Setting]

Example: to define a setting called “Wallpaper” under the “Display Properties” setting, create the section name

[Display Properties > Wallpaper]

You can include an additional sub-setting by including another “>” and sub-setting name:

[Main Setting > Sub-Setting > Sub-Sub-Setting]

Each setting may include none, one, or more tags describing registry, files, or INI values that define what is that setting.

Example:

[Control Panel]

[Control Panel > Keyboard]

[Control Panel > Keyboard > Screen Lock]

Flag=File

Base=c:\winnt\myfiles

Values=screen.ini

[Control Panel > Messenger]

Flag=File


Values=screen.ini

Network SettingsEach setting you define in a network settings file starts with a short section name describing the setting. Example: [Window drive Mapping], [TCP/IP], or [This one is mine].

For network settings, you can also define sub-items for a setting using the syntax described in Desktop Settings (page 79):

[Main Setting]

[Main Setting > Sub-itemSetting]


[Main Setting >Sub-itemSetting > Sub-Sub-Setting] . . .)
“Main” is the setting name for the main item and “Sub-item” is a description for each of its sub-items.

The following example shows how you could define a setting called “Altiris” that contains two sub-items: “Express Deployment Server” and “RapidInstall”.

[Altiris]

[Altiris > Deployment Server]

Flag=File


Values=screen.ini

[Altiris > RapidInstall]

Flag=File


Values=screen.ini

Setting TagsThis section gives examples and definitions of all setting keys and tags supported by PC Transplant. Users can use these keys and tags to capture specific registry and file settings on their source computer and control how these settings transplant on the target computer.

DetailYou can provide more information about a setting by including a Detail tag. Example: Detail=<Detail Text>. To view the details in a property page, click Properties button on Transplant PC’s Settings page in PCTWiz or on Transplant settings and data page when running a Personality Package.

[8.x]

Description=MS Word 97

Detail=Migrates your MSWord97 Settings

[8.x Settings]

Detail=Migrates Toolbars, Macros, Edit, Print, and Save settings.

[8.x Spelling and Grammar]

Detail=Migrates Spelling and Grammar settings for Office2000.


Users can use these tags in:

All .A2i files

dsktpXP.ini files

ntwrkXP.ini files

The files listed above can be found in the PC Transplant program folder. They are a valuable reference when creating your own .A2i files or modifying existing settings files.

For information about how to build a .A2i file, refer to Using the A2i Builder (page 72). For information on how to add your own desktop and network settings to the dsktp*.ini and ntwrk*.ini files, refer to the Desktop and Network Settings File Format (page 79).

Basic Structure (page 82)

Definitions (page 82)

Advanced Usage (page 90)

Environment Variables (page 97)

Values (page 99)

Basic StructureThe basic structure for capturing settings consists of a combination of the following keys:

Flag

Base

Values

Example:

Flag=File

Base=c:\one

Values=file1.txt,file2.txt

A combination of Flag, Base, and Values is referred to as an “item setting.” A combination of a group of setting items, contained within a section, is referred to as a setting.

Definitions

FlagFlag supports seven values: File, Registry, FileType, INI, API, Variables, and Warning.

Flag=File specifies that the setting captures files.

Flag=Registry specifies that the setting captures registry entries.

Flag=FileType specifies that the setting captures all files from the selected drives matching the specific file type.


Flag=INI specifies that the setting captures values from an INI file.
Flag=API is used internally by PC Transplant, and is not discussed here.

Flag=Variables defines a dynamic value that gets assigned, pending the version of the application.

Flag=Warning specifies that the path item is a warning message.

NoteFlag variables are only valid when used in an .A2i file, and within the Variables section of that file.

FLAG=INI. The Flag=INI is to be used in association with Flag=File. After capturing all the settings from an INI file you need to use Flag=File only once to add these settings to the package. You will also need to specify the correct path of the file using the NewDestination tag in Flag=File, otherwise the original path of the INI file will be incorrect.

Below is an example, using the following file c:\test.ini that includes the following data:

[MySection]

MyValue=value

[Another Section]

ValueOne=one

ValueTwo=two

To capture the value for MyValue and ValueTwo, the following would be defined in a setting file.

Flag=INI

Base=c:\test.ini

Values=MySection|MyValue

Flag=INI

Base=c:\test.ini

Values=Another Section|ValueTwo

Flag=File

Base=%MI_PCT_TEMP%

Values=test.ini

NewDestination=C:\


NoteFlag=INI works in conjunction with Flag=File. All Flag=INI path items must be followed by a single Flag=File path item as shown in the example above. The Base for this File path item will always be %MI_PCT_TEMP% and Values tag will contain the name of the INI file. If it is not followed by a Flag=File, then the path item has no significance. Each INI path item does not need a File path item. When all INI path items have been specified, they should be followed by a single File path item.
For more examples, please refer to the Lotus Notes.a2i and Qualcomm Eudora.a2i setting files.

BaseBase contains the parent path for the setting.

If Flag=File, then Base contains the name of the directory to find the required files.

If Flag=Registry, then Base contains the name of the registry key to find the required registry values.

If Flag=FileType, then Base is not used.

If Flag=INI, then Base contains the full path to the INI file.

If Flag=Variables, then Base contains the name of the variable.

If Flag=Warning, then Base is a comma-separated list of the target versions for which this warning is applicable to.

ValuesValues contains the name of the specific entities to capture.

If Flag=File, then Values contains a comma-separated list of file names. The path specified in Base is searched to find these files. Wildcards such as ? and * are supported when specifying a file name.

If Flag=Registry, then Values contains a comma-separated list of registry values. The key specified in Base is searched to find these registry values.

If Flag=FileType, then Values contains the name of the file type. Wildcards such as ? and * are supported when specifying a file name. All drives will be searched to locate the file type indicated.

If Flag=INI, then Values contains a comma-separated list of INI values. Values follow the syntax section name|key name<=default value> (item inside < > is optional).

If Flag=Variables, then Values contains the assigned value of the variable.

If Flag=Warning, Values is the actual text of the warning message.

NoteA warning message must not contain $ sign as this has an internal meaning.

ExamplesIn the following examples, Flag=File specifies that the entity being captured is a file.


How to Capture Files
The following item setting captures the files file1.txt, and file2.txt from directory c:\one.

Flag=File

Base=c:\one

Values=file1.txt,file2.txt

For additional examples, see the [9.x Settings] section in the access.A2i file located in the PC Transplant default installation directory.

How to Capture Directories

The following item setting captures all files as well as all subfolders (with their files) from directory “c:\one.”

Flag=File

Base=c:\one

Values=*.*


How to Capture Files from a Directory Based on a Wildcard

The following item setting captures all files whose extensions match “?xt”.

NoteNo subfolders are scanned. All combinations of wildcards ‘ * ’ and ‘?’ are supported.

Flag=File

Base=c:\one

Values=*.?xt

For additional examples, see the [9.x Custom Dictionary] section in the access.A2i file located in the PC Transplant default installation directory.

How to Capture Registry Values

In the next two examples, Flag=Registry specifies that the entity being captured is a registry entry.

The following item setting captures values “value1” and “value2” from the “HKEY_CURRENT_USER\Software\Microsoft\Access\7.0” registry key:

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Microsoft\Access\7.0

Values=value1,value2

For additional examples, see the [7.x Auto Correct File] section in the access.A2i file located in the PC Transplant default installation directory.


How to Capture Registry Keys
The following item setting captures all values and all subkeys (with their values) from the “HKEY_CURRENT_USER\Software\Microsoft\Access\7.0” registry key.

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Microsoft\Access\7.0

Values=*.*


How to Capture All Files on the Local Drives (Unfiltered) Matching a Given Extension

In the following example, Flag=FileType specifies that the entities being captured are files and belong to a particular file type (Example: *.doc, *.txt, . . .).

The following item captures all file names having the extension .doc from all the drives on the source computer.

Flag=FileType

Values=*.doc

NoteDrives which are filtered will not be scanned. If Flag=FileType, the Base tag can be omitted. If it is present, it has no significance.

For additional examples, see the [0 Associated Files > MDB Files] section in the access.A2i file located in the PC Transplant default installation directory.

How to Redirect Files, File Types, and Directories to a New Destination Path

Use the NewDestination=<path> tag to redirect files, file types, and directories to a new destination path. Example:

[My Files]

Flag=File

Base=c:\mydir

Values=*.*

NewDestination=d:\mydir

[My *.txt File Types]

Flag=FileType

Values=*.txt

NewDestination=d:\mydir


How to Grab a Setting from an .INI File
This following example gets the value of MAPI in the Mail section of the Win.ini file:

[My Settings]

Flag=INI

Base=%MI_WINDIR%\win.ini

Values=Mail|MAPI

The following example gets the value of MAPI in the Mail section of the Win.ini file. If the MAPI key cannot be found, it gets added to the package and its value gets set to 1:

Flag=INI

Base=%MI_WINDIR%\win.ini

Values=Mail|MAPI=1

How to Capture All Keys under a Specified Section of an INI File

Flag=INI

Base=c:\one\application.ini

Values=TestSection|*.*

Flag=File

Base=%MI_PCT_TEMP%

Values=application.ini

The above path items capture all keys under section “TestSection” from “c:\one\application.ini” file.

For an additional example, see the [0 E-mail and Address Book] section in the Qualcomm Eudora.A2i file.

How to capture specific keys under a specified section

Flag=INI


Values=TestSection|TestValue1,TestSection|TestValue2

Flag=File

Base=%MI_PCT_TEMP%


The above path items capture the keys “TestValue1” and “TestValue2” under section “TestSection” from “c:\one\application.ini” file.


How to capture specific keys from all sections
Flag=INI


Values=*.*|TestValue1

Flag=File

Base=%MI_PCT_TEMP%


The above path items capture the key “TestValue1” from all sections of the specified INI file.

How to set default values for captured keys

Flag=INI


Values=TestSection|TestValue1=1,TestSection|TestValue2=2

Flag=File

Base=%MI_PCT_TEMP%


The above path items capture the specified keys. If these keys are not found at the source, they will still be picked up with the default values mentioned. The usage of default values is optional.

Flag=Warning

Use this tag to define warning messages for a setting.

How to specify a warning for an application

The following example shows how to define a warning when migrating Fast Save settings from Word 97 to Word 2000/XP:

[8.x]

Description=MS Word 97

[8.x Settings]

Flag=Warning

Base=9.x,10.x

Values=Unable to migrate “Fast Save” from Word 97 to Word 2000/XP.


How to specify a warning when migrating a setting to an unsupported application version

The following example will display a warning while migrating any Spelling and Grammar setting to any other version.

[8.x Spelling and Grammar]

Flag=Warning

Base=

Values=Unable to migrate Spelling and Grammar.

How to specify warnings for Desktop and Network settings

In case of Desktop and Network settings “Base” can have one or more combinations of the following values: WinNT4, WinNT5, and WinXP.

Using the dsktpNT5.ini file, the following example displays a warning if a wallpaper is migrated from Windows 2000 to Windows XP.

[Display Properties Background Wallpaper]

Flag=Warning

Base=WinXP

Values=Active Desktop wallpaper may not be visible after migrating to Windows XP.

How to specify a warning when migrating to any OS version

Flag=Warning

Base=0

Values=Sound settings are unique to the sound device installed on a machine and cannot be migrated.

How to Create a New Variable for Version 4.x of Your Application

The following example assigns the value of 4.0 to VAR:001 if the version of the application is 4.x:

[0 Variables]

[0 Variables > 4.x]

Flag=Variables

Base=<#VAR:001#>

Values=4.0


The following example gets the path contained in a registry value and assigns it to VAR:002 if the version of the application is 4.x:
Flag=Variables

Base=<#VAR:002#>

Values= <%REG:HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Express\5.0\

DataPath%>

Advanced UsageWith the use of some additional tags, you can customize an item setting to create your own Base path definition. Example: rather than specifying a static path, you can use these advanced tags to retrieve a path from a registry value.

The advanced tags you can use in a Base path include:

<%REG:%>

<%MULTIREG:%> used along with <%REG%>

<%STRIPTAILSLASHES:%> used along with <%REG:%>

<%all%> used with or without <%REG:%>

<%allvalues%> used with or without <%REG:%>

<%INI:%>

Environment variables (used mainly to specify standard Windows directories. Example: desktop directory, Windows directory, system directory, current user name, and so on)

<%REG:%> <%REG:%> is used to define a directory or a file using a registry value.

How to Capture a File Using a Registry Value that Contains the Full Path of the File

If the registry value “Path” contains c:\one\two.txt, the following item setting would attempt to capture the file c:\one\two.txt.

Flag=File

Base=<%REG:HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\

Common\

AutoCorrect\Path%>

Values=

For additional examples, see the [7.x Auto Correct File] section in the access.a2i file located in the PC Transplant default installation directory.


How to Capture a File Using Your Own Directory Path, and a Registry Value That Contains Only the Filename
If the registry value “Filename” contains two.txt, the following item setting would attempt to capture the file c:\one\two.txt.

Flag=File

Base=c:\one\<%REG:HKEY_CURRENT_USER\Software\Microsoft\

Office\8.0\Common\

AutoCorrect\Filename%>

Values=

For additional examples, see the [8.x Settings] section in the access.a2i file located in the PC Transplant default installation directory.

How to Capture a File Whose Path is Specified in a Registry Value

If the registry value “DirPath” contains c:\one, the item following setting would attempt to capture the file c:\one\one.txt.

Flag=File


Common\

AutoCorrect\DirPath%>

Values=one.txt

<%REG:%> NestingThe <%REG:%> tag can be nested inside of other <%REG:%> tags. The order of nesting resolution is resolved from the inside out. By nesting these tags, you can build Base paths using a combination of these tags.

How to Capture a File by Building a Registry Path Whose Value Contains a Path to a File

If the registry value “HKEY_CURRENT_USER\two\value2” contains “value1,” and “HKEY_CURRENT_USER\one\key1\value1” contains “c:\1.reg,” the following item setting would attempt to capture the file c:\1.reg.

Flag=File

Base=<%REG:HKEY_CURRENT_USER\one\key1\<%REG:HKEY_CURRENT_USER\two\value2%>%>

Values=

<%MULTIREG:%> <%MULTIREG:%> is used to chain <%REG:%> definitions together to build a single path.


How to Capture a File Whose Directory is Specified in One Registry Value and Whose Name is Specified in Another Registry Value
If the registry value “HKEY_CURRENT_USER\key1\value1” contains c:\dir, and “HKEY_CURRENT_USER\key2\value2” contains file1.txt, the following item setting would attempt to capture the file c:\dir\file1.txt.

Flag=File

Base=<%MULTIREG:<%REG:HKEY_CURRENT_USER\key1\value1%>\

<%REG:HKEY_CURRENT_USER\key2\value2%>%>

Values=

Note<%MULTIREG:%> can encapsulate only two <%REG:%> expressions.

<%STRIPTAILSLASHESn:path%> <%STRIPTAILSLASHESn:path%> is used to strip files or folders from the end of a path. The tag can be used to get the path of a file or a parent path for a directory. The value n specifies the number of directories or files to be removed from the path. If the n value is not specified, then, by default, all slashes from path will be removed to extract the drive name only.

How to Capture a File Using the Path to a Different File in the Same Directory

After stripping back to the first slash, the base path would return c:\one, and the following item setting would attempt to capture c:\one\one.txt.

Flag=File

Base=<%STRIPTAILSLASHES1:c:\one\two.txt%>

Values=one.txt

How to Capture a File Using a Path Obtained from a Registry Value

Flag=File

Base=<%STRIPTAILSLASHES2:<%REG: HKEY_CURRENT_USER\Software\Express\Options\Directory%>%>

Values=one.txt

If the registry value “HKEY_CURRENT_USER\Software\Express\Options\Directory” contains c:\one\two\three.txt, after stripping back to the second back slash the base path would contain c:\one. Using the resulting path, the item setting above would attempt to capture the file c:\one\one.txt.

If you do not specify a value for n and specify the filename in the Value item, then the file C:\one.txt gets captured when the specified registry path points to a string "C:\one\two\three.txt".

Flag=File


Base=<%STRIPTAILSLASHES:<%REG:HKEY_CURRENT_USER\Software\Net scape\Netscape Navigator\biff\users\one\servers\two\popstatepath%>%>
Values=one.txt

For additional examples, see the [0 Bookmarks and Profiles (POP only)] section in the netscape.a2i file located in the PC Transplant default installation directory.

<%STRIPHEADSLASHESn:path%> <%STRIPHEADSLASHESn:path%> is used to strip files or folders from the beginning of a path. The tag can be used to get the path of a file or a parent path for a directory. The value n specifies the number of directories or files to be removed from the path. If the n value is not specified, then, by default, all slashes from path will be removed to extract the filename only. This tag can be used only with <%REG%>.

How to capture a file from a current directory or a parent directory of a filename whose path is specified in the registry

If the registry path HKEY_CURRENT_USER\Software\Netscape\Netscape Navigator\biff\users\one\servers\two\popstatepath points to a string that contains the complete file path - "C:\one\two\three.txt", then the path item will capture the file D:\two\three.txt. The tag STRIPHEADSLASHES2 removes the C: drive and the folder one.

Flag=File

Base=D:\<%STRIPHEADSLASHES2:<%REG:HKEY_CURRENT_USER\Software\Netscape\Netscape Navigator\biff\users\one\servers\two\popstatepath%>%>

Values=

How to Capture a File Using a Path Obtained from a Registry Value

If you do not specify any values for n and the Value item, then the file D:\three.txt gets captured when the specified registry path points to a string "C:\one\two\three.txt".

Flag=File

Base=D:\<%STRIPHEADSLASHES:<%REG:HKEY_CURRENT_USER\Software\Netscape\Netscape Navigator\biff\users\one\servers\two\popstatepath%>%>

Values=

<%all%> <%all%> is used to enumerate all subkeys found under a particular key. It is generally used when you do not know the names of the subkeys or you do not know how the number of subkeys present.

How to Capture a Specific Registry Value Defined Under Multiple Subkeys

Assume the following registry structure:

HKEY_CURRENT_USER\key1\subkey1\value1 = “0”


HKEY_CURRENT_USER\key1\subkey1\value2 = “c:\dir1\file1.txt”
HKEY_CURRENT_USER\key1\subkey1\value3 = “temp”



HKEY_CURRENT_USER\key1\subkey2\value3 = “hello”

If you want to capture “value3” located under subkey1 and subkey2, you can use the following item setting:

Flag=Registry

Base=HKEY_CURRENT_USER\key1\<%all%>

Values=value3

The above item setting will capture:

HKEY_CURRENT_USER\key1\subkey1\value3= “temp”

HKEY_CURRENT_USER\key1\subkey2\value3= “hello”

For additional examples, see the [8.x Settings] section in the MS Outlook.a2i file located in the PC Transplant default installation directory.

How to Capture Files Whose Paths are Defined Under Multiple Registry Values








If you want to capture files defined under registry value “value2,” you can use the following item setting:

Flag=File

Base=<%REG:HKEY_CURRENT_USER\key1\<%all%>\value2%>

Values=

The above item setting will capture the files:


C:\dir1\file1.txt
C:\dir2\file2.txt


<%allvalues%> <%allvalues%> is used to enumerate all values under a particular registry key.

How to Capture All Values Under a Registry Key




HKEY_CURRENT_USER\key1\subkey1\value3 = 255

If you want to capture all values under “subkey1,” you can use the following item setting:

Flag=Registry

Base=HKEY_CURRENT_USER\key1\subkey1\<%allvalues%>

Values=

NoteIf you want to include all values under a particular registry key AND all of its subkeys, you can use:

Flag=Registry

Base=HKEY_CURRENT_USER\key1\subkey1

Values=*.*

For additional examples, see the [9.x Custom Dictionary] section in the access.a2i file located in the PC Transplant default installation directory.

How to Capture Files that are Defined as Values Under a Registry Key





If you want to capture all files specified at all values under “subkey1,” you can use the following item setting:


Flag=File
Base=<%REG:HKEY_CURRENT_USER\key1\subkey1\<%allvalues%>%>

Values=

The above item setting will capture the files:

c:\dir0\file0.txt

c:\dir1\file1.txt

c:\dir2\file2.txt

For additional examples, see the [9.x Custom Dictionary] section in the access.a2i file located in the PC Transplant default installation directory.

<%INI:%> <%INI:%> is used to capture a file whose name is specified as a Key Value in an INI file.

To capture a file associated with a key value of an INI file follow the syntax below, where “INI Path” is the path to the INI file, “Section” is a valid Section within the INI file, and “Key Name” is a valid Key within that section.

Flag=File

Base=<%INI:File Path|Section Name|Key Name%>

Values=

Examples:

How to capture a file whose full path is specified in a key value

Flag=File

Base=<%INI:%MI_APPDIR%\Eudora.ini|Recent File List|File1%>

Values=

How to capture a file whose name is specified in a Key value

Flag=File

Base=c:\one\<%INI:c:\Winnt\Eudora.ini|Section 1|Filename%>

Values=

The above path item captures the file which is under c:\one and whose name is specified at the key value “Filename” under the Section “Section 1".

So, if “FileName” contains two.txt, then the above path item captures the file c:\one\two.txt.

How to capture a file whose directory name is specified in a key value


Flag=File
Base=<%INI:c:\Programfiles\Eudora\Eudora.ini|Files|

SigFiles%>

Values=one.txt

The above path item captures the file one.txt whose directory path is specified at the key value “SigFiles” under the Section Files of ini file Eudora.ini saved in directory:

c:\Programfiles\Eudora

So, if “SigFiles” contains c:\one, then the above pathitem captures the file c:\one\one.txt.

How to capture a file whose path is specified in a key value, the name of which is specified in another key value

(Nested usage of <%INI:%> in the “Base” Value)

Flag=File

Base=<%INI: c:\Programfiles\Eudora\Eudora.ini|Files|<%INI: c:\Programfiles\Eudora\Eudora.ini|Files|SigFiles%>%>

Values=

Assume that the key “SigFiles”points to the string “value1” and the key “value1” contains c:\1.reg, the file captured is c:\1.reg.

Environment VariablesEnvironment variables are mainly used for specifying standard Windows paths such as Windows folder, system folder, other Windows-defined folders or file names without having to define a static path such as “c:\windows”. Using environment variables gives you the flexibility of defining paths that might change depending on the logged on user, operating system, or directory structure of the computer.

NoteThe environment variables follow the syntax %variable name%, which varies from tags that follow the syntax <%tag%>.

The following is a list of environment variables supported:


Environment Variables

Variable Function

%MI_ALLUSERS_APPDATA% All users’ Local Application data directory

%MI_ALLUSERS_DESKTOP% All users’ desktop directories

%MI_ALLUSERS_STARTMENU% All users’ start menu directories

%MI_APPDATA% Current user’s application data directory

%MI_APPDIR% Defines the directory for an installed application. This environment variable is specific to a .A2i file, and will be valid only if the application executable is defined as an installed application under the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths

%MI_BASEAPPDIR% Defines the parent directory for an installed application. This environment variable is specific to a .A2i file, and will only be valid if the application executable is defined as an installed application under the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths

%MI_CACHE% Current user’s temporary internet file directory

%MI_COMPUTERNAME% Extends the command-line abilities of and other settings that require the flexibility of using a computer name

Example: you can use this variable to gather all user settings for a given computer and store them under that computer’s name:

Pctwiz.exe -f:\%MI_COMPUTERNAME%.exe

For additional examples, see the [9.x Custom Dictionary] section in the access.a2i file located in the default installation directory.

%MI_COOKIES% Current user’s cookies directory

%MI_DESKTOP% PC Transplant Current user’s desktop directory

%MI_FAVORITES% Current user’s favorites directory

%MI_FONTS% Current user’s fonts directory

%MI_HISTORY% Current user’s History folder

%MI_INPUT_LOCALE_ID% Numerical ID of the user’s current locale

%MI_LOCALAPPDATA% Current user’s local application data directory

%MI_LOCALSETTINGS% Current user’s Local Settings folder

%MI_NETHOOD% Current user’s NetHood folder

%MI_OFFICE_TEMPLATE% Current user’s Office Template folder

%MI_PCT_TEMP% The path uses to store temporary data extractions. In the case of INI files, the folder is used to extract out individual elements from the INI file that can be added to a package.

%MI_PERSONAL% PC Transplant Current user’s personal document directory

%MI_PICTURES% Current user’s Pictures folder


ValuesThe Values tag supports several additional separators. These separators include the comma, wildcards, pipe, question mark, and equals symbols.

Comma “ , ”A comma allows you to include more than one registry value or file name under the base path. Each value or file must be separated by a comma.

How to Use Commas for Registry Values

Flag=Registry

Base=HKEY_CURRENT_USER\Control Panel\Desktop

Values=Wallpaper,TileWallPaper,WallpaperStyle

%MI_PRINTHOOD% Current user’s printhood directory

%MI_PROFILEUSER% The name of the user that is currently being processed by the Wizard (PCTWiz.exe).

%MI_PROGRAMFILESDIR%PC Transplant

Windows program files directory

%MI_PROGRAMS% Current user’s Programs folder

%MI_RECENT% Current user’s Recent folder

%MI_SENDTO% Current user’s sendto directory

%MI_STARTMENU% Current user’s startmenu directory

%MI_STARTUP% Current user’s Startup folder

%MI_SYSDRIVE% Returns the system drive as C (without a backslash)

This was implemented because %SYSTEMDRIVE% fails on 9x.

%MI_SYSTEM% Current user’s Windows system directory

%MI_TEMPLATES% Current user’s Templates folder

%MI_USERPROFILE% Defines a setting in a dsktp*.ini, ntwrk*.ini, or *.A2i files that includes the user’s profile directory

%MI_USER% Current logged on user

Example: you can use it to redirect to a folder that is dynamic to each user:

Flag=File

Base=C:\My Docs

Values=*.*

NewDestination=C:\My Docs\%MI_USER%

%MI_WINDIR% Windows directory

%MI_ALLUSERS_TEMPLATES% All User's Templates directory

%MI_ALLUSERS_FAVOURITES% All User's Favorite directory

Environment Variables

Variable Function


How to Use Commas for Files
Flag=File

Base=%MI_WINDIR%

Values=win.hlp,notepad.hlp,calc.hlp

Wildcards “ ? ” and “ * ”Wildcards allow you to conditionally define a part of a path or file name. Only those files or directories that fit the condition will be considered. A “?” can be used in place of a character, where any valid file name character is allowed. An “*” is used to define multiple file name characters.

How to Grab All Help Files Located in the Windows Directory

Flag=File

Base=%MI_WINDIR%

Values=*.hlp

Pipe “ | ”The pipe symbol is used as a separator between a registry value and its type. A registry type can be a string (REG_SZ) or a number (REG_DWORD). The examples below show the use of the pipe symbol and these registry types to define values for registries that may exist on the source computer.

Flag=Registry


Values=Wallpaper=”c:\windows\background.bmp”|REG_SZ

If the registry value “Wallpaper” is not present on the source machine, PC Transplant will add it to the package and set its value to “c:\windows\background.bmp.”

Flag=Registry

Base=HKEY_CURRENT_USER\two

Values=Number1,Number2=26|REG_DWORD,Number3

The above item setting captures the registry values “HKEY_CURRENT_USER\two\Number1,” “HKEY_CURRENT_USER\two\Number2,” and “HKEY_CURRENT_USER\two\Number3.”

If “HKEY_CURRENT_USER\two\Number2” does not exist, it is added to the package and given a value of 26.

For additional examples, see the [Wallpaper] section in the dsktpnn.a2i file located in the PC Transplant default installation directory.


Question Mark “?”A question mark is used to replace one registry value with a value you define. A question mark follows a registry type and is immediately followed by a value.
How to Modify the Value of Captured Registry Values

The following item setting captures the registry “HKEY_CURRENT_USER\Control Panel\Desktop\WallpaperStyle” entity.

Flag=Registry


Values=WallpaperStyle=0|REG_SZ?10

If the data value of “WallpaperStyle” is “10,” then it is replaced with a value of “0.”

Settings and Item Setting PropertiesYou can manage how PC Transplant migrates settings and item settings by controlling their properties. Settings and item settings can have specific properties associated with them. Properties can be defined for each setting described with the Flag, Base, and Value. Properties supported by PC Transplant include:

LogError

Exclude

Reboot

DestOS

DestVersion

Compatibility

Replace

Admin

DeleteKeyBeforeMigrating

ExcludeFilePaths

Retain

NewDestination

For real life examples showing the use of all the settings and properties described here, refer to the .A2i files that come with PC Transplant. For a detailed listing and definitions of all .A2i and setting INI tags, refer to Setting Tags (page 81).

LogErrorThe LogError value will cause an error to appear in the log file if there is a problem. The value you assign to LogError can be one of two values: TRUE or FALSE. If you do not include this property, the default for LogError is FALSE.


How to Cause An Error to Be Logged If An Item Is Not Found
If value1 or value2 is not present or could not be captured, then an error will be reported in the error.log file and the section will not come up as “successfully captured” in the summary list.

Flag=Registry

Base=HKEY_CURRENT_USER\key1

Values=value1,value2

LogError=TRUE

ExcludeThe Exclude value can be used as a shortcut if you want to include all items except the ones defined under the Value definition. The value you assign to Exclude can be one of two values: TRUE or FALSE. If you do not include this property, the default for Exclude is FALSE.

How to Include All Values Found Under a Registry Key Except One

Flag=Registry


Values=Value1

Exclude=TRUE


RebootThe Reboot value is used to define the reboot options used after running a PC Transplant Package that contains a given setting. Some settings can be transplanted and the changes can be applied immediately, others may require the user to be logged off and logged back on, while others require a full reboot of the system. The value you assign to Reboot can be one of the following values: FALSE, TRUE, Logout, Logout_9x, Logout_NTx, Reboot_9x, or Reboot_NTx. If you assign a value of FALSE, no reboot will be executed after running the PC Transplant package. Using the other values will force a reboot or log off from all operating systems. If you do not include this property, the default for Reboot is FALSE.

How to Prompt for a Reboot After a Personality Package has Finished Executing

Flag=Registry


Values=*.*

Reboot=TRUE


For additional examples, see the [5.x Settings] section in the iexplore.a2i file located in the PC Transplant default installation directory.
DestOSThe DestOS value is used to assign a setting to a specific destination operating system (OS). When a setting is assigned to an operating system, the setting will only transplant if the Personality Package is run on that operating system. The value you assign to DestOS can be one of the following values: ALL, Match, WinNT5, WinXP, or WinNTx. A value of ALL, allows a setting to transplant to any Windows operating system. A value of Match requires the operating system the Package was built under and the destination operating system to match. All other values are used to define the destination operating system requirements. If you do not include this property, the default for DestOS is ALL.

How to Keep An Item Setting from Transplanting to a Different Operating System

[Printers]

Flag=Registry


Values=*.*

DestOS=WinNTx

If the Package is run under Windows 2000 or XP, the item setting will migrate. If run on any other Windows operating system, the setting will not be transplanted to the destination PC.

For additional examples, see the [Power Settings] section in the dsktpnt5.a2i file located in the PC Transplant default installation directory.

DestVersionThe DestVersion value is used to support the migration of a setting only if the application of the destination machine matches that of the source machine. The value you assign to DestVersion can be only one value: Match.

If you do not include this property, the default for DestVersion is support for all application types.

DestVersion=Match has been implemented for Flag=File as well as for Flag=Registry. In some cases, you do not want a particular setting or file to be migrated if the source and destination versions don't match.

In the following example for Microsoft Word, the registry setting will be migrated only if the versions of Word match.

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Microsoft\Office\Common\

Smart Tag

Values=*.*

ExcludeFilePaths=TRUE


DestVersion=Match
CompatibilityThe Compatibility value is used to assign an entire setting to a specific operating system. The value you assign to Compatibility can be one of the following values: ALL, Match, WinNT5, WinXP or WinNTx. If you do not include this property, the default for Compatibility is ALL.

How to Keep a Setting from Transplanting to a Different Operating System:

[Printers]

Compatibility=WinNTx

Flag=Registry


Values=*.*

Flag=File

Base=%MI_WINDIR%\printers

Values=*.dll

If the Package is run under Windows 2000, or XP, the registry settings and files will transplant to the destination PC. If run on any other Windows operating system, none of the item settings will be transplanted.

ReplaceThe Replace value lets the Personality Package know how to transplant the setting if it already exists. The value you assign to Replace can be one of four values:

Yes

No

Newer

Filepath

If Replace is set to No, the setting will not overwrite the destination computer’s setting if it already exists. If you do not include this property, the default for Replace is Yes.

Replace=Newer specifies that while installing if the same file already exists at the destination computer, it will be replaced only if the source file is newer.

Use Replace=Filepath to replace the filepath of the source application version with the path at the destination. The idea is that with Replace=Filepath, the file(s) to be picked up should be specified solely by the Base tag. The Values tag is to be used exclusively for specifying the destination folder, which essentially has to be a variable, as it would depend on the version of the application at the destination machine. This should not be a comma-separated list. Only one variable should be specified.


The Variables specified as Values are not used for any work at the wizard side. They are stored in the package to be resolved at install time. For the resolution, we use the options block for mapping the destination folder information to the correct file. This mapping is done by storing the filepath against the variable <#VAR:000#> in the options block, which is visible to the user as advanced settings.
When specifying the variables, you can specify the full filename along with the path, or just the path. In the latter case, the original file name will be appended to the path. This tag is also used with Flag=Registry. In this case, it updates the registry to refer to the file migrated.

The example below shows how to get a file using the path obtained from a registry value, then to substitute its path with the contents of VAR:003.

[8.x Settings]

Flag=File


Common\AutoCorrect\Path%>

Values=<#VAR:003#>

Replace=Filepath

Use Replace=Format to change the format of the registry value in case the version differs at the destination. Example: in Project 98, values stored in the registry under HKCU\Software\Microsoft\Office\8.0\MS Project are of type REG_SZ, but in Project 2000 they are stored as DWORD.

Replace=Format works in the same way as Replace=Filepath described above. Lets take the example of MS Project as an example. In MS Project, version 8 and 9 store the registry values using different formats, namely REG_SZ and REG_DWORD respectively. So, for proper migration across versions, it is essential that we change the registry format while migrating from version 8 to 9. Below is an example showing how this is done:

[8.x Settings]

Flag=Registry

Base=HKCU\Software\Microsoft\<#VAR:001#>\MS Project\Options\*.*

Values=<#VAR:002#>

Replace=Format


[9.x Settings]
Flag=Registry

Base=HKCU\Software\Microsoft\Office\9.0\MS Project\Options

Values=*.*

[0 Variables > 8.x]

Flag=Variables

Base=<#VAR:001#>

Values=Office\8.0

Flag=Variables

Base=<#VAR:002#>

Values=REG_SZ

[0 Variables > 9.x]

Flag=Variables

Base=<#VAR:001#>

Values=Office\9.0

Flag=Variables

Base=<#VAR:002#>


Values=REG_DWORD
As can be seen in 8.x settings section, Base should specify the path to the registry item including the key name. This can be a *.* or a specific key name. Values is used to specify the variable registry format of destination. In case the version differs at destination, this will be resolved, else no action will be taken. We haven’t used this flag in the 9.x settings section as we do not support backward migration from 9 to 8. So effectively, in this example even if we don’t specify value of <#VAR:002#> under 8.x Variables, it won’t make a difference.

How to Prevent a Personality Package from Replacing an Existing Item Setting on the Target Computer

Flag=Registry


Values=*.*

Replace=No

If any value with the same name under “HKEY_CURRENT_USER\key1\subkey1”, the values will not be replaced by the one in the Personality Package.

For additional examples, see the [Keyboard Settings] section in the dsktpnn.ini file located in the PC Transplant default installation directory.

AdminThe Admin value lets the Personality Package know if administrative privileges are required to apply a given setting. The value you assign to Admin can be one of two values: FALSE or TRUE. If Admin is set to TRUE and the current logged in user does not have administrative rights, the Personality Package will display an error and not run. If you do not include this property, the default for Admin is FALSE.

DeleteKeyBeforeMigratingThe DeleteKeyBeforeMigrating value lets the Personality Package know if it should delete a registry key, with all its subfolders and values, on the target PC prior to migrating a setting to the target PC. This can be valuable if you want a destination application to only contain the settings from the source application. The value you assign to DeleteKeyBeforeMigrating can be one of four values: FALSE, TRUE, LeaveOutFilePaths, and RetainSpecified. If DeleteKeyBeforeMigrating is set to TRUE, the registry key and all its subkeys and values will be deleted prior to transplanting the setting. If DeleteKeyBeforeMigrating is set to LeaveOutFilePaths, the registry key with all its subkeys and values will be deleted prior to transplanting the setting, unless the registry value contains a path. If DeleteKeyBeforeMigrating is set to RetainSpecified, this should be followed by another set of tags that specify the values to be retained. Each set of tags that specify values, should be followed by Retain=True (See Symantec Winfax Pro.a2i for an example). If you do not include this property, the default for DeleteKeyBeforeMigrating is FALSE.


How to Force a Personality Package to Delete a Complete Registry Key Before Migrating Its Contents from the Personality Package
Flag=Registry


Values=*.*

DeleteKeyBeforeMigrating=TRUE

The above item setting instructs the Personality Package to delete the key “HKEY_CURRENT_USER\key1\subkey1” (along with subkeys and all values) if it exists on the target PC prior to copying it from the Personality Package.

For additional examples, see the [0 Bookmarks and Profiles (POP only)] section in the netscape.a2i file located in the PC Transplant default installation directory.

DeleteKeyBeforeMigrating=RemoveFor cross version migration of the Office suite, it was identified that the migration won’t take place if a specific key exists at the destination. We have to remove that key. This tag does just that.

Example

Flag=Registry

Base=HKEY_LOCAL_MACHINE\Software\Microsoft\Office\ByPassMigration

Values=

DeleteKeyBeforeMigrating=Remove

DeleteKeyBeforeMigrating=RetainSpecifiedThere may be cases where you need to delete all but a certain set of items. Using this tag, followed by the items to retain provides this functionality.

Example

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Altiris\RapidInstall

Values=*.*

DeleteKeyBeforeMigrating=RetainSpecified

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Altiris\RapidInstall


values=Directory,Execute
Retain=TRUE

ExcludeFilePathsThe ExcludeFilePaths value lets the PC Transplant Wizard know if it should exclude registry values that have hard-coded file paths. The problem with transferring a registry value that has a hard-coded file path is the validity of the path on the destination computer. The value you assign to ExcludeFilePaths can be one of two values: FALSE or TRUE. If ExcludeFilePaths is set to TRUE, any registry value that includes a hard-coded path will not be included in the Personality Package. If you do not include this property, the default for ExcludeFilePaths is FALSE.

How to Capture All Registry Values Except Those Containing File Paths





.a2i item setting:

Flag=Registry

Base= HKEY_CURRENT_USER\key1\subkey1

Values=*.*

ExcludeFilePaths=TRUE

The above item setting captures:

HKEY_CURRENT_USER\key1\subkey1\value1


. . . but does not capture:


For additional examples, see the [7.x Auto Correct File] section in the access.a2i file located in the PC Transplant default installation directory.

RetainThe Retain tag allows a PC Transplant Undo package to restore all of the registry settings changed by the original Personality Package except those listed in the Values tag of the setting where this tag is used.

The only value that can be assigned to Retain is ForUndo. Example:

Flag=Registry


Base=HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Word\Data
Values=Settings,Toolbars

Retain=ForUndo

NewDestinationThe NewDestination tag lets you map the path to a file to a new location. The value you assign to NewDestination is a string, and gets assigned to the collected file at the time the package is created.

The following example shows how to transfer a file located in one folder to a new folder:

Flag=File

Base=c:\migrate\ver3.6

Values=word.a2i

NewDestination=c:\AllA2iFiles

The above setting instructs the Personality Package to collect the word.a2i file in the c:\migrate\ver3.6 folder, and add it to the package as C:\AllA2iFiles\word.a2i.

Application to Information (.A2i) FormatAn .A2i file follows the .ini file syntax with the exception that duplicate value names are allowed within a section. The .ini file definitions are broken down into three parts: section name, key name, and value. A typical .ini definition could look like the following:

[My Section]



[Another Section]




(etc.)

Application Executable (page 111)

Application Versions (page 113)

Application Settings (page 114)

INI Support (page 118)

Variable Support (page 119)


Application Executable
All .A2i files start with a section called “Applications”. Under that section a value name of EXE must exist. The value given for EXE can be defined in one of the following ways.

List the name of the application’s .exe file

Use the Program value

List the full path of the executable

List the registry path for the full path of the executable

Full, partial, or no path of executables with Type= SCAN flag

List the name of the application’s .exe file

One method is to list the application’s exe file. Example:

[Applications]

EXE=Express.exe

The EXE value listed must match the .exe filename listed under the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths

You may also support multiple values for the EXE tag. Each executable listed must be separated by a comma. This is valuable if the name of the EXE may change across different versions of the application. For best results it is recommended that exe names be written in an increasing order of version. Old version exe names should come first and the highest exe name should come at the end.

Microsoft recommends that all applications installed under Windows add the name of the application’s executable to this key and include a default value of the full path to the executable. If the PC Transplant Wizard cannot find the executable listed in the .A2i with the path defined in the registry, the application will not be displayed under the Applications tab.

Use the program value

If an application is not registered under the “App Paths” registry key, but is listed when viewing Control Panel > Add/Remove Programs, a second method can be combined with the .exe value called Program. Use the Program value followed by the description provided under Add/Remove Programs.

Example:

[Applications]

EXE=Express.exe

Program=Altiris eXpress 5.0

The Program value listed must match the full product name or the first part of the product name listed under the following registry key:


HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
List the full path of the executable

A third method is to list the full path of the executable. Example:

[Applications]

EXE=c:\windows\calc.exe

This option is not the preferred method of listing the application because it ties the path to the name of the executable. It is provided for custom applications that do not provide an installation and are always installed in the same directory. If the PC Transplant Wizard cannot find the executable using the full path listed in the .A2i, the application will not be displayed under the Applications tab.

If none of these methods allow you to install your files or registry items, you may want to consider adding them to the Desktop setting files (see Desktop and Network Settings File Format on page 79).

Use the path value

If an application is not registered under the “App Paths” or “Uninstall” registry key, but is listed when viewing Control Panel > Add/Remove Programs, a fourth method can be combined with the .exe value called Path. Use the Path value followed by the path of the executable’s location in registry.

Example:

[Applications]

EXE=vb6.exe

Path=HKEY_CLASSES_ROOT\VisualBasic.Project\shell\open\command\

Case 1:

The data of the key name is searched for the executable and the value is taken.

Example:

EXE=vb6.exe

Path=HKEY_CLASSES_ROOT\VisualBasic.Project\shell\open\command\customApp

The data of the key name (customApp) is searched for the executable(vb6.exe) and the value is taken.

Case 2:

If no key name is provided, then default key name is taken.

Example:

EXE=vb6.exe

Path=HKEY_CLASSES_ROOT\VisualBasic.Project\shell\open\command\\


Here no key name is provided, so default key name and it’s value is taken.

NoteIf no key name is provided, a backslash must be provided as given in the example.

Use the Type= SCAN flag

If an application is not registered under the “App Paths” or “Uninstall” registry key, an additional tag, ScanPath=<path>, can be used to specify the path to scan for the application’s exe. This tag is valid only if Type=Scan flag is provided in Application section of the A2i file. <path> can include one or more drives, paths, and environment variables. <path> also accepts folder names and wildcards. The following table provides some examples of ScanPath=<path>.

Application VersionsThe section of the .A2i file following the Applications section contains information about each version of the application. You can support all versions of your application within the same .A2i. If the application uses a different executable filename for each of its versions, you will need to create a separate .A2i for each one. Each version section must provide a Description value name followed by a description of the application.

Example:

[4.0]

Description=Altiris Express 4.0

[4.5]


If you have multiple versions of an application that use the same settings, you can use an “x” when defining the version number.

Example Function

ScanPath=C: Scans C drive only

ScanPath=C:,D: Scans C and D drives

ScanPath= or no ScanPath tag found

Scans all local drives

ScanPath=%MI_PROGRAMFILESDIR%

Scans the Program Files directory

ScanPath=%MI_USERPROFILE%

Scans each migrated user's profile folder

ScanPath= c:\dir* Scans any folder that starts with c:\dir. Example: c:\dir1, c:\dir2

ScanPath= dir*,app Scans only those folders that start with dir, or have the name 'app'


Example:
[4.x]

Description=Altiris Express 4

Using a version number of 0 lets you create common information about your application that can be used regardless of the version.

Example:

[0]

Description=Altiris Express

You can create sub-items (or settings) for each application version by defining a section name, starting with the version number, then the name of the sub-item.

Example:

[4.0]


[4.0 Settings]

[4.0 Files]

If you want a sub-item to exist for all versions of the application, you can use a version number of 0 before the name of the sub-item.

Example:

[0 Data Files]

If you want to include sub-items for a defined setting include a “>” after the setting name.

Example:

[4.0 Files > Documents]

[4.0 Files > Templates]

Application SettingsAn application setting can be a registry value, a file, an .INI value, a file type, or a combination of these. To define a setting requires the use of three value names: Flag, Base, and Values. These items can be repeated for each registry and file item you want associated with that application’s version.


Flag The Flag value can be one of seven types:
Registry

File

FileType

INI

API

Variables

Warnings

The Registry Flag type is used to describe registry keys and values. The File Flag type is used to describe directories and files. FileType is for a specific document type—use it if you want to include a specific file or type of file and don’t know where it is located. Since FileType does not need a path, the Base value name is ignored. The INI flag is similar to the Registry flag, in that it is used to describe INI sections, keys, and values. The API flag is used internally so it is not discussed here. The Variables flag is used to define a dynamic value and is assigned values pending the version of the application.

Base Use the Base value to describe the path to an item. The value you provide for Base must correspond to the Flag type you defined. Example: if a Flag value is of type Registry, you must specify a registry path. If a Flag value is of type File, you must use a directory path. A path may include system environment variables, a PC Transplant variable, or the contents of a registry value. File types don’t need a Base.

Supported PC Transplant variables include:

%MI_DESKTOP%

%MI_STARTMENU%

%MI_SENDTO%

%MI_FAVORITES%

%MI_SYSTEM%

%MI_ALLUSERS_STARTMENU%

%MI_ALLUSERS_DESKTOP%

%MI_APPDATA%

%MI_LOCALAPPDATA%

%MI_COOKIES%

%MI_FONTS%

%MI_WINDIR%

%MI_APPDIR%

%MI_CACHE%

%MI_PERSONAL%

%MI_BASEAPPDIR%


%MI_PROGRAMFILESDIR%
%MI_COMPUTERNAME%

%MI_SYSDRIVE%

%MI_USERPROFILE%

%MI_ALLUSERS_APPDATA%

%MI_STARTUP%

%MI_TEMPLATES%

%MI_PICTURES%

%MI_RECENT%

%MI_HISTORY%

%MI_NETHOOD%

%MI_WINSYSTEMDIR%

%MI_PROGRAMS%

%MI_INPUT_LOCALE_ID%

%MI_APPDATA%

%MI_OFFICE_TEMPLATE%

%MI_OFFICE_DIR%

%MI_LOCALSETTINGS%

To get the path from a registry value, use this syntax: <%Reg:registry path%>. If the registry value contains too much path information, you can nest the <%Reg:…%> value inside of <%STRIPTAILSLASHESn:%> (where n is a value greater than 0 and specifies the number of slashes to backup).

Example:

Suppose the registry value:

HKEY_LOCAL_MACHINE\Software\Altiris\express\InstallDir

contained a value of:

C:\Program Files\eXpress\express.exe

You could use this registry value to get the path of Altiris eXpress Deployment Server using the following Base value:

Base=<%STRIPTAILSLASHES1: <%Reg:HKEY_LOCAL_MACHINE\Software\Altiris\express\

InstallDir%>%>

The resulting definition would return:

c:\program files\express


ValuesA Value is the specific item you want to capture using the Base path you provided. You can use wildcards when specifying a Value for Files. You can specify multiple Values by separating each Value with a comma. If you are defining registry Values, you can also provide default Values for the registry items in case they can’t be found. The syntax for defining a default registry value is:
Values=RegVal=Value|RegType

RegVal is the name of the registry value.

=Value is optional. If used, a default registry value will be added to the package if the registry value is not found on the source PC.

|RegType is optional. RegType can be any one of the following values:

REG_SZ (strings)

REG_DWORD (numbers)

REG_BINARY (binary data)

The Value tag supports environment variables (see your OS help file for a complete listing of OS specific environment variables), PC Transplant variables (see Environment Variables for a list of internal PC Transplant variables, or A2i variables (see A2i Variables on how to define and use A2i defined variables). It also supports obtaining a value from the registry (see “Advanced Usage” under “Settings File Format” for a complete definition of how to return the contents of a registry value).

The following provides examples and descriptions of what each example does:

[4.5]


To capture all registry keys and values under the Altiris eXpress registry key

[4.5 Settings]

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Altiris\Altiris Express

Values=*.*

To capture the eXpress.ini and aclient.ini files located in the Windows directory

Flag=File

Base=%windir%

Values=express.ini,aclient.ini

To capture AutoUpdateClients, DatabaseDSN, and DatabaseSettings registry values under the Options registry key

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Altiris\Altiris Express\Options


Values=AutoUpdateClients,DatabaseDSN,DatabaseSettings
To capture AutoUpdateClients, DatabaseDSN, and DatabaseSettings registry values under the Options registry key

If a registry value does not exist for AutoUpdateClients, add the registry value to the package as a DWORD with a value of 1. If a registry value does not exist for DatabaseDSN, add the registry value to the package as a string with a value of Altiris eXpress Database.

Flag=Registry

Base=HKEY_CURRENT_USER\Software\Altiris\Altiris Express\Options

Values=AutoUpdateClients=1|REG_DWORD,DatabaseDSN=Altiris Express Database|REG_SZ,DatabaseSettings

To grab the path stored under the registry key:

“HKEY_CURRENT_USER\Software\Altiris\Altiris Express\directory”.

Add data to the path, and collect all *.db files:

Flag=File

Base=<%REG:HKEY_CURRENT_USER\Software\Altiris\Altiris Express\directory%>\data

Values=*.db

To scan all directories specified by the user for the file type *.img

Flag=FileType

Values=*.img

INI SupportA2i files support the migration of individual INI values. The syntax of the INI Flag and definition used in an A2i file is listed as follows:

Flag=INI

Base=FullPathOfTheIniFile

Values=SectionName|Key<=DefaultValue>,(repeat)

Example: the following setting could be used:

Flag=INI

Base=%MI_WINDIR%\Win.ini

Values=Desktop|Wallpaper,Desktop|TileWallpaper=1,Mail|Mapi

Flag=File

Base=%MI_PCT_TEMP%

Values=Win.ini

NewDestination=%MI_WINDIR%\


The previous example would do the following:

Open the Win.ini file located in the Windows directory.

Capture the Wallpaper value under the Desktop section.

Capture the TileWallpaper value under the Desktop section.

If TileWallpaper is not found, add it to the package, and give it a value of 1.

Capture the Mapi value under the Mail section.

The Value tag also supports wildcards. In the following example, all values defined under the Desktop section would be captured:

Values=Desktop|*.*

INI settings are stored in a temporary INI file. When completed, the INI files are added into the package using the INI file’s real path. When the INI file is migrated onto the destination PC, it is merged with the existing INI file.

Settings and how they are defined in an A2i file are the same as those defined for Network and Desktop settings files. For this reason, we have not gone into detail on their definitions and their use. For a complete description see the Desktop and Network Settings File Format on page 79.

Variable SupportVariables provide a way to dynamically define values that can be associated with a specific version of an application. By using variables, you can dynamically map registry keys, registry values, and files based on the version of the application found on the source or destination PC.

Example: Microsoft Word 97 uses the application’s install folder to store its template files, whereas Word 2000 uses the “Application Data\Microsoft\Templates” folder. By defining a variable, assigning the application's install directory for version 8.x (Word 97), and assigning “Application Data\Microsoft\Templates” for version 9.x (Word 2000), you can manage where the template files are placed based on the version of the application.

Variables can be used when defining a registry value or file in an A2i file.

To add support for variables in an A2i file, you must first provide the [0 Variables] section. It is standard procedure to start this section at the end of your existing A2i file. Next, define a variables section for each version of your application. Example: [0 Variables > 2.x], [0 Variables > 3.x]. Using the Flag, Base, and Values tags, define a variable and assign it a value.

NoteVariables can only be used in A2i files. It is invalid to use <#VAR:xxx#> without defining an appropriate Variables section in the A2i file.

The syntax for defining a variable is as follows:

Flag=Variables


This flag defines the type of information that will follow.
Base=<#VAR:nnn#>

Give the variable a number, where nnn can be any number from 001 - 999. Example: <#VAR:001#>, <#VAR:002#>, etc. While it is possible to assign any number to nnn, it is good practice to start the first variable with a value of 001, and increment this number by one for each succeeding variable.

Values=Assignment

Assign the variable a value. This value could be a path, a file, a registry value name or type. A value can also be assigned dynamically using environment variables or values obtained from the registry.

The example below shows how to define a new variable, assign a value to it based on the application version, and then how to use that variable in another setting. The example starts by adding two settings that will require special values based on the application version.

In the example below, version 8.x of my application stores a specific registry value under “HKEY_CURRENT_USER\Software\Microsoft\MyApp\8.0”.

In version 9.0, it has been moved to

HKEY_CURRENT_USER\Software\Microsoft\MyApp\9.0

The two application version settings are shown below:

[8.x > Setting]

Flag=Registry

Base= HKEY_CURRENT_USER\Software\Microsoft\MyApp\8.0

Values=MySetting

[9.x > Setting]

Flag=Registry

Base= HKEY_CURRENT_USER\Software\Microsoft\MyApp\9.0

Values=NewSettingName

The settings above would work fine if a user is migrating from an 8.x version to another 8.x version or from a 9.x version to a 9.x version. The setting transfer would not work when migrating from 8.x to 9.x because the registry paths are different between the two versions and the application uses a different registry value to store the setting. By defining a variable, you can dynamically decide a value based on the source application and destination application’s version. The example below shows how to take the settings above to do just that.

[8.x > Setting]

Flag=Registry


Base= HKEY_CURRENT_USER\Software\Microsoft\MyApp\<#VAR:001#>
Values=<#VAR:002#>

[9.x > Setting]

Flag=Registry

Base= HKEY_CURRENT_USER\Software\Microsoft\MyApp\<#VAR:001#>

Values=<#VAR:002#>

[0 Variables]

[0 Variables > 8.x]

Flag=Variables

Base=<#VAR:001#>

Values=8.0

Flag=Variables

Base=<#VAR:002#>

Values= MySetting

[0 Variables > 9.x]

Flag=Variables

Base=<#VAR:001#>

Values=9.0

Flag=Variables

Base=<#VAR:002#>

Values= NewSettingName

When version 8.x of the application is found on the source machine, the variables will be resolved for that version. When the Personality Package is applied to the 9.x version of the application on the destination machine the items will be mapped to fit the registry paths and values for that version.

How to use variables to change registry data types across different versions of an application

The following example will convert a registry value stored as a string, and convert it to a number.

[8.x Settings]

Flag=Registry

Base=HKEY_CURRENT_USER\Software\MyApplication\Values\*.*

Values=<#VAR:002#>


Replace=Format
[9.x Settings]

Flag=Registry

Base= HKEY_CURRENT_USER\Software\MyApplication\Values\*.*

Values=<#VAR:002#>

Replace=Format

[0 Variables]

[0 Variables 8.x]

Flag=Variables

Base=<#VAR:001#>

Values=REG_SZ

[0 Variables 9.x]

Flag=Variables

Base=<#VAR:001#>

Values=REG_DWORD

In the above example, version 8 of the application stores some of its settings under the specified key in string (REG_SZ) data format and version 9 of the application stores the same settings as a number (REG_DWORD) data format.

Notes

Replace=Format flag should be specified at the bottom of the path items where the intention is to change the format.

Base of these path items should completely point to the registry key as Values is used to specify the variable that will be resolved to the data type specified in the variables section.

PC Transplant supports the following conversions of data format:

REG_SZ to REG_DWORD

REG_SZ to REG_BINARY

REG_SZ to REG_EXPAND_SZ

REG_BINARY to REG_DWORD

Replace=Format should be used with caution. Use it only after studying the data formats of different application versions.

Replace=Flag flag is applicable only to Registry path items.

For additional examples, see the [8.x Settings] and [0 Variables] sections in the MS Project.A2i.


Adding comments in the settings files
You can now add comments in the settings files. The comment line must be preceded by a semicolon “;” and must always start in a new line.

The best place to reference for understanding variables can be found in the A2i files created for PC Transplant. Examples using variables, include the Word.A2i, Excel.A2i, as well as many others. You can also define variables in the A2i Builder that ships with PC Transplant.

Template File FormatA personality build template file (.pbt) is a simple text file that follows Microsoft’s Windows INI file format. This section includes the following topics:

General File Format (page 123)

Personality Build Template Sections (page 123)

General File FormatAn INI file is broken down into three parts: section name, key name, and value. Example:

[My Section]



[Another Section]




(etc.)

Personality Build Template SectionsA Personality Build Template (.pbt) file consists of five sections: Desktop, Network, Applications, Files, and Options. Under each section are keys that define items within that section. Key names are similar to items found in the wizard. A key name is case sensitive, and its assigned value can be one of the following:

Turned on or off by setting the value to 0 or 1. Example: Control Panel=1

A value that defines an option. Example: Replace Files=2 (Always replace files)

Defined using a string. Example: Exclude Files=“pagefile.sys”,“ntuser.dat”


Desktop, Network, and Applications Settings SectionsThe first three sections in a .PBT file correspond to the wizard’s Desktop, Network, and Applications settings. The keys defined under each section are the same as the names defined in the dsktp*.ini, ntwrk*.ini, and *.a2i files and correspond to what items are displayed by the wizard. A key name in a template file must match the name defined in the setting file or the key will be ignored. If a setting is nested below another setting, a full path will need to be included to define it. Items within a path are separated using the characters ‘>’.
The example below shows a description of correct and incorrect settings defined.

[Desktop]

Windows Shell=1 ;selects the Windows Shell setting and everything underneath it

Display Properties > Appearance > Colors=1

control panel=1 ;error - case sensitive

(Control Panel)

[Network]

Window drive Mapping=1;selects all mapped drives

Window drive Mapping > W: (\\pulp\documents)=1 ;captures drive W:, if the user has it mapped to \\pulp\documents

[Applications]

ICQ > Buddy List and Preferences=1

Microsoft FrontPage Editor > Settings=1

MS Access > Associated Files > MDB Files=1 ;error – version number is missing (2000)

MS Access 2000 > Auto Correct File=1

MS Access 2000 > Custom Dictionary=1

NoteTo select all or none of the desktop, network, or application settings use the All tag, and set its value to 1 or 0. Example: [Applications] All=1


Files SectionThe files section is used to define files, folders, file types, and exclusions (filters). Any file specified under Files and Folder override any file excluded under Exclude File, Exclude Folder, and Exclude keys. Each of these keys may include one or more values that describe a path or filename. To support long file names, paths and files should be contained inside of quotes. If a value must include more than one path or file, each item must be separated by a comma. The template file also supports the use of environment variables, which provides flexibility in the paths that can be defined under different operating systems.
Files

A key defining one or more files to be included for migration. Example:

Files=”F:\Builds\Wizard\CuteFTP.a2i”,

“F:\Builds\Wizard\Wz1070\default.bmp”,

"C:\Builds\Wizard\default.pbt"|Filter=0:|DestPath=1:c:\NewDestination|Date=1:0:0:6:15:20\9\2001:20\9\2001|Size=1:0:50|RetainDir=0|

The example uses the advanced options to define special handling options for the requested file. This will be discussed in the Files, Folders, and File Types Advanced section that follows.

Folder

A key defining one or more folders to be included for migration. Example:

Folder=”%MI_PERSONAL%”,”%MI_SENDTO%”,”%MI_STARTMENU%”,

“%MI_ALLUSERS_STARTMENU%”,”D:\shared”,”D:\Install”,

“C:\DlgTest”|Filter=1:*.doc|DestPath=1:c:\MyDocs|Date=0:0:0:6:15:20\9\2001:20\9\2001|Size=0:0:50|RetainDir=0|

The last example uses the advanced options to define special handling options for the requested directory. The special handling options can also be created using the Template Builder. In the example above all *.doc files found under C:\DlgTest and its subfolders will be collected, and moved to a c:\MyDocs folder. This will be discussed in the Files, Folders, and File Types Advanced section that follows.

File Types

A key defining one or more file types to be included for migration. A file type consists of a description, followed by the wildcard extension in parenthesis. If a file type is to be routed to a new destination, the value of the file type will also include a pipe (|) character followed by a path of the new destination. Example:

File Types=”a2b music (*.mes)”|”c:\mymusic”,”A2I File (*.a2i)”,”Address Book File (*.wab)”|”c:\myaddressbook”,

"a2b music(*.mes)"|Filter=0:|DestPath=1:C:\Music|

Date=0:0:0:6:15:20\9\2001:20\9\2001|Size=0:0:50|RetainDir=0|


The last example uses the advanced options to define special handling options for the requested file type. In the example above, all *.mes files found will be collected and moved to a C:\Music folder. For more information, see Files, Folders, and File Types Advanced on page 126.

Files, Folders, and File Types Advanced

Some files, folders, or file types may require special handling. Using Advanced options, such as new folder destinations, or filtering options, you can create a script that can describe how and if a file should be collected. These advanced options correspond to the options presented to the user when adding a file, directory, or file type in the PC Transplant Wizard. Supported Advanced options include: file names using wildcards, specifying new folder destinations, file dates, file sizes, and directory structure.

These advanced options can be created in the PC Transplant Wizard, or can be created by hand by editing your template file. The Advanced options are found after a file, folder, or file type, and follow the syntax:

|File Option|New Destination Option|Date Option|Size Option|Retain Directory Structure Option|

Each of these options will be described below:

File Option. Defines the name of the file you are interested in collecting. This option is only valid when working with folders. The syntax for using the File Option is

Filter=0 or 1(on or off);0 is the only valid value when used with Files

Example:

|Filter=0|

New Destination Option. Defines a new folder for the file collected. The syntax for using the New Destination Option is

DestPath=0 or 1 (Off or On):folder path

0 or 1 turns this feature off or on. The folder path represents a new path for the collected file.

Example:

|DestPath=0:|

|DestPath=1:c:\NewDestination|

Retain Directory Structure option. The Retain directory structure option will be stored in the template file, as part of the File Types key name. For each element listed under File Types, an element called RetainDir will be added. The value after the equal sign will determine if the option is on or off. Example:

File Types=”Adobe Acrobat Document (*.pdf)”|Filter=0:|


DestPath=1:C:\PDFFiles|Date=0:0:0:6:15:22\8\2001:22\8\2001|
Size=0:0:50|RetainDir=1|

Date Option. A file must meet the date criteria specified by this option in order for it to be collected. The syntax for using the Date Option is as follows:

Date=0 or 1(Off or On):0, 1 or 2(created, last accessed, modified):0, 1, or 2(last month, day, or date range):months:days:startdate:enddate

0 or 1 turns this feature off or on. Months, days, and start and end dates are only valid when used with the previous identifier. Dates follow the syntax day\month\year (such as 20\1\2001).

Example:

|Date=0:0:0:6:15:20\9\2001:20\9\2001| ;off

|Date=1:0:0:6:15:20\9\2001:20\9\2001| ;created in the last 6 months

|Date=1:1:0:6:15:20\9\2001:20\9\2001| ;last accessed in the last 6 months

|Date=1:2:0:6:15:20\9\2001:20\9\2001| ;modified in the last 6 months

|Date=1:0:1:6:15:20\9\2001:20\9\2001| ;created in the last 15 days

|Date=1:0:2:6:15:20\9\2001:21\9\2001| ;created between Sept. 20-21, 2001

Size Option. A file must meet the size criteria specified by this option in order for it to be collected. The syntax for using the Size Option is

Size=0 or 1(Off or On):0 or 1(at least, at most):nn(size in KB)

0 or 1 turns this feature off or on.

Example:

|Size=0:0:50| ;off

|Size=1:0:50| ;at least 50 KB

|Size=1:1:40| ;at most 40 KB

Exclude Files

A key defining one or more files to be excluded for migration. Example:

Exclude Files=”pagefile.sys”,”ntuser.dat”


Exclude Folder
A key defining one or more folders to be excluded for migration. Example:

Exclude Folder=”%MI_CACHE%”,”%MI_WINDIR%\Profiles\

ADMINI~1\LOCALS~1\Temp”

Exclude

A key defining one or more drives to be excluded for migration. Example:

Exclude=”C:\”,”E:\”

Options

The Options section defines any build, run, or install visual options supported by a package. The sections below describe these different options and their possible values.

Replace Files

Describes how to replace files during migration. Example:

Replace Files=0 (Older Files)

Replace Files=2 (Always Replace)

Replace Files=3 (Never Replace)

PromptOnReplace

Determines whether the user should be prompted to replace a file. Example:

PromptOnReplace=0 (no)

PromptOnReplace=1 (yes)

Reboot after Transplant

Determines if the PC should reboot after the migration is complete. Example:

Reboot after Transplant=0 (no)

Reboot after Transplant=1 (yes)

Description

User defined description of the package. Example:

Description=”Migrate settings and files”

Title

User defined title of the package. Example:

Title=”Personality package”


Splash

A string defining the full path of the splash screen bitmap that is displayed when the user runs the package. Example:

Splash=”F:\Builds\Wizard\Wz1070\default.bmp”

Splash Layout

Identifies the layout of the splash screen. Example:

Splash Layout=0 (Upper Left)

Splash Layout=1 (Tile)

Splash Layout=2 (Stretch)

Enable Undo

Determines if Undo is supported by the Package. Example:

Enable Undo=0 (no)

Enable Undo=1 (yes)

Abort Type

Determines when to abort the execution of a Package during insufficient disk space constraints.

Abort Type=0 (Abort Entire Installation)

Abort Type=1 (Delete Undo Only)

Span Size

Determines the maximum size of a package before it creates another span file. This may be valuable if you are moving the Personality Package later to media type that has a maximum size limitation, such as CD.

Example:

Span Size=650000000

Cleanup

If set, this option will instruct the PC Transplant Wizard to create a cleanup package, using the files added to a Personality Package. Once completed, a shortcut will be created and placed on the user’s desktop. Example:

Cleanup=0 (no)

Cleanup=1 (yes)


Filter Settings Files

Filters like exclude file, exclude folder, and exclude drive are by default applied to all files. There may be cases where a migration may not want filters applied to settings like Desktop, Network, and Application. By using the Filter Settings File option, you can enable or disable this feature.

Filter Settings Files=0 (no)

Filter Settings Files=1 (yes)

Security

Determines if the security information for files or folders must be migrated or not. It can also be used to set read rights to all the parent folders of the migrated file or folder. This can be cleared during the package execution.

Security=0: No Security

Security=1: Migrate security permissions

Security=2: Migrate security permissions and Propagate read permissions to parent

No compression

Files listed with this option are not compressed while creating personality packages and also during real-time migration.

NoCompress=”(*.zip)”,”(*.mp3)”,”(*.jpeg)”,”(*.cab)”,”(*.jpg)”,”(*.wma)”,”(*.mpeg)”,

Locale

Locale=EN : Language ID for the language of system on which pbt was created.

TroubleshootingStoring a Personality Package onto removable media with less than 10MB of free disk space is not recommended. If disk space is limited, you can span a Personality Package across multiple disks. If you take this approach, expect to do some disk swapping.

To run PC Transplant on Windows, we recommend that your user be a member of the Administrator group.

If you are a member of a Windows Domain and migrating a Windows computer name or recreating the Domain Computer account, then while logging on to the Domain after the migration, you might receive the following error: “The trust relationship between this workstation and the primary domain failed.”


Cause: The computer account has the incorrect role or its password has mismatched with that of the domain database.
Solution: Log on to the workstation only (Administrative rights required). Change the network membership to be a member of a Workgroup. Restart the computer and log on to the workstation as a member of that Workgroup. Change the network membership back to Domain and restart.

Turn off the migration of security permissions to improve the performance.

When migrating the Outlook settings, it may appear as though settings and personal folders were not migrated for a given user account.

Cause: This can occur if the profile account used on the source computer is not used when logging on to Outlook on the destination.

Solution: Please ensure that you are using the same account.

This problem can also occur if your system administrator has defined a Microsoft profile file to be used when Outlook is executed. A Microsoft Profile File or PRF is used by Microsoft to configure a user's profile and settings. An administrator can cause these to be run automatically when Outlook executes.

This can be accomplished by passing a /importprf to the outlook.exe. It can also be done by setting the ImportPRF registry value under Microsoft's Outlook\Setup key.


Index

AA2i Builder 72

INI file support 118A2i builder 72A2i Editor 75

menu functions 75A2i File Updates 23, 69A2i files

creating, editing 72editing 75submitting 74

A2I format 8, 9, 110Abort Type key 129Access 12Admin value 107Adobe 12Altiris test site 74AOL 12application

Access 12Approach 12Eudora 12Excel 12Exchange 12Fastsite 12Freelance 12FrontPage 12Instant Messenger 12Internet Explorer 12MSN Messenger 12Navigator 12NetMeeting 12Norton AntiVirus 12Notes 12Outlook 12Outlook Express 12Pager 12PC Anywhere 12Photoshop 12PowerPoint 12Presentation 12Publisher 12Quattro Pro 12RealJukebox 12RealPlayer 12ScreenCam 12settings 11Smart Center 12Virus Scan 12WinZip 12Word 12WordPerfect 12WordPro 12

application settings 23, 68application to information format 8, 9, 110Approach 12

Bbandwidth 26build templates 20

Ccommand line

switches 25command-line options 25command-line switches 49company

Adobe 12AOL 12Corel 12Lotus 12Microsoft 12Netscape 12Network Associates 12Novell 12Qualcomm 12RealAudio 12Symantec 12WinZip 12Yahoo 12

Compatibility value 104computer

synchronizing 7, 7upgrades 6, 6

computer name 22, 48, 67Corel 12creating a Personality Package 15

DDeleteKeyBeforeMigrating value 107Description key 128desktop settings 9, 21, 67, 79

settingsdesktop 79

DestOS value 103disconnected users 18, 47documentation 14

PC Transplant 14domain name 22, 48, 67

Eeditor 70

A2i 75

PC Transplant Package Editor 70Enable Undo key 129environment variables 97Eudora 12Excel 12Exchange 12exclude files 24Exclude Files key 127Exclude Folder key 128Exclude key 128Exclude value 102ExcludeFilePaths value 109exit values 42, 61

FFastsite 12features

A2I Builder 9Application Install

Administrator 8new in release 6.5 13PC Transplant Package Editor 9PC Transplant Wizard 7Personality Package 8Personality Template Builder 9real-time destination agent 8real-time migration 8

file format 79file types 77File Types key 125files

include, exclude 24format

A2I 8, 9, 110Freelance 12FrontPage 12

GGroupWise application

GroupWise 12

Iinclude files 24INI file support 118Instant Messenger 12Internet Explorer 12introduction

PC Transplant 6item setting properties 101


Kkeys 125
LLogError value 101Lotus 12

MMI_ALLUSERS_DESKTOP variable 98MI_ALLUSERS_STARTMENU variable 98MI_APPDATA variable 98, 99MI_APPDIR variable 98MI_BASEAPPDIR variable 98MI_CACHE variable 98MI_COMPUTERNAME variable 98MI_COOKIES variable 98MI_DESKTOP variable 98MI_FAVORITES variable 98MI_FONTS variable 98MI_LOCALAPPDATA variable 98MI_PERSONAL variable 98MI_PROGRAMFILESDIR variable 99MI_SENDTO variable 99MI_STARTMENU variable 99MI_SYSTEM variable 99MI_USER variable 99MI_WINDIR variable 99Microsoft 12MSN Messenger 12Multiple NIC Support 22, 67

NNavigator 12NetMeeting 12Netscape 12Network Associates 12network settings 11, 21, 67, 79, 80new features 13NICs, support of multiple 22, 67Norton AntiVirus 12Notes 12Novell 12

Ooperating system

upgrades 6Options key 128Organizer application

Organizer 12orphan accounts 18orphan user accounts 40, 60Outlook 12

Outlook Express 12

PPackage Contents Tool 42package viewing contents 42packages

command-line switches 49editing 70installing 45

Pager 12PC Anywhere 12PC settings 66PC Transplant

features and benefits 7introduction 6

PC Transplant Package Editor 70menu functions 70

PC Transplant Wizard 7PCT Package Contents Tool 42permissions 20personality

back up 7build templates 20restore 7

Personality Package 6creating 15running 45

Photoshop 12PowerPoint 12predefined templates 20Presentation 12PromptOnReplace key 128Publisher 12

QQualcomm 12Quattro Pro 12

RRealAudio 12RealJukebox 12RealPlayer 12real-time migration 8Reboot after Transplant key 128Reboot value 102Replace Files key 128Replace value 104reset status 34resource

sharing 7running a Personality Package 45

SScreenCam 12security

of transplanted files 19permissions 20

settingtags 81

settings 101application 11desktop 9network 11, 80PC 66transplantable 9

settings options 16, 46sharing resources 7Smart Center 12Splash key 129Splash Layout key 129switches

command line 25Symantec 12synchronizing multiple computers 7

Ttags 81template builder 66template settings options 66Title key 128transplantable settings 9

UUAC 33, 34, 56, 57upgrading computers 6upgrading operating systems 6User Account Control 33, 34, 56, 57user accounts

orphan 40user map file 19, 47

sample 19, 47user priority 41

Vvalue

exit 42, 61values 99variables

environment 97viewing package contents 42Virus Scan 12Vista 33, 34, 56, 57

WWinZip 12, 12wizard

command-line options 25Word 12WordPerfect 12WordPro 12


YYahoo 12