These release notes cover known issues with the Mission Control Desktop tools and technology. To view the Mission Control Desktop documentation and other information resources go to https://insight.netscape.com/insight/index/product/mission_control/documentation/index.html (DEAD link) - AOL removed it. You must be a member of Netscape Insight to do so. Netscape Insight is a private extranet site exclusively for authorized Netscape partners.

To view the release notes for Communicator 4.5, choose one of the following URLs:

• Windows
• Mac OS
• Unix

Configuration Editor

• Configure AutoUpdate URL
• Dynamically manage Communicator security
• Configure Messenger 4.5 features, such as multiple IMAP servers, LDAP search directory, read receipts, etc.
• Configure MIME types

Install Builder

• Step-by-step wizard (both Windows and Macintosh)
• Determine end user's experience during installation
• Customize the install by importing configuration settings, bookmarks, address books, etc.
• Option to create network installers for use in a shared drive environment
• Add up to two third-party components to the installer
• Specify the location of the dialup package folder

Netscape Communicator Deployment Guide

• Scenario-based information on deploying Communicator
• Real life examples and decision-making
• Tips for IS administrators

Messenger Control

• Leverages Netscape Console and Directory Server
• Easily set Netscape Messenger preferences for each group
• Dynamically manage Netscape Messenger configuration via Messenger Control

Roaming Access Control

• Easily set up Roaming Access servers
• Easily make users roaming-enabled

Communicator Upgrade Kit

• Communicator SmartUpdate packages
• Trigger scripts

SmartUpdate Builder

• Automatic install script creation
• Wizard interface
• Flexible deliverable handling
• Native installer launching
• Customizable installations
• Template-based script creation
• Integration with Netscape Signing Tool

• Configuration Editor and Configuration Files
• Windows Install Builder
• Macintosh Install Builder
• Netscape Signing Tool
• AutoUpdate
• SmartUpdate Builder
• Communicator Upgrade Kit
• Roaming Access Control
• Messenger Control
• Account Setup Editor
• Profile Manager

Configuration Editor and Configuration Files

• To turn off the Messenger Start page, add the following preference to the prefs.js file:

user_pref("mailnews.start_page.enabled", false);
• (Windows NT) To set a default template location in Composer, you must use defaultPref("editor.default_template_location","your template location here");. On all other platforms, the regular preference, defaultPref("editor.template_location","your template location here");, will work properly.
• (Windows or Mac OS) - if you used Communicator 4.5 PR2 to set passwords for your profiles, be sure to clear those passwords before you install the final version of Communicator 4.5. To clear your passwords, run the Profile Manager, which appears in the Windows Start menu and in the Mac OS Communicator folder. Select the appropriate profile, then choose Change Password and leave the new password fields blank. To use the profile password function in the final version of Communicator 4.5, you can use Mission Control Desktop to enable the profile password feature in the netscape.cfg file.
• (Mac OS) - in 4.5, MIME customizations are not possible in the .jsc file.
• There are some security preferences that will be removed in the final release of 4.5. These are the Security/Certificate Operations pane, Security/CA Certificates pane, and the "Alert message for disabled security functions" field in the Security/Navigator pane.
• If you launch Configuration Editor and Communicator is set to launch Messenger on startup, Communicator may halt.
• Configuration Editor may be slow when it does not have enough memory. This is noticeable, for example, when you try to save a file and it takes a long time. If Configuration Editor halts, increase Communicator's memory partition on the Macintosh. On Windows, make sure your machine has the recommended amount of RAM.
• (Windows 95) If you have multiple user profiles on your machine, and you attempt to start the Configuration Editor before you start Communicator, a warning message appears that indicates that the appropriate Configuration Editor file could not be found. You can dismiss the message and start Communicator, and the Configuration Editor will open. To avoid displaying the warning message in a multiuser setting, first open Communicator, then start the Configuration Editor.
• You cannot trigger multiple JAR files in the AutoConfig file.
• Some preferences, such as document encoding, do not appear dimmed to the user even though you can lock these preferences in the AutoConfig or the local configuration file.
• When creating a netscape.cfg file with more advanced JavaScript lines such as alert(), make sure that you use the Convert function within the Configuration Editor to convert the JavaScript file to a netscape.cfg file. If you save the JavaScript file using Save As, the additional JavaScript lines using the alert() function are not saved into the netscape.cfg file.
• In the Security Info window, under Passwords, you cannot lock the items under "Communicator Will Ask for This Password". The parameters are security.use_password and security.password_lifetime.
• The locker program includes an option in addition to the -p option that is described in the Mission Control Desktop Administrator's Guide (in "Using the Configuration Editor: Distributing Configuration Files to Users" in the "Customizing Communicator" section of the Guide). The -s option allows Communicator to launch if the netscape.cfg file is not present in the path specified by the -p option. If you do not use the -s option, but specify a path for the netscape.cfg file by using the -p option, Communicator looks for the netscape.cfg file in the specified path and launches only if the file is located. For example,

