Export (0) Print
Expand All

Appendix A through E

On This Page

Appendix A: Sample Customization Screens
Appendix B: ISP Sign-up Options
Appendix C: The Connection Manager Administration Kit
Appendix D: Creating a Pilot Program
Appendix E: Internet Explorer 5 Quick CD-ROM Deployment Guide

Appendix A: Sample Customization Screens


Figure 1: CD Autorun Screen showing custom CD Autorun bitmap and title bar text.


Figure 2: CD Autorun Screen showing title bar text and left setup bitmap.


Figure 3: CD Installation wizard showing top banner bitmap and component choices.


Figure 4: Customized browser showing title bar text, animated and static logo area in top-right corner. Custom toolbar buttons and background watermark are not shown, but would appear here.

Appendix B: ISP Sign-up Options

Automatic Connections

Automatic Connections can be configured on a user's workstation to automate the remote connection process. The ability to include a pre-configured dial-up connection to your RAS server significantly reduces the administrative overhead associated with supporting these connections. There are two different ways to create an automatic dial-up connection with your Internet Explorer 5 package: Creating Dial-up Networking (DUN) entries, or using the Connection Manager Admin Kit (CMAK). The trade-off between these two approaches is between simplicity and features. Creating or importing an existing DUN connection is a very easy way to set up an automatic connection, but it does not offer all of the customization options available from the CMAK. This Appendix is intended as a discussion of the merits and ramifications of each approach; technical specifics can be found in the IEAK Help file, Appendix C and the Customization wizard walkthrough.

Importing a Connection

The easiest way to set up an automatic connection is to create your DUN RAS settings on the IEAK workstation, and then import these connection settings during the Customization wizard. For ISPs, DUN connections can also be created during the sign-up process, and this is the recommended method. Importing a connection will create a DUN entry on each user workstation to match those on the IEAK workstation. Dial-up, protocol and proxy settings for each connection will also be imported. If more than one DUN entry is imported, the default connection will also be made the default on the user workstation. The primary advantage of this approach is that it is very easy. DUN entries are usually familiar to both users and support technicians, which helps to reduce both the learning curve and administrative overhead. Imported DUN entries can be used in conjunction with a user's existing DUN entries, such as a business RAS dialup.

The sign-up process can be used to create new DUN entries on the user's workstation. Both serverless and server-based sign-up deliver a customized Internet Settings (.ins) file that can contain the information necessary to create a DUN profile. Server-based sign-up using the Internet Connection Wizard (ICW) can also preconfigure the user name and password.

DUN entries are the recommended connection method for ISPs. By using a sign-up server, the customer can select a local dialup number, which is then used for day-to-day access. The DUN entry will become the default for Internet Explorer and Outlook Express, and will dial automatically when these applications are run.

The Connection Manager Administration Kit

The CMAK is the tool used to create and administer Connection Profiles for Microsoft Connection Manager. Connection Manager is a client application similar to DUN that supports multiple phone numbers per Connection Manager profile; the ability to run applications automatically before, during and after a connection takes place; and Virtual Private Network support. Connection Manager is part of Internet Connection Services for RAS, which is in the Windows NT® Server 4.0 Option Pack. Connection Manager can be integrated with Connection Point Services for Windows NT. Connection Point Services consists of a phonebook administrator and a phonebook service that can be used to automatically configure, administer and dynamically update connection numbers to a client Connection Manager profile.

The advantages of creating automatic connections by using the CMAK are support for multiple phone numbers per connection profile, and the ability to configure connection actions and auto-applications. This option would be desirable for organizations that have numerous RAS sites that their users need to connect to, or for organizations that need to constantly update a pool of dial-up numbers. A Connection Manager profile can be configured with custom bitmaps and license agreements, auto-applications, connect actions, Help files, user documentation and command-line parameters.

The primary disadvantage of using the CMAK is the added complexity of correctly configuring a Connection Manager Profile. Although static phonebook entries can be used, Microsoft Connection Services are required to administer multiple phone book entries. Connection Manager profiles are different from DUN entries, and will require both users and administrators to learn how to use them. The use of auto-applications and connect actions can be useful to an organization, but can increase the occurrence of tech support calls if they don't work as the user expects, or cause a software conflict (such as having both Outlook Express and Microsoft Outlook running at the same time). If, however, an organization is already using both Connection Manager and Connection Point Services, then a CMAK profile can be integrated into an Internet Explorer package with a minimum of administrative overhead. Detailed information on the CMAK can be found in Appendix C, and in the CMAK documentation.


