1. Application should be installed quietly from the command line on a Windows Vista computer.

Microsoft has provided guidelines to install applications on a Windows Vista computer.

According to Microsoft guidelines, you can install an application in the quiet mode on a Windows Vista computer using the Msiexec /I <Application installer package>.msi /qn FASTOEM=1 command line.

However, PC Transplant installation fails if you use the FASTOEM=1 command line. So, use the following command line to run PC Transplant in the quiet mode by running the command prompt as an administrator.

PCTSetup.exe /qn INSTALLDIR="<install location>"

Example:
C:\Folder>PCTSetup.exe /qn INSTALLDIR="C:\Program Files\Altiris\PCT"

When you use this command line, the Altiris PC Transplant 6.8 dialog appears. You have to select the installation language for PC Transplant on this dialog. After you have selected the language, the setup continues in a quiet mode.

You can use the following command line to view the confirmation dialog at the end of installation. A message appears on the confirmation dialog telling you whether the installation was successful.

PCTSetup.exe /qn+ INSTALLDIR="<install location>"

Example:
PCTSetup.exe /qn+ INSTALLDIR="C:\Program Files\Altiris\PCT"

1. Some settings on the Deploy Options page of PCTWiz and Template Builder are not restored to the default values.

The settings on the Deploy Options page in the following two scenarios are not restored to the default values.

Scenario I:

1. Run PCTWiz.exe.
   The Welcome to PC Transplant page appears.
2. Click Next.
3. On the Select a Migration Template page, select Common Predefined Templates and default.pbt and click Next.
4. On the Transplant Multiple Users page, select the required users and click Next.
5. On the Transplant PC’s Settings page, select the Desktop, Network, and Applications settings and click Next.
6. On the Transplant Source PC’s Files and Folders page, select the Files, Folders, and File Types and click Next.
7. On the Capture Options page, select the appropriate options and click Next.
8. On the Deploy Options page, select the Run Personality Package in quiet mode and Run minimized options.
9. In the Run/Edit Password field, specify a password and confirm it in the Confirm Password field.
10. Click Back and return to the Welcome to PC Transplant page.
11. Repeat the steps to reach the Deploy Options page.
    The default settings for the Run Personality Package in quiet mode, Run minimized, and the Run/Edit Password options are not restored.

Scenario II:

1. Run the Template Builder.
   The Welcome to the PC Transplant Template Builder page appears.
2. Click Next.
3. On the Select a Migration Template page, select Common Predefined Templates and default.pbt and click Next.
4. On the Transplant Multiple Users page, select the required users and click Next.
5. On the Transplant PC’s Settings page, select the Desktop, Network, and Applications settings and click Next.
6. On the Transplant Source PC’s Files and Folders page, select the Files, Folders, and File Types and click Next.
7. On the Capture Options page, select the appropriate options and click Next.
8. On the Deploy Options page, select the Run Personality Package in quiet mode and Run minimized options.
9. Click Back and return to the Welcome to PC Transplant Template Builder page.
10. Repeat the steps to reach the Deploy Options page.
    The default settings for Run Personality Package in quiet mode and Run minimized are not restored.

2. Running A2i Builder on a Japanese Windows XP and 2000 Operating System

If you run A2i Builder on a Japanese Windows XP and 2000 operating system, a blue dump screen appears and the computer restarts.

3. Running WinVNC and Launching PC Transplant Wizard

If you run WinVNC in App Mode on a Windows 98 computer and launch the PC Transplant Wizard on this computer, a “Another instance of WinVNC is already running” message appears during the package creation.

Note: Similar messages may appear for other applications too.

4. PCT Package Settings Tab

The PCT Package Settings tab is not displayed on Windows 9x and Windows NT 4.0 operating systems.

5. Application Migration Limitations

1. AOL

AOL stores the application and user settings in a proprietary file (main.idx.) As changes cannot be made to this file, the following limitations apply:

• PC Transplant does not migrate the main.idx setting file from AOL 6.0 to 7.0. AOL 7.0 cannot read a 6.0 main.idx file correctly. Because this file is not migrated, most settings are not transferred.
• AOL passwords cannot be migrated from one computer to another because AOL locks the passwords on the original installed computer.
• The download directory for Web files cannot be modified to match the destination computer folder path. The folder path is contained in the main.idx file, which cannot be modified.
• AOL Media Player as Default CD Player setting is not migrated. This setting is connected to operating system file type associations.

2. AT&T Global Network

PC Transplant supports the migration of the entire AT&T Global Network application. If you migrate it to a different installation path, the AT&T install.log file will not contain a valid path and you cannot fully uninstall the application on the destination computer using the Control Panel - Add/Remove Programs tool. However, you can uninstall it using the PC Transplant Undo package.

3. ICQ versions 4a to 4b

PC Transplant cannot migrate settings across 4a and 4b version types. PC Transplant can translate settings between applications that follow a standard major and minor version number release, that is 4.1 to 4.2. In the case of these two ICQ applications, they are only distinguished by build numbers, that is 4.1.1.132 and 4.1.1.165, but they still require translation.

4. Lotus Notes

PC Transplant may not migrate a signature if the signature is referenced in Lotus Notes as a separate file (such as a bitmap file). A reference to the location of the signature file is kept in the proprietary file format of Lotus Notes. PC Transplant cannot interprete this file.

Additionally, if the destination computer has Lotus Notes 6 installed for multiple users, PC Transplant does not support migration between version 4 and 6 and version 5 and 6.

While migrating Lotus Notes 6.5, if "Multi-User Installation" is carried out on the source computer and "Single User Installation" is carried out on the destination computer, then the user last processed has the settings migrated. The file settings of the other users are overwritten because the user data is stored on a central location.

5. McAfee

To migrate the McAfee antivirus settings, PC Transplant must stop the McAfee service. PC Transplant cannot stop this service if it is run under a limited user context. This limits PC Transplant from migrating McAfee settings.

6. Microsoft Access 97 to Microsoft Access 2000/2002