locker -p /netscapedir netscape

indicates that Communicator looks in the /netscapedir/app-defaults directory for the netscape.cfg file. If Communicator can't locate the file in that directory, it doesn't launch. However, locker -s -p /netscapedir netscape indicates that Communicator launches regardless of whether the netscape.cfg file is in the /netscapedir/app-defaults directory.

(Windows 95/98) If you've specified the paths for the small and large custom animation BMP files, the paths are not saved when you save the configuration. When you open the saved configuration, you must click Config Items, select Animated Logo, and then re-enter the paths to the BMP files. Also, do not include a dash when entering the number of frames.

Install Builder (Windows)

• Creating Navigator installers is not supported in this release.
• Network installers - When using a UNC path for the network installer, the user will encounter the following message - "Unable to start Java applet. Can't find java40.jar in your class path". A workaround is to map the UNC drive.
• The last screen will sometimes become blank if another window is dragged over it while the installer is building.
• If you've specified the paths for the small and large custom animation files, the paths are not saved when you save the Install Builder configuration. When you open the saved Install Builder configuration, you must go to the Customization Files, continued... screen and re-enter the paths to these files.

Install Builder (Mac OS)

• Creating Navigator installers is not supported in this release.

Netscape Signing Tool

• Netscape Signing Tool is included as part of Mission Control Desktop 4.5 in the tools directory. Documentation for Netscape Signing Tool is available at http://developer.netscape.com/library/documentation/signedobj/zigbert/index.htm

For further details about Netscape's object-signing tools, see the information provided at http://developer.netscape.com/software/index.html?content=signedobj/jarpack.html

AutoUpdate

• AutoUpdate silent installs do not function correctly in this release. If you specify a silent install, your users will still see dialog boxes during the installation.

SmartUpdate Builder

• Sometimes after clicking the Create JAR button in Step 3, a blank Navigator window remains open that hides the next step. Close the blank window to bring Step 4 into view. To avoid this blank window in the future, do the following:
1. Choose Preferences from the Edit menu.
2. Select Netscape SignTool Commands from the list.
3. Click Edit.
4. Deselect the "Always ask before opening downloaded files of this type" option.
5. Click OK twice to return to the main Communicator window.
• If you are including a large number of files (i.e. more than 200) in your JAR, clicking Verify may take several minutes. To view the results without having to click Verify, open a text editor and open su_bldr.out, located in the directory you specified in Step 3 as the "Location for temporary files".
• When exiting SmartUpdate Builder, if you try to save your JAR file to a directory that does not exist, SmartUpdate Builder may close without saving the JAR. Make sure that you save your JAR before attempting to exit SmartUpdate Builder by clicking Save.

Communicator Upgrade Kit

• Upgrades from 4.0 or 4.01 are not supported from the Communicator Upgrade Kit. To upgrade users from these versions to 4.5, you must create a native installer, as described in Chapter 4 of the Mission Control Desktop Administrator's Guide (dead link) - [AOL removed it] on the Netscape Insight website.
• Using an FTP server for deploying Communicator SmartUpdate JARs during an AutoUpdate deployment causes Communicator to halt during the upgrade. Instead, you can use an HTTP server for this type of deployment.

