Release Notes

Microsoft Internet Security and Acceleration Server 2004 Standard Edition Service Pack 1 Release Notes

1. Installing	3. Remote Management
2. Administering	4. Troubleshooting

1. Installing

ISA Server 2004 Standard Edition Service Pack 1 consists of two components: one to update the ISA Server computer, and the other to update computers running ISA Server 2004 Firewall Client software. To update Firewall client computers, do one of the following:
- Install the Firewall Client update included in the service pack download on each client computer.
- Update Firewall client computers from the Firewall Client Share on the ISA Server computer. You can do this by one or two methods:
Ensure that the Windows Installer service is enabled before installing Service Pack 1.
To uninstall ISA Server 2004 Standard Edition Service Pack 1 after installation, you must install Microsoft Windows Installer 3.0 before installing the service pack. You can install this application on the ISA Server computer, and on client computers running Firewall Client software. Download this application from Windows Installer 3.0 Redistributable.
During uninstall, the service pack installation source files are required (for example, the CD or the network location of the ISA Server Standard Edition installation files).
The packet filter driver (fweng) that applies the firewall policy may be stopped briefly during uninstall. We recommended that you physically disconnect the ISA Server computer from untrusted networks before uninstalling Service Pack 1.
After running an unattended install of ISA Server 2004 Service Pack 1 (or running Repair) on a computer running Windows 2000 Server, error messages related to performance counters (Event ID 3009) may appear in the Event Viewer. These can be ignored.
Before uninstalling Service Pack 1, disable the Routing and Remote Access service.

Back to Contents

2. Administering

Note the following import and export limitations:

Exporting and importing confidential information from ISA Server 2004 Standard Edition with Service Pack 1 to ISA Server 2004 Standard Edition (without Service Pack 1) is not supported.
Confidential information cannot be imported from ISA Server 2004 Standard Edition with Service Pack 1 to ISA Server 2004 Enterprise Edition. This operation will trigger a wrong password error, although the password is correct.

If you select to allow outgoing connections from the local site to the remote site when you configure a virtual private network (VPN) site-to-site network with Point-to-Point Tunneling Protocol (PPTP) or Layer Two Tunneling Protocol (L2TP), the domain name specified in the outgoing credentials must not exceed 15 characters. NetBIOS names are used during authentication, and such names have a 15-character limit.
Service Pack 1 addresses the following issues, and includes the following hot fixes:
- Article 884569: The ISACTRL and WSPSRV services do not start when you install ISA Server 2004 on a multiprocessor computer
- Article 884560: You cannot use RADIUS when you use the Outlook Web Access (OWA) Forms-Based Authentication on a Web publishing rule
- Article 884580: Active mode FTP client programs cannot access an FTP server behind Internet Security and Acceleration Server 2004
- Article 888422: CookieAuthFilter fails to logon credentials that include an Umlaute
- Article 891510: CRL check on Web Publishing fails when ROOT certificate has no CDP extension
- Article 891719: Request fails when CRL verification is enabled on ISA Server
- Article 885683: "401 Unauthorized" error message when you use the Internet Security and Acceleration Server 2004 Firewall client to access a Web page.
- Article 893171: Issues with ISA Server 2004 Firewall Client running on Windows 98

Back to Contents

3. Remote Management

To access logs and sessions on a remote ISA Server running Service Pack 1, the computer running ISA Server Management console must have Service Pack 1 installed.

Back to Contents

4. Troubleshooting

By default, a log is not created when you install a hotfix or service pack. Logging can be useful for troubleshooting if installation fails. To specify that a log should be created during installation of this service pack, run the installation as follows from the command line:
- Msiexec /p ServicePack_Name.msp REINSTALL=ALL REINSTALLMODE=omus /l*vx! Logfile_Name.log
Where:
- /p applies an update.
- ServicePack_Name.msp is the name and path of the hotfix or service pack file.
- REINSTALL=ALL indicates that features that are already installed are to be reinstalled. Use this command with REINSTALLMODE to indicate the type of reinstallation. Notice that REINSTALL is in all uppercase letters.
- REINSTALLMODE=omus is used with REINSTALL to specify the type of reinstall to perform. Notice that REINSTALLMODE is in all uppercase letters. The default omus indicates the following:
- /l indicates logging.
- *vx indicates a wildcard character that logs all information with verbose output.
- Logfile_Name.log is the name of the log file. By default, the log file is created in the same folder where you ran the msiexec command.
You can also examine the Event Viewer for any relevant information. An event is issued confirming that installation has been successful or has failed.

Back to Contents

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, people, and events depicted herein are fictitious and no association with any real company, organization, product, person, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries/regions.

Back to Contents