PC Transplant cannot migrate the New Database sort order settings from Microsoft Access 97 to Microsoft Access 2000/2002. The data value for this setting is modified between these versions and cannot be converted.

7. Microsoft Access XP to Access 2003

PC Transplant cannot migrate the following settings:

• Tools > Options > Advanced > Command-line arguments
• Tools > Options > International > Use Hijri Calender

8. Microsoft Internet Explorer

• The migrated settings of Microsoft Internet Explorer cannot be loaded on a destination computer until the destination computer connects successfully to the Internet.
• Internet Program selections - PC Transplant does not support the migration of the Internet Programs page. The setting may become unusable if the application contained in the setting is not installed or resides under a different path. There is no way to locate the executable in case of this event.
• PC Transplant cannot migrate the temporary Internet cache size from Windows 95 and 98 to Windows ME\NT4.0\2000\XP. Windows 95 and 98 are not consistent in their cache size definitions.
• Explorer and Internet Explorer Status Bar - PC Transplant cannot migrate the Status Bar settings. The details on how different versions store this data are not known.
• The settings for the Content Advisor cannot be migrated from Internet Explorer 5.0 to 6.0. The storage types used between these two versions are not compatible.
• The migration of the selection of the Internet Programs associated with the HTML Editor, E-Mail, Newsgroups, Internet Call, Calendar, and Contact list are not supported.

9. Microsoft Office 97

The Auto Correct and Taskbar settings in Microsoft Office 97 may not migrate to a non-profile Windows 9x computer with Microsoft Office 07. The settings for these options are migrated, but in some cases Microsoft Office 97 removes these migrated settings if they did not already exist.
The solution for this problem is to run the Microsoft Office 97 application, select these two features, and migrate the Microsoft Office 97 settings again.

10. Microsoft Office 2000 to Microsoft Office XP

Microsoft Office toolbars are not migrated from Office 2000 to Microsoft XP because the Office 2000 ppt.pcb file is incompatible with Office XP.

11. Microsoft Outlook and Outlook Express

• Due to the change in the setting name from “MS Outlook POP - IMAP accounts” in PC Transplant 3.6 to “Accounts - POP-IMAP” in 4.0 and later, PC Transplant 4.0 and later does not recognize the setting selection from a PC Transplant 3.6 template file.
• PC Transplant does not migrate the Time Zone setting in Microsoft Outlook. This is an operating system related setting and not an application setting. To migrate the Time Zone setting, use the Desktop > Regional Settings options in PC Transplant.
• Outlook Express 4.x to 5.x - Due to current limitations, PC Transplant currently cannot migrate settings from Outlook Express 4.x to 5.x. Settings stored under the 4.x application’s registry have been moved to a dynamically created user account area for 5.x. This dynamic location currently makes it impossible for PC Transplant to migrate 4.x settings to 5.x.
• Outlook Express 4.x to 5.x - PC Transplant cannot migrate the Outlook Express 4.0 mailbox to Outlook Express 5.0. Outlook Express 4.0 mailbox files (.IDX, .MBX, and .NCH) are no longer used in Outlook Express 5.0, which now uses a .DBX file. You must use the Outlook Express 5.0 Import Wizard to convert a 4.0 mailbox file to 5.0.
• If you are migrating the Account information with Outlook, the same service (Exchange, Internet, and so on) must exist at the destination. If the destination Outlook is new and does not have any services installed, follow these steps: 1) Transfer the Personality Package to the destination computer; 2) Run Outlook; 3) The Startup Wizard will prompt you for the service you are using. If your source Outlook was using the Internet, select the Internet option. If you are using Exchange, select the Workgroup option. Outlook will recognize that you already have a profile setup for that service and will take you directly into Outlook. If you are using Exchange and Offline Storage, your Offline Storage files (.ost) may not be synchronized with the server. If this is the case, Outlook asks you to delete these files so they can be re-created.
• Migrating Outlook 2003 to Outlook 2003 can give error because Outlook searches for vpmsece.dll in the extend.dat file. The location of the vpmsece.dll file could change due to one of the following reasons:
  • Uninstalling Norton AntiVirus Corporate Edition, and installing Symantec AntiVirus Corporate Edition.
  • Upgrading Norton AntiVirus Corporate Edition to Symantec AntiVirus Corporate Edition.
  • Upgrading Symantec AntiVirus Corporate Edition to a newer version of Symantec Corporate Edition.

  If Outlook is migrated when any of the earlier three installations are performed before or after migration, Outlook displays a message "The add-in "C:\Program File\NavNt\vpmsece.dll" could not be installed or loaded." This problem can be resolved by using Detect and Repair on the Help menu, which migrates all the settings properly and also does not affect the migration of settings. When the user clicks Detect and Repair on the Help menu, extend.dat file gets updated internally. This problem is not reproduced when Norton or Symantec AntiVirus is installed or uninstalled multiple times.

  A solution for this problem is to identify whether Norton or Symantec AntiVirus is installed or un-installed multiple times during the migration of Outlook settings. If you are sure that Norton/Symantec AntiVirus is installed/un-installed multiple times, you can delete the extend.dat file, and Outlook re-creates this file when it is run next time.

  More information about the same can be found at http://service1.symantec.com/SUPPORT/ent-security.nsf/pfdocs/2002090613375148?Open&dtype=corp. This problem is also fixed in the latest version of Symantec AntiVirus Corporate Edition (Symantec Antivirus Corporate Edition 8.1.1 MR6).

12. Microsoft PowerPoint 97 to Microsoft PowerPoint 2000/2002

PC Transplant cannot migrate the Save PowerPoint file as setting from Microsoft PowerPoint 97 to Microsoft PowerPoint 2000/2002. Microsoft stores this setting using a different format between these versions that cannot be converted.

13. Microsoft PowerPoint XP to Microsoft PowerPoint 2003

PC Transplant cannot migrate Toolbars from Microsoft PowerPoint XP to PowerPoint 2003.

14. Microsoft Word 97 to Microsoft Word 2000/2002