ISPs can specify how users sign up with their service and connect to the Internet. Sign-up is the process of collecting information from the user and then using that information to customize browser and connection options. Sign-up can be handled in four different ways:

The server-based sign-up server using the Internet Connection Wizard (ICW) is the recommended method for signing up users. The ICW acts as a shell, displaying a series of customized active server pages that accept user information, billing data and location information, and then customize a DUN connection for the user. Examples of ICW-based sign-up files are included in the IEAK Toolkit.

The server-based sign-up server using a kiosk mode start page option dials a default (usually toll-free) number, then displays a series of Web pages that collect account and billing information from the user. This information can be integrated into an existing user database by using CGI or ActiveX scripts. Once this information has been collected, the sign-up server returns a customized Internet Setting (.ins) file that configures the browser settings and creates a DUN connection profile automatically. Once sign-up is complete, the browser will be configured with a local dial-up number as well as account and password information for that user. A server-based sign-up page that does not use the ICW must be run in kiosk mode. This is a good option for ISPs that already have a sign-up page that they do not want to change.

The serverless sign-up option configures account and connection information, but doesn't require a sign-up server. If you select the serverless method, the Internet Explorer Customization wizard prompts you to provide the necessary information to control all aspects of the sign-up process. If you choose this option, you'll be prompted for connection information. A separate configuration file will be generated for each set of connection settings, and these configuration files are included locally with the browser installation package. When users start the browser for the first time, they are shown a local HTML sign-up page that prompts them to choose between connection options, and then configures the browser and connection settings.

The serverless sign-up option is appropriate if the ISP has only a few dial-up locations for the user to choose from, and does not want to automate the collection of new customer information by the browser by setting up a sign-up server.

The no sign-up method is used if an ISP doesn't want users to go through a sign-up procedure when they install their custom browser. This option works for ISPs that have a single dial-up location and will be manually providing account and password information to users. An automatic dial-up connection profile can be created by importing connection settings from the IEAK workstation. This is also a good option if the ISP has a sign-up process in place that does not integrate with the IEAK.

Internet Sign-up Using the Internet Connection Wizard

The ICW uses a series of eight .asp pages to collect user information. During the ICW, the user enters account and billing information, chooses an account name and password, and selects billing information. The ICW writes this information to a database, then returns an Internet Settings (.ins) file to the browser. This .ins file configures the browser with configuration information and branding information, and creates a DUN profile configured with a local dialup, account information and a password.

The sign-up process happens in three steps:

  1. The new customer connects to your sign-up server. A file called ICWsign.htm is included in the Internet Explorer package, as well as a connection settings file called signup.isp. The ICWsign.htm file is used to select a local dial-up connection so that the ICW can connect to the server-based sign-up files. The signup.isp file contains the settings for this initial connection. The purpose of using the ICWSign.htm start page is to allow the browser to connect to the sign-up server without having to make a toll call. ICWsign.htm could give the user the choice of local call numbers, or use a single toll-free number.

  2. Once a connection has been made to the sign-up server, the ICW runs eight sign-up HTML files and collects information from the user and adds the customer information to your customer database. The location for these files is specified during the Customization wizard.

  3. Your server creates and passes an .ins configuration file back to the customer's computer. This file includes information about configuration and branding. It also includes a local phone number so the customer can access the ISP.

Note that if the user's Security options are set to High, the sign-up server will not work, because the necessary files will not be downloaded.

Samples of ICWsign.htm and the eight HTML files that are used by the ICW are included in the \ieak\toolkit\ISP\Server\ICW subdirectories. Specific directions on how to customize each page of the ICW are available in the Internet Explorer HTML Help by searching for "Internet Connection Wizard."

Sign-up Files


This wizard page imports the ICWsign.htm file into the Internet Explorer package. ICWsign.htm provides the user with a series of connection options for the initial, temporary connection to the ISP's sign-up server. ICWsign.htm prompts the user to select a connection option, and then uses an .isp file to create the temporary connection. The .isp files can be imported in this page, or they can be created and/or modified by selecting the .isp check box. The .isp connection files also contain a reference to the Signup01.htm file that is to be used by the ICW.