Roaming Access Control

• HTTP MOVE is not supported on non-Netscape HTTP servers. If you choose to run Roaming Access on a non-Netscape HTTP server, there is a preference that must be set in the user's preference file or Roaming will not work. The following line should be added:

user_pref("li.server.http.useSimplePut", true);
You must add the line above because only Netscape Enterprise Server supports the MOVE method, which allows for safe data transfer for users of Roaming Access. Note: Non-Netscape HTTP servers are not recommended for Roaming Access, because files may become corrupted on the server if uploads are cancelled in progress. For more details, see Chapter 7 (dead link) - [AOL removed it] of the Netscape Communicator Deployment Guide.
• Users of Enterprise Server 3.51 and earlier versions on Windows NT will see li****.tmp files in their Roaming Access directory. These files are harmless but should be deleted on a regular basis. Enterprise Server 3.6 (available soon) will not have this problem.
• When you are running the Mission Control Desktop installer and click "Install Messenger Control and Roaming Access Control", you are taken to the Console directory.

1. Double-click mnr.zip in the Console directory.
2. Double-click setup.exe in Winzip.
3. Choose a setup type: Express, Typical, or Custom.
4. Click Next.
5. Choose a destination directory for the control(s). Click Next.
6. Specify whether you want to install Roaming Access Control, Messenger Control, or both.

To install just one control, click Change and select the desired control.
7. Specify the user ID and password of the administrator who will manage the controls. This user must already exist.
8. Click Next.

The next screen shows you the information you specified. If the information is incorrect, click Back to fix any problems. If the information is correct, click Next.

1. From the mcontrol\Console directory, run setup.exe.
2. Untar and unzip mnr.tar.gzip and run setup.exe.

Messenger Control

• If you lock a directory-based preference, and then unlock it, the change will not take effect until the second time you launch Communicator.
• When setting up one or more IMAP mail servers, be sure to lock down the IMAP mail server type on at least one of the server instances. Failing to do so will cause the mail server type to revert to POP3 and will prevent IMAP mail servers from appearing in the mail servers panel (under Mail & Newsgroups in the Preferences panel).
• When adding directory servers to Communicator, Messenger Control creates a unique serverKey based on the directory server's hostname. If you are adding more than one directory from the same host (for example, with different base DN's), you will need to manually edit the directory entry created by Messenger Control to specify a unique serverKey.
• (Windows) When you are running the Mission Control Desktop installer and click "Install Messenger Control and Roaming Access Control", you are taken to the Console directory. To install Messenger Control, double-click mnr.zip. For more details on installing Messenger Control or Roaming Access Control on Windows and Unix, see the Known Issues for Roaming Access Control above.

Account Setup Editor

• Do not minimize or resize the Account Setup Editor window. Doing so may cause the Account Setup Editor window to resize incorrectly or become non-functional.
• Account Setup Editor now defaults to a new global option, "Offer Netscape Registration Server and Offline Account Creation (NCI Mode)." This option provides users with the choice of connecting to Netscape's registration server to choose from a variety of ISPs and account plans, or setting up an existing account using information they've received from their ISP. For further information, see "Creating a Dial-Up Communicator Installer" at https://insight.netscape.com/insight/index/product/mission_control/documentation/index.html(dead link) - AOL removed it.

Profile Manager

• Netscape Communicator 4.5 allows users to set a password that can be used to restrict access to stored mail, preferences, and address book information through Communicator. For more information about the profile password feature, and for details about how to enable it, see the Mission Control Desktop documentation Insight website(dead link) - [AOL removed it].

	Netscape 2.x browser archive ·  Netscape 3.x browser archive ·  Netscape 4.x browser archive Netscape 4.5 browser archive ·  Netscape 4.6 browser archive ·  Netscape 4.7 browser archive Netscape 6.x browser archive ·  Netscape 6.2 browser archive