PC Transplant cannot migrate “Fast Save” and “Background repagination” settings from Microsoft Word 97 to Microsoft Word 2000/2002. The binary data that Microsoft Word uses to store these settings is not compatible across different versions.

15. Microsoft Word 97 to Microsoft Word 2000/XP

If the logged on user at the destination computer does not have administrative rights, PC Transplant cannot migrate most of the settings from Microsoft Word 97 to Microsoft Word 2000/XP.

16. Microsoft Word 2000 to Microsoft XP

If the logged on user at the destination computer does not have administrative rights, PC Transplant cannot migrate most of the settings from Microsoft 2000 to Microsoft Word XP.

17. Microsoft Word 2000 to Microsoft Word 2003

PC Transplant cannot migrate the following settings from Microsoft Word 2000 to Microsoft Word 2003:

• Tools > Options > General > Navigation Keys for WordPerfect users
• Tools > Customize > Options > Show Standard and Formatting toolbars on two rows
• Tools > Customize > Toolbars > Toolbars

The binary data that Word uses to store these settings is not compatible across different versions.

18. Microsoft Word XP to Microsoft Word 2003

PC Transplant cannot migrate the following settings from Microsoft Word XP to Microsoft Word 2003:

• Global Macros
• Tools > Options > View > Smart tags
• Tools > Options > General > Navigation Keys for WordPerfect users
• Tools > Customize > Options > Show Standard and Formatting toolbars on two rows
• Tools > Customize > Toolbars > Toolbars

The binary data that Microsoft Word uses to store these settings is not compatible across different versions.

19. Netscape

Only POP account profiles can be migrated. IMAP account profiles cannot be migrated. Some settings do not migrate if the path of Netscape differs at source and destination computers. PC Transplant does not recognize the Netscape versions 7.0 and later.

20. pcAnywhere

Version 9.0 to 10 - Hosts, remotes, and file transfer items and their properties are not migrated from pcAnywhere 9.0 to pcAnywhere 10.0. The .BCF files in which the settings are stored have inconsistent format across these two versions of pcAnywhere and cannot be translated.

21. WordPerfect

Version 8 to 9 - PC Transplant cannot migrate custom toolbar settings from WordPerfect 8 to WordPerfect 9. The binary data WordPerfect uses to store these settings is not compatible across different versions.

22. Symantec ACT

If redirection of files, database, and file types is done during migration, then the layouts are not migrated. This is applicable for same and cross version migration.

• Custom menus are not migrated from ACT 4.0 to ACT 2000.
• Keyboard shortcuts and custom commands are not migrated from ACT 4.0 to ACT 2000.

23. Eudora

After migrating Eudora 4.0 to Eudora 5.1, the same settings are applied to all profiles.

24. Pagemaker 7.0

Paths for "Download to folder" and "Web browser" in online preferences are not resolved. The path of the source computer is migrated to the destination computer.

25. Microsoft Project 98 to Microsoft Project 2000

PC Transplant cannot migrate the Options > Spelling setting from Microsoft Project 98 to Microsoft Project 2000.

26. Norton AntiVirus Desktop Edition

PC Transplant does not support cross version migrations.

27. WinZip

The Option > Configuration > System > Associate WinZip with archives setting is migrated only if it is selected on the source computer.

The following settings are not migrating for Winzip:

• Options > Configuration > System > Include WinZip Quick Pick in the taskbar tray
• Options > Configuration > System > Include Winzip in the start menu

6. Desktop Settings Migration Limitations

1. Control Panel

Keyboard Settings

Keyboard language settings do not migrate across different platforms. Keyboard language files are platform specific. Windows NT uses .DLL files, where as Windows 95 and Windows 98 use .KBD files. Because transferring the language files could affect the integrity of the operating system, we have opted not to migrate the settings. If you are transferring a language file to a similar operating system, the language setting and language file can be migrated by editing the Personality file and adding the following registry settings (add everything under the following key):

HKEY_CURRENT_USER\ Keyboard Layout\ Preload

Use the Values stored under the “Preload” key, 1 through n. Use the Value as a reference and lookup the Keyboard filename specified under HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Control\ Keyboard Layouts\ <value>\ Layout file.
Example: if the US English keyboard is selected, the value Preload\ 1 will be 0000409. Going to the HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Control\ Keyboard Layouts\ 0000409\ Layout file under 95/98 shows kbdus.kbd. Copy this file from your Windows directory into your Personality file.

Mouse Settings

All the mouse settings are not migrated. PC Transplant supports the migration of only the standard mouse settings and does not migrate manufacturer-specific mouse settings.

Printer Property Tabs

Some printer specific property tabs are not available when migrating a printer from Windows ME to Windows ME. We currently have seen this only with the “Color Management” tab when migrating an HP LaserJet 2100, but other printers can experience a similar problem.

Regional Settings

PC Transplant cannot migrate Time Zone settings from Windows 9x to NTx as the detail on how these two different operating system types store time zone information is not known.

Sound Settings

Sound settings are unique to the sound device installed on a computer and cannot be migrated. The location of these settings differs between manufactures of the devices. Sound schemes and Program events can be migrated along with their supporting files, as these are defined by the operating system.

2. Display Properties

PC Transplant has certain limitations in migrating the active desktop, appearance, background, and screen saver settings.

Fonts

PC Transplant cannot migrate font settings without administrative rights.

Wallpaper Settings

• Active Desktop wallpaper may not be visible after migrating to Windows XP. PC Transplant cannot turn on Active Desktop under Windows XP. Microsoft hopes to correct this in its final release.
• When migrating HTML wallpaper, the setting is migrated but in some instances Windows Explorer may replace the setting.

Screen Saver

• If you are trying to transfer a theme screen saver from a computer that has the Plus pack to a computer that does not have the Plus pack, it will not work. This is because the screen saver requires the Plus pack in order to function.
• Screen Savers may not work across different operating systems. This restriction is determined by the creator of the screen saver.
• Screen Saver options - PC Transplant can set the screen saver, as well as its time and password. Screen savers do not have a standard location where the settings are stored. The settings could be located in the registry, in the control.ini, in an .INI file of the screen savers, or in any other file. Some screen savers may need to have a custom .A2I file created for the screen savers.