Sign-up Server Information


This page is used to create new .isp connection pages, or to edit pages that were imported in the previous wizard screen. These are temporary connections that are used solely to connect to the sign-up server. Permanent DUN connections are created as .ins files by the ICW based on information gathered during sign-up.

Each .isp file contains a reference to the URL location of the signupX.asp files that the ICW will use to collect user information, set up billing information and configure the browser. Examples of these files are in the \ieak\toolkit\isp\server\icw\asp subdirectory. PERL-based sign-up files are also available. The ICW acts as a shell for these sign-up files.

Information on the configuration and deployment of the ICW signup.asp pages is in the IEAK Help.

The Advanced button can specify advanced connection configuration information, such as DNS, Compression and Encryption settings.

A support phone number can be entered that will be available during the ICW process.

Internet Settings Files


Permanent Settings files can be created and integrated with the ICW. Specific instructions on how to create and reference these files within the ICW signup.asp pages is available in the Internet Explorer HTML Help.

Internet Connection Wizard


Just like the CD Autorun customizations, the ICW can be branded with a custom title bar, top logo and left logo.



Title Bar Text

Enter the text that will appear in the ICW title bar.

Top Image

The Top Image size must be 49 X 49 pixels.

Left Image

The Left Image size must be 164 X 458 pixels.

Internet Sign-up Server Using Kiosk Mode

The server-based sign-up process is a Web browser-based mechanism that automates the task of adding new customers to your customer database. The sign-up process happens in three steps:

  • The new customer connects to your sign-up server.

  • An HTML/HTTP-based dialog box collects information from the user and adds the customer information to your customer database.

  • Your server passes an .ins configuration file back to the customer's computer. This file includes information about configuration and branding. It also includes the local phone number so the customer can access the ISP.

Note that if the user's Security options are set to High, the sign-up server will not work, because the necessary files will not be downloaded.

After the customer has provided you with the information you need, you must return the following information to the customer:

  • Data for configuring Internet connections

  • Capabilities of the customer's account (including e-mail and newsreaders)

  • Branding information

This information must be passed back to the computer in an IEAK profile, or .ins file. The IEAK can create an .ins file for each specified dial-up location during the Customization wizard, and these settings can be edited manually as appropriate. Some settings, such as Entry, User, Phone, Device, Server and TCP/IP, cannot be specified in the wizard, but can be customized by using HTML scripts.

If you want to provide a variety of custom "private branded" versions of Internet Explorer (containing such items as custom logos, title bar, Favorites, Search bar, start page, special links on the Links bar and the location for online assistance) to different customer groups, you should maintain a variety of sets of branding information on the server for downloading in the .ins file. This means that all of the compact discs you send out will be the same, but they will be branded differently when the user signs up. This eliminates the potential for a large inventory problem.

The Server-based sign-up process is an extremely versatile tool that can be customized far beyond the examples included in the \toolkit\isp\server subdirectory. More information on how to customize and deploy an Internet Sign-up Server are included in the IEAK Help file and the \toolkit\isp\server subdirectory.

Custom Sign-up Files


This is the first page in the "Server-based sign-up using kiosk mode" track.

This page imports the Signup.htm file into the Internet Explorer package. Signup.htm is run in kiosk mode the first time that Internet Explorer is started after installation. The Signup.htm file gives the user the option to connect to the ISP and includes a link to the .isp connection file. The connection (.isp) file contains two main sections: all of the connection information necessary to dial the sign-up server, and the URL of the actual sign-up home page. Signup.isp will be created by the next Customization wizard screen.

Signup.htm and Signup.isp are used for a one-time connection to the ISP, and then are used to run a kiosk-mode sign-up page. The kiosk-mode sign-up page is specified toward the beginning of the Customization wizard.

Sign-up Server Information


This page creates the signup.isp file that is referenced by the Signup.htm file specified in the previous page. Signup.isp contains the connection information necessary to dial the sign-up server, a guest username and password, and the URL of the sign-up pages. There are two ways to specify sign-up locations so that users will not have to make a toll call to connect to the sign-up server:

  • The administrator can create multiple .isp files, and reference each of them in Signup.htm by area code.

  • The administrator can use a toll-free number for sign-up.

