Before Internet Explorer is installed, you can use the Internet Explorer Customization wizard to preconfigure your custom packages to include automatic browser configuration and Automatic Detection. With these features, the users' computers can automatically locate the auto-configuration .ins file (which is maintained on your server) and use it to update browser configuration settings at a specified interval.
After Internet Explorer is installed, you can use the IEAK Profile Manager to maintain browser configuration settings on your users' computers. With the IEAK Profile Manager, you can open any auto-configuration .ins file and change settings, such as digital signature and security zone options.
You can also use the IEAK Profile Manager to enable automatic browser configuration if you didn't preconfigure this feature before installation. The Automatic Detection feature (if enabled) will locate the updated auto-configuration .ins file, or you can set the automatic browser configuration manually on client computers.
For more information about setting up automatic browser configuration and Automatic Detection, see Chapter 21, "Using Automatic Configuration and Automatic Proxy." For more information about setting up your servers for automatic browser configuration and automatic detection, see Chapter 13, "Setting Up Servers."
The Internet Explorer Customization wizard creates an auto-configuration .ins file for each custom package you build. By default, this file is named Install.ins, but you can rename the file for each custom package.
After you install the browser, you can use the IEAK Profile Manager to update configuration settings by opening the auto-configuration .ins file, changing settings, and then saving the file. The IEAK Profile Manager also keeps the companion files current each time you save the auto-configuration .ins file.
You can change two types of configuration settings:
The following illustration shows the Wizard Settings screen.
The default location for saving the auto-configuration .ins file is the
\build directory\Ins\operating system\language folder. For example, an English version of the .ins file that was created for the Windows 32-bit platform might be saved in the \Build1\Ins\Win32\En folder.
Before updating the configuration settings on your users' computers, you should copy the auto-configuration .ins file and the companion .cab files generated by the IEAK Profile Manager to a working directory and test the configuration. After you validate your changes, copy the new auto-configuration .ins file to your production server. The automatic browser configuration feature then updates the configuration settings on the users' computers.
When you update and save your configuration settings, the IEAK Profile Manager generates the following files:
The auto-configuration .cab files also contain information (.inf) files.
Each .inf file also contains version information. When you change configuration settings, the IEAK Profile Manager updates the affected .inf files and their version information and repackages the companion .cab files.
Internet Explorer downloads and processes the contents of the auto-configuration .ins file and makes the necessary configuration changes on the users' computers. Internet Explorer also downloads and unpacks the companion .cab files for the operating system to process. If the version number of the auto-configuration .ins file does not change, new .cab files are not downloaded. The version number consists of the date the .ins file was modified and the number of times the file has been revised.
If you have users with different needs or if you want to change some users' configuration settings independently of others, you can create multiple auto-configuration .ins files. You can use the IEAK Profile Manager to specify different configuration settings for each group and save them as individual usergroup.ins files, where usergroup is a unique name for each user group. The IEAK Profile Manager automatically generates the companion .cab files. For example, you could specify a unique configuration for the Finance Department and save the configuration as Finance.ins. The IEAK Profile Manager would then generate the necessary companion .cab files.
Note If you create multiple auto-configuration .ins files, make sure that your custom packages are configured to use the correct file. You can also use an automated server solution, which enables you to use multiple .ins files without rebuilding your custom packages. For more information about using an automated server solution, see Chapter 17, "Time-Saving Strategies That Address Diverse User Needs."
The IEAK Profile Manager uses a default set of Windows policy template, or administration (.adm), files to define the rules for system policies and restrictions. The .adm files and system policies and restrictions are standard features of Windows 32-bit and Windows 16-bit platforms. If you are familiar with .adm files, you can create your own templates to define additional restrictions. For more information, see your Windows documentation.
Using the IEAK Profile Manager, you can import your own custom .adm files and include them with your updated configuration settings. The IEAK Profile Manager generates an associated .inf file, using the file prefix for the custom .adm file that you import. For example, if you import a file named Custom.adm, a Custom.inf file is generated and added to the companion .cab files. For more information about using custom .adm files, see Appendix E, "Setting System Policies and Restrictions."
If you need to move the auto-configuration .ins file to a different production server, you can use the IEAK Profile Manager to update the URL for automatic browser configuration. If you set the auto-configuration .ins file to update at a specified interval, you must allow for two intervals after you update the URL for automatic browser configuration before the change takes effect.
The following illustration shows the Automatic Browser Configuration options.
You must copy any .cab files that are created in the build folder to the same folder that contains your .ins file.
When the user starts the browser and the configuration settings are scheduled to be updated, the pointer to the URL for automatic browser configuration is then updated on the user's computer. At this point, the browser is still using the settings from the original auto-configuration .ins file (for example, http://existing path/Default.ins).
When the user starts the browser a second time and the configuration settings are scheduled to be updated again, the browser reads the new auto-configuration .ins file (for example, http://new path/Default.ins). When you are sure that the settings on all users' computers have been updated, you can remove the copy of the auto-configuration .ins file from its original location.