3. Windows Shell

Desktop or Link Icon

If the icon of a link is tied to another file or executable that is different than the link, the supported icon files are not transferred.

Shortcut Links

• Icons - In some cases an icon associated with a shortcut link on a destination computer may not look the same as the one assigned on the source. These icons are defined using an index that is associated with a file. The manufacturer of that file may remove your icon or the index of your icon may shift to another index. PC Transplant can migrate the index, but it cannot fix the index in the case described.
• If a link is tied to a file that does not exist on the destination computer, the shortcut file can be created if you run the
  -unresolved command-line option with the package or the PC Transplant Wizard.
• The location of the icons to be placed on the desktop is not supported.

Taskbar Settings

• PC Transplant cannot migrate Taskbar settings under Windows 95, 98, and NT, due to registry limitations.
• Positioning of the taskbar is not supported.

7. Network Settings Migration Limitations

1. Computer Name and Domain Name

Password does not get validated for Windows 9x and Windows ME.

2. Network, TCP/IP Settings

Physically removing a network card from a computer will not keep the PC Transplant migration wizard from displaying the card under the Wizard’s Network, TCP/IP settings. The adapter must be removed from the Windows network adapter list.

3. Folder / Drive Share Assignments

File and Print Sharing must already be installed on the destination computer or a share will not migrate.

8. File, Directory, and File Type Migration Limitations

1. File Type Associations

PC Transplant does not migrate any custom application associations you have made to your existing file types. For example, if you have modified your Web pages (.HTM or .HTML files) to be associated with Netscape when opened, your association will need to be reset on your destination computer.

2. NTFS Encryption

PC Transplant does not support the migration of NTFS encrypted files. You need to turn off encryption prior to migration or the user will need to manually migrate these files.

3. Common Start Menu

If a template is being used on a Windows 9x computer, PC Transplant will resolve and capture the Common Start Menu folder only if the following value is present in the Windows 98 registry:

-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Shell Folders\Common Start Menu

The Common Start Menu folder is resolved to whatever path is present as the data for this value. This particular value may not always be present in the registry of Windows 9x computers. In the absence of this value, PC Transplant does not resolve the path of the Common Start Menu folder.

9. Real-time Migration Limitations

Unable to push the PCTRTDestAgent to a Windows XP computer that is a member of a Workgroup:

For PC Transplant to push the PCTRTDestAgent to another Windows NTx type computer, PC Transplant must be able to connect to the computer as an Administrator. Windows XP defines a local service that, by default, forces all accounts that connect to the computer to log on as Guest.

This is the default setting in Microsoft under a Workgroup environment. This problem does not exist for computers that are members of a domain. You will either need to run the PCTRTDestAgent manually on Windows XP Workgroup computers or change their security setting.

To change the security setting

1. Open your Local Security Settings by selecting Control Panel > Administrative Tools > Local Security Policy.
2. Under the Security Settings tree, select Local Policies > Security Options.
3. In the right pane, right-click Network Access: Sharing and Security Model for local accounts.
4. Select Properties.
5. Change the option from Guest only to Classic.

10. Migrating Profile Folders

If you want to migrate to profile folders, which reside on UNC paths, then you must map drives to those folders and make those paths the profile folder’s paths. Then use the -netdrives command-line option to perform such a migration.

Example: Consider a case where “Application Data” is mapped to the \\User\Shared folder on the destination computer. You must map the network drive to the \\User\Shared folder by selecting an appropriate drive letter (example: G drive) in the Map Network Drive option of Windows operating system. Make “Application Data” point to drive G instead of \\User\Shared and use command-line option -netdrives while migrating.

11. Spanning Media using Quiet Mode

When saving a Personality Package, PC Transplant supports spanning media. Normally, a user will be prompted to change the media as needed. However, when using the PC Transplant Wizard in quiet mode (using -q and -qm switches), it does not provide any user prompts, even in the case of needing to swap out a removable media disk. When using quiet mode, the media must have enough space to save the complete package.

12. Simulation Mode

PC Transplant cannot determine if a printer will install successfully in simulation mode. To provide this ability, the Package would need to install the printer, which would defeat the purpose of simulating an installation. PC Transplant cannot simulate for the applications, which are not installed on the destination computer but are selected for installation.

13. Issues with Installing Packages through a Service

1. Display Settings

When installing a package through a service, such as Altiris® Deployment Server™ or Microsoft SMS, if the computer is at the Windows NT/2000/XP logon screen, Display Settings cannot be migrated.

2. Network Printers

Network printers’ settings cannot be migrated when the package is run under the System user account. This can be resolved if the application running under the system account can run the package under a valid user context. Altiris Deployment Server and Altiris® Notification Server™ provide support to do this.

3. Mapped Drives

Mapped drives cannot be created if a Personality Package is run through a service. For example, Altiris Deployment Server or Microsoft SMS.

14. Error Opening Package

When building a package from a Windows 9x platform with a Uniform Naming Convention (UNC) path, you may get this error: Error occurred while opening personality.

Cause: There is more than one dot used in the folder name of the UNC path (example: \\server\folder.1.2\package.exe)

Resolution: On Windows 9x platforms, do not use folder paths that include more than one dot.

15. File Size of Edited Packages

When a Personality Package is edited, the changes are appended to the existing file, thus making the package file larger in size with each edit.

16. Printer Settings

1. Printer Support

• If the destination computer is a NT4 computer, and if you directly provide an .INF file path, which is of a new dynamic OS platform format, then PC Transplant cannot migrate the printer. Note: If the destination computer is 2K or XP, then the printers are migrated.
• If you provide a global .INF path using the –printer command-line option, then PC Transplant finds the appropriate .INF file for each available printer. If any of the .INF file is of a new dynamic OS platform format, which is required for a particular printer, then PC Transplant cannot map the file to that printer.

