Using the Profile Migration Tool
This appendix explains how to use the profile migration tool to migrate Cisco Aironet 350 series and CB20A wireless LAN client adapter profiles to profiles that can be used with Cisco Aironet CB21AG and PI21AG client adapters.
The following topics are covered in this appendix:
•Overview of the Profile Migration Tool
•Rules Governing Profile Migration
•Installing the Profile Migration Tool
•Running the Profile Migration Tool
•Command Line Options
•Uninstalling the Profile Migration Tool
Overview of the Profile Migration Tool
The profile migration tool is designed to migrate Cisco Aironet 350 series and CB20A wireless LAN client adapter profiles to profiles that can be used with Cisco Aironet CB21AG and PI21AG client adapters. The tool is meant to migrate profiles with minimal modification, but its behavior can be altered by command line options. The legacy 350 and CB20A profiles are not deleted or modified in any way.
Cisco expects the profile migration tool to be executed once, most likely immediately after installing or updating the CB21AG/PI21AG client adapter software. Upon completion, the profile migration tool may be removed from your computer.
Note Profile migration tool 1.0 can be used only with Install Wizard 2.5. To find the current version number of the profile migration tool, find the PMT.exe file in the directory where ADU is installed, right-click the file, and click Properties and the Version tab.
Rules Governing Profile Migration
These rules govern the operation of the profile migration tool:
•Legacy profiles that are configured for host-based EAP are not migrated.
•Passwords that are stored in LEAP and EAP-FAST profiles may or may not be migrated, depending on the encryption method used for those passwords. Passwords that are not migrated must be re-entered after the migration.
•The PAC files for EAP-FAST profiles are not migrated. They must be reprovisioned after the migration.
•A profile's auto profile selection properties are migrated only if auto profile selection is enabled.
•Legacy profiles that were created using older versions of ACU may experience problems during migration. In such cases, the profile migration tool migrates the information that it can and ignores any additional information.
•CB21AG and PI21AG client adapters have a limit of 16 profiles, so the total number of profiles that can be migrated is 16 minus the number of existing CB21AG and PI21AG profiles. If the number of profiles to migrate is greater than the number of profiles that can be migrated, some legacy profiles are not migrated. In this case, the client adapter priority is as follows, unless overridden by command line options:
1. 350 PCMCIA
2. 350 PCI
3. 350 mini PCI
For each client adapter, profiles are migrated in this order:
1. Default profiles
2. Auto-selectable profiles
3. Any current profiles for inserted legacy client adapters that have not already been migrated
4. Any remaining profiles
•If multiple instances of the same profile name exist, the names are mangled unless overridden by command line options. The default name-mangling scheme causes subsequent profiles with the same name to have an _a or _b appended to the end of the name, indicating whether the profile migrated from an 802.11a (CB20A) or 802.11b (350) radio. A third instance would have an _aa or _bb appended and so on (for example, Office, Office_a, Office_aa).
Note If the original name is too long to be appended, it is shortened by truncating as necessary.
•Profile names that existed before the migration are preserved unless the -replace command is executed.
Installing the Profile Migration Tool
When you install the client adapter software, the Install Wizard automatically installs the profile migration tool, unless your system administrator used an administrative tool to prevent its installation. It is saved in the same directory as ADU.
Running the Profile Migration Tool
Follow these steps to run the profile migration tool to migrate your 350 and CB20A profiles to CB21AG/PI21AG profiles.
Note The best time to run the profile migration tool is immediately after the Install Wizard has installed the client adapter software.
Note The following conditions must be true before the profile migration tool can be run successfully:
- Your computer must contain the 350 and CB20A profiles that you want to migrate.
- ADU must be installed on the same computer but must not be running during the profile migration.
- A CB21AG or PI21AG client adapter must be inserted into your computer.
Step 1 Perform one of the following:
•If the profile migration tool runs automatically after the Install Wizard installs the client adapter software, go to Step 4.
•If you want to manually activate the profile migration tool, open the Windows Command Prompt from Start > Programs > Accessories. Go to Step 2.
Step 2 Use MS-DOS commands to access the directory where the profile migration tool (PMT.exe) is located on your computer.
Step 3 Type PMT and press Enter. The profile migration tool runs and displays the results.
Note See the "Command Line Options" section below if you want to alter the behavior of the profile migration tool before running it.
Step 4 Reboot your computer.
Step 5 Open ADU. Your migrated 350 and CB20A profiles now appear as CB21AG/PI21AG profiles on the Profile Management window and are ready for use.
Step 6 If desired, you can view the log file generated by the profile migration tool. This file shows the profiles that were processed, their status, and the reason why any profiles were not migrated.
Note Unless you changed the default name and location of the log file using the -logfile command, you can find the log file at C:\migrate.log.
Step 7 If desired, you can remove the profile migration tool from your computer.
Command Line Options
These command line options can be used to alter the behavior of the profile migration tool. The correct format is PMT -command.
Note Leave a space between multiple commands (such as -command -command).
•-AllowReRun—Enables the profile migration tool to be run multiple times. When you rerun the tool, it migrates all the existing profiles, even the ones that were already migrated. If you have modified any of the previously migrated profiles, the modifications are lost.
Note If you do not use this command, you can run the profile migration tool only once. If you attempt to run it again, a message appears indicating that the profiles have already been migrated and that the tool does not need to be run again.
•-CardOrder <cardtype> <cardtype>...—Specifies the order in which profiles are migrated when multiple client adapters are selected.
Example: PMT -CardOrder -pci350 -pcmcia350
•-CB20A—Selects only CB20A profiles for migration. This command can be used alone or in conjunction with the -CardOrder <cardtype> <cardtype>... command to specify the order in which client adapter profiles are migrated.
Examples: PMT -CB20A
PMT -CardOrder -CB20A -pcmcia350
•-ConfigFile <filename> <filename>...—Enables you to run the profile migration tool using multiple command lines that are specified within one or more configuration files. You can create the configuration file(s) using a text editor such as Notepad. To do so, simply type the desired commands (such as -miniPCI -replace) in the text editor and save the file. (Do not include PMT when typing the commands in the text editor.) After you have created the configuration file(s), use the -ConfigFile command with the file(s) you created.
Examples: PMT -ConfigFile filename1.txt
PMT -ConfigFile filename1.txt filename2.txt
Note If more than one file is specified, the profile migration tool performs all its functions for each file. It ignores all other command line options and executes only the options in the file(s) in order to prevent confusion regarding command priority.
•-logfile <logfile name>—Enables you to change the name and location of the log file, which identifies the migrated and unmigrated profiles after you run the profile migration tool. The default name is migrate.log, and its default location is the system drive root (for example, C:).
Examples: PMT -logfile logfile.log
PMT -logfile C:\Cisco Aironet\migrate.log
Note If you specify a new location for the log file, that location must already exist. Otherwise, the file is saved to the system drive root (for example, C:).
Note If the -logfile command is used without the <logfile name> parameter, a log file is not generated.
•-miniPCI—Selects only 350 mini PCI profiles for migration. This command can be used alone or in conjunction with the -CardOrder <cardtype> <cardtype>... command to specify the order in which client adapter profiles are migrated.
Examples: PMT -miniPCI
PMT -CardOrder -CB20A -miniPCI -pci350
•-pci350—Selects only 350 PCI profiles for migration. This command can be used alone or in conjunction with the -CardOrder <cardtype> <cardtype>... command to specify the order in which client adapter profiles are migrated.
Examples: PMT -pci350
PMT -CardOrder -miniPCI -pci350
•-pcmcia350—Selects only 350 PCMCIA profiles for migration. This command can be used alone or in conjunction with the -CardOrder <cardtype> <cardtype>... command to specify the order in which client adapter profiles are migrated.
Examples: PMT -pcmcia350
PMT -CardOrder -pcmcia350 -pci350
•-replace—Causes legacy profiles with the same name as existing CB21AG/PI21AG profiles to replace the existing profiles. This command is intended to minimize the number of similarly named profiles on your system.
For example, if both a 350 PCI legacy profile and a CB21AG profile have the same name (such as Office), the legacy profile replaces the CB21AG profile, resulting in only one Office profile. If this command is not used, you have two profiles after migration: Office and Office_b.
Note If you have multiple legacy profiles with the same name (such as Home), only one Home profile is available after migration.
Uninstalling the Profile Migration Tool
The profile migration tool is uninstalled automatically when the client adapter software is uninstalled. If you want to uninstall only the profile migration tool, find the PMT.exe file in the directory where ADU is installed and delete it.