Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Arabic)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Chinese - Simplified)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Chinese - Traditional)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Dutch)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (English)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes (see below). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (French)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (German)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Hebrew)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Japanese)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Korean)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Portuguese (Brazil))
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Spanish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Swedish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP3 (Thai)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.aspIn addition, users should review the Windows NT Server 4.0 SP4 Year 2000compliance 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:
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:
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:
contents/wuarchive/nt4svcpk3/default.asp
An update for Windows NT Server version 4.0 Service Pack 3 can be obtained at either: or ftp://ftp.microsoft.com/bussys
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:
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 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.
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.
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.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Arabic)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 04 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Chinese - Simplified)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 04 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Chinese - Traditional)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Dutch)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (English)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (French)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (German)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Hebrew)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Japanese)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Korean)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Portuguese (Brazil))
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Spanish)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Swedish)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (See Below) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP4 (Thai)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (See Below) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 4 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 Service Pack 4 and Windows NT Server 4.0 Service Pack 4, 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 six issues that are addressed by post-Service Pack 4 (SP4) updates. Microsoft recommends that users evaluate the post-SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide ( HERE) for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Server 4.0 operating system on a computer 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Server installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP4. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Server 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Server 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 8 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Y2K updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)1. 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. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot(Contact your hardware manufacturer for BIOS details).2. MFC40.dll Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877) An internal function within Mfc40.dll(ColeDateTime) is designed to add 1900 to every 2-digit date that is passed to it. For example, 99 is returned as 1999. If more than 2 digits are passed, nothing is added. Programs that use this function may incorrectly parse a date after the year 2000 (for example, January 1, 2000, may become January 1, 100). This problem has been observed with the following applications: Microsoft System Information (Msinfo32.exe).3. 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.4. 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.5. 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 two-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.6. 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.
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Server 4.0 operating system itself and each of the options listed in Table 2 below should be updated after applying SP4. Table 2
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 3 (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 installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Arabic)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Chinese - Simplified)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Chinese - Traditional)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Dutch)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (English)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 29 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (French)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (German)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Hebrew)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Japanese)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Korean)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Portuguese (Brazil))
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Spanish)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Swedish)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP5 (Thai)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP5 and Windows NT Server 4.0 SP5, 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.Introduction Service Pack 5 (SP5) provides the latest updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). SP5 contains known Year 2000 updates for Windows NT 4.0. These Year 2000 updates are also available as separate Web downloads that customers may apply to a Service Pack 4 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP5 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP5 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 5.The current Windows NT 4 Service Pack 5 (SP5) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 5 plus additional year 2000 software updates. Additionally, Microsoft intends to maintain the compliance of SP4, SP5, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP5 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known Year 2000 issues, requiring updates. In order to update these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP5 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP5. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP5, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP5 to the Target System. SP5 can be obtained here.The installation of SP5 applies updates to the base Windows NT Server 4.0 product including the installation options. Post SP5 Updates
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP5. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server 4.0 SP6 (English)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| see below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 01 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[This information applies to both Windows NT Server 4.0 SP6 and Windows NT Server 4.0 SP6, Enterprise Edition.] Introduction Service Pack 6 (SP6) provides the latest year 2000 software updates to Microsoft Windows NT Workstation 4.0 and Windows NT Server 4.0 (including Enterprise Edition). These year 2000 software updates are also available as separate Web downloads that customers may apply to a Service Pack 4 or Service Pack 5 system. Providing this option gives organizations the flexibility to choose which path is easier for them to address Year 2000 issues. SP6 is not a required upgrade for year 2000 compliance; Microsoft recommends that each customer consult the Windows NT4 SP6 documentation and then determine whether to deploy it. Click HERE for more information or to download Service Pack 6.The current Windows NT 4 Service Pack 6 (SP6) combined with the following actions addresses known Year 2000 issues. The compliance rating for Windows NT Server 4.0 above is dependent upon completing the steps below. Windows NT4 has had a number of service packs since its release. To reach a Compliant state with Windows NT 4, Microsoft recommends customers apply Service Pack 6 plus additional year 2000 software updates (see below). Additionally, Microsoft intends to maintain the compliance of SP4, SP5, SP6, and any subsequent service packs, through January 1, 2001. Year 2000 Remediation Process with SP6 When users load the Windows NT Server 4.0 operating system on a computer, 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 on a given system, all options and features must be considered when assessing the system’s 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 have known year 2000 issues, requiring updates. In order to update these known year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the year 2000 issue can be addressed by users applying updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Step 1 SP6 itself will address most known year 2000 issues. However, users must update or upgrade certain features to newer versions, in addition to applying SP6. Table 1A (below) lists the Windows NT Server 4.0 features that must be updated or upgraded in addition to applying SP6, along with specific update/upgrade instructions. Table 1B (below) lists the Windows NT Server 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP6 to the Target System. SP6 can be obtained HERE.The installation of SP6 applies updates to the base Windows NT Server 4.0 product including the installation options. Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 in the appendix of this document. Following successful completion of steps 1 and 2 above, the options are rated at 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 installed on the Target System.
Table 2
Conclusion: If all of the Windows NT Server 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table below, Steps 1 and 2 were conducted correctly and the copy of Windows NT Server 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes:
Content/ServicePacks/Default.asp 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.
8. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: When users load the Windows NT Server 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 3 below. The known Year 2000 issues with each of the options listed in Table 3 below should be updated after applying SP6. Table 3
For convenience, the Table 4 (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 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server NetShow Services 3.01 (English)
| - | ||
| None | ||
| Windows NT Server 4.0 with Service Pack 4 | ||
| Uses the operating system date/time routines | ||
| 23 Nov 1998 | ||
|
Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusiveRelease Date: 4Q/1998 How the product handles dates: Two-digit short-cut handling For input, this is not applicable. As described above, output is handled by system calls to get user-defined preferences for short date (GetDateFormat) and time (GetTimeFormat).
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server NetShow Services 3.01 (French)
| - | ||
| None | ||
| Windows NT Server 4.0 with Service Pack 4 | ||
| Uses the operating system date/time routines | ||
| 23 Nov 1998 | ||
|
Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusiveRelease Date: 4Q/1998 How the product handles dates: Two-digit short-cut handling For input, this is not applicable. As described above, output is handled by system calls to get user-defined preferences for short date (GetDateFormat) and time (GetTimeFormat).
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server NetShow Services 3.01 (German)
| - | ||
| None | ||
| Windows NT Server 4.0 with Service Pack 4 | ||
| Uses the operating system date/time routines | ||
| 23 Nov 1998 | ||
|
Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusiveRelease Date: 4Q/1998 How the product handles dates: Two-digit short-cut handling For input, this is not applicable. As described above, output is handled by system calls to get user-defined preferences for short date (GetDateFormat) and time (GetTimeFormat).
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server NetShow Services 3.01 (Japanese)
| - | ||
| None | ||
| Windows NT Server 4.0 with Service Pack 4 | ||
| Uses the operating system date/time routines | ||
| 23 Nov 1998 | ||
|
Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusiveRelease Date: 4Q/1998 How the product handles dates: Two-digit short-cut handling For input, this is not applicable. As described above, output is handled by system calls to get user-defined preferences for short date (GetDateFormat) and time (GetTimeFormat).
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Server NetShow Services 3.01 (Spanish)
| - | ||
| None | ||
| Windows NT Server 4.0 with Service Pack 4 | ||
| Uses the operating system date/time routines | ||
| 23 Nov 1998 | ||
|
Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusiveRelease Date: 4Q/1998 How the product handles dates: Two-digit short-cut handling For input, this is not applicable. As described above, output is handled by system calls to get user-defined preferences for short date (GetDateFormat) and time (GetTimeFormat).
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (English)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Platform(s): Windows NT 4.0, The password synchronization daemons run on HP-UNIX, Sun Solaris-UNIX, Digital Unix. Product: Windows NT Services for Unix Add-On Pack How the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (English)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Platform(s): Windows NT 4.0, The password synchronization daemons run on HP-UNIX, Sun Solaris-UNIX, Digital Unix. Product: Windows NT Services for Unix Add-On Pack How the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (English)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Platform(s): Windows NT 4.0, The password synchronization daemons run on HP-UNIX, Sun Solaris-UNIX, Digital Unix. Product: Windows NT Services for Unix Add-On Pack How the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (English)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Platform(s): Windows NT 4.0, The password synchronization daemons run on HP-UNIX, Sun Solaris-UNIX, Digital Unix. Product: Windows NT Services for Unix Add-On Pack How the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (French)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Product: Windows NT Services for Unix Add-On PackHow the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (German)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Product: Windows NT Services for Unix Add-On PackHow the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (Japanese)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Product: Windows NT Services for Unix Add-On PackHow the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Services for Unix 1.0a (Spanish)
| 01 Jan 1996 - 31 Dec 2036 | ||
| None | ||
| Windows NT 4.0 Service Pack 3 or greater | ||
| System Clock | ||
| 03 Nov 1999 | ||
|
Product: Windows NT Services for Unix Add-On PackHow the product handles dates: The Telnet, NFS, and Password Synchronization components of this product rely on the underlying Operating Systems for date handling. This product therefore utilizes the operational date range of the Operating System. The product can be installed on Windows NT 4 Service Pack 3 or greater. However, since this product depends on Windows NT for date handling, it is recommended that the Windows NT Year 2000 Product Guide be reviewed to determine steps needed to address the known issues with Windows NT Service Pack 3 or greater.
Usage of 2-digit years occur within the Unix Shell where the date command in a script can be formatted to output the year in two digits. The date command has options to format its output using the syntax ‘date +format’ where format can specify the display to include year, month, day, hour, minute, second. One of these options is ‘-%y’ (lower case), which is the format specifier for a 2-digit year. A 2-digit year is defined as an offset from ‘-%C’, the century specifier. If the user writes a script that formats the date to a 2-digit year and fails to account for the century indicator, then the user’s script would encounter a problem beyond the year 2000. In this case, the user’s script may fail to operate as intended, but Services for Unix would be unaffected. The alternative is for the user to account for the century indicator, or to use ‘-%Y’ (upper case), which causes the date command to output a 4-digit year.
Common date usage errors: Scripts intended to be run under the Unix Shell in this product should ensure they do not rely on the 2-digit format specifier for the Date command as indicated above.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Chinese - Simplified)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 software update | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Chinese - Traditional)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 software update | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Danish)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Dutch)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (English)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT Service 3.51 Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Finnish)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (French)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (German)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| None | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Italian)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Japanese)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Korean)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Norwegian)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Portuguese (Brazil))
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Spanish)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 3.51 (Swedish)
| 30 May 1995 - 31 Dec 2036 | |||||||||||||
| Windows NT 3.51 Service Pack 5 and hot fix | |||||||||||||
| none | |||||||||||||
| System clock | |||||||||||||
| 21 Oct 1999 | |||||||||||||
|
What are the prerequisites for compliance? Windows NT 3.51 is compliant with the following software installed:
The software update addresses the following issues:
9. FTP File Service displays incorrect file date for Year 2000 ( MicrosoftKnowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan. 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. Latest Year 2000 Updates:
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 Year 2000 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.
Description of how dates are handled in the product:
| |||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Arabic)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Chinese - Simplified)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Chinese - Traditional)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Czech)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Systen clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Danish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Dutch)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (English)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes (see below). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Finnish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (French)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (German)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes (see below). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Hebrew)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Hungarian)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Italian)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Japanese)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Korean)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Norwegian)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Pan-Chinese)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Polish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Portuguese (Brazil))
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Russian)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Spanish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Swedish)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP3 (Thai)
| 01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 3, and Year 2000 fixes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 SP3 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.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.Introduction When users load the Windows NT Workstation 4.0 operating system they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. Microsoft is committed to maintaining Windows NT Workstation 4.0 with SP4 as the year 2000 compliant platform and strongly suggests that 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 Workstation 4.0 SP4 Year 2000 compliance document for additional information.Microsoft recognizes that, in light of Microsoft’s recommendation that users upgrade to Windows NT Workstation Service Pack 4 (SP4), some users of Windows NT Workstation 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 Workstation 4.0 operating system and Windows NT Workstation 4.0 features. Users should note, however, that:
Further, Microsoft intends to maintain Windows NT Workstation 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 Workstation 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 Workstation 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 Workstation 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 Workstation 4.0 with SP3, the options and features that need to be addressed in order attain a status of Compliant# are:
Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.
Evaluating the Status of a Windows NT Workstation 4.0 Service Pack 3 System Microsoft has assigned the base Windows NT Workstation 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:
Default.asp.
An update for the English Language version of Windows NT Workstation version 4.0 Service Pack 3 can be obtained at: or ftp://ftp.microsoft.com/bussys/winnt
1. User Manager Does Not Recognize February 2000 As a Leap Year. ( 2. 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.3. Find Files Displays Garbled Date if Year is 2000 or Greater . (Q183123) When using the Windows NT Find Files or Folders feature, the two-digit abbreviation of the year does not appear correctly.4. 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.5. 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."6. 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.7. 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.8. 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.9. 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.10. NetWare client time & date synchronization . (Q194726) When an MS-DOS-based NetWare client attaches or logs on to a Windows NT Workstation 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.
11. PS1 compatible machines. ( Q207799) PS1 Compatible machines will not boot if the year is set to 2000.12. 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.13. 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.
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:
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 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 four 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 four digit year format. However, users can manually enter a four 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 Workstation 4.0 operating system (with SP3) that must be evaluated to determine compliance. Installation options included in the Compliant# status of Windows NT Workstation 4.0 (with SP3) are listed in Table 1 (below). Table 1.
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature and to apply appropriate updates when necessary.
Table 2.
Appendix: For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 3.
Notes:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP4 (Arabic)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (see below) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Workstation 4.0 Service Pack 4 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 Windows NT Workstation 4.0 SP4] 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 five issues that are addressed by post-Service Pack 4 updates. Microsoft recommends that users evaluate the post-SP4 year 2000 updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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 HERE for details.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 on a given system, all options and features must be considered when assessing the system’s Year 2000 readiness status. Microsoft has determined that Windows NT Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. In order to address these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be updated by users applying updates. In other cases, users are instructed to upgrade a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Workstation installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to their later releases, in addition to applying SP4. Table 1A (below) lists the Windows NT 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific repair/update instructions. Table 1B (below) lists the Windows NT 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Workstation 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Workstation 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 7 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Year 2000 updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Workstation 4.0 operating system itself and each of the options listed in Table 2 below should have been updated after SP4 was applied. Table 2
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 3 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Workstation 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table, Steps 1 and 2 were conducted correctly and the copy of Windows NT Workstation 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes: 1. To determine which versions of FrontPage Server Extensions are actively in use on a system, 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. 2. This Not Compliant version of this feature should only be present if the procedures outlined in Step 1 have not been performed correctly. 3. This Not Compliant version of this feature should only be present if the procedures outlined in Step 2 have not been performed correctly. 4. There is no Content Analyzer feature in Site Server Express 3.0. A replacement version that is Year 2000-compliant will be made available. 5. 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. 6. To verify the version number of a dynamic link library (DLL) file, users should:
7. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP4 (Chinese - Simplified)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Workstation 4.0 Service Pack 4 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 Windows NT Workstation 4.0 SP4] 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 five issues that are addressed by post-Service Pack 4 updates. Microsoft recommends that users evaluate the post-SP4 year 2000 updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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 HERE for details.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 on a given system, all options and features must be considered when assessing the system’s Year 2000 readiness status. Microsoft has determined that Windows NT Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. In order to address these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be updated by users applying updates. In other cases, users are instructed to upgrade a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Workstation installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to their later releases, in addition to applying SP4. Table 1A (below) lists the Windows NT 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific repair/update instructions. Table 1B (below) lists the Windows NT 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Workstation 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Workstation 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 7 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Year 2000 updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Workstation 4.0 operating system itself and each of the options listed in Table 2 below should have been updated after SP4 was applied. Table 2
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 3 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Workstation 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table, Steps 1 and 2 were conducted correctly and the copy of Windows NT Workstation 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes: 1. To determine which versions of FrontPage Server Extensions are actively in use on a system, 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. 2. This Not Compliant version of this feature should only be present if the procedures outlined in Step 1 have not been performed correctly. 3. This Not Compliant version of this feature should only be present if the procedures outlined in Step 2 have not been performed correctly. 4. There is no Content Analyzer feature in Site Server Express 3.0. A replacement version that is Year 2000-compliant will be made available. 5. 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. 6. To verify the version number of a dynamic link library (DLL) file, users should:
7. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP4 (Chinese - Traditional)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Workstation 4.0 Service Pack 4 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 Windows NT Workstation 4.0 SP4] 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 five issues that are addressed by post-Service Pack 4 updates. Microsoft recommends that users evaluate the post-SP4 year 2000 updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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 HERE for details.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 on a given system, all options and features must be considered when assessing the system’s Year 2000 readiness status. Microsoft has determined that Windows NT Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. In order to address these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be updated by users applying updates. In other cases, users are instructed to upgrade a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Workstation installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to their later releases, in addition to applying SP4. Table 1A (below) lists the Windows NT 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific repair/update instructions. Table 1B (below) lists the Windows NT 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Workstation 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Workstation 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 7 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Year 2000 updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Workstation 4.0 operating system itself and each of the options listed in Table 2 below should have been updated after SP4 was applied. Table 2
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 3 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Workstation 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table, Steps 1 and 2 were conducted correctly and the copy of Windows NT Workstation 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes: 1. To determine which versions of FrontPage Server Extensions are actively in use on a system, 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. 2. This Not Compliant version of this feature should only be present if the procedures outlined in Step 1 have not been performed correctly. 3. This Not Compliant version of this feature should only be present if the procedures outlined in Step 2 have not been performed correctly. 4. There is no Content Analyzer feature in Site Server Express 3.0. A replacement version that is Year 2000-compliant will be made available. 5. 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. 6. To verify the version number of a dynamic link library (DLL) file, users should:
7. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP4 (Czech)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (see below) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Workstation 4.0 Service Pack 4 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 Windows NT Workstation 4.0 SP4] 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 five issues that are addressed by post-Service Pack 4 updates. Microsoft recommends that users evaluate the post-SP4 year 2000 updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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 HERE for details.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 on a given system, all options and features must be considered when assessing the system’s Year 2000 readiness status. Microsoft has determined that Windows NT Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. In order to address these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be updated by users applying updates. In other cases, users are instructed to upgrade a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Workstation installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to their later releases, in addition to applying SP4. Table 1A (below) lists the Windows NT 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific repair/update instructions. Table 1B (below) lists the Windows NT 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Workstation 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Workstation 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 7 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Year 2000 updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Workstation 4.0 operating system itself and each of the options listed in Table 2 below should have been updated after SP4 was applied. Table 2
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 3 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Workstation 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table, Steps 1 and 2 were conducted correctly and the copy of Windows NT Workstation 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes: 1. To determine which versions of FrontPage Server Extensions are actively in use on a system, 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. 2. This Not Compliant version of this feature should only be present if the procedures outlined in Step 1 have not been performed correctly. 3. This Not Compliant version of this feature should only be present if the procedures outlined in Step 2 have not been performed correctly. 4. There is no Content Analyzer feature in Site Server Express 3.0. A replacement version that is Year 2000-compliant will be made available. 5. 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. 6. To verify the version number of a dynamic link library (DLL) file, users should:
7. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP4 (Danish)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (see below) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Workstation 4.0 Service Pack 4 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 Windows NT Workstation 4.0 SP4] 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 five issues that are addressed by post-Service Pack 4 updates. Microsoft recommends that users evaluate the post-SP4 year 2000 updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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 HERE for details.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 on a given system, all options and features must be considered when assessing the system’s Year 2000 readiness status. Microsoft has determined that Windows NT Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. In order to address these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be updated by users applying updates. In other cases, users are instructed to upgrade a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Workstation installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to their later releases, in addition to applying SP4. Table 1A (below) lists the Windows NT 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific repair/update instructions. Table 1B (below) lists the Windows NT 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Workstation 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Workstation 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 7 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Year 2000 updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Workstation 4.0 operating system itself and each of the options listed in Table 2 below should have been updated after SP4 was applied. Table 2
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 3 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Workstation 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table, Steps 1 and 2 were conducted correctly and the copy of Windows NT Workstation 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes: 1. To determine which versions of FrontPage Server Extensions are actively in use on a system, 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. 2. This Not Compliant version of this feature should only be present if the procedures outlined in Step 1 have not been performed correctly. 3. This Not Compliant version of this feature should only be present if the procedures outlined in Step 2 have not been performed correctly. 4. There is no Content Analyzer feature in Site Server Express 3.0. A replacement version that is Year 2000-compliant will be made available. 5. 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. 6. To verify the version number of a dynamic link library (DLL) file, users should:
7. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows NT Workstation 4.0 SP4 (Dutch)
| 01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (see below) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 Workstation 4.0 Service Pack 4 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 Windows NT Workstation 4.0 SP4] 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 five issues that are addressed by post-Service Pack 4 updates. Microsoft recommends that users evaluate the post-SP4 year 2000 updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below. 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 HERE for details.Microsoft recently announced the release of Service Pack 5 for Windows NT 4. Service Pack 5 is not required for Year 2000 compliance. Service Pack 5 may provide a more simple Year 2000 remediation process for some customers. Customers should consult the Windows NT 4 SP5 compliance document in the Year 2000 product guide for details.Introduction Windows NT 4.0 has had a number of service packs since its release. To reach a compliant state with Windows NT 4.0, Service Pack 4 plus additional Year 2000 software updates must be installed. Additionally, Microsoft intends to maintain the compliance of Service Pack 4 through January 1, 2001, in addition to any subsequent service packs. When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. In addition, Microsoft has made additional Windows NT Workstation 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 on a given system, all options and features must be considered when assessing the system’s Year 2000 readiness status. Microsoft has determined that Windows NT Workstation 4.0 and some versions of additional Windows NT Workstation 4.0 features have known Year 2000 issues, requiring upgrades. In order to address these known Year 2000 issues, users must first determine the set of options and features that they have installed on a given system (the "Target System") and follow the three-step procedure described below. In some cases the Year 2000 issue can be updated by users applying updates. In other cases, users are instructed to upgrade a feature to a newer version of the feature to address known issues. The steps identified below take a comprehensive approach to correcting known issues.
Important Preliminary Notes:
Step 1 Microsoft has created Service Pack 4 (SP4) to help users address the majority of Year 2000 compliance issues with their Windows NT Workstation installations in a simple and automated fashion. SP4 itself will address most known Year 2000 issues. However, users must update or upgrade certain features to their later releases, in addition to applying SP4. Table 1A (below) lists the Windows NT 4.0 features that must be updated or upgraded in addition to applying SP4, along with specific repair/update instructions. Table 1B (below) lists the Windows NT 4.0 Optional features that must be updated or upgraded only if previous versions exist on the machine. Note that these updates and upgrades can be performed either before or after applying SP4 (which is outlined in Step 2). Table 1A: System Components.
Table 1B: Optional Components.
Step 2 Apply SP4 to the Target System. SP4 can be obtained at: http://support.microsoft.com/Support/NTServer/Content/ServicePacks/Default.aspThe installation of SP4 applies updates to the base Windows NT Workstation 4.0 product including the installation options. Applying SP4 also updates certain Windows NT Workstation 4.0 features. Microsoft previously recommended that customers also run Y2KSETUP.EXE. to address the following components: Microsoft Data Access Components, Site Server Express, Microsoft Internet Explorer. These areas are now addressed in step 1. Refer to Note 7 for additional details. Users should also apply any Windows NT Year 2000 (Y2K) Updates that have been made available post-SP4. The current post-SP4 Year 2000 updates are listed below. Current post-SP4 Updates and their respective Knowledge Base (KB) Articles address the following known Year 2000 issues: (Additional information about these issues can be obtained at http://support.microsoft.com/support/)
Step 3: Overview: The final step of the process is to audit the target system to verify that Step 1 and Step 2 have been performed correctly.
Detail: When users load the Windows NT Workstation 4.0 operating system on a computer they are asked to select from many installation options. These options are listed in Table 2 (below). The known Year 2000 issues with Windows NT Workstation 4.0 operating system itself and each of the options listed in Table 2 below should have been updated after SP4 was applied. Table 2
In addition to the selectable options offered during installation of the Windows NT Workstation 4.0 operating system, there are additional features of the Windows NT Workstation 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 Workstation Web site. Table 3 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of the Windows NT Workstation 4.0 product since its original release. Use this table to verify the compliance of each Windows NT Workstation 4.0 feature installed on the Target System.
Table 3
Conclusion: If all of the Windows NT Workstation 4.0 features that remain on the system after performing Step 1 and Step 2 are listed as "Compliant" in the table, Steps 1 and 2 were conducted correctly and the copy of Windows NT Workstation 4.0 on the Target System should have no known Year 2000 issues. If a feature with a "Not Compliant" rating remains on the Target System, the most likely cause is a failure to perform both Step 1 and Step 2 to completion. In this case, please review/retry those steps and associated actions.
Notes: 1. To determine which versions of FrontPage Server Extensions are actively in use on a system, 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. 2. This Not Compliant version of this feature should only be present if the procedures outlined in Step 1 have not been performed correctly. 3. This Not Compliant version of this feature should only be present if the procedures outlined in Step 2 have not been performed correctly. 4. There is no Content Analyzer feature in Site Server Express 3.0. A replacement version that is Year 2000-compliant will be made available. 5. 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. 6. To verify the version number of a dynamic link library (DLL) file, users should:
7. Y2KSETUP.EXE has been removed from the recommended remediation path.
Appendix: For convenience, the Table 4 (below) lists features and products that Microsoft has made available on the Windows NT Workstation web site that Microsoft does not consider to be part of the Window NT Workstation 4.0 product for Year 2000 compliance purposes. Table 4
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Itemized List of products in each Volume
|
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA. 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.
|
||
|
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. 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.  | ||