To determine if your printer’s .INF file uses this format, open the .INF file in a text editor and look under the Manufacturer section. If multiple definitions provided after the equals sign are separated by commas, the .INF file supports dynamic OS platforms (that is, %HP%=HP,NTx86.5.1).

To change your .INF file to support a specific OS platform, modify the manufacture value to only include one platform (that is, %HP%=HP).

2. Security Permissions

In Windows NT/2000/XP, network printer security permissions are not migrated. Example: Print, Manage Printers, Manage Documents, and so on.

3. Migrating PDF Printers

PDF printers are not migrated properly because the printer includes a conversion utility that is not supported by PC Transplant. If you try to migrate the PDF printer, the destination PDF printer will be unstable.

17. International Versions of PC Transplant

1. Microsoft Screen Savers

PC Transplant cannot migrate a Microsoft Windows 9x screen saver to Windows NTx when run under an international version of the operating system. The file names under Windows 9x have different file names than those used with NTx. PC Transplant cannot translate the English file names from those unlike platforms. The international versions of the operating systems change these file names and break the automatic mapping.

2. Microsoft Outlook 2000 French

In some cases, PC Transplant may not be able to migrate a user's Outlook settings if Outlook contains multiple user profiles. This occurs because Outlook French fails to match the default profile's name with its setting definition, making it impossible to locate. Microsoft has corrected this in Outlook XP.

18. Application Installation

If you use the standard support provided by PC Transplant for silent application installation, some applications will be installed in the path predefined in the .ISS files. If required, you can change the default path. The Serial Key for some applications also needs to be specified in the .ISS file to complete the installation. You can also specify the name of your organization in the .ISS file.

Note: The keys that specify the installation path are mentioned in the Keys to specify (Optional) column.

The following keys for the applications have to be specified in the .ISS file:

Application	File Name	Keys to Specify (Mandatory)	Keys to Specify (Optional)
Adobe Acrobat 3	AdobeAcrobat3.iss	-	SzDir
Adobe Acrobat 4	AdobeAcrobat4.iss	-	SzDir
Adobe Acrobat 5	AdobeAcrobat5.iss	-	SzDir
Adobe PageMaker 7	AdobePage7.iss	FirstName, SerialNumber, and Company	SzDir
Adobe Photoshop 5	AdobePhotoshop5.iss	FirstName, SerialNumber, and Company	SzDir
Adobe Photoshop 6	AdobePhotoshop6.iss	FirstName, SerialNumber, and Company	SzDir
Eudora 5	Eudora5.iss	-	SzDir
Lotus Office Release 9	Instsuit.rsp	UserName and CompanyName	-
Netscape 4	Netscape4.iss	-	SzDir
WinFaxPro	WinFax.iss	SzCompany and SzName	SzExeDir, szFaxDir, szCoverDir, and szBackupDir

19. Storing the Package on a Secure Web Server

Install the Client Authentication (CA) Security Certificate on Windows XP to store the package on a secure Web server.

20. Web Store not Supported on Windows XP Service Pack 2 Computer using SSL

Saving a package on a Web Store installed on a computer running Windows XP with Service Pack 2 using secure channel (SSL) is not supported. However, you can save a package on a Web Store installed on a computer running Windows XP with Service Pack 2 that does not use SSL.

21. English characters appear blurred on a Chinese operating system

When running the English locale of PC Transplant on a Chinese operating system, the English texts appearing on the buttons, check boxes, radio buttons, and other dialog boxes do not appear properly. This problem occurs with the MS Sans Serif font shipped with Windows.

22. Windows 9x Limitations

1. No information about selected settings appears on a Windows 9x computer.

While running PC Transplant Wizard or Template Builder on a Windows 9x computer, if you select a desktop, network, or application setting and click the Properties button to view the properties of the settings, no information appears in the Properties dialog.

2. Analysis Report does display package information.

On a 9x computer, if you generate an Analysis Report, no information is displayed in the Summary and Details tabs.

23. Summary Log contains garbage characters

While performing real-time migration in the Chinese and Japanese PC Transplant versions, the Summary Log displays few garbage characters. If you open the Summary Log in Notepad, it displays valid characters.

24. Running A2i Builder on a Chinese Windows XP operating system

If you run the A2i Builder on a Chinese Windows XP operating system, the computer restarts after you click the Try Now button on the A2i File Creation page.

25. No localized help for Run/Edit Password field

On the Deploy Options page of the Altiris PC Transplant Wizard, the description of the Run/Edit Password field is provided in the Help in the English version only. The description of this field is not provided in the Help for localized languages.

26. Migrating to Internet Explorer 7

1. The following settings are not migrated from Internet Explorer 4 to Internet Explorer 7

• Toolbar icons

The Internet Explorer 4 and Internet Explorer 7 versions use different logic to store the binary values. So the toolbar icons cannot be migrated.

• Tools > Internet Options > General > Fonts

Internet Explorer 4 maintains a different registry structure to store the settings for the fonts. Internet Explorer 4 has different keys for different scripts and stores the settings in the selected script.

• View > Status bar

The Internet Explorer 4 and Internet Explorer 7 versions store the status bar settings with different keys. Internet Explorer 7 maintains a separate key for this setting, which does not match with the status bar settings in Internet Explorer 4.

• View > Explorer Bar > (All settings)

Internet Explorer 4 stores the Explorer bar settings in one binary value. Internet Explorer 7 stores these settings in 3 different keys. So these settings cannot be migrated.

• View > Text size

Internet Explorer 4 maintains one registry value in different "character set" keys and updates the value from the selected character set key. This value cannot be read at run time during migration.

• Tools > Internet Options > Security > (Different zone levels)

The versions maintain different detailed settings under custom level for the Security settings and so the settings cannot be migrated.

• Tools > Internet Options > Connections > Dial-up and Virtual Private Network

These settings cannot be migrated.

2. The following settings cannot be migrated from Internet Explorer 5 to Internet Explorer 7:

• Toolbar icons