The customer will not permanently use the phone number specified in this screen. The permanent dial-up number will be created in the next Customization wizard screen, and will be passed to the user in a customized .ins file at the end of the sign-up process.

The Advanced Options button allows the administrator to specify advanced dial-up options, such as DNS, Compression and Encryption settings.

Once the temporary connection is established, the .isp file will run the URL specified here. This is the first page of the ISP's HTML-based sign-up process.

Internet Settings File


The Internet Settings files (.ins files) created in this page contain the permanent dial-up connection settings that will be passed to the users. This page creates an .ins file (specified in the file name entry) that contains all of the branding and configuration information from the Customization wizard, as well as the connection information specified here. This .ins file is passed to the browser at the end of the sign-up process and can be configured with user-specific information such as account name, password and connection location.

This page is used to pre-build location-specific customized .ins files for the administrator's convenience. Further user-specific customizations from information in the sign-up pages can be added by CGI or ActiveX scripts. Examples of how to do this are included in the \toolkit\isp\server subdirectory.

Serverless Sign-up

The serverless sign-up process presents a user with several pre-created configurations in an HTML sign-up page that is automatically displayed after package installation. These sets of configurations are stored in a .ins file that is created during the IEAK wizard. Internet Explorer takes the settings in the .ins file and uses them to configure options from the Customization wizard, including browser branding and options, policies and dial-up connection settings. The serverless sign-up process enables ISPs that will not be using a sign-up server to provide customized connection options to customers.

Note: No information from the serverless sign-up process is returned to the ISP. The ISP will need to give the user a dial-up account name and password, as will also have to collect all necessary billing and account information from the customer by other means.

In the serverless version, the configuration file is created by the IEAK before the package is shipped, and it is included in the installation package. Therefore, the configuration file contains no user-specific configuration information. A sign-up HTML file, Signup.htm, is run automatically by the browser in kiosk mode the first time that Internet Explorer is run. The sign-up page gives the user the option to select one or several configuration options. These options are linked to .ins installation files that can configure the installation and create a Dial-Up Networking entry based on that configuration option. The \toolkit\isp\servless subdirectory contains examples of single and multiple installation options that can be customized and then included in the sign-up package.

If you are creating multiple customized versions of Internet Explorer and have many settings that stay the same across several or all versions, you can simplify the process. For more information, see "Creating Multiple Versions of the Browser" in the IEAK Help.

Serverless sign-up runs only in kiosk mode, and works only for CD distributions. Web distributions should use a server-based sign-up page. The kiosk mode start page, signup.htm, must be specified at the beginning of the IEAK Customization wizard.

Serverless Sign-up Files


This imports the Signup.htm file into the Internet Explorer package. Signup.htm is the HTML page that will run in kiosk mode the first time that Internet Explorer is started. Check the c:\program files\ieak\toolkit\isp\servless subdirectory for examples of Signup.htm. Signup.htm will contain one or several links to Internet Settings files (.ins). These .ins files will either be created by the IEAK in the next Customization wizard page, or created in advance and copied to the folder specified here. .Ins files are text files that contain all of the branding information from the Customization wizard, as well as entries for creating a Dial-Up Networking entry. Specific examples on how to customize the Signup.htm and .ins files are at the bottom of the "Serverless Sign-up" section.

The Customization wizard will create a new .ins file for every dial-up connection that the administrator configures. The need for different configuration options based on dial-up location is the most common use of serverless sign-up, but the .ins files can be used to separately configure other installation options as well. For instance, the Signup.htm file could let users choose from different branding options, color options or sets of Favorites.

Sign-Up Server Information


This is the wizard screen that is used to generate the customized .ins files that are linked in the Signup.htm file. These .ins files are created automatically by the IEAK and included with the Internet Explorer package along with any .ins files that were in the Signup.htm path specified in the previous wizard page. The .ins file will configure the Internet Explorer installation, and create a Dial-Up Networking entry with the settings specified here. Multiple .ins files can be created by selecting the Add button.

Serverless Signup.htm Screen Example


This screen is an example of the Signup.htm file that is run automatically in kiosk mode the first time that Internet Explorer is run. This page contains a single button that links to the .ins file created in the IEAK wizard. This screen is a customized example of the demo files included in the \toolkit\isp\servless\oneINS subdirectory. Multiple connection locations can be specified by creating multiple .ins entries in the Customization wizard, and then configuring the example in the \toolkit\isp\servless\multiINS subdirectory to refer to these .ins files.

