Microsoft Year 2000 Readiness Disclosure & Resource Center

Product Summary

Product: Windows NT Server Version: 4.0 SP3 Category: Compliant*# Operating System: Win NT Language: Swedish Release Date: N/A Operational Range: 01 Jan 1996 - 31 Dec 2036 Prerequisites: Windows NT Service Pack 3, and Year 2000 fixes Product Dependencies: None Clock Dependencies: System clock Last Updated: 30 Sep 1999

Product Details

Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customersÆ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 3 as compliant# through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. [This information applies to both Windows NT Server 4.0 SP3 and Windows NT Server 4.0 SP3, Enterprise Edition.] Updated Information A new issue has been discovered in versions of Outlook Express installed by Internet Explorer 4. Users of Outlook Express should consult the Internet Explorer Product Guide for details. Through our ongoing testing, Microsoft has identified two additional acceptable deviations. (April 1999) These issues are considered to be minor and do not affect the compliance rating of Windows NT 4.0 Service Pack 3. A year 2000 issue has been discovered in the Jet 3.5 data engine. Microsoft has provided a software update to address this issue. Consult the MDAC product guide for details. Important Preliminary Notes: Users who chose to install Windows NT Service Pack 4, and have both Microsoft Message Queue Service version 1.0 and Site Server Express version 2.0 installed on Windows NT Server 4.0 should review Microsoft Knowledge Base article Q197533 before proceeding.   Introduction When users load the Windows NT Server 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Server 4.0 features available to licensed users via Service Packs, the Windows NT Option Pack and the Windows NT Web site. Because users may have selected a variety of options and installed additional features, all options and features must be considered when assessing Year 2000 readiness status. Microsoft has determined that Windows NT Server 4.0 (including some installation options) and some versions of additional Windows NT Server 4.0 features are not fully compliant. Microsoft is committed to maintaining Windows NT Server 4.0 with SP4 as year 2000 compliant and strongly suggests customers evaluate and deploy SP4. The process for obtaining SP4 can be found at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.asp In addition, users should review the Windows NT Server 4.0 SP4 Year 2000 compliance document. Microsoft recognizes that, in light of MicrosoftÆs recommendation that users upgrade to Windows NT Server Service Pack 4 (SP4), some users of Windows NT Server 4.0 would prefer to remain on Service Pack 3 (SP3) until after January 1, 2000. To address the needs of these users, Microsoft has prepared a number of updates to the base Windows NT Server 4.0 operating system and Windows NT Server 4.0 features. Users should note, however, that: Microsoft has assigned a compliance rating of "Compliant#" to Windows NT Server 4.0-based systems where these post-SP3 updates have been applied Microsoft is committed to maintaining SP4 as the "Compliant" platform. The highest compliance rating that Microsoft will assign to a system running Windows NT Server 4.0 with SP3 is, "Compliant#." Further, Microsoft intends to maintain Windows NT Server 4.0 with SP3 compliance rating at the "Compliant#" level through January 1, 2001 (for one year after January 1, 2000). Microsoft will do this by producing updates if new Year 2000-related issues are discovered that would otherwise cause Microsoft to lower the rating of Windows NT Server 4.0 with SP3 below the "Compliant#" level. The tables included below list the specific options and features (by version) that users of Windows NT Server 4.0 SP3 may have installed on their systems and lists the compliance status of each option and feature. Where appropriate, the table describes a procedure for bringing an option or feature to a Compliant or Compliant# status on a system running SP3. Note that some options and features of Windows NT Server cannot be brought to a Compliant status without applying SP4, which Microsoft is committed to maintaining as the Compliant platform. Using the information below, however, the options and features can be brought to at least a Compliant# status. In summary, for users of Windows NT Server 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are: The base Windows NT Server operating system (Not Compliant; several updates are required to reach Compliant# status) Active Directory Services Interface version 1.0 (Not Tested; upgrade required to ensure Compliant status) Microsoft FrontPage 97 (Not Compliant; updates required to reach Compliant status) Microsoft FrontPage 97 Server Extensions (Not Compliant; upgrade required to reach Compliant status) Microsoft Internet Explorer version 2.0 (Not Tested; upgrade required to ensure Compliant status) Microsoft Internet Explorer version 3.02 (Not Compliant; updates required to reach Compliant status) Microsoft Internet Explorer version 4.01 (Not Compliant; updates required to reach Compliant status) Microsoft Internet Locator Service version 1.0 (Not Compliant; upgrade required to reach Compliant status) Microsoft Transaction Server version 1.0 (Not Tested; upgrade required to ensure Compliant status) Microsoft Transaction Server version 1.1 (Not Tested; upgrade required to ensure Compliant status) Site Server Express version 2.0 (Not Compliant; upgrade required to reach Compliant status) Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.   Evaluating the Status of a Windows NT Server 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Server 4.0 operating system (with SP3 installed) a status of Compliant#. This status includes options that can be selected during the installation process. This Compliant# status is based on having the following software installed: Microsoft Windows NT 4.0 Service Pack 3. Obtain SP3 at: http://www.microsoft.com/windows/downloads/ contents/wuarchive/nt4svcpk3/default.asp Windows NT post-SP3 Year 2000 Updates û released on February 26, 1999 An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: http://www.microsoft.com/ntserver or ftp://ftp.microsoft.com/bussys A list of the issues addressed by the post-SP3 Updates is listed below: User Manager Does Not Recognize February 2000 As a Leap Year. (Q175093) User Manager and User Manager for Domains will not accept February 29, 2000 as a valid date to expire an account. Control Panel Date/Time applet. (Q180122) The Control Panel Date/Time appletÆs date displayed may jump ahead one more day than expected. The system date is correct; only the displayed date is wrong. Find Files Displays Garbled Date if Year is 2000 or Greater. (Q183123) When using the Windows NT Find Files or Folders feature, the 2-digit abbreviation of the year does not appear correctly. Shell Doc Property Dialog: Custom Date Incorrect after Year 2000. (Q183125) When using the document properties viewer to define a custom property to include a date type in a file, the year may not be saved correctly. Year æ00Æ in Office Documents. (Q184132) When users try to add a Custom Date using the year æ00Æ on the Custom tab of the properties sheet for a Microsoft Office document, they will receive the following error message: "The value entered does not match with the specified type. The value will be stored as text." File & Print for NetWare file dates. (Q186669) The File and Print Services for NetWare (FPNW) service Logout.exe program may report the year incorrectly for files created on or after January 1, 2000. Print job date display. (Q191768) When users view a print job spooled on a different print server, such as Windows 9x or LAN Manager, from a Windows NT client, the date displayed in the print queue may be incorrect and possibly off by one year. Problems in Date/Time after Choosing February 29 (Q193056) Several odd behaviors may result if the Date/Time tool in Control Panel is used to select February 29 in a Leap Year. NetWare account migration. (Q193434) Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date. NetWare client time & date synchronization. (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Server computer running File and Print Services for NetWare (FPNW), the client's date and time are not synchronized with that of the server when the server's date and time are beyond 12/31/1999 at 11:59:59pm. PS1 compatible machines. (Q207799) PS1 Compatible machines will not boot if the year is set to æ2000Æ. Restore log dates. (Q216916) When files are backed up using NTBackup.exe after 12/31/1999 at 11:59:59pm, and subsequently restored, "year" values will be listed as starting with æ1900Æ in the restore log. NNTP Service Converts Two-Digit Years Incorrectly (Q238020) When a messaging client application attempts to post a message to an News Network Transfer Protocol (NNTP) server using a 2-digit year, the fact that the 2-digit year is converted incorrectly may cause an error message to be displayed. Microsoft is not aware of any messaging clients that post messages using 2-digit dates. The NNTP server was shipped with Internet Information Server as part of the Windows NT Option Pack and with MCIS 2.0. NET USER /TIME Command does not work in Year 2000 (Q240195) The /TIMES function can be used to set the valid logon times of Windows NT user accounts via the command line utility NET USER. The Y2K issue causes the /TIMES function to cease functioning in years 2000 or greater. The User Manager GUI application is not affected and can be used to effectively set account valid logon times in the year 2000 and beyond.   Users should note that some known issues in the base Windows NT Server 4.0 operating system with SP3 are not being addressed, hence the rating of "Compliant#." It is for this reason Microsoft recommends upgrading to Windows NT Server Service Pack 4. Listed below are the known acceptable deviations remaining in SP3 after the application of the post-SP3 Year 2000 Updates. 1. WINS/DHCP Admin show Expiration Dates incorrectly. (Q193371) Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). This is a display issue only. 2. Custom date properties in .DOC property dialog box. (Q207807) When a Word 97 file is selected on the desktop and the user right clicks on the file, selects "Properties", selects the "custom" tab, and then enters a date with a 2-digit year value of æ01Æ, this issue may cause the date to automatically decrement by 1 day when the "Add" button is clicked. This issue only manifests if time zone is set to Far East region time zone (Greenwich Mean Time (GMT)+8 or Greenwich Mean Time (GMT)+9). 3. BIOS Date Value does not Immediately Update on January 1, 2000. (Q216913) When the Window NT System Time value rolls over from the year æ1999Æ to æ2000Æ, the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. This behavior may cause unexpected behavior under two conditions: In a dual boot scenario, the other operating system(s) may not handle this situation properly. MS-DOS is in this class of operating systems. Some BIOSes detect this behavior as an invalid date and query the user for the correct date. This would prevent a system from rebooting without user input.   4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the OLE Automation white paper for more information: 5. Incorrect Date Displayed when viewing a saved System Info Report. (Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102". 6. Four-Digit Year Format for Non-English Regional Settings. (Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring a systemÆs Regional Settings Short Date Style, users may not be able to choose a 4-digit year format. However, users can manually enter a 4-digit date style. 7. Dates may display improperly using the Configuration Back-up option from the IIS 4.0 HTML Administrator. (Q230335) When using the Configuration Back-up option from the HTML version of the IIS 4.0 Internet Server Manager it is possible that the date displayed for the stored configuration may display the current date improperly if the configuration was stored on or after 1/1/2000. 8. MSMQ Err: Error While Creating MSMQ Internal Certificate. Error: 0x8000ffff (Q230050) When you click Renew Internal Certificate in the Microsoft Message Queue Control Panel utility on February 29 of a leap year (for example 2000, 2004, 2008, and so on), you receive the following error message: Error while creating MSMQ internal certificate. Error: 0x8000ffff.     Additional Software Components The information below outlines features in addition to the base Windows NT Server 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Server 4.0 (with SP3) are listed in Table 1 (below). Table 1. Option/Service Name Compliance Rating DHCP Relay Agent Compliant# DLC Protocol Compliant Gateway Services for NetWare Compliant Microsoft DHCP Server Compliant Microsoft DNS Server Compliant Microsoft TCP/IP Printing Compliant NetBEUI Protocol Compliant NetBIOS Interface Compliant Network Monitor Agent Compliant Network Monitor Tools and Agent Compliant NWLink IPX/SPX-Compatible Transport Compliant Point To Point Tunneling Protocol Compliant Remote Access Service Compliant Remote Boot Service Compliant RIP for Internet Protocol Compliant RIP for NWLink IPX/SPX-Compatible Transport Compliant RPC Configuration Compliant RPC Support for Banyan Compliant SAP Agent Compliant Server Compliant Services for Macintosh Compliant Simple TCP/IP Services Compliant SNMP Service Compliant Streams Environment Compliant TCP/IP Protocol Compliant Windows Internet Name Service Compliant# Windows Messenger Service Compliant Workstation Compliant In addition to the selectable options offered during installation of the Windows NT Server 4.0 operating system, there are additional features of the Windows NT Server 4.0 product that may be installed on the Target System. These features have been made available by Microsoft via Service Packs, the Windows NT Option Pack and the Windows NT Server Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Server 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Server 4.0 feature and to apply appropriate updates when necessary.   Table 2. Feature Name Version Compliance Rating Required Actions Active Directory Services Interface (ADSI) 1.0 Not Tested Install ADSI 2.0 from: Active Directory Services Interface 2.0 Compliant None Active Directory Services Interface 2.5 Compliant None Certificate Server 1.0 Compliant See Note 1 Distributed File Service 4.0 Compliant None Distributed File Service 4.1 Compliant None Imaging for Windows N/A Compliant None û the Compliant rating applies to versions that run on Windows NT Server 4.0 Index Server 1.0 Compliant None Index Server 1.1 Compliant None Index Server 2.0 Compliant None Internet Connection Services for Microsoft Remote Access Service 1.0 Compliant None Microsoft Cluster Services 1.0 Compliant None Microsoft Data Access Components See Required Actions See Required Actions Some versions of MDAC are not compliant. To make MDAC compliant, please review the MDAC product guide for latest information on year 2000 issues and updates for MDAC. Microsoft Euro Currency Support for Windows NT 4.0 N/A Compliant None Microsoft FrontPage 97 æ97Æ Not Compliant To make compliant, install FrontPage 97 Year 2000 updates Microsoft FrontPage 97 Server Extensions æ97Æ Not Compliant To make compliant, install FrontPage 98 Server Extensions from the Windows NT Option Pack. Also see Note 2. Microsoft FrontPage 97 æ97Æ with updates Compliant To determine that Microsoft Front Page 97 updates are installed, verify the version number of the file named: "(system directory)\system32\fp20tl.dll" is at least02.00.3002.23. See note 5 for instructions on verifying version numbers of .DLL files. Microsoft FrontPage 98 Server Extensions æ98Æ Compliant None û Also see note 2. Microsoft Internet Explorer Multiple Versions See Required Actions Consult the Year 2000 Product Guide for Details Users who wish to install IE 4.01 SP2 or IE 5 Technology without adding IE icons and without making IE the default browser should consult KB article Q224088. Microsoft Internet Information Server 2.0 Compliant None Microsoft Internet Information Server 3.0 Compliant None Microsoft Internet Information Server 4.0 Compliant An additional issue has been identified for IIS4.0. Consult the Not-Fixed Issues list(Issue #7) of this document for details. Microsoft Internet Locator Service 1.0 Not Compliant To make compliant, install Microsoft Internet Locator Service version 2.0 Microsoft Internet Locator Service 2.0 Compliant None Microsoft Management Console 1.0 Compliant None Microsoft Management Console 1.1 Compliant Microsoft Message Queue Server 1.0 Compliant Consult the following Knowledge Base article for required updates to MSMQ: Q230050 Microsoft Message Queue Server 1.0E Compliant Consult the following Knowledge Base article for required updates to MSMQ: Q230050 Microsoft Transaction Server 1.0 Not Tested To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack Microsoft Transaction Server 1.1 Not Tested To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack Microsoft Transaction Server 2.0 Compliant None Microsoft Transaction Server 2.0 SP Compliant None Microsoft Virtual Machine (Many versions) See required action for description Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues. NetShow Services 1.0 Not Tested To make compliant, install NetShow 3.0 NetShow Services 3.0 Compliant None Routing and Remote Access Services 4.0 Compliant None Site Server Express 2.0 Not Compliant To make compliant, install Site Server Express version 3.0 Site Server Express 3.0 Compliant None - See Note 3 TAPI SDK 2.1 Compliant None Web Administrator for Microsoft Windows NT Server 4.0 2.0 Compliant None Windows Load Balancing Service 2.2 Compliant Windows Media Player 6.0 Compliant None Windows Scripting Host 1.0 Compliant None Zero Administration Kit for Windows NT 4.0 N/A Compliant None -See Note 4 Zero Administration Kit for Windows NT 4.0, Terminal Server Edition N/A Compliant None -See Note 4 Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Server web site that Microsoft does not consider to be part of the Window NT Server 4.0 product for Year 2000 compliance purposes. Table 3. Feature/Product Name Notes ADSI Implemented in Java Available only in Beta test versions. Client 32 support for NetWare This is a Novell product; consult Novell for compliance information. Dial-Up Networking Access Service Performance and Security Upgrade Applies only to Windows 95 should not be present with Windows NT Server 4.0. I2O (Intelligent I/O Architecture) Drivers for Windows NT Available only in Beta test versions. Microsoft Windows NT Services for UNIX Available only in Beta test versions. Personal Web Services 4.0 Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0. Routing and Remote Access Service Performance and Security Upgrade This is a collection of updates that have no impact on Year 2000 compliance ratings. Routing and Remote Access Service Upgrade for Windows NT Server This is a collection of updates that have no impact on Year 2000 compliance ratings. Windows NT Server Management Tools for Windows 95 Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0. Notes: Certificate Server version 1.0 cannot be installed when the date is 2/29/2000. To determine which versions of FrontPage Server Extensions are actively in use, run the FrontPage Server Administrator (Fpsrvwin.exe). Click on each of the Web servers or virtual servers (listed in the box in the upper left area) that have been configured with the FrontPage Server Extensions. The version number of the FrontPage Server Extension is displayed to the right of the list. Version numbers where the first digit is æ3Æ or greater resolve known Year 2000 issues (e.g. 3.0.2.1706). If the first digit of the version number is æ1Æ or æ2Æ, users should install an updated version of the FrontPage Server Extensions. Refer to http://www.microsoft.com/frontpage/ for more details. There is no Content Analyzer feature in Site Server Express 3.0. An updated Content Analyzer is available from the Windows NT Server Service Pack 4 Download page. http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer. The Compliant ratings for Zero Administration Kits (ZAK kit) are based on being used with Compliant versions of the software configured for installation by the ZAK kit. To verify the version number of a dynamic link library (DLL) file, users should: Start Windows NT Explorer from the "Start/Programs" menu Locate the DLL file to be verified Select the file by pointing the mouse cursor at the file and clicking the left mouse button once Click the right mouse button once to display a menu Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once Visually Locate the version number in the field labeled "File Version"

Return to Search Screen

If after reviewing this information you have additional questions related to this product, click here.

ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.

This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.