The Internet Explorer 5 and Internet Explorer 7 versions use different logic to store the binary values. So, the toolbar icons cannot be migrated.

• View > Status bar

The versions store the status bar settings with different keys. Internet Explorer 7 maintains a separate key for this setting, which does not match with the status bar settings in Internet Explorer 5.

• Tools > Internet Options > Security > (Different zone levels)

The versions maintain different detailed settings under custom level for the Security settings and so the settings cannot be migrated.

• View > Explorer Bar > (All settings)

Internet Explorer 5 stores the Explorer bar settings in one binary value. Internet Explorer 7 stores these settings in 3 different keys. So these settings cannot be migrated.

• Tools > Internet Options > Connections > Dial-up and Virtual Private Network

These settings cannot be migrated.

3. Following settings are not migrated from Internet Explorer 6 to Internet Explorer 7:

• Toolbar icons

The Internet Explorer 6 and Internet Explorer 7 versions use different logic to store the binary values. So, the toolbar icons cannot be migrated.

• View > Explorer Bar > (All settings)

Internet Explorer 6 stores the Explorer bar settings in one binary value. Internet Explorer 7 stores these settings in 3 different keys. So these settings cannot be migrated.

• Tools > Internet Options > Security > (Different zone levels)

The versions maintain different detailed settings under custom level for the Security settings and so the settings cannot be migrated.

• Tools > Internet Options > Connections > Dial-up and Virtual Private Network

These settings cannot be migrated.

4. The following setting is not migrated from Internet Explorer 7 to Internet Explorer 7:

• Tools > Internet Options > Connections > Dial-up and Virtual Private Network

27. Migrating to Microsoft Access 2007

1. The following settings are not migrated from Microsoft Access 97 to Microsoft Access 2007:

• General > New Database Sort Order to Personalize > File Settings

The A2i file is modified for this setting. The Microsoft Access 97 and Microsoft Access 2007 versions use different DWORD values.

• Datasheet > Default colors

The Microsoft Access 97 and Microsoft Access 2007 versions use different DWORD values.

2. The following setting cannot be migrated from Microsoft Access 2000 to Microsoft 2007.

• Datasheet > Default colors

The Microsoft Access 2000 and 2007 versions use different DWORD values.

3. The following settings cannot be migrated from Microsoft Access XP to Microsoft Access 2007.

• Datasheet > Default colors

The Microsoft Access XP and 2007 versions use different DWORD values.

• There is no Pages tab in Microsoft Office 2007

There is no Pages tab in Microsoft Office 2007, so these settings cannot be migrated from Microsoft Access XP to Microsoft Office 2007.

4. The following settings cannot be migrated from Microsoft Access 2003 to Microsoft Access 2007:

• Datasheet > Default colors

The registry value names are the same in the Microsoft Access 2003 and 2007 versions but the value takes a different DWORD value for the same color in the two versions.

• Forms\Reports > Error Checking > Error indicating color

The registry value names are the same in the Microsoft Access 2003 and 2007 versions but the value takes a different DWORD value for the same color in the two versions.

28. Migrating to Microsoft Excel 2007

1. The following settings cannot be migrated from Microsoft Excel 97 to Microsoft Excel 2007:

• Tools > Options > Calculation > Calculation
• Tools > Options > Calculation > Iteration

In Microsoft Office, these settings are combined in one setting: Enable Iterative Calculation.

2. Migrating from Microsoft Excel 2003 and Microsoft Excel XP to Microsoft Excel 2007

The settings for Tools > Options > Save > Workbook options > Disable AutoRecover are saved along with the file in Microsoft Excel 2003 and Microsoft Excel XP.

3. Migrating from Microsoft Excel 2000 to Microsoft 2007

Microsoft Excel 2000 stores the user name in a binary value whereas Microsoft Excel 2007 stores it in a string value. So the user name cannot be migrated.

29. Migrating to Microsoft PowerPoint 2007

1. The following setting cannot be migrated from Microsoft PowerPoint XP to Microsoft PowerPoint 2007.

• Tools > Options > Save > Save PowerPoint files as

The Microsoft PowerPoint 2000 and 2007 versions use different DWORD values to store this setting.

2. The following settings are not migrated from Microsoft PowerPoint 2003 to Microsoft PowerPoint 2007.

• Tools > Options > General > User information > Name

In Microsoft PowerPoint 2003 this setting is stored as a binary value, while in PowerPoint 2007 it is stored as a string value.

• Tools > Options > General > User Information > Initials

In Microsoft PowerPoint 2003 this setting is stored as a binary value, while in PowerPoint 2007 it is stored as a string value.

• Tools > Options > Save > Save PowerPoint files as

The Microsoft PowerPoint 2003 and 2007 versions use different DWORD values to store this setting.

3. The following settings are not migrated from Microsoft PowerPoint XP to Microsoft PowerPoint 2007:

• Tools > Options > General > User Information > Name

In Microsoft PowerPoint XP this setting is stored in a binary value, while in Microsoft PowerPoint 2007 it is stored in a string value.

• Tools > Options > General > User Information > Initials

In Microsoft PowerPoint, this setting is stored in a binary value, while in Microsoft PowerPoint 2007 it is stored in a string value.

• Tools > Options > Save > Save PowerPoint files as

The Microsoft PowerPoint XP and Microsoft PowerPoint 2007 versions use different DWORD values to save this setting.

30. Settings not migrated in Microsoft Outlook