Serverless Signup.htm Text Example


This screen shows an example of the text references used to customize the Signup.htm file. This example is a customized copy of the example included in the \toolkit\isp\servless\oneINS subdirectory. Note that in the highlighted section the Seattle.ins file created in the IEAK Customization wizard is the referenced as the action for the "Click the button" entry. A user could choose from multiple .ins files, as shown in the \toolkit\isp\servless\multiINS subdirectory.

No Sign-up

The No Sign-up option is a flexible option that can be used under several circumstances. This option can be used if the ISP is using a sign-up method that cannot be integrated with the IEAK Sign-up process, or if no sign-up is to be used.

Appendix C: The Connection Manager Administration Kit

Connection Manager provides a graphical interface so that a user can connect to their service using connection features that the administrator defines. These features are defined using the Connection Manager Administration Kit (CMAK), which supports the creation and updating of multiple versions of Connection Manager, each of which the administrator should define to meet the needs of a specific target audience. The CMAK can be used to create a Connection Manager profile on a user's desktop. A Connection Manager profile is similar to, but not the same as, a Dial-up Networking connection. See Appendix B for more discussion on Automatic Connections.


This screen allows the administrator to create a new profile or edit a previously created profile. For the profile to be visible to the CMAK, it must be located in the Profiles subdirectory in the C:\program files\cmak directory.


Each profile has a friendly service name and a profile file name. The files are limited to 40 and 8 characters, respectively.


If an administrator has existing service profiles that already contain information needed in the service, that information can be included by merging those service profiles with the service. .Each time the CMAK wizard is run, administrators must specify whether they want to create a new service profile or edit an existing one. Merging a profile is useful if there is an existing phone book or configuration information to add to a new profile, without editing the old one.


The support information entered here is displayed every time the Connection Manager is run.


