Merging phone books and other features from existing service profiles
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Merging phone books and other features from existing service profiles
If you have information in existing service profiles that you need in the service profile you are building, you can use the Connection Manager Administration Kit (CMAK) wizard to merge much of the information from existing profiles into the profile you are building. A profile that contains information from other service profiles is called the top-level profile. A service profile that has its information merged into another service profile is called a component profile.
Why merge service profiles?
Merging service profiles is especially useful for incorporating information from multiple phone books, including service types, Point of Presence (POP) names, and access numbers, and to consolidate different Internet access points that are covered by more than one of your phone books. By merging existing service profiles into the service profile you are building, you can make several dissimilar networks appear to be a single, cohesive service.
For example, you can merge service profiles from different geographical locations to create a worldwide profile. Or you can create profiles that have specific administration requirements and network configurations, including authentication and TCP/IP characteristics and, after they are created, you can merge them together within a top-level service profile. Merging service profiles is especially useful where multiple entities, whether corporations or Internet service providers (ISPs), share in providing a service. The following examples show how you can use merged service profiles to simplify network access through diverse access points:
Example 1: Creating a service profile to support access to the Internet from remote service areas. If a local ISP contracts with a roaming consortium to provide dial-up services outside the ISP's primary service area, the local ISP could create a top-level service profile containing the local ISP's network information and merging the service profiles of the other members of the roaming consortium. Each component service profile could contain the individual phone-book and network attributes, including a unique realm name, of an individual ISP. Merging all of the component service profiles would support the need for users of the local ISP service to roam outside of the ISP's primary service area by enabling them to connect through the cooperating ISPs. All ISPs can maintain their own service profiles, simply redistributing profiles to other members of the consortium whenever they are updated. The consortium itself might also create a top-level service profile aggregating the services of all member ISPs.
Example 2: Implementing a corporate virtual private network (VPN). Corporations using VPN connections for a session by establishing a tunnel through the Internet to the corporation often use ISP-provided dial-up access to support corporate access from remote locations. By merging service profiles, the corporation could combine its own phone book of internal dial-up numbers with those of remote ISPs contracted to provide access points for the remote corporate users, enabling VPN connections to be established even for dial-up connections through the public network access point of the ISP. The corporation and each ISP could maintain its own service profiles, but the corporation could merge all of the ISP service profiles into the corporate profile. The distribution of the top-level service profile by the corporation to all corporate users would support access from multiple locations. This access would appear to users as if it were made using the corporation's own access points.
What information is merged
The following table shows which features of a component service profile are merged into the top-level service profile and how the CMAK wizard incorporates the merged information. Only the items from the component service profile that are listed in the Merged features column are recognized and used by the top-level service profile.
| Merged features | Implementation notes |
|---|---|
File name |
Files contained in the component service profiles retain the names used by the component service profiles. |
Merged profiles |
You can merge only one level of service profiles. For example, if you merge service profile A, which contains component profiles B and C, these second-level component profiles (B and C) are ignored. |
Realm name |
If a realm name is specified in the top-level service profile, it will be used in all instances, and all realm names specified in the component service profiles are ignored. If no realm name is specified in the top-level service profile, the realm names specified in the component service profiles are used for connections that are made using entries from the component service profiles. |
Dial-up entries |
The script specified for each dial-up entry must have a unique name than all other scripts contained in the top-level service profile and any component profiles. |
Phone books |
If the same service types exist in more than one profile, the information is merged. If duplicate states (or provinces), or POPs exist among top-level and component service profiles, Connection Manager removes the duplicates when it runs the top-level service profile. Connection Manager treats two phone book entries as duplicates if they display the same information in the user interface (except that Connection Manager is not case sensitive). If two phone book entries appear as duplicates but have separate configuration data in the POP, Connection Manager still removes one of the phone book entries. |
Download phone book |
Each time the user establishes a connection, Connection Manager automatically checks for the phone books with each server that is running Phone Book Service (PBS). PBS checks the phone book version and, if necessary, downloads phone book updates to the user. Phone books specified in the top-level and component phone books are downloaded, as appropriate to the respective service profiles. |
URL for downloads |
The URLs specified in the top-level and component service profiles are used for downloads to phone books for the respective service profiles. |
The top-level service profile does not merge information related to the following features of the component profile. To affect these features, you must specify them in the top-level service profile:
Service name
Support information specified for the logon dialog box
VPN support
Custom actions
Monitored applications
Custom graphics for the logon dialog box and Phone Book dialog box
Message to display next to the More access numbers box when alternate access numbers are available for the selected geographic location
Custom icons
Customization options for the notification area shortcut menu
Custom Help files
Option to include Connection Manager software in the service profile
License agreement
Additional files
Note
- To support VPN connections for component service profiles, in the VPN Support pane of the CMAK wizard, under Establish a virtual private network (VPN) connection when the user dials a phone number from these phone books, select the Phone books from the merged profiles check box.
Where the files are located
When you create a service profile, the CMAK wizard copies all files referenced in the service profile, including the component service-profile files, into the \Program Files\CMAK\Profiles\ServiceProfileFileName folder for that service profile.
When you use the CMAK wizard to merge features, the top-level service profile includes references to the component (merged) service profiles. For example, for phone books in merged service profiles, the resulting service profile installs multiple files in the folder specified for the profile rather than combining the phone books into a single file. However, when users select a POP involving phone books merged from two other service profiles, the users see the information from all the phone books as a single phone book.
When you edit a top-level service profile, the CMAK wizard attempts to use the latest version of the component service profile. If the CMAK wizard cannot find the merged service profile in the \Program Files\CMAK\Profiles\MergedServiceProfileFileName folder (for the top-level service profile), it uses the current version of the merged service profile that was originally stored with the service profile being edited.
Special considerations for building merged profiles
When building merged service profiles:
If you merge a Connection Manager 1.0 service profile into a Connection Manager 1.3 service profile, the CMAK wizard automatically updates the merged information to Connection Manager 1.3. Any changes you have made manually to the .inf file (using advanced customization techniques) will not be retained in the upgraded file. However, the CMAK wizard creates a backup of the old .inf file before creating the updated file.
You should provide separate service profiles for each network that has unique characteristics or requirements.
You must ensure that all scripts specified for dial-up entries in the merged service profile are available when you build the top-level service profile.