• During migration from Microsoft Outlook 2000 to Microsoft Outlook XP, Microsoft Outlook XP to Microsoft Outlook Vista, and from Microsoft Outlook XP to Microsoft Outlook Vista all three options in the Tools > Options > Resource scheduling have to be set to ON. During the migration of the .PST file, these settings are not migrated to the destination computer.
• The AutoCorrect option in Tools > Options > Spelling cannot be migrated from Microsoft Outlook 2003 to Microsoft Outlook 2007 because Microsoft Outlook 2003 and Microsoft Outlook XP save these settings as a DWORD value, while Microsoft Outlook 2007 saves these settings as a binary value.
• During the migration of the rules setting, an error message is displayed. This error occurs because Microsoft Outlook 2007 does not make the .PST file that is migrated as the default data file.
• The Maximum space on hard disk [] kilobytes setting in Tools > Options > Other > Advanced options > Custom Forms is represented by a binary value in the registry. During migration, this value is not migrated to the destination computer as a binary value. So, the setting cannot be migrated.
• The Background color setting in Tools > Options > Preferences > Calendar options is migrated to Default color in Tools > Options > Preferences > Calendar options. However, Microsoft Outlook 2007 cannot read the value in the registry and reads a different color as the default color. So, this setting cannot be migrated.
• Microsoft Outlook stops responding if you select the following setting:

• Tools > Options > Spelling > Spellings and Auto Corrections > Editor options > Advanced > Editing Options > Automatically create drawing canvas when inserting AutoShapes

31. Settings not migrated in Microsoft Word

The settings for Microsoft Word are in HKCU\Software\Microsoft\Office\12.0\Data\Settings in a binary format. However, the settings are not reflected in cross version migration because the internal structure for the binary data has changed in Microsoft Office 2007.

32. PCTWiz stops responding if a language or an input method is changed during Real-time migration

During real-time migration, if you try to change the input method or language, PCTWiz may stop responding.

To avoid this problem, during a real-time migration, you should not modify the input method, the language, or any other operating system setting.

33. PC Transplant 6.8 SP1 setup terminates if a PC Transplant 6.5 Hotfix is installed on the computer

If you install PC Transplant 6.5 Hotfix on a computer having PC Transplant 6.8, the PC Transplant 6.8 setup is terminated.

You have to uninstall the Hotfix version manually and install the 6.8 version.

34. Microsoft Office 2007 Exchange Server message dialog does not appear when you configure the mail account on the destination computer after migration.

If you migrate Microsoft Outlook 2007 with an account set on Microsoft Exchange Server and launch it on the destination computer after migration, the Microsoft Exchange Server dialog appears. You can configure the mail account by entering the user name in the Mailbox field. If you launch Microsoft Outlook after you have configured the mail account, the Microsoft Exchange Server dialog does not appear.

To overcome this problem, you have to manually connect to the Microsoft Exchange Server. The Microsoft Exchange Server validates the user and synchronizes the offline folder.

35. After migrating Microsoft Outlook settings, the *.PST file may not be set for the account on the destination computer

After migrating Microsoft Outlook settings, the*.PST file may not be set for the account on the destination computer. After launching the Microsoft Outlook application on the destination computer, you may get a message to select the *.PST file. If so, browse and select the *.PST file from the following location:

<system_drive>:\document and settings\<user_name>\Local Settings\Application Data\Microsoft\Outlook

You can also change the location of the *.PST file from the Control Panel.

1. Select Start > Settings > Control Panel > Mails. The Mail Setup - Outlook window appears.
2. Click Data Files. The Outlook Data Files - Outlook window appears.
3. Add the *.PST file from the following location:
   <system_drive>document and settings\<user_name>\Local Settings\Application Data\Microsoft\Outlook

After launching Microsoft Outlook, your account gets configured with the selected *.PST file.

36. The PCTWiz user interface does not offer the settings options for when Microsoft Office is installed on a virtual layer.

To create a new personality package in PCTWiz, the settings related to the various applications in the Microsoft Office suite do not appear correctly. This issue occurs if Microsoft Office is installed on a virtual layer of Altiris® Software Virtualization Solution™ (SVS™) software.

This is a known issue in SVS with short filenames. SVS does not resolve the short filename in the registry correctly. Until a solution is provided, you can resolve this issue by changing the short filename in the layer for each application in the Microsoft Office suite to a longer filename.

Note: This issue occurs only on native hardware. It does not occur on a virtual machine.

37. An error is reported when you build a personality template using Personality Monitor and open it with template.exe.

When you build a personality template using Personality Monitor and open it with template.exe, an error is reported.

This error occurs because the template generated using Personality Monitor is not designed to be used with the Template Builder. The template created using Personality Monitor can be opened only with PCTWiz.

1. PC Transplant Web Store cannot be installed on a Windows Vista computer

The PC Transplant Web Store cannot be installed to a Windows Vista operating system.

2. Restarting the computer is necessary after the Migration to a Windows Vista installed computer is complete

When you run the PC Transplant Wizard in the User Interface mode and perform a real-time migration to a Windows Vista computer, you are not prompted to restart the computer after the migration completes. You have to manually start the computer after migration. This is applicable only for a Vista to Vista migration.

3. Unspecified Advance Appearance Settings will migrate to a Windows Vista computer

If you create a personality package on a Windows 2000 computer and run the package on a Windows Vista computer, various advanced appearance settings not specified in the template are also migrated.

4. Which Desktop Settings are not migrated to a Windows Vista computer?

The following desktop setting is not migrated to a Windows Vista computer:

• Power options

5. Which Spelling Settings are not migrated to a Windows Vista computer?

The following spelling settings cannot be migrated from Microsoft Access 2000, Microsoft Excel 2000, Microsoft Access XP, Microsoft Access 2003, Microsoft Publisher 2003, Microsoft Excel 2003, Microsoft PowerPoint 2000, Microsoft PowerPoint 2003, and Microsoft PowerPoint XP to Windows Vista:

• Words in uppercase
• Words with numbers
• Internet and file addresses

Note: Windows Vista has different registry paths and different value names to save these settings.

6. How do I migrate the Rating System settings for Microsoft Internet Explorer in Windows Vista?

By default, in Internet Explorer 5 and Internet Explorer 6, the Rating System (rsaci.rat) file is selected under Tools > Internet Options > Content > Content Advisor > Settings > General > Rating Systems. This file is present in the System32 folder of the operating systems up to Windows XP. By default, this folder is filtered in PCTWiz while creating a package. This file is not available in Windows Vista.

To migrate the Rating System settings from Internet Explorer 5 or 6 to Internet Explorer 7 on Windows Vista

