PC Transplant Release Notes - Symantec SSL Certificates Support
Transcription
PC Transplant Release Notes - Symantec SSL Certificates Support
PC Transplant 6.5 Release Notes April 13, 2006 NOTICE The content in this document represents the current view of Altiris as of the date of publication. Because Altiris responds continually to changing market conditions, this document should not be interpreted as a commitment on the part of Altiris. Altiris cannot guarantee the accuracy of any information presented after the date of publication. © 2006 Altiris, Inc. All rights reserved. Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy, and RapidInstall are registered trademarks of Altiris, Inc. in the United States. Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark of Altiris, Inc. in other countries. Altiris eXpress, Deployment Server, Deployment Solution, My IT Forum, Notification Server, Vision, Web Reports and other product names are trademarks of Altiris, Inc. in the United States and other countries. All other brand names are trademarks or registered trademarks of their respective companies. Information in this document is subject to change without notice. For the latest documentation, visit our Web site at www.altiris.com. RNT: H Release Notes PC Transplant 6.5 Page 1 of 20 Contents Section 1 – Overview .......................................................................................................................... 3 Section 2 – Installation and Licensing................................................................................................. 3 Section 3 – New Features in this Release ............................................................................................ 5 Section 4 – Known Issues ................................................................................................................... 8 Section 5 – Vista Known Issues ........................................................................................................ 18 Section 6 – Troubleshooting.............................................................................................................. 19 Release Notes PC Transplant 6.5 Page 2 of 20 Section 1 – Overview 1.1 Document Purpose This document provides new and existing PC Transplant users with a detailed list of new features, known issues, and troubleshooting steps for the 6.5 release of PC Transplant. 1.2 Background PC Transplant uses its wizard-driven interface to capture 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 simplifies the deployment and migration of new computers or Windows operating systems by facilitating the migration of data and settings. It complements existing desktop management tools, meeting an easily identified need that none of these tools currently address. With PC Transplant, you not only can migrate to a new computer quickly and efficiently, but you can 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. 1.3 Documentation Product documentation is available as online help (pctransplant.chm) and in the .PDF format (pctransplant.pdf). The PC Transplant Reference Guide (pctransplantref.pdf) is also included with the product. To view Altiris product documentation in .PDF format, use Adobe Acrobat Reader (available at: http://www.adobe.com). Section 2 – Installation and Licensing 2.1 Installation Installation and licensing information is provided in the Readme – Quick Install .PDF file (included in the solution zip file downloaded from the Altiris Web site), in the Altiris Getting Started Guide, and in the Altiris Notification Server Product Guide. 2.1.1 Installing PC Transplant To install PC Transplant a. Run PCTSetup.exe from the Altiris Product CD or from the files downloaded from www.altiris.com. Release Notes b. In the Language list of the Setup Language dialog box, click the language of your choice c. for installation. On the Welcome screen, click Next. d. Choose a license option: 1. If you have not yet purchased a license for PC Transplant, you can install using a 7-day evaluation license. To use the 7-day evaluation, leave the Activation Key File Information field blank and click Next. 2. If you want to evaluate PC Transplant for more than seven days, you can register at the Altiris Web site and receive a 30-day evaluation license. To apply for a 30day evaluation license, enter or browse to the location of pc_eval.lic file you downloaded from the Altiris Web site and click Next. PC Transplant 6.5 Page 3 of 20 For downloaded files and information, see http://www.altiris.com/products/pctransplantpro/. 3. If you have purchased a license, enter the filename or browse to the location of the PC Transplant Activation Key license file (.LIC) and click Next. e. f. If you applied a license, verify the Activation Key information and click Next. Read the license agreement and choose I accept the terms in the license agreement to accept it. g. Click Next to install PC Transplant. Option Description A standard installation includes the following Windows-based utilities: Standard h. Release Notes • PC Transplant Wizard • Template Builder • A2i Builder • PC Transplant Package Editor • Application Administrator • Password Encryption Utility • Product Licensing Utility • Package Content • Windows Firewall Manipulator • Application Installer • Crossover configuration utility • PC Transplant Destination Agent • Profile Merger If you selected Standard, the default destination location is <System Drive>:\Program Files\Altiris\PCT. To change the destination location, click Change and enter or browse to new destination. Click Next, Install, and then Finish. Note: If you do a standard installation, select Start > Programs > Altiris > PC Transplant > Tools to access the utilities. If you want to access PC Transplant using a UNC path, then the client computer must be given sufficient rights to invoke the PC Transplant Wizard. PC Transplant 6.5 Page 4 of 20 Section 3 – New Features in this Release 3.1 Unicode Support PC Transplant supports Unicode natively. All PC Transplant applications are Unicode-enabled. 3.2 Personality Service Monitor The Personality Service Monitor captures a computer's personality when it is run for the first time. When you decide to migrate your computer, execute the Personality Service Monitor to capture the computer's personality again. The Personality Service Monitor displays the changes that have occurred on your computer and lets you select the files, folders, files types, and application settings to migrate. The Personality Service Monitor will not work with an evaluation license of PC Transplant. It only works with fully licensed copies of PC Transplant. The Personality Service Monitor is supported on Windows NTx or later computers. It does not support Win9x and ME computers. 3.3 A2iEditor and Improved A2iBuilder The A2iEditor provides an easy to use GUI for editing an existing .A2i file. The A2iBuilder has been made more user-friendly with an improved GUI. The Try Now option of the A2i Editor is disabled by default. This option is enabled after you open an .A2i file and save it. 3.4 Merging User Profiles The Profile Merger tool lets you merge multiple profiles to a single profile on the same computer. This tool only copies profile data and not profile setting information. 3.5 Command-line Section in Template Files You can save command-line options as part of a template file. This saves the time and effort involved in typing long command-line strings in the PC Transplant Wizard. 3.6 Migration and Resolution of Security Permission Now, PC Transplant supports migration and resolution of security permissions for files and folders across domains and computers. Example: Consider a scenario where the users Altiris\solutions1, Altiris\solutions2, and Altiris\solutions3 have different permissions on a file or folder on the source computer. Altiris\solutions1 has only read and write permissions and Altiris\solutions2 has read, write, and execute permissions. While executing the package on the destination computer, if you map Altiris\solutions1 to Altiris \solutions2, then Altiris\solution2 should have all the permissions of Altiris\solutions1. After completing the migration, you can check the permissions of a file or folder by right-clicking on the migrated file or folder. Altiris\solutions2 has only read and write permissions instead of read, write, and execute permissions. On the destination computer, the permissions of Altiris\solutions3 will remain the same because you have not mapped this user to any other user. 3.7 Crossover configuration PC Transplant supports migration by using a crossover cable. A new utility, PCTCrossConfig, is included for configuring the destination computer for real-time migration using a crossover cable. Release Notes PC Transplant 6.5 Page 5 of 20 3.8 Display Password Dialog In the earlier version, you cannot re-enter the password if you enter a wrong password during package execution. The package execution was terminated at this point. Now, you can re-enter the password until the password is validated or cancel the package execution. 3.9 New Command–line Switches Some of the new command-line switches available are: • Command-line support for specifying an administrator user (For package): To run a package, you need administrator rights on the destination computer. You can specify a user with administrator rights using this command-line. -ConnectAs: <DomainName>$<UserName>$<Password> • Command-line support for drive mapping (For package and real-time migration): During migration, you can change the destination drive for any source drive using this commandline. -DriveMap: <SourceDrive>$<DestinationDrive> • Command-line support for redirecting path (For package and real-time migration): You can provide comma-separated paths to redirect drives using this command-line. -RedirectPaths: <SourcePath>$<DestinationPath>;<SourcePath>$<DestinationPath> 3.10 Service Pack Information in the About Dialog box In the earlier version, only product version information and build number are displayed in the About dialog box. Now, service pack information is also displayed in the About dialog box, if any service pack is installed. 3.11 New Product Icons The User Interface of PC Transplant and its tools now have a new look with 3D icons. 3.12 Tag Settings for File Path In the settings file, tags are provided to allow extraction of files from a path. The tags available are: o <%STRIPHEADSLASHESn:path%> o <%STRIPTAILSLASHESn:path%> These two tags can be used in combination to generate a path using the <%REG%> tag. Example 1: <%STRIPHEADSLASHES1:C:\one\two.txt%> Strips up to one slash from the head of the string “C:\one\two.txt.” This expression evaluates to “\one\two.txt.” Example 2: <%STRIPHEADSLASHES2:C:\one\two.txt%> Strips up to two slashes from the head of the string “C:\one\two.txt.” This expression evaluates to “two.txt.” Example 3: <%STRIPHEADSLASHES:C:\one\two.txt%> Release Notes PC Transplant 6.5 Page 6 of 20 Strips out all slashes from the head of the string “C:\one\two.txt.” This expression evaluates to “two.txt.” Example 4: <%STRIPTAILSLASHES:C:\one\two.txt%> Strips out all slashes from the tail of the string “C:\one\two.txt.” This expression evaluates to “C.” 3.13 Migrate Security Permissions for Printers PC Transplant 6.5 supports migration of local printer security permissions. This feature was not available in the earlier version. 3.14 Spanned Package path The paths of all span files for a package are listed in the Summary.log file. This feature was not available in the earlier version. 3.15 Check for Incorrect Installation File Selection A warning message is displayed when an incorrect installation file is opened in the Transplant Install Application page in PC Transplant Wizard. 3.16 Support for Automatic configuration of Windows XP Firewall Settings PC Transplant detects the status of the firewall on Windows XP SP 2 computers, and automatically configures the firewall on destination computer for migration to continue. The original firewall settings are restored after the migration is completed. 3.17 Creation of Migration Log Files Earlier, a log file was not created if there were no errors during the migration process. Now, if no errors occur during the migration process, then the log file will still be created. It displays the source and destination users, the time when the migration was completed, and any additional information. 3.18 Enhanced –printer Command-line The –printer command-line switch is extended to include or exclude printers from a specific print server while creating a package. The wildcards * and ? are supported for this command-line. For example: –printer:+printserver=jon* captures all printers on print servers whose names begin with “jon.” The extended printerserver switch works with the existing –printer functionality. 3.19 Documentation Available in Supported languages The .PDF format of the product documentation is available in the respective language folders. Release Notes PC Transplant 6.5 Page 7 of 20 Section 4 – Known Issues 4.1 Executing A2i Builder on a Japanese Windows XP and 2000 Operating System If you execute A2i Builder on a Japanese Windows XP and 2000 Operating System, a blue dump screen appears and the computer restarts. 4.2 Running WinVNC and Launching PC Transplant Wizard If you run WinVNC in App Mode on a Win 98 computer and launch PC Transplant Wizard on this computer, a “Another instance of Winvnc is already running” message pops up during package creation. Note: Similar messages may appear for other applications too. 4.3 PCT Package Settings Tab The PCT Package Settings tab is not displayed on Win 9x and Win NT 4.0 Operating Systems. 4.4 Application Migration Limitations 4.4.1 AOL AOL stores application and user settings in a proprietary file (main.idx). As changes cannot be made to this file, the following limitations apply: o PC Transplant does not migrate the main.idx setting file from AOL 6.0 to 7.0. AOL 7.0 cannot correctly read a 6.0 main.idx file. Since this file is not migrated, most settings are not transferred. o AOL passwords cannot be migrated from one computer to another. AOL locks passwords on the original installed computer. o 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. o AOL Media Player as Default CD Player setting is not migrated. This setting is connected to OS file type associations. 4.4.2 AT&T Global Network PC Transplant supports the migration of the entire AT&T Global Network application. If you choose to migrate it to a different installation path, the AT&T install.log file will not contain a valid path and you will not be able to fully uninstall the application on the destination computer using the Control Panel - Add/Remove Programs tool. However, you can uninstall it using PC Transplant’s Undo package. 4.4.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.4.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 Lotus Notes’ proprietary file format. PC Transplant has no way of interpreting this file. Release Notes PC Transplant 6.5 Page 8 of 20 Additionally, if the destination computer has Lotus Notes 6 installed for multi-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 whichever user is processed last will have his settings migrated and other user’s files will be overwritten because the user data is stored on a central location. 4.4.5 McAfee In order to migrate McAfee’s anti-virus settings, PC Transplant must stop the McAfee service from running. PC Transplant cannot stop this service if it is run under a limited user context. This limits PC Transplant from migrating McAfee settings. 4.4.6 Microsoft Access 97 to Access 2000/2002 PC Transplant cannot migrate “New Database sort order” from MS Access 97 to 2000/2002. The data value for this setting is modified between these versions and cannot be converted. 4.4.7 Microsoft Access XP to Access 2003 PC Transplant cannot migrate the following settings: o Tools > Options > Advanced > Command-line arguments o Tools > Options > International > Use Hijri Calendar 4.4.8 Microsoft Internet Explorer o No settings may appear to migrate if Internet Explorer has never connected on the destination computer. In this case, Internet Explorer will not load the migrated settings until it has performed a successful connection to the Internet. o 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 the case of this event. o 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. o 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. o The settings for the Content Advisor cannot be migrated from I.E 5.0 to 6.0. The storage types used between these two versions are not compatible. o The migration of the selection of Internet Programs associated with the HTML Editor, EMail, Newsgroups, Internet Call, Calendar, and Contact list are not supported. 4.4.9 Microsoft Office 97 When migrating Office 97 settings to a non-profile Windows 9x computer with Office 97, you may find that Auto Correct and Taskbar do not migrate. The settings for these options are being migrated, but in some cases Microsoft Office 97 will remove these migrated settings if they did not already exist. Solution: Run your Office 97 application and turn on these two features. Then migrate your Office 97 settings again. 4.4.10 Microsoft Office 2000 to Office XP Microsoft Office toolbars are not migrated from Office 2000 to Office XP because the Office 2000 ppt.pcb file is incompatible with Office XP. 4.4.11 o Release Notes Microsoft Outlook and Outlook Express Due to the change in the setting name in PCT 3.6 from “MS Outlook POP - IMAP accounts” to “Accounts - POP-IMAP” in 4.0 and later, PCT 4.0 and later will not recognize the setting selection from a PCT 3.6 template file. PC Transplant 6.5 Page 9 of 20 o Outlook “Time zone” setting - PC Transplant does not migrate the “Time zone” setting in Outlook. This is an OS related setting and not an application setting. To migrate the Time Zone setting, use the Desktop > Regional Settings options in PC Transplant. o 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. o 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. o If you are migrating “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, choose 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 will tell you to delete these files so they can be recreated. o Migrating Outlook 2003 to Outlook 2003 gives error because Outlook is looking for vpmsece.dll in the extend.dat file. The location of vpmsece.dll file could change due to one of the following reasons: Uninstalling Norton AntiVirus Corporate Edition, and then 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 work around 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 recreates this file when it is executed next time. More information about the same can be found at http://service1.symantec.com/SUPPORT/entsecurity.nsf/pfdocs/2002090613375148?Open&dtype=corp. Also this problem is fixed in the latest version of Symantec AntiVirus Corporate Edition (Symantec Antivirus Corporate Edition 8.1.1 MR6). 4.4.12 Microsoft PowerPoint 97 to PowerPoint 2000/2002 PC Transplant cannot migrate “Save PowerPoint file as” setting from PowerPoint 97 to 2000/2002. Microsoft stores this setting using a different format between these versions that cannot be converted. 4.4.13 Microsoft PowerPoint XP to PowerPoint 2003 PC Transplant cannot migrate Toolbars from MS PowerPoint XP to PowerPoint 2003. Release Notes PC Transplant 6.5 Page 10 of 20 4.4.14 Microsoft Word 97 to Word 2000/2002 PC Transplant cannot migrate “Fast Save” and “Background repagination” settings from Word 97 to Word 2000/2002. The binary data that Word uses to store these settings is not compatible across different versions. 4.4.15 Microsoft Word 97 to Word 2000/XP If the logged on user at the destination computer does not have administrative rights, then PC Transplant cannot migrate most of the settings from MS Word 97 to MS Word 2000/XP. 4.4.16 Microsoft Word 2000 to Word XP If the logged on user at the destination computer does not have administrative rights, then PC Transplant cannot migrate most of the settings from MS Word 2000 to MS Word XP. 4.4.17 Microsoft Word 2000 to Word 2003 PC Transplant cannot migrate the following settings from Word 2000 to Word 2003: o Tools > Options > General > Navigation Keys for WordPerfect users o Tools > Customize > Options > Show Standard and Formatting toolbars on two rows o Tools > Customize > Toolbars > Toolbars The binary data that Word uses to store these settings is not compatible across different versions. 4.4.18 Microsoft Word XP to Word 2003 PC Transplant cannot migrate the following settings from Word XP to Word 2003: o Global Macros o Tools > Options > View > Smart tags o Tools > Options > General > Navigation Keys for WordPerfect users o Tools > Customize > Options > Show Standard and Formatting toolbars on two rows o Tools > Customize > Toolbars > Toolbars The binary data that Word uses to store these settings is not compatible across different versions. 4.4.19 Netscape Only POP account profiles can be migrated. IMAP account profiles cannot be migrated. Some settings will 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. 4.4.20 pcAnywhere Version 9.0 to 10 - Hosts, remotes, 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. 4.4.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. 4.4.22 o Release Notes 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. PC Transplant 6.5 Page 11 of 20 o Custom menus are not migrated from ACT 4.0 to ACT 2000. o Keyboard shortcuts and custom commands are not migrated from ACT 4.0 to ACT 2000. 4.4.23 Eudora After migrating Eudora 4.0 to Eudora 5.1, same settings are applied to all profiles. 4.4.24 Pagemaker 7.0 Paths for ‘Download to folder’ and ‘Web browser’ in online preferences are not resolved. Source computer’s path is migrated to the destination computer. 4.4.25 Microsoft Project 98 to Project 2000 PC Transplant cannot migrate the Options > Spelling from MS Project 98 to MS Project 2000. 4.4.26 Norton Anti-virus Desktop Edition PC Transplant does not support cross version migrations. 4.4.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: 4.5 o Options > Configuration > System > Include WinZip Quick Pick in the taskbar tray o Options >Configuration >System > Include Winzip in the start menu Desktop Settings Migration Limitations 4.5.1 Control Panel Keyboard Settings Keyboard language settings do not migrate across different platforms. Keyboard language files are platform specific. NT uses .DLL files, where as 95 and 98 use .KBD files. Since transferring the language files could affect the integrity of the OS, 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. For 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 of the mouse settings are not migrated. PC Transplant only supports the migration of 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 only seen this with the “Color Management” tab when migrating a 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 OS types store time zone information is not known. Release Notes PC Transplant 6.5 Page 12 of 20 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. 4.5.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 Setting o 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. o When migrating HTML wallpaper, the setting is migrated but in some instances Windows Explorer may replace the setting. Screen Saver o 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. o Screen Savers may not work across different operating systems. This restriction is determined by the creator of the screen saver. o Screen Saver options - PC Transplant can set the screen saver, its time and password. Screen savers do not have a standard location where they must store their settings. Their settings could be located in the registry, in the control.ini, in their own .INI, or in any file for that matter. Some screen savers may need to have a custom .a2i file created for them. 4.5.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 o 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. o 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 with package or PC Transplant Wizard. o The location of the icons to be placed on the desktop is not supported. Taskbar Settings Release Notes o PC Transplant cannot migrate Taskbar settings under Windows 95, 98, and NT, due to registry limitations. o Positioning of the taskbar is not supported. PC Transplant 6.5 Page 13 of 20 4.6 Network Settings Migration Limitations 4.6.1 Computer Name and Domain Name Password does not get validated for Windows 9x and Windows ME. 4.6.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. 4.6.3 Folder / Drive Share Assignments File and Print Sharing must already be installed on the destination computer or a share will not migrate. 4.7 File, Directory, and File Type Migration Limitations 4.7.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. 4.7.2 NTFS Encryption PC Transplant does not support the migration of NTFS encrypted files. Turn off encryption prior to migration, or these files will need to be migrated by the user manually. 4.7.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. 4.8 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 Microsoft’s default setting 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, open your Local Security Settings by selecting Control Panel > Administrative Tools > Local Security Policy. Under the Security Settings tree, select Local Policies > Security Options. In the right pane, right-click Network Access: Sharing and Security Model for local accounts, and select Properties. Change the option from Guest only to Classic. 4.9 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. Release Notes PC Transplant 6.5 Page 14 of 20 Example: Consider a case where “Application Data” is mapped to \\User\Shared on Destination computer. You must map network drive to \\User\Shared say drive G. Make “Application Data” point to drive G instead of \\User\Shared and use command-line option -netdrives while migrating. 4.10 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. 4.11 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 install. PC Transplant cannot simulate for the applications, which are not installed on the destination computer but are selected for installation. 4.12 Issues with Installing Packages through a Service 4.12.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. 4.12.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. 4.12.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. 4.13 Error Opening Package When building a package from a Windows 9x platform with a Uniform Naming Convention (UNC) path, you may get the 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. 4.14 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. 4.15 Printer Settings 4.15.1 Release Notes Printer Support o 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. o 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 PC Transplant 6.5 Page 15 of 20 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). 4.15.2 Security Permissions In Windows NT/2000/XP, network printer security permissions are not migrated. Example: Print, Manage Printers, Manage Documents, and so on. 4.15.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. 4.16 International Versions of PC Transplant 4.16.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 OS. The filenames under Windows 9x have different filenames than those used under NTx. PC Transplant cannot translate the English filenames from these unlike platforms. The International versions of the OS changes these filenames and breaks the automatic mapping. 4.16.2 MS 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. Cause: Outlook French failed to match the default profile’s name with its setting definition, making it impossible to locate. Microsoft has corrected this in Outlook XP. 4.17 Application Installation 4.17.1 Standard Support 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 Filename Keys to Specify (Mandatory) Keys to Specify (Optional) Adobe Acrobat 3 AdobeAcrobat3.iss - SzDir Adobe Acrobat 4 AdobeAcrobat4.iss - SzDir Release Notes PC Transplant 6.5 Page 16 of 20 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 SzCompany and SzName. SzExeDir, szFaxDir, szCoverDir, and szBackupDir. WinFaxPro Winfax.iss 4.18 Storing the Package on a Secure Web Server Install the Client Authentication (CA) Security Certificate on Windows XP computer to store the package on a secure Web server. 4.19 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. 4.20 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, checkboxes, radio buttons, and other dialog boxes are not displayed properly. This problem occurs with the MS Sans Serif font shipped with Windows. 4.21 Windows 9x Limitations 4.21.1 No Information about selected settings is displayed 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 setting’s properties, no information is displayed in the Properties dialog box. Release Notes PC Transplant 6.5 Page 17 of 20 4.21.2 Analysis Report does not Display Package Information On a 9x computer, if you generate an Analysis Report, no information is displayed in the Summary and Details tabs. 4.22 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. 4.23 Running A2i Builder on a Chinese Windows XP Operating System If you run A2i Builder on a Chinese Windows XP Operating system, the computer restarts after clicking the Try Now button in the A2i File Creation page. 4.24 No localized help for Run/Edit Password field On the Deploy Options page of Altiris PC Transplant Wizard, the description of the Run/Edit Password field is provided in the help for English version only. The description for this field is not provided in the help for other localized languages. Section 5 – Vista Known Issues 5.1 PC Transplant Wizard in Elevated Mode If you run the PC Transplant Wizard in the elevated mode on a Vista computer and use a template that does not include any user settings or using the command line without specifying the -user switch, the “No user account matches the specified filter criteria” message appears and the PC Transplant Wizard stops running. 5.2 Destination Agent The destination agent is not being pushed on a Vista computer. 5.3 System Tray Icons The PC Transplant Destination Agent icon does not appear in the System Tray. While the destination agent icon does not appear in the System Tray in Beta 1, PC Transplant is still able to connect and transfer personality information to the destination computer during a real-time migration. 5.4 PCT Webstore The PCT Webstore cannot be installed onto a Microsoft Vista operating system. 5.5 Restart After the Migration Completes If you are running PC Transplant Wizard in User Interface mode and performing real-time migration to a computer with Vista installed, you will not be prompted to restart the computer after the migration completes. 5.6 Advanced Appearance Settings If you create a personality package on a Windows 2000 computer and run that package on a Vista computer, various advanced appearance settings not specified in the template are also migrated. 5.7 White Text on Black Background Release Notes PC Transplant 6.5 Page 18 of 20 Various program windows in the User Interface mode display white text on a black background. 5.8 Warning Message A warning message is displayed when the Template Builder is run on a Vista computer. 5.9 Undo Shortcut Link and Undo File The Undo shortcut link and the undo file do not run on a Vista computer. 5.10 User Credentials If you attempt to perform real-time migration from a Vista computer to another operating system, the user credentials provided are not accepted. 5.11 TCP/IP Settings TCP/IP settings cannot be migrated to a Vista computer. 5.12 Desktop Settings The following desktop settings do not migrate accurately to a Vista computer: • Power options • Folder Options -> View -> Show Drive Letters 5.13 Real-time Migration You cannot perform real-time migration from one Vista computer to another Vista computer. Section 6 – Troubleshooting 6.1 Removable Media We do not recommend storing a Personality Package on a removable media with less than 10MB of free disk space. If disk space is limited, you can span a personality package across multiple disks. If you use this approach, expect to do some disk swapping. 6.2 Boot Disk Configuration When creating a boot disk configuration, set the disk to map to the root directory or share the location of the program's executable. Example: if the program is located in \\<server1>\PC Transplant, you will need to tell the Boot Disk Wizard to create a map manually and assign it to map to \\<server1> and the "PC Transplant" share. 6.3 User Accounts, Groups, Computer Names, and Domains To run PC Transplant on Windows NT, 2000, or XP, we recommend that your user be a member of the Administrator group. If you are a member of a Windows Domain and are migrating a Windows NT, 2000, or XP computer name or are re-creating the Domain Computer account, then you might receive the following error while logging on to the Domain after the migration: “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. Release Notes PC Transplant 6.5 Page 19 of 20 Solution: Log on to the workstation (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. 6.4 Improve Performance Turn off the migration of security permissions to improve the performance. 6.5 Outlook Settings When migrating the Outlook settings, it appears as though settings and personal folders were not migrated for a given user account. Cause: The profile account used on the source computer is not used when logging on to Outlook on the destination. Solution: 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 (PRF) is used by Microsoft to configure a user's profile and settings. An administrator can configure these to 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. Release Notes PC Transplant 6.5 Page 20 of 20