Administrators can specify a realm name prefix (such as AcmeISP/) or suffix (such as to be added to the user name that a user enters when connecting to the service. The realm name includes any separator characters, such as @ or /. If the realm is specified, users do not have to type it.

Note: Realm names are typically not used by ISPs.


The administrator can create Dial-up Networking (DUN) entries that match certain phone numbers in the Connection Manager phone book. This is a separate feature from importing or creating DUN connections in the IEAK. To set up custom DUN entries for a particular POP, administrators associate DUN entries set up in the phonebook file (.pbk) with the DUN entries set up in the service profile. Before running the CMAK wizard, administrators must define the entries to set up with custom DUN, and the options to use for each. The following information must be specified for each entry that will be customized:

  • The name of the phonebook DUN entries to customize. This entry must match the phonebook DUN entries in the phonebook. If a phonebook is not being used, the DUN entries name must be the same as the service name. For example, to create a custom DUN entry for a service profile name ACME ISP that has no phonebook, administrators would specify "ACME ISP" as the Phonebook DUN entry on the worksheet and in the CMAK wizard.

  • Whether or not to use the server-assigned address or to use specific Domain Name System (DNS) and Windows Internet Name Service (WINS) addresses. To assign specific addresses to the DUN, administrators can specify both primary and secondary DNS and WINS IP addresses.

To use server-assigned addresses, end-point servers running Windows NT Server must be configured to use the Dynamic Host Configuration Protocol (DHCP) to automatically assign remote TCP/IP client IP addresses.


The secure connection feature uses Point-to-Point Tunneling Protocol (PPTP) with Microsoft Point-to-Point Compression (MPPC) and Microsoft Point-to-Point Encryption (MPPE). To use secure connections, there must be a PPTP server on the network side.


To set up the service profile to automatically start programs or install software when a user connects to the service, administrators must correctly specify the connect-action programs when running the CMAK wizard. These actions, especially post-connect actions, should not be confused with auto-applications. A separate wizard screen is provided for running applications automatically after connection.

Pre-connect actions run immediately after the user selects connect, but before any connection actually takes place.

Post-connect actions run after establishing the DUN connection. Some post-connect actions, such as automatically updating phonebook entries and using MCIS logon information, have been pre-configured into the post-connect dialog box that follows.

Disconnect actions run immediately after disconnecting.


Pre-connect actions run immediately after the user selects connect, but before any connection actually takes place.


Post-connect actions run after establishing the DUN connection. Some post-connect actions, such as automatically updating phonebook entries and using MCIS logon information, have been pre-configured into the post-connect dialog box.


Disconnect Actions take place after a service has been disconnected.


The Auto-Applications screen is used to run applications automatically when a user connects to the service. Auto-Applications are different from Connect Actions in that when an Auto-Application is closed, so is the connection. Each application can be run with parameters specified during the Add and Edit dialog boxes:


Administrators can include the program in the service profile, but the only program included will be the executable itself. Any additional files needed to run the program will need to be in place on the user's machine for the program to work. If the Include box is not checked, then the Connection Manager will attempt to run the program from the same location as on the IEAK workstation.


This screen allows administrators to use the default logon bitmap or to specify one. The bitmap must be 256 colors, 330 X 131 pixels.


The Phonebook Bitmap is a 114 X 304-pixel bitmap that appears on the left side of the Phone Book dialog box. If no bitmap is specified, then the default bitmap will be used.


In addition to the CMAK, the Microsoft Windows NT Server 4.0 Option Pack contains Connection Point Services. Connection Point Services provides support for creating, maintaining and updating Phone Books. Administrators can also create Phone Books, but the complexity of the format and requirements makes this difficult if there is more than a single POP. Search the CMAK Help file for the words "phone book" for detailed instructions on creating and configuring Phone Books, either manually or with Connection Point Services.


The administrator must specify the .ico files to use for the Program, Title bar and Status-area icons.

Note: These files are icon (.ico) files and not bitmap (.bmp) files. If no custom icons are specified, then the default icons will be used.


Administrators can customize the pop-up shortcut menu that users receive when they right-click on the Connection Manager status-area icon. This dialog box allows the administrator to add additional programs to the shortcut menu. Possible uses for this feature could be a virus-checking program, traffic analysis tool or shortcuts to Internet Explorer and Outlook Express.


The administrator can specify a custom Help file or use the default Connection Manager Help file.


This dialog box allows the administrator to specify whether the Connection Manager software is included in the profile. The Connection Manager software adds about 400K to the size of the profile, for a total of 500K. Including the software is a good idea because it ensures that users have the latest version and are using a consistent version of the Connection Manager software.


The administrator can include a customized license agreement in the connection manager profile. The license agreement must be saved as a text (.txt) file.


The administrator can add to the service profile other files that users should have, such as supporting files for connect actions. When these additional files are specified in the CMAK wizard, the service profile copies the files to the Connection Manager folder. Some advanced customization techniques require administrators to include files in the service profile. When administrators make advanced customization decisions, they should add any files required by those decisions to this list of additional files. For example, all the files required to provide any user documentation or customized error handlers should be included as additional files. For more information on advanced customization techniques, see the CMAK Help file.


Once the package has been generated, it will be automatically added to the Internet Explorer custom package. The package will be saved to c:\program files\cmak\profiles\<profile name>.

Appendix D: Creating a Pilot Program

The following outlines steps ISPs follow to create an abbreviated pilot program. These steps are a subset of the steps that a corporate organization would use to set up a production-level pilot for a line-of-business application deployment.

It makes good practice to prepare a test plan and checklists for lab tests, and then use the checklists to record satisfactory completion of tasks and note all problems with the process. Also, prepare a checklist to test each deployment and distribution strategy.

ISP Lab Deployment Steps:

Prepare custom packages for deployment:

  • Install and run the IEAK Configuration wizard.

  • Build custom packages containing the distribution files.

  • Configure browser automatic configuration (.ins, .js, .pac) files.

  • Configure download sites and install the distribution files.

  • Copy distribution files to compact discs and floppy disks.

Deploy custom package to lab clients:

  • Run Internet Explorer 5 Setup to install the custom package on each client.

  • Install using each available user install option.

Operate lab client software after custom package is installed:

  • Test sign-up procedure, if used.

  • Run Internet Explorer to test all add-ins and features.

  • Run business applications to check for satisfactory operation.

Restore lab clients to their original state:

  • Uninstall Internet Explorer 5 and add-ins.

  • Verify that Internet Explorer components have been removed.

  • Test the desktop and business applications.

Administrators should prepare a test lab and then test the proposed deployment strategies on lab computers that represent typical client configurations for the ISP. If an ISP has customers with vastly different computing environments or needs, administrators may need to prepare multiple test labs and conduct tests at several different sites.

Appendix E: Internet Explorer 5 Quick CD-ROM Deployment Guide


This guide will produce a package for deployment on CD-ROM. A typical customer installation would go as follows:

  • The user inserts the CD-ROM into the PC, and the Installation wizard walks the user through the license agreement and other installation options.

  • A branded and customized Internet Explorer package will be installed on the user's PC. After the Installation wizard is completed, the user is prompted to reboot the PC.

  • The first time that Internet Explorer is run, a sign-up page will automatically run in kiosk (full-screen) mode.1 This sign-up page will give the user the option to choose a local dial-up connection number. Once this option is chosen, Internet Explorer will configure itself and create a default dial-up networking connection.

    Internet Explorer is now installed and configured on the user's PC. The installed code will include:

    • Internet Explorer and any additional components specified by the administrator.

    • Outlook Express, pre-configured with necessary e-mail and Usenet settings.

    • An automated dial-up networking connection, configured as the default for the browser.

Including the sign-up page with the browser code is known as "serverless" sign-up. The IEAK also supports "Internet Signup Server" customization, which allows the ISP to collect account and billing information, integrate this information into an existing customer management system, and then customize Internet Explorer with branding and connection information. More information on deploying an Internet sign-up server can be found in the IEAK Help file, the full IEAK deployment guide, and the sign-up examples included in the IEAK \toolkit subdirectory.


The following checklist can be used to gather the necessary information before using the IEAK 5. An asterisk (*) denotes required information. More information about specific components can be found in the Glossary.






How To Deploy a CD-ROM Distribution Package

The IEAK generates a CD subdirectory in the c:\builds folder. The Windows Explorer view of your generated packages should be similar to this:


Copy everything from within the c:\builds\<build_number>\CD subdirectory onto the root of the master CD. The root of the CD-ROM will contain the Win32 subdirectory, Autorun.inf, and a setup file. All necessary sign-up and configuration files are contained within the installation .cab files.

The 10-Minute Walkthrough

The IEAK Customization wizard can be easily completed in 10 minutes by following this walkthrough. Accept the default for any screen that is not shown here, or does not require information that was gathered in the checklist.

Welcome Page




Accept the values on the current page and move to next page.


Display any previous page. May have to retype some of the values you've entered.


Exit this package.


Need more information about using a page or specific feature.


Company Name and Customization Code




Company Name

Type the name of your company. This information is put in the Registry for identification.

Customization Code

Type the code you received from Microsoft at the IEAK Web site.

Get Customization Code

Selecting this option will take you to the Microsoft IEAK registration Web page. At this page you will be able to register your copy of the IEAK and receive a customization code.

The title that best fits your role

Because the customization code is specific for your role, the wizard automatically selects Content Provider. Be sure to select Service Provider option to receive all of the necessary wizard options for Service Providers.

Platform Options


The next screen allows administrators to select the platform version of Internet Explorer 5.

File Locations




Destination folder

This is the location that the packages will be placed in after the wizard is finished.

Language Selection


Localized versions of the Internet Explorer package can be created by selecting a language from the pull-down box. The wizard must be run once for each localized version that is created.

Media Selection


Select the CD-ROM media type only. Distributions via other media types are covered in the full IEAK deployment guide.

Feature Selection


You can determine which remaining screens of the Customization wizard are displayed by selecting or clearing the check boxes in this screen. This will make it faster and easier to complete the Customization wizard. Checking or clearing these boxes will not affect functionality; rather, these boxes will determine which items in the IEAK Customization wizard you can customize. Clear all boxes except the following:

  • Setup Customizations

  • Browser Customizations

  • URL Customizations

  • Favorites and Links

  • Sign-up Settings

  • Outlook Express Customization

Automatic Version Synchronization


Use this screen to synchronize the individual Internet Explorer components to the latest versions. It is recommended that all components be synchronized before continuing the wizard, but this is not required.

Note: Synchronization time will depend on the type of connection available and number of components that are synchronized. Synchronization time for 70 MB of Internet Explorer components over a modem is not included in the 10-minute completion goal for this paper.

CD Autorun Customization


This screen can be used to customize several different CD Autorun items, but the two that are most easily customized are the CD Autorun title bar text and custom background bitmap. These two items are used to identify the ISP before the Installation wizard actually begins.



Title Bar Text

This is the text that goes in the CD Autorun title bar.

Custom Background Bitmap Location

You can provide a bitmap that appears behind the text. Make sure the background color doesn't conflict with the text color. This bitmap must be 540 X 347 pixels.

More CD Options


This screen allows you to specify a "more information" text file, as well as the kiosk mode sign-up page that is seen when Internet Explorer first runs. The path to the serverless sign-up page, signup.htm, is specified in here.

Customize Setup


Add the Setup wizard title bar text that was collected in the IEAK Checklist.

Installation Type


These installation types will be available to the user when installing Internet Explorer. Remove undesired options by selecting the option, then the Delete key. Some organizations may wish their customers to have the ability to choose an installation type; others may wish to only support a specific set of features. The ability of the user to add or remove components from an installation type is determined later in the Customization wizard.

Browser Title


Check the Customize Title Bars button, and add your company name. The browser title bar will read "Microsoft Internet Explorer provided by Your ISP" in this example.

Important URLs


The two items that can be most easily customized in this page are the Home Page and Support page URL. These items were collected in the Checklist and should be entered here.

Note: The IEAK does not check the validity of these sites. Double-check the entries to make sure that they are typed correctly.

Favorites and Links


There are two ways to pre-populate a set of Favorites in Internet Explorer. The first is to select the Add URL button and manually enter a name and address for each Favorite. An easier and more reliable way is to edit the Internet Explorer Favorites on the IEAK workstation, and then import these Favorites by selecting the Import button.

Sign-up Method


Select serverless sign-up as the sign-up method. Serverless sign-up will include an HTML page, signup.htm, in the browser package. Signup.htm will give the user a choice of dial-up locations. Once the user selects a local dial-up, signup.htm will return an Internet Settings (.ins) file to the browser that will configure the browser and create a dial-up networking connection.

You can also select the No sign-up option at this point. Selecting No sign-up will configure the browser with the settings specified during the customization wizard. This option would be appropriate for an organization that already has a sign-up procedure in place, or one that is providing a browser to clients with pre-existing Internet connections.

An example of the Signup.htm file is included in the \ieak\toolkit\isp\servless subdirectory, and should be customized before proceeding past this point. Complete instructions on how to customize signup.htm are included in Appendix B, "Automatic Connections" and "Sign-up."

Serverless Sign-up Files


This screen imports the Signup.HTM file into the Internet Explorer package. Signup.htm is the HTML page that will run in kiosk mode the first time that Internet Explorer is started. Check the c:\program files\toolkit\isp\servless subdirectory for examples of Signup.htm. Signup.htm will contain one or several links to Internet Settings files (.ins). These .ins files will be created by the IEAK in the next Customization wizard page. .Ins files are text files that contain all of the branding information from the Customization wizard, as well as entries for creating a Dial-Up Networking entry. Specific examples on how to customize the Signup.htm and .ins files are in Appendix B, "Automatic Connections" and "Sign-up."

Sign-up Server Information


This is the wizard screen that is used to generate the customized .ins files that are linked to in the Signup.htm file. These .ins files are created automatically by the IEAK and included with the Internet Explorer package along with any .ins files that were in the Signup.htm path specified in the previous wizard page. The .ins file will configure the Internet Explorer installation, and create a Dial-Up Networking entry with the settings specified here. Selecting the Add button can create additional .ins files. Users use the signup.htm page to choose between these multiple .ins files.

The Advanced Options page allows the administrator to specify advanced connection settings, such as DNS, Compression and Encryption settings.

Outlook Express Accounts


Enter the DNS names for the mail and news servers in this page. These entries will configure Outlook Express for the user.

Wizard Complete


Congratulations! You have completed the IEAK Customization wizard. The Customization wizard will now generate all of the code necessary for a CD-ROM-based installation, using the files and settings that you have specified. Before deploying this installation to your customers, it should be tested on a few typical client machines to ensure that sign-up works correctly, and all of the files and logos are correctly formatted.

1 The user will need to provide account and password information to the dial-up networking profile.

© 2016 Microsoft