1. Launch PCTWiz.
2. On the Transplant PC’s Settings page, select Applications > MS Internet Explorer.
3. On the Transplant Source PC’s Files and Folders page, click Filter.
4. In Folder Filter, clear the C:\Windows\System32 folder check box.
5. Click OK.
6. Click Add new.
7. Select the rsaci.rat file from the C:\Windows\System32 folder.
   OR
   Select the required rating system file from the C:\Windows\System32 folder to migrate the Rating System file you have downloaded in same or in cross-version migration.
8. Create the package and execute it on the destination computer.

7. User Account Control in Windows Vista cannot be handled programmatically

When you run PCTWiz or any other PCT package, the User Account Control dialog appears. The functionality of the User Account Control is specific to the operating system. The UAC dialog cannot be handled programmatically.

If you want to run PCTWiz or Package in the -q/-qm mode, disable the User Account Control dialog from the control panel so that it does not appear when the command is run. However, we do not recommend this option. Therefore, to run PCTWiz or Package in a quiet mode, run the command prompt in an elevated mode and run the required command-line through the elevated command prompt.

8. The display of the Welcome to PC Transplant window of the Altiris Personality Migration Wizard is sometimes incorrect

The Welcome to PC Transplant window of the Altiris Personality Migration Wizard sometimes displays incorrectly. Only the black background and the buttons on the page appear. This problem does not occur when the package is run locally. This occurs because the window is not correctly repainted by Microsoft.

This is observed when you create a data-logic separated package; capture some settings and data in it, and run this package on a destination Windows Vista computer.

To resolve this problem:

• Minimize the window and reopen it.
  Or
• Change the focus to another window and refocus to the Welcome to PC Transplant window.

9. Some Environment Variables do not work in Windows Vista

The following environmental variables found in the HKLM\"Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders" registry are different in Windows Vista.

• %MI_ALLUSERS_APPDATA%

Opens the Program Data in the system drive.

• %MI_APPDATA%

Opens the Roaming folder in <system drive>\users\solutions1\AppData.

• %MI_LOCALAPPDATA%

Opens the Local folder in <system drive>\users\solutions1\AppData. In case of computers other than Windows Vista, this variable opens the Application data folder present in the Local settings of the current user.

The following variables are not accessible from the File dialog. But these variables can be used in the Template Builder.

• %MI_FONTS%
• %MI_HISTORY%
• %MI_RECENT%

The following variables do not work with the file open, but they can be used in the Template Builder.

• %MI_PROFILEUSER%
• %MI_USER%
• %MI_INPUT_LOCALE_ID%

This variable is not supported in Vista:

• %MI_LOCALSETTINGS%

10. The Launch button is disabled in the A2i Builder in Windows Vista

The Launch button on the A2i Settings screen of the A2i Builder Wizard is disabled in Windows Vista because it does not work and gives an error.

11. The .INF file path dialog appears on a Windows Vista computer even if you run a package containing local printer settings

If you run a package containing local printer settings on a Windows Vista computer, you are prompted to enter the .INF file path of the printers. However, if you run the package after uninstalling the migrated printers, you are not prompted to specify the .INF file path.

12. Migration of Outlook Express 6 from or to Windows Vista is not supported

In Windows Vista, the .EXE file for Outlook Express 6 (msimn.exe) refers to the .EXE file of Windows Mail (WinMail.exe) in the registry. Following are the registry keys in Windows Vista:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App paths\msimn.exe

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App paths\WinMail.exe

Outlook Express 6 and Windows Mail are similar applications with their registry settings at different locations.

PC Transplant cannot migrate the settings from Outlook Express 6 to Windows Mail because both have the same version 6. PC Transplant also does not support Windows Mail.

13. PCTWiz cannot run from network share on Windows Vista and gives a license expired message

Following are the three scenarios when PCTWiz gives a license expired message.

• If you run PCTWiz from a share on a Windows Vista operating system, you get a license expired message on all operating systems regardless of how PCTWiz is licensed.
• If PC Transplant is installed on Windows Vista with an evaluation license, and you run PCTWiz with a restricted user on the same computer, you get the license expired message.
  To avoid this problem, you can run PCTWiz as an elevated user.
• If you have a PC Transplant share on any supported operating system other than Windows Vista with an evaluation license, and you run PCTWiz on Windows Vista under a restricted user, you get the license expired error.
  To avoid this problem, you can run PCTWiz as an elevated user.

14. The User Context option cannot be migrated from Windows Vista to Windows Vista

On a source Windows Vista computer, even after getting access rights to the destination Windows Vista, the User Context option cannot be migrated to the Windows Vista destination computer. This problem may be due to some settings on the source computer which cannot be resolved.

15. Some settings cannot be migrated from Windows Vista to Windows Vista

The following settings cannot be migrated from Windows Vista to Windows Vista:

• Make the computer easier to see > Make things on the screen easier to see > Make rectangle thicker (check box)
• Make the keyboard easier to use > Turn on sticky keys (check box)
• Make it easier to focus on tasks > Turn on sticky keys (check box)
• Windows Defender
• Color Management > Device (Tab)
• People near me > Change picture > Choose a new picture for your account
• Offline files

16. Some Mouse Settings are not restored after running the Undo package for Windows XP to Windows Vista migration

When migrating from Windows XP to Windows Vista, after running the Undo package, the following settings are not restored:

• Control Panel > Mouse > Pointer Options (Tab) > Show location of pointer when I Press the CTRL key

17. The Data Logic package displays an error message after editing the package with PCTWiz or PCTEdit

If you create a data logic package on a Windows XP or Windows Vista source computer and run the package on a Windows Vista destination computer, the UAC dialog displays the company name information correctly. After editing this package with PCTWiz or PCTEdit on the source computer, if you run the edited package on the Windows Vista destination computer, the An unidentified program wants to access your computer error is reported.

When you edit the package, the digital signature becomes invalid and the package cannot be signed again. This results in an error when the edited package is run on the destination computer.