Microsoft TechNet ITHome - Microsoft Year 2000 Product Guide
Microsoft Products
Product Entry Guide Detail


The Microsoft Year 2000 Resource Center Product Guide details specific Year 2000 information concerning Microsoft products. The information in the product guide is presented to assist IT professionals in planning their transition to the Year 2000. If you cannot find a specific product and it is not on the "Microsoft Products: Testing Yet to be Completed" list, you can assume it will NOT be tested for compliancy.
Microsoft will continually update the Year 2000 Product Guide with the most current Year 2000 test information. Visit the Year 2000 Product Guide for more details regarding the Microsoft Compliance Categories.

------------------------
Microsoft Year 2000 Resource Center
Windows Media Player  5.2   (Turkish)

Product Summary
Product: Windows Media Player Version: 5.2 Category:Compliant*
Language: Turkish OS: 32-Bit Win Release Date: 01 Jan 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance:

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre-or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Basque)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Basque OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Catalan)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Catalan OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Chinese - Simplified)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Chinese - Traditional)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Chinese - Traditional OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Czech)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Czech OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Danish)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Danish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Dutch)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Dutch OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (English)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Finnish)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Finnish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (French)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (German)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Greek)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Greek OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Hungarian)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Hungarian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Italian)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Japanese)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Korean)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Norwegian)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Norwegian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Polish)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Polish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Portuguese (Brazil))

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Portuguese)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Portuguese OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Russian)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Slovak)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Slovak OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Slovenian)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Slovenian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Spanish)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Swedish)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Swedish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.0   (Turkish)

Product Summary
Product: Windows Media Player Version: 6.0 Category:Compliant*
Language: Turkish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Basque)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Basque OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Catalan)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Catalan OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Chinese - Simplified)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Chinese - Traditional)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Chinese - Traditional OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Czech)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Czech OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Danish)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Danish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Dutch)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Dutch OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (English)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Finnish)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Finnish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (French)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (German)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Greek)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Greek OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Hungarian)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Hungarian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Italian)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Japanese)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Korean)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Norwegian)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Norwegian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Polish)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant
Language: Polish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: None
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Portuguese (Brazil))

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Portuguese)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Portuguese OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Russian)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Slovak)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Slovak OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Slovenian)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Slovenian OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Spanish)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Swedish)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Swedish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 Media Player  6.1   (Turkish)

Product Summary
Product: Windows Media Player Version: 6.1 Category:Compliant*
Language: Turkish OS: 32-Bit Win Release Date: 09 Mar 1999
Operational Range: 01 Jan 1900 - 31 Dec 2035
Prerequisites: DirectX 3.0 Runtime, Active X 3.01 Runtime
Product Dependencies: None
Clock Dependencies: None
Last Updated: 02 Nov 1999
Product Details

Note: There have been no known Internationalization concerns to test. Thus, this product is not dependent on an English language platform for compliance.

How the product handles dates:

The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored.

Two-digit shortcut handling:

Not applicable.

Recommendations to meet compliance

Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430

Testing guidelines and recommendations:

  • Users with the system clock set to some date before year 2000 can play back content authored in the pre- or post- year 2000 era.
  • Users with the system clock set to some date after year 2000 can play back content authored in the pre- or post- year 2000 era.

 


Legend of Symbols:
*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 MediaPlayer2  5.01.51.0402   (English)

Product Summary
Product: Windows MediaPlayer2 Version: 5.01.51.0402 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 01 Apr 1998
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, or Windows NT4 Service Pack 3
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 13 Sep 1999
Product Details

This information applies to: version 5.01.51.0402 & greater.

How the product handles dates:

There is an OCX programmability property of the MediaPlayer called CreationDate, which is encoded into stored content at the time it is created. It is based on the system date of the machine that is doing the encoding. In the case of content that is encoded in realtime, the CreationDate can come from two places:

1) The encoding server (or "Rex server"). In this case, the URL for the file is msbd://servername

2) The Netshow server. In this case, a Rex server is sending content to a Netshow server to be streamed. The URL for these cases takes the form http://some_web_server/filename.asx. Here the CreationDate

In both cases, the internals of the MediaPlayer do not modify this value.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string in the form "Copyright 1994-1995, Microsoft Corporation". In addition there are the system attributes for file creation, access, and modification dates, but these are not used internally by the MediaPlayer.

Version checking for the MediaPlayer and installed codecs is based upon the standard version format, which does not include the year. (For Example – The current version is 5.01.51.0402, in which 0402 represents April 2nd.)

Two-digit shortcut handling:

There is no user interface for specifying the CreationDate, since it is generated by operating system. There is no 2-digit shortcut handling.

In some embedded cases, the CreationDate is formatted by embedded environment into mm/dd/yy when it is displayed as a string. In these cases, the years 1900-99 are displayed as 2-digit years (e.g. 04/02/98). The years 2000-99 are displayed as four digits (e.g. 04/02/2034). In any case, this formatting is not handled directly by the MediaPlayer, but instead by the embedded environment. The supported embedded environments are Netscape Navigator (Versions 3 and 4), Internet Explorer (3.02 and 4.01), Visual Basic, and Visual C++.

Testing guidelines and recommendations:

Confirmation of CreationDate:

1)Stored Content- Test the specified range of dates by setting the system date and encoding test files.

2)Real-time Encoded Content- Verify the specified range of dates by setting the system date of a Netshow server that is streaming real-time encoded content.


Legend of Symbols:
*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 Embedded  4.0   (English)

Product Summary
Product: Windows NT Embedded Version: 4.0 Category:Compliant*
Language: English OS: Win NT Release Date: 16 Jun 1999
Operational Range: -
Prerequisites: Consult the Windows NT4 Service Pack 5 compliance document for any issues or updates related to relevant Windows NT4 platform technology included in Windows NT Embedded 4.0
Product Dependencies:
Clock Dependencies: System Clock
Last Updated: 14 Oct 1999
Product Details

Windows NT Embedded 4.0 consists of an authoring environment and a user-generated embedded target operating system, which is based on a Windows NT Server 4.0 and service pack 5 binary repository. Please consult the Windows NT4 SP5 compliance document for any issues or updates related to relevant Windows NT4 platform technology accessible from the Windows NT Embedded 4.0 Target Designer tool. The authoring tools, Target Designer and Component Designer do not contain any known Year 2000 issues.

How the product handles dates:

In the Windows NT Embedded authoring tools (Target Designer, Component Designer), date values are generated and manipulated in the following scenarios:

  • During license enforcement, native NT system calls are utilized and time values are manipulated as type LARGE_INTEGER (64 bits).
  • When a new target configuration is created within Target Designer, the date/time is manipulated with the GetSystemTimeAsFileTime() API.

Two-digit shortcut handling:

The first 2 digits are assumed according to a specific rule in cases where only 2 digits are supplied for the date. The rule is:

  • 2-digit dates between 00-79 are assumed to occur in the 2000s.
  • 2-digit dates between 80-99 are assumed to occur in the 1900s.

 

Testing guidelines and recommendations:

It is recommended that you verify the year 2000 readiness of all components that are included as part of an embedded configuration. The following tables enumerate the technologies included in the Windows NT Embedded 4.0 product:

Table 1: Included Microsoft technology

Technology

Version

Feature Compliance Rating

Notes

Windows NT Server

4.0 + SP5

Compliant

 

Microsoft Management Console

1.0

Compliant

 

Routing and Remote Access Services

4.0

Compliant

 

Microsoft Data Access Components (MDAC)

2.1

Compliant

SP1 of MDAC 2.1 already applied on the repository.

Resource Kit

4.0

Compliant

One utility - shutdown.exe

Microsoft Internet Information Server

3.0

Compliant

 

 

Table 2: Windows NT Embedded 4.0 – embedded-enabling features

Feature

Type

Compliance Rating

El-Torito driver

Mass Storage Device

Compliant

Write-Filter driver

Storage filter driver

Compliant

Serial Console

Remote Administration

Compliant

Graphical Remote Admin

Remote Administration

Compliant

System Message Interception

Error Recovery

Compliant

No Page file support

Virtual Memory

Compliant

 


Legend of Symbols:
*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 Embedded  4.0   (German)

Product Summary
Product: Windows NT Embedded Version: 4.0 Category:Compliant*
Language: German OS: Win NT Release Date: 16 Jun 1999
Operational Range: -
Prerequisites: Consult the Windows NT4 Service Pack 5 compliance document for any issues or updates related to relevant Windows NT4 platform technology included in Windows NT Embedded 4.0
Product Dependencies:
Clock Dependencies: System Clock
Last Updated: 04 Nov 1999
Product Details

Windows NT Embedded 4.0 consists of an authoring environment and a user-generated embedded target operating system, which is based on a Windows NT Server 4.0 and service pack 5 binary repository. Please consult the Windows NT4 SP5 compliance document for any issues or updates related to relevant Windows NT4 platform technology accessible from the Windows NT Embedded 4.0 Target Designer tool. The authoring tools, Target Designer and Component Designer do not contain any known Year 2000 issues.

How the product handles dates:

In the Windows NT Embedded authoring tools (Target Designer, Component Designer), date values are generated and manipulated in the following scenarios:

  • During license enforcement, native NT system calls are utilized and time values are manipulated as type LARGE_INTEGER (64 bits).
  • When a new target configuration is created within Target Designer, the date/time is manipulated with the GetSystemTimeAsFileTime() API.

Two-digit shortcut handling:

The first 2 digits are assumed according to a specific rule in cases where only 2 digits are supplied for the date. The rule is:

  • 2-digit dates between 00-79 are assumed to occur in the 2000s.
  • 2-digit dates between 80-99 are assumed to occur in the 1900s.

 

Testing guidelines and recommendations:

It is recommended that you verify the year 2000 readiness of all components that are included as part of an embedded configuration. The following tables enumerate the technologies included in the Windows NT Embedded 4.0 product:

Table 1: Included Microsoft technology

Technology

Version

Feature Compliance Rating

Notes

Windows NT Server

4.0 + SP5

Compliant

 

Microsoft Management Console

1.0

Compliant

 

Routing and Remote Access Services

4.0

Compliant

 

Microsoft Data Access Components (MDAC)

2.1

Compliant

SP1 of MDAC 2.1 already applied on the repository.

Resource Kit

4.0

Compliant

One utility - shutdown.exe

Microsoft Internet Information Server

3.0

Compliant

 

 

Table 2: Windows NT Embedded 4.0 – embedded-enabling features

Feature

Type

Compliance Rating

El-Torito driver

Mass Storage Device

Compliant

Write-Filter driver

Storage filter driver

Compliant

Serial Console

Remote Administration

Compliant

Graphical Remote Admin

Remote Administration

Compliant

System Message Interception

Error Recovery

Compliant

No Page file support

Virtual Memory

Compliant

 


Legend of Symbols:
*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 Embedded  4.0   (Japanese)

Product Summary
Product: Windows NT Embedded Version: 4.0 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 16 Jun 1999
Operational Range: -
Prerequisites: Consult the Windows NT4 Service Pack 5 compliance document for any issues or updates related to relevant Windows NT4 platform technology included in Windows NT Embedded 4.0
Product Dependencies:
Clock Dependencies: System Clock
Last Updated: 05 Nov 1999
Product Details

Windows NT Embedded 4.0 consists of an authoring environment and a user-generated embedded target operating system, which is based on a Windows NT Server 4.0 and service pack 5 binary repository. Please consult the Windows NT4 SP5 compliance document for any issues or updates related to relevant Windows NT4 platform technology accessible from the Windows NT Embedded 4.0 Target Designer tool. The authoring tools, Target Designer and Component Designer do not contain any known Year 2000 issues.

How the product handles dates:

In the Windows NT Embedded authoring tools (Target Designer, Component Designer), date values are generated and manipulated in the following scenarios:

  • During license enforcement, native NT system calls are utilized and time values are manipulated as type LARGE_INTEGER (64 bits).
  • When a new target configuration is created within Target Designer, the date/time is manipulated with the GetSystemTimeAsFileTime() API.

Two-digit shortcut handling:

The first 2 digits are assumed according to a specific rule in cases where only 2 digits are supplied for the date. The rule is:

  • 2-digit dates between 00-79 are assumed to occur in the 2000s.
  • 2-digit dates between 80-99 are assumed to occur in the 1900s.

 

Testing guidelines and recommendations:

It is recommended that you verify the year 2000 readiness of all components that are included as part of an embedded configuration. The following tables enumerate the technologies included in the Windows NT Embedded 4.0 product:

Table 1: Included Microsoft technology

Technology

Version

Feature Compliance Rating

Notes

Windows NT Server

4.0 + SP5

Compliant

 

Microsoft Management Console

1.0

Compliant

 

Routing and Remote Access Services

4.0

Compliant

 

Microsoft Data Access Components (MDAC)

2.1

Compliant

SP1 of MDAC 2.1 already applied on the repository.

Resource Kit

4.0

Compliant

One utility - shutdown.exe

Microsoft Internet Information Server

3.0

Compliant

 

 

Table 2: Windows NT Embedded 4.0 – embedded-enabling features

Feature

Type

Compliance Rating

El-Torito driver

Mass Storage Device

Compliant

Write-Filter driver

Storage filter driver

Compliant

Serial Console

Remote Administration

Compliant

Graphical Remote Admin

Remote Administration

Compliant

System Message Interception

Error Recovery

Compliant

No Page file support

Virtual Memory

Compliant

 


Legend of Symbols:
*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 Option Pack  4.0   (Arabic)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Arabic OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Chinese - Simplified)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Chinese - Simplified OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Chinese - Traditional)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Chinese - Traditional OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Czech)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Czech OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Danish)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Danish OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Dutch)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Dutch OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (English)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: English OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Finnish)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Finnish OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (French)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: French OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (German)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: German OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Hebrew)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Hebrew OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Hungarian)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Hungarian OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Italian)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Italian OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Japanese)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Japanese OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Korean)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Korean OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Norwegian)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Norwegian OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Pan-Chinese)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Pan-Chinese OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Polish)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Polish OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Portuguese (Brazil))

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Portuguese (Brazil) OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Russian)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Russian OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Spanish)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Spanish OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Swedish)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Swedish OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Option Pack  4.0   (Thai)

Product Summary
Product: Windows NT Option Pack Version: 4.0 Category:Compliant*
Language: Thai OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates.
Product Dependencies:
Clock Dependencies:
Last Updated: 20 Oct 1999
Product Details

Windows NT Option Pack 4.0 is an integral part of Windows NT 4.0. To achieve compliance, Windows NT 4.0 Service Pack 4 or higher must be installed, along with any necessary post-service pack updates.

For further information, see the Windows NT Server 4.0, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4.0, SP4, SP5 and SP6 compliance documents.

Note: This page is merely a redirect to the Windows NT compliance documents and does not signify Windows NT Option Pack or any of its components are stand alone products.


Legend of Symbols:
*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 Resource Kit  4.0   (English)

Product Summary
Product: Windows NT Resource Kit Version: 4.0 Category:Compliant*#
Language: English OS: Win NT Release Date: 16 Jul 1997
Operational Range: 01 Jan 1980 - 31 Dec 2035
Prerequisites: Windows NT4 Service Pack 4
Product Dependencies: Windows NT Server 4.0
Clock Dependencies: None
Last Updated: 18 Oct 1999
Product Details

Certain tools comprising the Windows NT4 Resource Kit Tools Supplement 2 were tested for year 2000 issues. Those tools comprising the Windows NT4 Resource Kit Tools Supplement 2 that were tested for year 2000 date related issues are identified below. The tools that have known year 2000 issues are identified below. Following these, is a table of tools (Table A), that where tested and no year 2000 date related issues were identified at the conclusion of the year 2000 testing:

TOOLS WITH IDENTIFIED YEAR 2000 ISSUES:

Available Updates for Windows NT Resource Kit:

Available year 2000 updates for the Windows NT 4.0 Resource Kit can be found here: ftp://ftp.microsoft.com/reskit/y2kfix/.

 

Windows NT 4 Resource Kit Tools Module Exception Status

ForFiles.Exe

FORFILES.exe treats 2-digit dates as follows: 00 through 79 are assumed in the year 2000; 81 through 99 are assumed in the year 1900 and 80 does not produce any output.

The FORFILES.exe allows a single digit year entry and then treats that entry as a year in the 1900s. It does not allow 4-digit dates to be entered.

An update is available that resolves the above issue for the FORFILES.exe can be found at ftp://ftp.microsoft.com/reskit/y2kfix/.

Logtime.Exe

Logtime.exe logs dates using 2 digits for the year. It is up to the consumer of the logged time to interpret it correctly.

An updated version of logtime.exe that uses a 4-digit year is available at ftp://ftp.microsoft.com/reskit/y2kfix/.

TimeServ

The Windows NT Resource Kit Time service supports a number of different methods for obtaining the correct time. Some of these solutions are hardware based (GPS-based expansion cards, radio clocks, etc.) while others are software based (dial-up or NTP connection to a service such as USNO or NIST, Lanman within the network – as Primary and Secondary). Due to the lack of hardware availability, Microsoft cannot test the support for the hardware based solutions and therefore cannot comment on their Y2K compliance. Microsoft has tested the network-based synchronization (NTP and Lanman) and no year 2000 date related issues were identified at the conclusion of the year 2000 testing. Microsoft cannot explicitly test the dial-up support for the various Time Service providers. Based on our code review, there was no readily identifiable date dependent functionality in this portion of the application. The USNO and NIST (ACTS) return ASCII strings based on UTC Time. Neither the generation of these strings nor the handling of these stings by TimeServ revealed year 2000 date related issues at the conclusion of the year 2000 testing. Microsoft cannot test year 2000 date related issues for the numerous supported Time Service Providers (e.g. USNO, NIST, ACTS) or the numerous modems that may be in use. Microsoft recommends that customers perform their own testing of TimeServ in their environment and contact the Time Service Providers they are using to determine their year 2000 Compliance.

It should also be noted that, after the first successful synchronization, TimeServ will not replicate a Time/Date that is more than a 12 hour variation from the current time. This is to prevent an erroneous time propagating through the network.

 

Earlier in 1999, before TimeServ testing had been completed, Microsoft had made a version of W32Time available (ftp://ftp.microsoft.com/reskit/y2kfix/) for customers to use instead of TimeServ. W32Time is the time service that will be included as part of Windows 2000. It was modified to work with Windows NT 4.0 and made available for customers. This was done because of the complexities of TimeServ hardware support and the fact that Microsoft cannot test all of TimeServ. W32Time only supports the NTP/Lanman synchronization method. No year 2000 date related issues were identified at the conclusion of the year 2000 testing the NTP/Lanman synchronization used by TimeServ and that used by W32Time.

Customers who have deployed W32Time are recommended to continue using W32Time. An updated version of W32Time has recently been made available to address several customer reported, non-year 2000 related issues. Customers who are experiencing any of these issues should update their version of W32Time here: ftp://ftp.microsoft.com/reskit/y2kfix/

A Note Regarding Platform Support and Interoperability: It should be noted that TimeServ can be used on Windows NT 3.51 and Windows NT 4.0. It should also be noted that our testing coverage of W32Time and TimeServ also included interoperability testing with both tools acting as both server and client.

In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain W32Time for NT4 as compliant through January 1, 2001. Additionally, Microsoft intends to maintain the tested portions of TimeServ as compliant through January 1, 2001.

WINAT has a known year 2000 issue that is addressed by Windows NT Service Pack 5.

KixStart has not been tested for year 2000 date related issues. At this time Microsoft has no plans to test these applications.

REXX has not been tested for year 2000 date related issues. At this time Microsoft has no plans to test this application. Microsoft is aware of one issue in the REXX application. The DATE("U") function within REXX operates using an offset from 1900. For example, if the system date is set to 09/27/2004, the function will return 09/27/104. At this time, Microsoft has no plans to make any updates to this application. Customers should evaluate their use of this function within REXX and ensure proper use of the function.

Applications in APPS folder have not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

Applications in PERL folder have not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

Applications in POSIX folder have not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

Public Domain software in the SOURCE\GNU folder has not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

TABLE A

Windows NT 4 Resource Kit Tools Tested

No year 2000 date related issues were identified at the conclusion of the year 2000 testing of the following NT4 Resource Kit tools.

ADDUSERS.EXE

DRIVERS.EXE

NETDOM.EXE

RCONMODE.EXE

SNMPUTIL.EXE

ANIEDIT.EXE

DSKPROBE.EXE

NETSVC.EXE

RCONSTAT.EXE

SOON.EXE

APIMON.EXE

DUMPEL.EXE

NETWATCH.EXE

RCONSVC.EXE

SRVANY.EXE

ASSOCIATE.EXE

EM2MS.EXE

NLMON.EXE

RCRUNCMD.EXE

SRVCHECK.EXE

ATANLYZR.EXE

EMPTY.EXE

NLTEST.EXE

REG.EXE

SRVINFO.EXE

AUDITPOL.EXE

EMPTY.EXE

NOW.EXE

REGBACK.EXE

SRVINSTW.EXE

AUTOEXNT.EXE

ENUMPRN.EXE

NTIMER.EXE

REGDMP.EXE

SRVMON.EXE

AUTOLOG.EXE

EXCTRLST.EXE

NTRIGHTS.EXE

REGFIND.EXE

SU.EXE

BREAKFTM.EXE

EXCTRLST.EXE

NTUUCODE.EXE

REGINI.EXE

SUBINACL.EXE

BROWMON.EXE

EXETYPE.EXE

OH.EXE

REGKEY.EXE

SUSS.EXE

BROWSTAT.EXE

EXPNDW32.EXE

OLEVIEW.EXE

REGREST.EXE

SYSDIFF.EXE

C2CONFIG.EXE

FILEVER.EXE

PASSPROP.EXE

REMOTE.EXE

TDISHOW.EXE

CCDIST.EXE

FINDGRP.EXE

PATHMAN.EXE

RKILL.EXE

TELNETD.EXE

CCDIST35.EXE

FIXACLS.EXE

PDLCNFIG.EXE

RKILLSRV.EXE

TEXTVIEW.EXE

CHOICE.EXE

FLOPLOCK.EXE

PDLSVC.EXE

RMTSHARE.EXE

TIMEOUT.EXE

CLEARMEM.EXE

FREEDISK.EXE

PDUMP.EXE

ROBOCOPY.EXE

TIMETHIS.EXE

CLEARMEM.EXE

FTEDIT.EXE

PERF2MIB.EXE

RSHSETUP.EXE

TLIST.EXE

CLIP.EXE

GETMAC.EXE

PERFMTR.EXE

RSHSVC.EXE

TLIST.EXE

CLIPSTOR.EXE

GETSID.EXE

PERFMTR.EXE

RSMSVC.EXE

TLOCMGR.EXE

COMPREG.EXE

GFLAGS.EXE

PERMCOPY.EXE

SC.EXE

TOP.EXE

COMPRESS.EXE

GLOBAL.EXE

PERMS.EXE

SCANREG.EXE

TOPDESK.EXE

CPUSTRES.EXE

GRPCPY.EXE

PFMON.EXE

SCLIST.EXE

TOTLPROC.EXE

CPUSTRES.EXE

HEAPMON.EXE

PFMON.EXE

SCOPY.EXE

TRANSLATE.EXE

CREATFIL.EXE

IFMEMBER.EXE

PMON.EXE

SECADD.EXE

TZEDIT.EXE

CREATFIL.EXE

IMAGEDIT.EXE

PMON.EXE

SECEDIT.EXE

UNDOINST.EXE

CTRLIST.EXE

INET.EXE

PPERF.EXE

SETEDIT.EXE

UPTOMP.EXE

CTRLIST.EXE

INSTALER.EXE

PROBE.EXE

SETEDIT.EXE

USRSTAT.EXE

DATALOG.EXE

INSTEXNT.EXE

PROBEPRC.EXE

SETUPMGR.EXE

USRTOGRP.EXE

DATALOG.EXE

INSTSRV.EXE

PROFILE.EXE

SETX.EXE

VADUMP.EXE

DEFPTR.EXE

KERNPROF.EXE

PSTAT.EXE

SHORTCUT.EXE

VDESK.EXE

DELPROF.EXE

KILL.EXE

PSTAT.EXE

SHOWACLS.EXE

WAIT.EXE

DELSRV.EXE

KILL.EXE

PULIST.EXE

SHOWDISK.EXE

WAIT.EXE

DEPENDS.EXE

LEAKYAPP.EXE

PVIEW.EXE

SHOWGRPS.EXE

WAITFOR.EXE

DESKTOPS.EXE

LEAKYAPP.EXE

PVIEW.EXE

SHOWINST.EXE

WHOAMI.EXE

DFLYDIST.EXE

LINKCK.EXE

PVIEWER.EXE

SHOWMBRS.EXE

WINDIFF.EXE

DH.EXE

LOCAL.EXE

PVIEWER.EXE

SHOWPERF.EXE

WINMSDP.EXE

DHCPCMD.EXE

LOGEVENT.EXE

QSLICE.EXE

SHOWPERF.EXE

WINSCHK.EXE

DHCPLOC.EXE

LOGOFF.EXE

QUICKRES.EXE

SHUTDOWN.EXE

WINSCL.EXE

DIRUSE.EXE

MIBCC.EXE

RASLIST.EXE

SHUTGUI.EXE

WINSDMP.EXE

DISKMAP.EXE

MONITOR.EXE

RASUSERS.EXE

SIPANEL.EXE

WNTIPCFG.EXE

DISKSAVE.EXE

MONITOR.EXE

RCLIENT.EXE

SLEEP.EXE

WPERF.EXE

DISKUSE.EXE

MUNGE.EXE

RCMD.EXE

SMCONFIG.EXE

WRKILL.EXE

DNSCMD.EXE

NETCLIP.EXE

RCMDSVC.EXE

SNMPMON.EXE

XCACLS.EXE

DOMMON.EXE

NETCONS.EXE

RCONGRP.EXE

DRIVERS.EXE


Legend of Symbols:
*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 - Terminal  4.0 SP3   (English)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP3 Category:Compliant*#
Language: English OS: Win NT Release Date: 16 Jun 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 3 Year 2000 Update (see below)
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time.
Last Updated: 21 Sep 1999
Product Details

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3").

When users load the Terminal Server operating system on a computer they are asked to select from a number of installation options. In addition, Microsoft has made additional features available to licensed users on the Terminal Server CD and via the Microsoft website. 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 Year 2000 readiness status. .

 

Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features contain known Year 2000 issues that require updates. In order to update a given computer running Terminal Server 4.0 (the Target System) to a Compliant status, users must install the Windows NT Server, Terminal Server Edition, Service Pack 4 (TS SP4), expected to be released in June 1999. Once available, this approach is recommended. Information on this Service Pack is available on the Terminal Server web site. See the Windows NT Server Terminal Server 4.0, SP4 Year 2000 compliance document for more information.

Microsoft recognizes that some users of Terminal Server 4.0 would prefer or need to remain on the base system (which is integrated with Service Pack 3) until after January 1, 2000. To address the needs of these users, Microsoft has prepared a number of updates to the base Terminal Server 4.0 operating system and features. Users should note, however, that:

  • Microsoft has assigned a compliance rating of "Compliant# to Terminal Server 4.0-based systems where these updates have been applied
  • Users must apply TS SP4 to get the rating of "Compliant" for the target system
  • The highest compliance rating that Microsoft will assign to a system running Terminal Server 4.0 without Service Pack 4 or greater is, "Compliant#"

Further, for those Terminal Server systems without Service Pack 4.0 or greater installed, Microsoft intends to maintain Terminal Server 4.0 with compliance rating at the "Compliant# level through January 1, 2001. Microsoft will do this by producing updates to the extent that new, Year 2000-related issues are discovered that would otherwise cause Microsoft to lower the rating of Terminal Server 4.0 below the "Compliant# level.

The tables included below list the specific options and features (by version) that users of Windows NT Server 4.0, Terminal Server Edition 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 that has not been upgraded to TS SP4 or greater.

Note that some options and features of Terminal Server cannot be brought to a Compliant status without applying SP4. Using the information below, however, the options and features can be brought to at least a Compliant# status.

In summary, for users of Terminal Server 4.0 without TS SP4 or greater, the options and features that need to be addressed in order to attain a status of Compliant# are:

  • Active Directory Services Interface version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft FrontPage 97 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft FrontPage 97 Server Extensions (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Internet Explorer version 2.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Internet Explorer version 3.02 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Explorer version 4.01 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Locator Service version 1.0 (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Transaction Server version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Transaction Server version 1.1 (Not Tested; upgrade required to ensure Compliant status)
  • Site Server Express version 2.0 (Not Compliant; upgrade required to reach Compliant status)

Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.

 

Evaluating the Status of a Windows NT Server 4.0, Terminal Server Edition System

Microsoft has assigned the base (SP3) Terminal Server 4.0 operating system 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:

 

  • Windows NT Server, Terminal Server Edition post-SP3 Year 2000 update -- a single install released on February 26, 1999 installs these file on to user systems.

An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either:

http://www.microsoft.com/ntserver/all/downloads

or

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/

 

 

  • A list of the issues addressed by the post SP3 Year 2000 update is listed below:
    1. User Manager Does Not Recognize February 2000 As a Leap Year. (Q175093) User Manager and User Manager for Domains will not accept February 29, 2000 as a valid date to expire an account.
    2. Control Panel Date/Time applet. (Q180122) The date displayed by the Control Panel Date/Time applet 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 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 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 Server computer running File and Print Services for NetWare (FPNW), the client's date and time are not synchronized with that of the server when the server's date and time are beyond 12/31/1999 at 11:59:59 pm.
    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.
  • Users should note that some known issues in the base (SP3) Windows NT Server 4.0, Terminal Server Edition operating system are not being addressed, hence the rating of "Compliant#." It is for this reason Microsoft recommends upgrading to Windows NT Server, Terminal Server Edition Service Pack 4. Listed below are the known acceptable deviations remaining in SP3 after the application of the Post-Service Pack 3 Year 2000 Update.

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:

    1. In a dual boot scenario, the other operating system(s) may not handle this situation properly. MS-DOS is in this class of operating systems.
    2. Some BIOSes detect this behavior as an invalid date and query the user for the correct date. This would prevent a system from rebooting without user input.

 

4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the OLE Automation product guide for more information.

5. Incorrect Date Displayed when viewing a saved System Info Report. (Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".

6. Four-Digit Year Format for Non-English Regional Settings. (Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring the Regional Settings Short Date Style of a system, users may not be able to choose a 4-digit year format. However, users can manually enter a 4-digit date style.

 

Installation options included in the Compliant# status of Windows NT Server 4.0, Terminal Server Edition are listed in Table 1 (below).

Table 1.

Option/Service Name

Compliance Rating

DHCP Relay Agent

Compliant#

DLC Protocol

Compliant

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

Remote Boot Service

Compliant

RIP for Internet Protocol

Compliant

RIP for NWLink IPX/SPX-Compatible Transport

Compliant

RPC Configuration

Compliant

RPC Support for Banyan

Compliant

SAP Agent

Compliant

Server

Compliant

Services for Macintosh

Compliant

Simple TCP/IP Services

Compliant

SNMP Service

Compliant

Streams Environment

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant#

Workstation

Compliant

In addition to the selectable options offered during installation of Terminal Server, there are additional features that may be or may have been installed on the Target System.

Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of Terminal Server 4.0 via the Terminal Server CD and the Terminal Server web page since release. In addition, because some users have installed various Windows NT Server 4.0 features and components on to Terminal Server, Table 2 includes a list of features that Microsoft has made available for Windows NT Server 4.0. This does not imply support or testing of the listed Windows NT Server features and options on Terminal Server. Use this table to verify the compliance of each feature installed on the Target Machine and to apply appropriate fixes where necessary. The Required Actions below must be performed to bring the listed features to Year 2000 compliance. Year 2000 compliance information on NT Server and other Microsoft products are found at http://www.microsoft.com/y2k.

Table 2.

Feature Name

Version

Initial Compliance Rating

Required Actions

Active Directory Services Interface (ADSI)

1.0

Not Tested

Install ADSI 2.0

Active Directory Services Interface

2.0

Compliant

None

Certificate Server

1.0

Compliant

See Note 1

Distributed File Service

4.0

Compliant

None

Distributed File Service

4.1

Compliant

None

Imaging for Windows

N/A

Compliant

None – the Compliant rating applies to versions that run on Windows NT Server 4.0

Index Server

1.0

Compliant

None

Index Server

1.1

Compliant

None

Index Server

2.0

Compliant

None

Internet Connection Services for Microsoft Remote Access Service

1.0

Compliant

None

Microsoft Cluster Services

1.0

Compliant

None

Microsoft Data Access Components

See Required Actions

See Required Actions

Some versions of MDAC are not compliant. To make MDAC compliant, please review MDAC product guide for latest information on year 2000 issues and updates for MDAC.

Microsoft Euro Currency Support for
Windows NT 4.0

N/A

Compliant

None

Microsoft Euro Currency Support for
Terminal Server

N/A

Compliant

None

Microsoft FrontPage 97

"97"

Not Compliant

To make compliant, install FrontPage 97 Year 2000 hot fixes.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

To make compliant, install FrontPage 98 Server Extensions from the Windows NT Option Pack. Also see Note 2.

Microsoft FrontPage 97

"97" with fixes

Compliant

To determine that Microsoft Front Page 97 fixes are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least02.00.3002.23. See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

None -- Also see note 2.

Microsoft Internet Explorer

2.00

Not Tested

To make compliant, upgrade to Internet Explorer 4.01 SP1+fixes

Microsoft Internet Explorer

3.02

Not Compliant

To make compliant, apply year 2000 fixes

Microsoft Internet Explorer

3.02 with Year 2000 fixes

Compliant

To determine that Microsoft Internet Explorer version 3.02 fixes are installed, verify the version number of the file named:
"(system directory)\system32\wininet.dll"
is in the range of either:

  • 4.70.0.1335 to 4.70.0.1399 (for browsers with "File Upload" features enabled)

or

  • 4.70.0.1460 to 4.70.0.1499 (for browsers without "File Upload" features enabled)

See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft Internet Explorer

4.01

Not Compliant

To make compliant, upgrade to Internet Explorer version 4.01 SP1+fixes

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1

Compliant#

To determine that Microsoft Internet Explorer version 4.01 SP1 is installed, verify the version number of the file named:
"(system directory)\system32\comctl32.dll"
is at least 4.70.3110.9 or higher.

See note 5 for instructions on verifying version numbers of .DLL files.

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1A

Compliant#

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1 or SP1A w/ additional fixes

Compliant

Additional fixes can be found on Internet Explorer 4.0x year 2000 Product Guide. www.microsoft.com/y2k

Microsoft Internet Information Server

2.0

Compliant

None

Microsoft Internet Information Server

3.0

Compliant

None

Microsoft Internet Information Server

4.0

Compliant

None

Microsoft Internet Locator Service

1.0

Not Compliant

To make compliant, install Microsoft Internet Locator Service version 2.0

Microsoft Internet Locator Service

2.0

Compliant

None

Microsoft Management Console

1.0

Compliant

None

Microsoft Message Queue Server

1.0

Compliant

None

Microsoft Message Queue Server

1.0E

Compliant

None

Microsoft Transaction Server

1.0

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

1.1

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

2.0

Compliant

None

Microsoft Transaction Server

2.0 SP

Compliant

None

Microsoft Virtual Machine

(Many versions)

See required action for description

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

To make compliant, install NetShow 3.0

NetShow Services

3.0

Compliant

None

Routing and Remote Access Services

4.0

Compliant

None

Site Server Express

2.0

Not Compliant

To make compliant, install Site Server Express version 3.0

Site Server Express

3.0

Compliant

None - See Note 3

TAPI SDK

2.1

Compliant

None

Terminal Server client

16-bit

Compliant

None

Terminal Server client

32-bit

Compliant

None

Web Administrator for Microsoft Windows NT Server 4.0

2.0

Compliant

None

Windows Load Balancing Service

2.2

Compliant

Windows Media Player

6.0

Compliant

None

Windows Scripting Host

1.0

Compliant

None

Zero Administration Kit for Windows NT 4.0

N/A

Compliant

None –See Note 4

Zero Administration Kit for Windows NT 4.0, Terminal Server Edition

N/A

Compliant

None –See Note 4

Appendix:

For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Server web site that Microsoft does not consider to be part of the Window NT Server 4.0 or Terminal Server 4.0 product for Year 2000 compliance purposes.

Table 3.

Feature/Product Name

Notes

ADSI Implemented in Java

Available only in Beta test versions.

Client 32 support for NetWare

This is a Novell product; consult Novell for compliance information.

Dial-Up Networking Access Service Performance and Security Upgrade

Applies only to Windows 95 should not be present with Windows NT Server 4.0.

I2O (Intelligent I/O Architecture) Drivers for Windows NT

Available only in Beta test versions.

Microsoft Windows NT Services for UNIX

Available only in Beta test versions.

Personal Web Services 4.0

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Routing and Remote Access Service Performance and Security Upgrade

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Routing and Remote Access Service Upgrade for Windows NT Server

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Windows NT Server Management Tools for Windows 95

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Notes:

  1. Certificate Server version 1.0 cannot be installed when the date is 2/29/2000.
  2. To determine which versions of FrontPage Server Extensions are actively in use, run the FrontPage Server Administrator (Fpsrvwin.exe). Click on each of the Web servers or virtual servers (listed in the box in the upper left area) that have been configured with the FrontPage Server Extensions. The version number of the FrontPage Server Extension is displayed to the right of the list. Version numbers where the first digit is "3" or greater resolve known Year 2000 issues (e.g. 3.0.2.1706). If the first digit of the version number is "1" or "2", users should install an updated version of the FrontPage Server Extensions. Refer to http://www.microsoft.com/frontpage/ for more details.
  3. There is no Content Analyzer feature in Site Server Express 3.0. An updated Content Analyzer is available from the Windows NT Server Service Pack 4 Download page.
  4. http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.

  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:
  • Start Windows NT Explorer from the "Start/Programs" menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file and clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

 

 


Legend of Symbols:
*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 - Terminal  4.0 SP3   (French)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP3 Category:Compliant*#
Language: French OS: Win NT Release Date: 16 Jun 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 3 Year 2000 Update (see below)
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time.
Last Updated: 21 Sep 1999
Product Details

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3").

When users load the Terminal Server operating system on a computer they are asked to select from a number of installation options. In addition, Microsoft has made additional features available to licensed users on the Terminal Server CD and via the Microsoft website. 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 Year 2000 readiness status. .

Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features contain known Year 2000 issues that require updates. In order to update a given computer running Terminal Server 4.0 (the Target System) to a Compliant status, users must install the Windows NT Server, Terminal Server Edition, Service Pack 4 (TS SP4), expected to be released in June 1999. Once available, this approach is recommended. Information on this Service Pack will be made available on the Terminal Server website at or before release time. A Terminal Server 4.0, SP4 Year 2000 compliance document will also be made available at http://www.microsoft.com/y2k in July 1999.

Microsoft recognizes that some users of Terminal Server 4.0 would prefer or need to remain on the base system (which is integrated with Service Pack 3) until after January 1, 2000. To address the needs of these users, Microsoft has prepared a number of updates to the base Terminal Server 4.0 operating system and features. Users should note, however, that:

  • Microsoft has assigned a compliance rating of "Compliant# to Terminal Server 4.0-based systems where these updates have been applied
  • Users must apply TS SP4 to get the rating of "Compliant" for the target system
  • The highest compliance rating that Microsoft will assign to a system running Terminal Server 4.0 without Service Pack 4 or greater is, "Compliant#"

Further, for those Terminal Server systems without Service Pack 4.0 or greater installed, Microsoft intends to maintain Terminal Server 4.0 with compliance rating at the "Compliant# level through January 1, 2001. Microsoft will do this by producing updates to the extent that new, Year 2000-related issues are discovered that would otherwise cause Microsoft to lower the rating of Terminal Server 4.0 below the "Compliant# level.

The tables included below list the specific options and features (by version) that users of Windows NT Server 4.0, Terminal Server Edition 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 that has not been upgraded to TS SP4 or greater.

Note that some options and features of Terminal Server cannot be brought to a Compliant status without applying SP4. Using the information below, however, the options and features can be brought to at least a Compliant# status.

In summary, for users of Terminal Server 4.0 without TS SP4 or greater, the options and features that need to be addressed in order to attain a status of Compliant# are:

  • Active Directory Services Interface version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft FrontPage 97 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft FrontPage 97 Server Extensions (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Internet Explorer version 2.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Internet Explorer version 3.02 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Explorer version 4.01 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Locator Service version 1.0 (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Transaction Server version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Transaction Server version 1.1 (Not Tested; upgrade required to ensure Compliant status)
  • Site Server Express version 2.0 (Not Compliant; upgrade required to reach Compliant status)

Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.

 

Evaluating the Status of a Windows NT Server 4.0, Terminal Server Edition System

Microsoft has assigned the base (SP3) Terminal Server 4.0 operating system 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:

 

  • Windows NT Server, Terminal Server Edition post-SP3 Year 2000 update -- a single install released on February 26, 1999 installs these file on to user systems.

An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either:

http://www.microsoft.com/ntserver/all/downloads

or

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/

 

 

  • A list of the issues addressed by the post SP3 Year 2000 update is listed below:
    1. User Manager Does Not Recognize February 2000 As a Leap Year. (Q175093) User Manager and User Manager for Domains will not accept February 29, 2000 as a valid date to expire an account.
    2. Control Panel Date/Time applet. (Q180122) The date displayed by the Control Panel Date/Time applet 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 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 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 Server computer running File and Print Services for NetWare (FPNW), the client's date and time are not synchronized with that of the server when the server's date and time are beyond 12/31/1999 at 11:59:59 pm.
    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.
  • Users should note that some known issues in the base (SP3) Windows NT Server 4.0, Terminal Server Edition operating system are not being addressed, hence the rating of "Compliant#." It is for this reason Microsoft recommends upgrading to Windows NT Server, Terminal Server Edition Service Pack 4. Listed below are the known acceptable deviations remaining in SP3 after the application of the Post-Service Pack 3 Year 2000 Update.

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:

    1. In a dual boot scenario, the other operating system(s) may not handle this situation properly. MS-DOS is in this class of operating systems.
    2. Some BIOSes detect this behavior as an invalid date and query the user for the correct date. This would prevent a system from rebooting without user input.

 

4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the OLE Automation product guide for more information.

5. Incorrect Date Displayed when viewing a saved System Info Report. (Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".

6. Four-Digit Year Format for Non-English Regional Settings. (Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring the Regional Settings Short Date Style of a system, users may not be able to choose a 4-digit year format. However, users can manually enter a 4-digit date style.

 

Installation options included in the Compliant# status of Windows NT Server 4.0, Terminal Server Edition are listed in Table 1 (below).

Table 1.

Option/Service Name

Compliance Rating

DHCP Relay Agent

Compliant#

DLC Protocol

Compliant

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

Remote Boot Service

Compliant

RIP for Internet Protocol

Compliant

RIP for NWLink IPX/SPX-Compatible Transport

Compliant

RPC Configuration

Compliant

RPC Support for Banyan

Compliant

SAP Agent

Compliant

Server

Compliant

Services for Macintosh

Compliant

Simple TCP/IP Services

Compliant

SNMP Service

Compliant

Streams Environment

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant#

Workstation

Compliant

In addition to the selectable options offered during installation of Terminal Server, there are additional features that may be or may have been installed on the Target System.

Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of Terminal Server 4.0 via the Terminal Server CD and the Terminal Server web page since release. In addition, because some users have installed various Windows NT Server 4.0 features and components on to Terminal Server, Table 2 includes a list of features that Microsoft has made available for Windows NT Server 4.0. This does not imply support or testing of the listed Windows NT Server features and options on Terminal Server. Use this table to verify the compliance of each feature installed on the Target Machine and to apply appropriate fixes where necessary. The Required Actions below must be performed to bring the listed features to Year 2000 compliance. Year 2000 compliance information on NT Server and other Microsoft products are found at http://www.microsoft.com/y2k.

Table 2.

Feature Name

Version

Initial Compliance Rating

Required Actions

Active Directory Services Interface (ADSI)

1.0

Not Tested

Install ADSI 2.0

Active Directory Services Interface

2.0

Compliant

None

Certificate Server

1.0

Compliant

See Note 1

Distributed File Service

4.0

Compliant

None

Distributed File Service

4.1

Compliant

None

Imaging for Windows

N/A

Compliant

None – the Compliant rating applies to versions that run on Windows NT Server 4.0

Index Server

1.0

Compliant

None

Index Server

1.1

Compliant

None

Index Server

2.0

Compliant

None

Internet Connection Services for Microsoft Remote Access Service

1.0

Compliant

None

Microsoft Cluster Services

1.0

Compliant

None

Microsoft Data Access Components

See Required Actions

See Required Actions

Some versions of MDAC are not compliant. To make MDAC compliant, please review MDAC product guide for latest information on year 2000 issues and updates for MDAC.

Microsoft Euro Currency Support for
Windows NT 4.0

N/A

Compliant

None

Microsoft Euro Currency Support for
Terminal Server

N/A

Compliant

None

Microsoft FrontPage 97

"97"

Not Compliant

To make compliant, install FrontPage 97 Year 2000 hot fixes.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

To make compliant, install FrontPage 98 Server Extensions from the Windows NT Option Pack. Also see Note 2.

Microsoft FrontPage 97

"97" with fixes

Compliant

To determine that Microsoft Front Page 97 fixes are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least02.00.3002.23. See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

None -- Also see note 2.

Microsoft Internet Explorer

2.00

Not Tested

To make compliant, upgrade to Internet Explorer 4.01 SP1+fixes

Microsoft Internet Explorer

3.02

Not Compliant

To make compliant, apply year 2000 fixes

Microsoft Internet Explorer

3.02 with Year 2000 fixes

Compliant

To determine that Microsoft Internet Explorer version 3.02 fixes are installed, verify the version number of the file named:
"(system directory)\system32\wininet.dll"
is in the range of either:

  • 4.70.0.1335 to 4.70.0.1399 (for browsers with "File Upload" features enabled)

or

  • 4.70.0.1460 to 4.70.0.1499 (for browsers without "File Upload" features enabled)

See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft Internet Explorer

4.01

Not Compliant

To make compliant, upgrade to Internet Explorer version 4.01 SP1+fixes

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1

Compliant#

To determine that Microsoft Internet Explorer version 4.01 SP1 is installed, verify the version number of the file named:
"(system directory)\system32\comctl32.dll"
is at least 4.70.3110.9 or higher.

See note 5 for instructions on verifying version numbers of .DLL files.

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1A

Compliant#

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1 or SP1A w/ additional fixes

Compliant

Additional fixes can be found on Internet Explorer 4.0x year 2000 Product Guide. www.microsoft.com/y2k

Microsoft Internet Information Server

2.0

Compliant

None

Microsoft Internet Information Server

3.0

Compliant

None

Microsoft Internet Information Server

4.0

Compliant

None

Microsoft Internet Locator Service

1.0

Not Compliant

To make compliant, install Microsoft Internet Locator Service version 2.0

Microsoft Internet Locator Service

2.0

Compliant

None

Microsoft Management Console

1.0

Compliant

None

Microsoft Message Queue Server

1.0

Compliant

None

Microsoft Message Queue Server

1.0E

Compliant

None

Microsoft Transaction Server

1.0

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

1.1

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

2.0

Compliant

None

Microsoft Transaction Server

2.0 SP

Compliant

None

Microsoft Virtual Machine

(Many versions)

See required action for description

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

To make compliant, install NetShow 3.0

NetShow Services

3.0

Compliant

None

Routing and Remote Access Services

4.0

Compliant

None

Site Server Express

2.0

Not Compliant

To make compliant, install Site Server Express version 3.0

Site Server Express

3.0

Compliant

None - See Note 3

TAPI SDK

2.1

Compliant

None

Terminal Server client

16-bit

Compliant

None

Terminal Server client

32-bit

Compliant

None

Web Administrator for Microsoft Windows NT Server 4.0

2.0

Compliant

None

Windows Load Balancing Service

2.2

Compliant

Windows Media Player

6.0

Compliant

None

Windows Scripting Host

1.0

Compliant

None

Zero Administration Kit for Windows NT 4.0

N/A

Compliant

None –See Note 4

Zero Administration Kit for Windows NT 4.0, Terminal Server Edition

N/A

Compliant

None –See Note 4

Appendix:

For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Server web site that Microsoft does not consider to be part of the Window NT Server 4.0 or Terminal Server 4.0 product for Year 2000 compliance purposes.

Table 3.

Feature/Product Name

Notes

ADSI Implemented in Java

Available only in Beta test versions.

Client 32 support for NetWare

This is a Novell product; consult Novell for compliance information.

Dial-Up Networking Access Service Performance and Security Upgrade

Applies only to Windows 95 should not be present with Windows NT Server 4.0.

I2O (Intelligent I/O Architecture) Drivers for Windows NT

Available only in Beta test versions.

Microsoft Windows NT Services for UNIX

Available only in Beta test versions.

Personal Web Services 4.0

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Routing and Remote Access Service Performance and Security Upgrade

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Routing and Remote Access Service Upgrade for Windows NT Server

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Windows NT Server Management Tools for Windows 95

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Notes:

  1. Certificate Server version 1.0 cannot be installed when the date is 2/29/2000.
  2. To determine which versions of FrontPage Server Extensions are actively in use, run the FrontPage Server Administrator (Fpsrvwin.exe). Click on each of the Web servers or virtual servers (listed in the box in the upper left area) that have been configured with the FrontPage Server Extensions. The version number of the FrontPage Server Extension is displayed to the right of the list. Version numbers where the first digit is "3" or greater resolve known Year 2000 issues (e.g. 3.0.2.1706). If the first digit of the version number is "1" or "2", users should install an updated version of the FrontPage Server Extensions. Refer to http://www.microsoft.com/frontpage/ for more details.
  3. There is no Content Analyzer feature in Site Server Express 3.0. An updated Content Analyzer is available from the Windows NT Server Service Pack 4 Download page.
  4. http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.

  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:
  • Start Windows NT Explorer from the "Start/Programs" menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file and clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

 

 


Legend of Symbols:
*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 - Terminal  4.0 SP3   (German)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP3 Category:Compliant*#
Language: German OS: Win NT Release Date: 16 Jun 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 3 Year 2000 Update (see below)
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time.
Last Updated: 21 Sep 1999
Product Details

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3").

When users load the Terminal Server operating system on a computer they are asked to select from a number of installation options. In addition, Microsoft has made additional features available to licensed users on the Terminal Server CD and via the Microsoft website. 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 Year 2000 readiness status. .

Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features contain known Year 2000 issues that require updates. In order to update a given computer running Terminal Server 4.0 (the Target System) to a Compliant status, users must install the Windows NT Server, Terminal Server Edition, Service Pack 4 (TS SP4), expected to be released in June 1999. Once available, this approach is recommended. Information on this Service Pack will be made available on the Terminal Server website at or before release time. A Terminal Server 4.0, SP4 Year 2000 compliance document will also be made available at http://www.microsoft.com/y2k in July 1999.

Microsoft recognizes that some users of Terminal Server 4.0 would prefer or need to remain on the base system (which is integrated with Service Pack 3) until after January 1, 2000. To address the needs of these users, Microsoft has prepared a number of updates to the base Terminal Server 4.0 operating system and features. Users should note, however, that:

  • Microsoft has assigned a compliance rating of "Compliant# to Terminal Server 4.0-based systems where these updates have been applied
  • Users must apply TS SP4 to get the rating of "Compliant" for the target system
  • The highest compliance rating that Microsoft will assign to a system running Terminal Server 4.0 without Service Pack 4 or greater is, "Compliant#"

Further, for those Terminal Server systems without Service Pack 4.0 or greater installed, Microsoft intends to maintain Terminal Server 4.0 with compliance rating at the "Compliant# level through January 1, 2001. Microsoft will do this by producing updates to the extent that new, Year 2000-related issues are discovered that would otherwise cause Microsoft to lower the rating of Terminal Server 4.0 below the "Compliant# level.

The tables included below list the specific options and features (by version) that users of Windows NT Server 4.0, Terminal Server Edition 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 that has not been upgraded to TS SP4 or greater.

Note that some options and features of Terminal Server cannot be brought to a Compliant status without applying SP4. Using the information below, however, the options and features can be brought to at least a Compliant# status.

In summary, for users of Terminal Server 4.0 without TS SP4 or greater, the options and features that need to be addressed in order to attain a status of Compliant# are:

  • Active Directory Services Interface version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft FrontPage 97 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft FrontPage 97 Server Extensions (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Internet Explorer version 2.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Internet Explorer version 3.02 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Explorer version 4.01 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Locator Service version 1.0 (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Transaction Server version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Transaction Server version 1.1 (Not Tested; upgrade required to ensure Compliant status)
  • Site Server Express version 2.0 (Not Compliant; upgrade required to reach Compliant status)

Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.

 

Evaluating the Status of a Windows NT Server 4.0, Terminal Server Edition System

Microsoft has assigned the base (SP3) Terminal Server 4.0 operating system 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:

 

  • Windows NT Server, Terminal Server Edition post-SP3 Year 2000 update -- a single install released on February 26, 1999 installs these file on to user systems.

An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either:

http://www.microsoft.com/ntserver/all/downloads

or

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/

 

 

  • A list of the issues addressed by the post SP3 Year 2000 update is listed below:
    1. User Manager Does Not Recognize February 2000 As a Leap Year. (Q175093) User Manager and User Manager for Domains will not accept February 29, 2000 as a valid date to expire an account.
    2. Control Panel Date/Time applet. (Q180122) The date displayed by the Control Panel Date/Time applet 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 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 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 Server computer running File and Print Services for NetWare (FPNW), the client's date and time are not synchronized with that of the server when the server's date and time are beyond 12/31/1999 at 11:59:59 pm.
    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.
  • Users should note that some known issues in the base (SP3) Windows NT Server 4.0, Terminal Server Edition operating system are not being addressed, hence the rating of "Compliant#." It is for this reason Microsoft recommends upgrading to Windows NT Server, Terminal Server Edition Service Pack 4. Listed below are the known acceptable deviations remaining in SP3 after the application of the Post-Service Pack 3 Year 2000 Update.

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:

    1. In a dual boot scenario, the other operating system(s) may not handle this situation properly. MS-DOS is in this class of operating systems.
    2. Some BIOSes detect this behavior as an invalid date and query the user for the correct date. This would prevent a system from rebooting without user input.

 

4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the OLE Automation product guide for more information.

5. Incorrect Date Displayed when viewing a saved System Info Report. (Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".

6. Four-Digit Year Format for Non-English Regional Settings. (Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring the Regional Settings Short Date Style of a system, users may not be able to choose a 4-digit year format. However, users can manually enter a 4-digit date style.

 

Installation options included in the Compliant# status of Windows NT Server 4.0, Terminal Server Edition are listed in Table 1 (below).

Table 1.

Option/Service Name

Compliance Rating

DHCP Relay Agent

Compliant#

DLC Protocol

Compliant

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

Remote Boot Service

Compliant

RIP for Internet Protocol

Compliant

RIP for NWLink IPX/SPX-Compatible Transport

Compliant

RPC Configuration

Compliant

RPC Support for Banyan

Compliant

SAP Agent

Compliant

Server

Compliant

Services for Macintosh

Compliant

Simple TCP/IP Services

Compliant

SNMP Service

Compliant

Streams Environment

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant#

Workstation

Compliant

In addition to the selectable options offered during installation of Terminal Server, there are additional features that may be or may have been installed on the Target System.

Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of Terminal Server 4.0 via the Terminal Server CD and the Terminal Server web page since release. In addition, because some users have installed various Windows NT Server 4.0 features and components on to Terminal Server, Table 2 includes a list of features that Microsoft has made available for Windows NT Server 4.0. This does not imply support or testing of the listed Windows NT Server features and options on Terminal Server. Use this table to verify the compliance of each feature installed on the Target Machine and to apply appropriate fixes where necessary. The Required Actions below must be performed to bring the listed features to Year 2000 compliance. Year 2000 compliance information on NT Server and other Microsoft products are found at http://www.microsoft.com/y2k.

Table 2.

Feature Name

Version

Initial Compliance Rating

Required Actions

Active Directory Services Interface (ADSI)

1.0

Not Tested

Install ADSI 2.0

Active Directory Services Interface

2.0

Compliant

None

Certificate Server

1.0

Compliant

See Note 1

Distributed File Service

4.0

Compliant

None

Distributed File Service

4.1

Compliant

None

Imaging for Windows

N/A

Compliant

None – the Compliant rating applies to versions that run on Windows NT Server 4.0

Index Server

1.0

Compliant

None

Index Server

1.1

Compliant

None

Index Server

2.0

Compliant

None

Internet Connection Services for Microsoft Remote Access Service

1.0

Compliant

None

Microsoft Cluster Services

1.0

Compliant

None

Microsoft Data Access Components

See Required Actions

See Required Actions

Some versions of MDAC are not compliant. To make MDAC compliant, please review MDAC product guide for latest information on year 2000 issues and updates for MDAC.

Microsoft Euro Currency Support for
Windows NT 4.0

N/A

Compliant

None

Microsoft Euro Currency Support for
Terminal Server

N/A

Compliant

None

Microsoft FrontPage 97

"97"

Not Compliant

To make compliant, install FrontPage 97 Year 2000 hot fixes.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

To make compliant, install FrontPage 98 Server Extensions from the Windows NT Option Pack. Also see Note 2.

Microsoft FrontPage 97

"97" with fixes

Compliant

To determine that Microsoft Front Page 97 fixes are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least02.00.3002.23. See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

None -- Also see note 2.

Microsoft Internet Explorer

2.00

Not Tested

To make compliant, upgrade to Internet Explorer 4.01 SP1+fixes

Microsoft Internet Explorer

3.02

Not Compliant

To make compliant, apply year 2000 fixes

Microsoft Internet Explorer

3.02 with Year 2000 fixes

Compliant

To determine that Microsoft Internet Explorer version 3.02 fixes are installed, verify the version number of the file named:
"(system directory)\system32\wininet.dll"
is in the range of either:

  • 4.70.0.1335 to 4.70.0.1399 (for browsers with "File Upload" features enabled)

or

  • 4.70.0.1460 to 4.70.0.1499 (for browsers without "File Upload" features enabled)

See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft Internet Explorer

4.01

Not Compliant

To make compliant, upgrade to Internet Explorer version 4.01 SP1+fixes

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1

Compliant#

To determine that Microsoft Internet Explorer version 4.01 SP1 is installed, verify the version number of the file named:
"(system directory)\system32\comctl32.dll"
is at least 4.70.3110.9 or higher.

See note 5 for instructions on verifying version numbers of .DLL files.

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1A

Compliant#

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1 or SP1A w/ additional fixes

Compliant

Additional fixes can be found on Internet Explorer 4.0x year 2000 Product Guide. www.microsoft.com/y2k

Microsoft Internet Information Server

2.0

Compliant

None

Microsoft Internet Information Server

3.0

Compliant

None

Microsoft Internet Information Server

4.0

Compliant

None

Microsoft Internet Locator Service

1.0

Not Compliant

To make compliant, install Microsoft Internet Locator Service version 2.0

Microsoft Internet Locator Service

2.0

Compliant

None

Microsoft Management Console

1.0

Compliant

None

Microsoft Message Queue Server

1.0

Compliant

None

Microsoft Message Queue Server

1.0E

Compliant

None

Microsoft Transaction Server

1.0

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

1.1

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

2.0

Compliant

None

Microsoft Transaction Server

2.0 SP

Compliant

None

Microsoft Virtual Machine

(Many versions)

See required action for description

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

To make compliant, install NetShow 3.0

NetShow Services

3.0

Compliant

None

Routing and Remote Access Services

4.0

Compliant

None

Site Server Express

2.0

Not Compliant

To make compliant, install Site Server Express version 3.0

Site Server Express

3.0

Compliant

None - See Note 3

TAPI SDK

2.1

Compliant

None

Terminal Server client

16-bit

Compliant

None

Terminal Server client

32-bit

Compliant

None

Web Administrator for Microsoft Windows NT Server 4.0

2.0

Compliant

None

Windows Load Balancing Service

2.2

Compliant

Windows Media Player

6.0

Compliant

None

Windows Scripting Host

1.0

Compliant

None

Zero Administration Kit for Windows NT 4.0

N/A

Compliant

None –See Note 4

Zero Administration Kit for Windows NT 4.0, Terminal Server Edition

N/A

Compliant

None –See Note 4

Appendix:

For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Server web site that Microsoft does not consider to be part of the Window NT Server 4.0 or Terminal Server 4.0 product for Year 2000 compliance purposes.

Table 3.

Feature/Product Name

Notes

ADSI Implemented in Java

Available only in Beta test versions.

Client 32 support for NetWare

This is a Novell product; consult Novell for compliance information.

Dial-Up Networking Access Service Performance and Security Upgrade

Applies only to Windows 95 should not be present with Windows NT Server 4.0.

I2O (Intelligent I/O Architecture) Drivers for Windows NT

Available only in Beta test versions.

Microsoft Windows NT Services for UNIX

Available only in Beta test versions.

Personal Web Services 4.0

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Routing and Remote Access Service Performance and Security Upgrade

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Routing and Remote Access Service Upgrade for Windows NT Server

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Windows NT Server Management Tools for Windows 95

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Notes:

  1. Certificate Server version 1.0 cannot be installed when the date is 2/29/2000.
  2. To determine which versions of FrontPage Server Extensions are actively in use, run the FrontPage Server Administrator (Fpsrvwin.exe). Click on each of the Web servers or virtual servers (listed in the box in the upper left area) that have been configured with the FrontPage Server Extensions. The version number of the FrontPage Server Extension is displayed to the right of the list. Version numbers where the first digit is "3" or greater resolve known Year 2000 issues (e.g. 3.0.2.1706). If the first digit of the version number is "1" or "2", users should install an updated version of the FrontPage Server Extensions. Refer to http://www.microsoft.com/frontpage/ for more details.
  3. There is no Content Analyzer feature in Site Server Express 3.0. An updated Content Analyzer is available from the Windows NT Server Service Pack 4 Download page.
  4. http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.

  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:
  • Start Windows NT Explorer from the "Start/Programs" menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file and clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

 

 


Legend of Symbols:
*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 - Terminal  4.0 SP3   (Japanese)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP3 Category:Compliant*#
Language: Japanese OS: Win NT Release Date: 16 Jun 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 3 Year 2000 Update (see below)
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time.
Last Updated: 21 Sep 1999
Product Details

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3").

When users load the Terminal Server operating system on a computer they are asked to select from a number of installation options. In addition, Microsoft has made additional features available to licensed users on the Terminal Server CD and via the Microsoft website. 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 Year 2000 readiness status. .

Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features contain known Year 2000 issues that require updates. In order to update a given computer running Terminal Server 4.0 (the Target System) to a Compliant status, users must install the Windows NT Server, Terminal Server Edition, Service Pack 4 (TS SP4), expected to be released in June 1999. Once available, this approach is recommended. Information on this Service Pack will be made available on the Terminal Server website at or before release time. A Terminal Server 4.0, SP4 Year 2000 compliance document will also be made available at http://www.microsoft.com/y2k by July 1999.

Microsoft recognizes that some users of Terminal Server 4.0 would prefer or need to remain on the base system (which is integrated with Service Pack 3) until after January 1, 2000. To address the needs of these users, Microsoft has prepared a number of updates to the base Terminal Server 4.0 operating system and features. Users should note, however, that:

  • Microsoft has assigned a compliance rating of "Compliant# to Terminal Server 4.0-based systems where these updates have been applied
  • Users must apply TS SP4 to get the rating of "Compliant" for the target system
  • The highest compliance rating that Microsoft will assign to a system running Terminal Server 4.0 without Service Pack 4 or greater is, "Compliant#"

Further, for those Terminal Server systems without Service Pack 4.0 or greater installed, Microsoft intends to maintain Terminal Server 4.0 with compliance rating at the "Compliant# level through January 1, 2001. Microsoft will do this by producing updates to the extent that new, Year 2000-related issues are discovered that would otherwise cause Microsoft to lower the rating of Terminal Server 4.0 below the "Compliant# level.

The tables included below list the specific options and features (by version) that users of Windows NT Server 4.0, Terminal Server Edition 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 that has not been upgraded to TS SP4 or greater.

Note that some options and features of Terminal Server cannot be brought to a Compliant status without applying SP4. Using the information below, however, the options and features can be brought to at least a Compliant# status.

In summary, for users of Terminal Server 4.0 without TS SP4 or greater, the options and features that need to be addressed in order to attain a status of Compliant# are:

  • Active Directory Services Interface version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft FrontPage 97 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft FrontPage 97 Server Extensions (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Internet Explorer version 2.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Internet Explorer version 3.02 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Explorer version 4.01 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Locator Service version 1.0 (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Transaction Server version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Transaction Server version 1.1 (Not Tested; upgrade required to ensure Compliant status)
  • Site Server Express version 2.0 (Not Compliant; upgrade required to reach Compliant status)

Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.

 

Evaluating the Status of a Windows NT Server 4.0, Terminal Server Edition System

Microsoft has assigned the base (SP3) Terminal Server 4.0 operating system 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:

 

  • Windows NT Server, Terminal Server Edition post-SP3 Year 2000 update -- a single install released on February 26, 1999 installs these file on to user systems.

An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either:

http://www.microsoft.com/ntserver/all/downloads

or

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/

 

 

  • A list of the issues addressed by the post SP3 Year 2000 update is listed below:
    1. User Manager Does Not Recognize February 2000 As a Leap Year. (Q175093) User Manager and User Manager for Domains will not accept February 29, 2000 as a valid date to expire an account.
    2. Control Panel Date/Time applet. (Q180122) The date displayed by the Control Panel Date/Time applet 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 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 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 Server computer running File and Print Services for NetWare (FPNW), the client's date and time are not synchronized with that of the server when the server's date and time are beyond 12/31/1999 at 11:59:59 pm.
    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.
  • Users should note that some known issues in the base (SP3) Windows NT Server 4.0, Terminal Server Edition operating system are not being addressed, hence the rating of "Compliant#." It is for this reason Microsoft recommends upgrading to Windows NT Server, Terminal Server Edition Service Pack 4. Listed below are the known acceptable deviations remaining in SP3 after the application of the Post-Service Pack 3 Year 2000 Update.

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:

    1. In a dual boot scenario, the other operating system(s) may not handle this situation properly. MS-DOS is in this class of operating systems.
    2. Some BIOSes detect this behavior as an invalid date and query the user for the correct date. This would prevent a system from rebooting without user input.

 

4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the OLE Automation product guide for more information.

5. Incorrect Date Displayed when viewing a saved System Info Report. (Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".

6. Four-Digit Year Format for Non-English Regional Settings. (Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring the Regional Settings Short Date Style of a system, users may not be able to choose a 4-digit year format. However, users can manually enter a 4-digit date style.

 

Installation options included in the Compliant# status of Windows NT Server 4.0, Terminal Server Edition are listed in Table 1 (below).

Table 1.

Option/Service Name

Compliance Rating

DHCP Relay Agent

Compliant#

DLC Protocol

Compliant

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

Remote Boot Service

Compliant

RIP for Internet Protocol

Compliant

RIP for NWLink IPX/SPX-Compatible Transport

Compliant

RPC Configuration

Compliant

RPC Support for Banyan

Compliant

SAP Agent

Compliant

Server

Compliant

Services for Macintosh

Compliant

Simple TCP/IP Services

Compliant

SNMP Service

Compliant

Streams Environment

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant#

Workstation

Compliant

In addition to the selectable options offered during installation of Terminal Server, there are additional features that may be or may have been installed on the Target System.

Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of Terminal Server 4.0 via the Terminal Server CD and the Terminal Server web page since release. In addition, because some users have installed various Windows NT Server 4.0 features and components on to Terminal Server, Table 2 includes a list of features that Microsoft has made available for Windows NT Server 4.0. This does not imply support or testing of the listed Windows NT Server features and options on Terminal Server. Use this table to verify the compliance of each feature installed on the Target Machine and to apply appropriate fixes where necessary. The Required Actions below must be performed to bring the listed features to Year 2000 compliance. Year 2000 compliance information on NT Server and other Microsoft products are found at http://www.microsoft.com/y2k.

Table 2.

Feature Name

Version

Initial Compliance Rating

Required Actions

Active Directory Services Interface (ADSI)

1.0

Not Tested

Install ADSI 2.0

Active Directory Services Interface

2.0

Compliant

None

Certificate Server

1.0

Compliant

See Note 1

Distributed File Service

4.0

Compliant

None

Distributed File Service

4.1

Compliant

None

Imaging for Windows

N/A

Compliant

None – the Compliant rating applies to versions that run on Windows NT Server 4.0

Index Server

1.0

Compliant

None

Index Server

1.1

Compliant

None

Index Server

2.0

Compliant

None

Internet Connection Services for Microsoft Remote Access Service

1.0

Compliant

None

Microsoft Cluster Services

1.0

Compliant

None

Microsoft Data Access Components

See Required Actions

See Required Actions

Some versions of MDAC are not compliant. To make MDAC compliant, please review MDAC product guide for latest information on year 2000 issues and updates for MDAC.

Microsoft Euro Currency Support for
Windows NT 4.0

N/A

Compliant

None

Microsoft Euro Currency Support for
Terminal Server

N/A

Compliant

None

Microsoft FrontPage 97

"97"

Not Compliant

To make compliant, install FrontPage 97 Year 2000 hot fixes.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

To make compliant, install FrontPage 98 Server Extensions from the Windows NT Option Pack. Also see Note 2.

Microsoft FrontPage 97

"97" with fixes

Compliant

To determine that Microsoft Front Page 97 fixes are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least02.00.3002.23. See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

None -- Also see note 2.

Microsoft Internet Explorer

2.00

Not Tested

To make compliant, upgrade to Internet Explorer 4.01 SP1+fixes

Microsoft Internet Explorer

3.02

Not Compliant

To make compliant, apply year 2000 fixes

Microsoft Internet Explorer

3.02 with Year 2000 fixes

Compliant

To determine that Microsoft Internet Explorer version 3.02 fixes are installed, verify the version number of the file named:
"(system directory)\system32\wininet.dll"
is in the range of either:

  • 4.70.0.1335 to 4.70.0.1399 (for browsers with "File Upload" features enabled)

or

  • 4.70.0.1460 to 4.70.0.1499 (for browsers without "File Upload" features enabled)

See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft Internet Explorer

4.01

Not Compliant

To make compliant, upgrade to Internet Explorer version 4.01 SP1+fixes

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1

Compliant#

To determine that Microsoft Internet Explorer version 4.01 SP1 is installed, verify the version number of the file named:
"(system directory)\system32\comctl32.dll"
is at least 4.70.3110.9 or higher.

See note 5 for instructions on verifying version numbers of .DLL files.

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1A

Compliant#

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1 or SP1A w/ additional fixes

Compliant

Additional fixes can be found on Internet Explorer 4.0x year 2000 Product Guide. www.microsoft.com/y2k

Microsoft Internet Information Server

2.0

Compliant

None

Microsoft Internet Information Server

3.0

Compliant

None

Microsoft Internet Information Server

4.0

Compliant

None

Microsoft Internet Locator Service

1.0

Not Compliant

To make compliant, install Microsoft Internet Locator Service version 2.0

Microsoft Internet Locator Service

2.0

Compliant

None

Microsoft Management Console

1.0

Compliant

None

Microsoft Message Queue Server

1.0

Compliant

None

Microsoft Message Queue Server

1.0E

Compliant

None

Microsoft Transaction Server

1.0

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

1.1

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

2.0

Compliant

None

Microsoft Transaction Server

2.0 SP

Compliant

None

Microsoft Virtual Machine

(Many versions)

See required action for description

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

To make compliant, install NetShow 3.0

NetShow Services

3.0

Compliant

None

Routing and Remote Access Services

4.0

Compliant

None

Site Server Express

2.0

Not Compliant

To make compliant, install Site Server Express version 3.0

Site Server Express

3.0

Compliant

None - See Note 3

TAPI SDK

2.1

Compliant

None

Terminal Server client

16-bit

Compliant

None

Terminal Server client

32-bit

Compliant

None

Web Administrator for Microsoft Windows NT Server 4.0

2.0

Compliant

None

Windows Load Balancing Service

2.2

Compliant

Windows Media Player

6.0

Compliant

None

Windows Scripting Host

1.0

Compliant

None

Zero Administration Kit for Windows NT 4.0

N/A

Compliant

None –See Note 4

Zero Administration Kit for Windows NT 4.0, Terminal Server Edition

N/A

Compliant

None –See Note 4

Appendix:

For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Server web site that Microsoft does not consider to be part of the Window NT Server 4.0 or Terminal Server 4.0 product for Year 2000 compliance purposes.

Table 3.

Feature/Product Name

Notes

ADSI Implemented in Java

Available only in Beta test versions.

Client 32 support for NetWare

This is a Novell product; consult Novell for compliance information.

Dial-Up Networking Access Service Performance and Security Upgrade

Applies only to Windows 95 should not be present with Windows NT Server 4.0.

I2O (Intelligent I/O Architecture) Drivers for Windows NT

Available only in Beta test versions.

Microsoft Windows NT Services for UNIX

Available only in Beta test versions.

Personal Web Services 4.0

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Routing and Remote Access Service Performance and Security Upgrade

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Routing and Remote Access Service Upgrade for Windows NT Server

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Windows NT Server Management Tools for Windows 95

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Notes:

  1. Certificate Server version 1.0 cannot be installed when the date is 2/29/2000.
  2. To determine which versions of FrontPage Server Extensions are actively in use, run the FrontPage Server Administrator (Fpsrvwin.exe). Click on each of the Web servers or virtual servers (listed in the box in the upper left area) that have been configured with the FrontPage Server Extensions. The version number of the FrontPage Server Extension is displayed to the right of the list. Version numbers where the first digit is "3" or greater resolve known Year 2000 issues (e.g. 3.0.2.1706). If the first digit of the version number is "1" or "2", users should install an updated version of the FrontPage Server Extensions. Refer to http://www.microsoft.com/frontpage/ for more details.
  3. There is no Content Analyzer feature in Site Server Express 3.0. An updated Content Analyzer is available from the Windows NT Server Service Pack 4 Download page.
  4. http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.

  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:
  • Start Windows NT Explorer from the "Start/Programs" menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file and clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

 

 


Legend of Symbols:
*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 - Terminal  4.0 SP3   (Spanish)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP3 Category:Compliant*#
Language: Spanish OS: Win NT Release Date: 16 Jun 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 3 Year 2000 Update (see below)
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time.
Last Updated: 21 Sep 1999
Product Details

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3").

When users load the Terminal Server operating system on a computer they are asked to select from a number of installation options. In addition, Microsoft has made additional features available to licensed users on the Terminal Server CD and via the Microsoft website. 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 Year 2000 readiness status. .

Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features contain known Year 2000 issues that require updates. In order to update a given computer running Terminal Server 4.0 (the Target System) to a Compliant status, users must install the Windows NT Server, Terminal Server Edition, Service Pack 4 (TS SP4), expected to be released in June 1999. Once available, this approach is recommended. Information on this Service Pack will be made available on the Terminal Server website at or before release time. A Terminal Server 4.0, SP4 Year 2000 compliance document will also be made available at http://www.microsoft.com/y2k by July 1999.

Microsoft recognizes that some users of Terminal Server 4.0 would prefer or need to remain on the base system (which is integrated with Service Pack 3) until after January 1, 2000. To address the needs of these users, Microsoft has prepared a number of updates to the base Terminal Server 4.0 operating system and features. Users should note, however, that:

  • Microsoft has assigned a compliance rating of "Compliant# to Terminal Server 4.0-based systems where these updates have been applied
  • Users must apply TS SP4 to get the rating of "Compliant" for the target system
  • The highest compliance rating that Microsoft will assign to a system running Terminal Server 4.0 without Service Pack 4 or greater is, "Compliant#"

Further, for those Terminal Server systems without Service Pack 4.0 or greater installed, Microsoft intends to maintain Terminal Server 4.0 with compliance rating at the "Compliant# level through January 1, 2001. Microsoft will do this by producing updates to the extent that new, Year 2000-related issues are discovered that would otherwise cause Microsoft to lower the rating of Terminal Server 4.0 below the "Compliant# level.

The tables included below list the specific options and features (by version) that users of Windows NT Server 4.0, Terminal Server Edition 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 that has not been upgraded to TS SP4 or greater.

Note that some options and features of Terminal Server cannot be brought to a Compliant status without applying SP4. Using the information below, however, the options and features can be brought to at least a Compliant# status.

In summary, for users of Terminal Server 4.0 without TS SP4 or greater, the options and features that need to be addressed in order to attain a status of Compliant# are:

  • Active Directory Services Interface version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft FrontPage 97 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft FrontPage 97 Server Extensions (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Internet Explorer version 2.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Internet Explorer version 3.02 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Explorer version 4.01 (Not Compliant; hot fixes required to reach Compliant status)
  • Microsoft Internet Locator Service version 1.0 (Not Compliant; upgrade required to reach Compliant status)
  • Microsoft Transaction Server version 1.0 (Not Tested; upgrade required to ensure Compliant status)
  • Microsoft Transaction Server version 1.1 (Not Tested; upgrade required to ensure Compliant status)
  • Site Server Express version 2.0 (Not Compliant; upgrade required to reach Compliant status)

Detailed information about addressing year 2000 compliance issues on a feature-by-feature basis is provided below.

 

Evaluating the Status of a Windows NT Server 4.0, Terminal Server Edition System

Microsoft has assigned the base (SP3) Terminal Server 4.0 operating system 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:

 

  • Windows NT Server, Terminal Server Edition post-SP3 Year 2000 update -- a single install released on February 26, 1999 installs these file on to user systems.

An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either:

http://www.microsoft.com/ntserver/all/downloads

or

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/

 

 

  • A list of the issues addressed by the post SP3 Year 2000 update is listed below:
    1. User Manager Does Not Recognize February 2000 As a Leap Year. (Q175093) User Manager and User Manager for Domains will not accept February 29, 2000 as a valid date to expire an account.
    2. Control Panel Date/Time applet. (Q180122) The date displayed by the Control Panel Date/Time applet 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 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 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 Server computer running File and Print Services for NetWare (FPNW), the client's date and time are not synchronized with that of the server when the server's date and time are beyond 12/31/1999 at 11:59:59 pm.
    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.
  • Users should note that some known issues in the base (SP3) Windows NT Server 4.0, Terminal Server Edition operating system are not being addressed, hence the rating of "Compliant#." It is for this reason Microsoft recommends upgrading to Windows NT Server, Terminal Server Edition Service Pack 4. Listed below are the known acceptable deviations remaining in SP3 after the application of the Post-Service Pack 3 Year 2000 Update.

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:

    1. In a dual boot scenario, the other operating system(s) may not handle this situation properly. MS-DOS is in this class of operating systems.
    2. Some BIOSes detect this behavior as an invalid date and query the user for the correct date. This would prevent a system from rebooting without user input.

 

4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the OLE Automation product guide for more information.

5. Incorrect Date Displayed when viewing a saved System Info Report. (Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".

6. Four-Digit Year Format for Non-English Regional Settings. (Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring the Regional Settings Short Date Style of a system, users may not be able to choose a 4-digit year format. However, users can manually enter a 4-digit date style.

 

Installation options included in the Compliant# status of Windows NT Server 4.0, Terminal Server Edition are listed in Table 1 (below).

Table 1.

Option/Service Name

Compliance Rating

DHCP Relay Agent

Compliant#

DLC Protocol

Compliant

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

Remote Boot Service

Compliant

RIP for Internet Protocol

Compliant

RIP for NWLink IPX/SPX-Compatible Transport

Compliant

RPC Configuration

Compliant

RPC Support for Banyan

Compliant

SAP Agent

Compliant

Server

Compliant

Services for Macintosh

Compliant

Simple TCP/IP Services

Compliant

SNMP Service

Compliant

Streams Environment

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant#

Workstation

Compliant

In addition to the selectable options offered during installation of Terminal Server, there are additional features that may be or may have been installed on the Target System.

Table 2 (below) lists the additional features (and their versions) that Microsoft has made available to licensed users of Terminal Server 4.0 via the Terminal Server CD and the Terminal Server web page since release. In addition, because some users have installed various Windows NT Server 4.0 features and components on to Terminal Server, Table 2 includes a list of features that Microsoft has made available for Windows NT Server 4.0. This does not imply support or testing of the listed Windows NT Server features and options on Terminal Server. Use this table to verify the compliance of each feature installed on the Target Machine and to apply appropriate fixes where necessary. The Required Actions below must be performed to bring the listed features to Year 2000 compliance. Year 2000 compliance information on NT Server and other Microsoft products are found at http://www.microsoft.com/y2k.

Table 2.

Feature Name

Version

Initial Compliance Rating

Required Actions

Active Directory Services Interface (ADSI)

1.0

Not Tested

Install ADSI 2.0

Active Directory Services Interface

2.0

Compliant

None

Certificate Server

1.0

Compliant

See Note 1

Distributed File Service

4.0

Compliant

None

Distributed File Service

4.1

Compliant

None

Imaging for Windows

N/A

Compliant

None – the Compliant rating applies to versions that run on Windows NT Server 4.0

Index Server

1.0

Compliant

None

Index Server

1.1

Compliant

None

Index Server

2.0

Compliant

None

Internet Connection Services for Microsoft Remote Access Service

1.0

Compliant

None

Microsoft Cluster Services

1.0

Compliant

None

Microsoft Data Access Components

See Required Actions

See Required Actions

Some versions of MDAC are not compliant. To make MDAC compliant, please review MDAC product guide for latest information on year 2000 issues and updates for MDAC.

Microsoft Euro Currency Support for
Windows NT 4.0

N/A

Compliant

None

Microsoft Euro Currency Support for
Terminal Server

N/A

Compliant

None

Microsoft FrontPage 97

"97"

Not Compliant

To make compliant, install FrontPage 97 Year 2000 hot fixes.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

To make compliant, install FrontPage 98 Server Extensions from the Windows NT Option Pack. Also see Note 2.

Microsoft FrontPage 97

"97" with fixes

Compliant

To determine that Microsoft Front Page 97 fixes are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least02.00.3002.23. See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

None -- Also see note 2.

Microsoft Internet Explorer

2.00

Not Tested

To make compliant, upgrade to Internet Explorer 4.01 SP1+fixes

Microsoft Internet Explorer

3.02

Not Compliant

To make compliant, apply year 2000 fixes

Microsoft Internet Explorer

3.02 with Year 2000 fixes

Compliant

To determine that Microsoft Internet Explorer version 3.02 fixes are installed, verify the version number of the file named:
"(system directory)\system32\wininet.dll"
is in the range of either:

  • 4.70.0.1335 to 4.70.0.1399 (for browsers with "File Upload" features enabled)

or

  • 4.70.0.1460 to 4.70.0.1499 (for browsers without "File Upload" features enabled)

See note 5 for instructions on verifying version numbers of .DLL files.

Microsoft Internet Explorer

4.01

Not Compliant

To make compliant, upgrade to Internet Explorer version 4.01 SP1+fixes

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1

Compliant#

To determine that Microsoft Internet Explorer version 4.01 SP1 is installed, verify the version number of the file named:
"(system directory)\system32\comctl32.dll"
is at least 4.70.3110.9 or higher.

See note 5 for instructions on verifying version numbers of .DLL files.

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1A

Compliant#

In order to make compliant, there are additional fixes needed that are posted on www.microsoft.com/y2k for Internet Explorer 4.0x 32bit.

Microsoft Internet Explorer

4.01 SP1 or SP1A w/ additional fixes

Compliant

Additional fixes can be found on Internet Explorer 4.0x year 2000 Product Guide. www.microsoft.com/y2k

Microsoft Internet Information Server

2.0

Compliant

None

Microsoft Internet Information Server

3.0

Compliant

None

Microsoft Internet Information Server

4.0

Compliant

None

Microsoft Internet Locator Service

1.0

Not Compliant

To make compliant, install Microsoft Internet Locator Service version 2.0

Microsoft Internet Locator Service

2.0

Compliant

None

Microsoft Management Console

1.0

Compliant

None

Microsoft Message Queue Server

1.0

Compliant

None

Microsoft Message Queue Server

1.0E

Compliant

None

Microsoft Transaction Server

1.0

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

1.1

Not Tested

To make compliant, install Microsoft Transaction Server 2.0 from the Windows NT Option Pack

Microsoft Transaction Server

2.0

Compliant

None

Microsoft Transaction Server

2.0 SP

Compliant

None

Microsoft Virtual Machine

(Many versions)

See required action for description

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

To make compliant, install NetShow 3.0

NetShow Services

3.0

Compliant

None

Routing and Remote Access Services

4.0

Compliant

None

Site Server Express

2.0

Not Compliant

To make compliant, install Site Server Express version 3.0

Site Server Express

3.0

Compliant

None - See Note 3

TAPI SDK

2.1

Compliant

None

Terminal Server client

16-bit

Compliant

None

Terminal Server client

32-bit

Compliant

None

Web Administrator for Microsoft Windows NT Server 4.0

2.0

Compliant

None

Windows Load Balancing Service

2.2

Compliant

Windows Media Player

6.0

Compliant

None

Windows Scripting Host

1.0

Compliant

None

Zero Administration Kit for Windows NT 4.0

N/A

Compliant

None –See Note 4

Zero Administration Kit for Windows NT 4.0, Terminal Server Edition

N/A

Compliant

None –See Note 4

Appendix:

For convenience, Table 3 (below) lists features and products that Microsoft has made available on the Windows NT Server web site that Microsoft does not consider to be part of the Window NT Server 4.0 or Terminal Server 4.0 product for Year 2000 compliance purposes.

Table 3.

Feature/Product Name

Notes

ADSI Implemented in Java

Available only in Beta test versions.

Client 32 support for NetWare

This is a Novell product; consult Novell for compliance information.

Dial-Up Networking Access Service Performance and Security Upgrade

Applies only to Windows 95 should not be present with Windows NT Server 4.0.

I2O (Intelligent I/O Architecture) Drivers for Windows NT

Available only in Beta test versions.

Microsoft Windows NT Services for UNIX

Available only in Beta test versions.

Personal Web Services 4.0

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Routing and Remote Access Service Performance and Security Upgrade

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Routing and Remote Access Service Upgrade for Windows NT Server

This is a collection of hot fixes that have no impact on Year 2000 compliance ratings.

Windows NT Server Management Tools for Windows 95

Runs only on Windows NT Workstation 4.0 and Windows 98 and should not be present with Windows NT Server 4.0.

Notes:

  1. Certificate Server version 1.0 cannot be installed when the date is 2/29/2000.
  2. To determine which versions of FrontPage Server Extensions are actively in use, run the FrontPage Server Administrator (Fpsrvwin.exe). Click on each of the Web servers or virtual servers (listed in the box in the upper left area) that have been configured with the FrontPage Server Extensions. The version number of the FrontPage Server Extension is displayed to the right of the list. Version numbers where the first digit is "3" or greater resolve known Year 2000 issues (e.g. 3.0.2.1706). If the first digit of the version number is "1" or "2", users should install an updated version of the FrontPage Server Extensions. Refer to http://www.microsoft.com/frontpage/ for more details.
  3. There is no Content Analyzer feature in Site Server Express 3.0. An updated Content Analyzer is available from the Windows NT Server Service Pack 4 Download page.
  4. http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.

  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:
  • Start Windows NT Explorer from the "Start/Programs" menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file and clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

 

 


Legend of Symbols:
*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 - Terminal  4.0 SP4   (English)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP4 Category:Compliant*+
Language: English OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 4 Year 2000 Update; IE 4.01 SP2 updates
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time
Last Updated: 21 Sep 1999
Product Details

Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 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 Server 4.0 Service Pack 4, Terminal Server 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. (Internet Explorer 4.01 Service Pack 2 is included on the Terminal Server 4 Service Pack 4 CD-ROM.)

Through ongoing testing, Microsoft has identified two year 2000 issues, which are addressed by post-Service Pack 4 for Terminal Server (TS SP4) updates. Microsoft recommends that users evaluate the post-TS SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below.

 

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3"). Recently, Service Pack 4 for Terminal Server was released. Microsoft intends to maintain Year 2000 compliance of Service Pack 4 through January 1, 2001, in addition to maintaining the Year 2000 compliance of subsequent Service Packs through January 1, 2001.

When users load the Terminal Server operating system on a computer, they are asked to select from a number of installation options. In addition, Microsoft has made additional Windows NT Server 4.0 features available to licensed users via the Terminal Server CD. 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.

As mentioned above, Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features have known Year 2000 issues that have updates we recommend you apply. 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 software updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues.

  • Please Note: Installation of Service Pack 4 for Terminal Server (TS SP4) must be performed with the system in "install" mode. This is performed automatically with the TS SP4 CD. Alternatively, at the command prompt, type: change user /install prior to installing TS SP4.

The steps identified below take a comprehensive approach to addressing known issues.

  • Step 1 prepares the target system for Terminal Server SP4 by addressing any updates that are needed before SP4 is applied.
  • Step 2 installs Terminal Server SP4 and any post-SP4 Year 2000 Updates to analyze the target system, remove versions that have known issues, and install updated versions that have no known issues.
  • Step 3 then audits the target system. To confirm all known issues have been addressed and steps 1 and 2 have been done correctly, the results of the audit should indicate that only those versions having a "compliant" rating (as identified on the tables below) remain on the target system after Steps 1 and 2 have been completed.

Step 1

TS SP4 itself will address most known Year 2000 issues. However, we recommend users update or upgrade certain features to newer versions, in addition to applying TS SP4.

Table 1A (below) lists the features that we recommend be updated or upgraded in addition to applying TS SP4, along with specific update/upgrade instructions.

Table 1B (below) lists the Terminal Server Optional features that we recommend 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 TS SP4 (which is outlined in Step 2).

Table 1A: System Components.

Feature Name

Version

Action Required Prior to Step 2

Microsoft Internet Explorer (IE)

Multiple Versions

Upgrade to IE4.01 SP2 including any applicable Year 2000 software Updates.

For information on additional Year 2000 Updates for IE, refer HERE.

IE 4.01 SP2 is included on the Terminal Server SP4 CD-ROM.

(Users who prefer to remain on IE 4.01 SP1 should refer to the IE4 Year 2000 Compliance document available HERE for appropriate actions. Additional software updates are recommended in addition to SP1.)

Table 1B: Optional Components.

Feature Name

Version

Action Required Prior to Step 2

Microsoft Data Access Components (MDAC)

Multiple Versions

Install MDAC 2.1 SP1 or newer including any applicable Year 2000 software Updates.

For information on additional Year 2000 Updates for MDAC, refer HERE.

Go Here for MDAC Downloads

Please note that the TSLicense service should be stopped before installing MDAC.

Microsoft FrontPage 97

"97"

Install FrontPage 97 Year 2000 Updates

 

Step 2

We recommend users apply SP4 for Terminal Server to the Target System. TS SP4 can be obtained by clicking here.

The installation of SP4 applies updates to the base Terminal Server product, features and installation options.

We recommend users also apply any Terminal Server Year 2000 updates that have been made available post-TS SP4.

When available, the post-TS SP4 year 2000 updates will be posted here.

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). A software update will be available in August 1999. Check back here then for further information.

2. License Server will not start on February 29, 2000. If users attempt to start the Terminal Server License Server on 2/29/2000, the following error message is displayed in the event log: "Can't load server's certificate. See Terminal Server Licensing help topic for more information. Event ID = 7 Type = error." Clients will still be allowed to connect, but will not be issued a license. A Knowledge Base article (Q236405) and software update will be available in August 1999. Check back here then for further information.

 

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.

  • Create a list of the Terminal Server 4.0 installation options and additional features installed on the target system
  • Review the compliance status of the installation options and features using Tables 2 & 3.
  • Confirm that only installation options and features having a "compliant" rating (as identified on the tables below) remain on the target system after Steps 1 and 2 have been completed.

Detail:

When users load the Terminal 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 the Terminal Server operating system itself and each of the options listed in Table 2 below should be updated after applying TS SP4.

Table 2

Option/Server Name

Compliance Rating

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

SAP Agent

Compliant

Server

Compliant

Simple TCP/IP Services

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant

Windows Messenger Service

Compliant

Workstation

Compliant

 

The compliance ratings listed above are subject to change without notice. Please review this information frequently to assess whether there have been any changes to the compliance status of the installation option you have selected.

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. Microsoft has made these features available via Service Packs and the Windows NT Option Pack.

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

Feature Name

Version

Feature Compliance Rating

Notes

Distributed File Service

4.0

Compliant

Distributed File Service

4.1

Compliant

Imaging for Windows

Not Applicable

Compliant

Applies to all Versions that run on Windows NT Server 4.0

Microsoft Data Access Components(MDAC)

Multiple Versions

See Table 1B for Required Action

See Table 1B for Required Action

Microsoft Euro Currency Support for
Windows NT 4.0

Not Applicable

Compliant

Microsoft FrontPage 97

"97"

Not Compliant

See Note 2

Microsoft FrontPage 97

"97" with Updates

Compliant

To determine that Microsoft Front Page 97 updates are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least 02.00.3002.23. See note 3 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

See Note 1

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

See Note 1

Microsoft Internet Explorer

Multiple Versions

See Table 1A for Required Action

See Table 1A for Required Action

Microsoft Internet Information Server

3.0

Compliant

Microsoft Internet Information Server

4.0

See Note 4

Microsoft Management Console

1.0

Compliant

Microsoft Message Queue Server

All Versions

See Note 5

Microsoft Virtual Machine

(Many Versions)

See Notes for Required Action

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have known Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

NetShow Services

3.0

Compliant

Windows Media Player

6.0

Compliant

To verify that Windows Media Player 6.0 is installed, users should select "Help/About Windows Media Player" from within Windows Media Player and verify that the version number is 5.01.52.0701 or greater.

 

The compliance ratings listed above are subject to change without notice. Please review this information frequently to assess whether there have been any changes to the compliance status of the features you have installed.

 

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 Table 3, 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:

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. To verify the version number of a dynamic link library (DLL) file, users should:

  • Start Windows NT Explorer from the Start/Programs menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

4. Internet Information Server 4.0 has not been tested for compatibility with Terminal Server 4.0. For additional IIS year 2000 compliance information, consult the Windows NT 4.0 Compliance Documents.

5. MSMQ has not been tested for compatibility with Terminal Server 4.0. For additional MSMQ year 2000 compliance information, consult the Windows NT 4.0 Compliance Documents.


Legend of Symbols:
*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 - Terminal  4.0 SP4   (German)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP4 Category:Compliant*+
Language: German OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 4 Year 2000 Update; IE 4.01 SP2 updates
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time
Last Updated: 21 Sep 1999
Product Details

Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 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 Server 4.0 Service Pack 4, Terminal Server 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. (Internet Explorer 4.01 Service Pack 2 is included on the Terminal Server 4 Service Pack 4 CD-ROM.)

Through ongoing testing, Microsoft has identified two year 2000 issues, which are addressed by post-Service Pack 4 for Terminal Server (TS SP4) updates. Microsoft recommends that users evaluate the post-TS SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below.

 

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3"). Recently, Service Pack 4 for Terminal Server was released. Microsoft intends to maintain Year 2000 compliance of Service Pack 4 through January 1, 2001, in addition to maintaining the Year 2000 compliance of subsequent Service Packs through January 1, 2001.

When users load the Terminal Server operating system on a computer, they are asked to select from a number of installation options. In addition, Microsoft has made additional Windows NT Server 4.0 features available to licensed users via the Terminal Server CD. 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.

As mentioned above, Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features have known Year 2000 issues that have updates we recommend you apply. 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 software updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues.

  • Please Note: Installation of Service Pack 4 for Terminal Server (TS SP4) must be performed with the system in "install" mode. This is performed automatically with the TS SP4 CD. Alternatively, at the command prompt, type: change user /install prior to installing TS SP4.

The steps identified below take a comprehensive approach to addressing known issues.

  • Step 1 prepares the target system for Terminal Server SP4 by addressing any updates that are needed before SP4 is applied.
  • Step 2 installs Terminal Server SP4 and any post-SP4 Year 2000 Updates to analyze the target system, remove versions that have known issues, and install updated versions that have no known issues.
  • Step 3 then audits the target system. To confirm all known issues have been addressed and steps 1 and 2 have been done correctly, the results of the audit should indicate that only those versions having a "compliant" rating (as identified on the tables below) remain on the target system after Steps 1 and 2 have been completed.

Step 1

TS SP4 itself will address most known Year 2000 issues. However, we recommend users update or upgrade certain features to newer versions, in addition to applying TS SP4.

Table 1A (below) lists the features that we recommend be updated or upgraded in addition to applying TS SP4, along with specific update/upgrade instructions.

Table 1B (below) lists the Terminal Server Optional features that we recommend 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 TS SP4 (which is outlined in Step 2).

Table 1A: System Components.

Feature Name

Version

Action Required Prior to Step 2

Microsoft Internet Explorer (IE)

Multiple Versions

Upgrade to IE4.01 SP2 including any applicable Year 2000 software Updates.

For information on additional Year 2000 Updates for IE, refer HERE.

IE 4.01 SP2 is included on the Terminal Server SP4 CD-ROM.

(Users who prefer to remain on IE 4.01 SP1 should refer to the IE4 Year 2000 Compliance document available HERE for appropriate actions. Additional software updates are recommended in addition to SP1.)

Table 1B: Optional Components.

Feature Name

Version

Action Required Prior to Step 2

Microsoft Data Access Components (MDAC)

Multiple Versions

Install MDAC 2.1 SP1 or newer including any applicable Year 2000 software Updates.

For information on additional Year 2000 Updates for MDAC, refer HERE.

Go Here for MDAC Downloads

Please note that the TSLicense service should be stopped before installing MDAC.

Microsoft FrontPage 97

"97"

Install FrontPage 97 Year 2000 Updates

 

Step 2

We recommend users apply SP4 for Terminal Server to the Target System. TS SP4 can be obtained by clicking here.

The installation of SP4 applies updates to the base Terminal Server product, features and installation options.

We recommend users also apply any Terminal Server Year 2000 updates that have been made available post-TS SP4.

When available, the post-TS SP4 year 2000 updates will be posted here.

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). A software update will be available in August 1999. Check back here then for further information.

2. License Server will not start on February 29, 2000. If users attempt to start the Terminal Server License Server on 2/29/2000, the following error message is displayed in the event log: "Can't load server's certificate. See Terminal Server Licensing help topic for more information. Event ID = 7 Type = error." Clients will still be allowed to connect, but will not be issued a license. A Knowledge Base article (Q236405) and software update will be available in August 1999. Check back here then for further information.

 

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.

  • Create a list of the Terminal Server 4.0 installation options and additional features installed on the target system
  • Review the compliance status of the installation options and features using Tables 2 & 3.
  • Confirm that only installation options and features having a "compliant" rating (as identified on the tables below) remain on the target system after Steps 1 and 2 have been completed.

Detail:

When users load the Terminal 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 the Terminal Server operating system itself and each of the options listed in Table 2 below should be updated after applying TS SP4.

Table 2

Option/Server Name

Compliance Rating

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

SAP Agent

Compliant

Server

Compliant

Simple TCP/IP Services

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant

Windows Messenger Service

Compliant

Workstation

Compliant

 

The compliance ratings listed above are subject to change without notice. Please review this information frequently to assess whether there have been any changes to the compliance status of the installation option you have selected.

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. Microsoft has made these features available via Service Packs and the Windows NT Option Pack.

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

Feature Name

Version

Feature Compliance Rating

Notes

Distributed File Service

4.0

Compliant

Distributed File Service

4.1

Compliant

Imaging for Windows

Not Applicable

Compliant

Applies to all Versions that run on Windows NT Server 4.0

Microsoft Data Access Components(MDAC)

Multiple Versions

See Table 1B for Required Action

See Table 1B for Required Action

Microsoft Euro Currency Support for
Windows NT 4.0

Not Applicable

Compliant

Microsoft FrontPage 97

"97"

Not Compliant

See Note 2

Microsoft FrontPage 97

"97" with Updates

Compliant

To determine that Microsoft Front Page 97 updates are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least 02.00.3002.23. See note 3 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

See Note 1

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

See Note 1

Microsoft Internet Explorer

Multiple Versions

See Table 1A for Required Action

See Table 1A for Required Action

Microsoft Internet Information Server

3.0

Compliant

Microsoft Internet Information Server

4.0

See Note 4

Microsoft Management Console

1.0

Compliant

Microsoft Message Queue Server

All Versions

See Note 5

Microsoft Virtual Machine

(Many Versions)

See Notes for Required Action

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have known Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

NetShow Services

3.0

Compliant

Windows Media Player

6.0

Compliant

To verify that Windows Media Player 6.0 is installed, users should select "Help/About Windows Media Player" from within Windows Media Player and verify that the version number is 5.01.52.0701 or greater.

 

The compliance ratings listed above are subject to change without notice. Please review this information frequently to assess whether there have been any changes to the compliance status of the features you have installed.

 

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 Table 3, 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:

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. To verify the version number of a dynamic link library (DLL) file, users should:

  • Start Windows NT Explorer from the Start/Programs menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

4. Internet Information Server 4.0 has not been tested for compatibility with Terminal Server 4.0. For additional IIS year 2000 compliance information, consult the Windows NT 4.0 Compliance Documents.

5. MSMQ has not been tested for compatibility with Terminal Server 4.0. For additional MSMQ year 2000 compliance information, consult the Windows NT 4.0 Compliance Documents.


Legend of Symbols:
*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 - Terminal  4.0 SP4   (Japanese)

Product Summary
Product: Windows NT Server - Terminal Version: 4.0 SP4 Category:Compliant*+
Language: Japanese OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Post-Service Pack 4 Year 2000 Update; IE 4.01 SP2 updates
Product Dependencies: None
Clock Dependencies: Relative date queries are resolved using current system time
Last Updated: 21 Sep 1999
Product Details

Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 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 Server 4.0 Service Pack 4, Terminal Server 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. (Internet Explorer 4.01 Service Pack 2 is included on the Terminal Server 4 Service Pack 4 CD-ROM.)

Through ongoing testing, Microsoft has identified two year 2000 issues, which are addressed by post-Service Pack 4 for Terminal Server (TS SP4) updates. Microsoft recommends that users evaluate the post-TS SP4 Year 2000 software updates and consider deploying them based on their exposure to each issue. The issues are detailed in Step 2 below.

 

Introduction

Windows NT Server 4.0, Terminal Server Edition ("Terminal Server") is a version of the Windows NT Server 4.0 operating system released in June 1998. Terminal Server was released integrated with Service Pack 3 ("SP3"). Recently, Service Pack 4 for Terminal Server was released. Microsoft intends to maintain Year 2000 compliance of Service Pack 4 through January 1, 2001, in addition to maintaining the Year 2000 compliance of subsequent Service Packs through January 1, 2001.

When users load the Terminal Server operating system on a computer, they are asked to select from a number of installation options. In addition, Microsoft has made additional Windows NT Server 4.0 features available to licensed users via the Terminal Server CD. 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.

As mentioned above, Microsoft has determined that Terminal Server 4.0 and some versions of additional Terminal Server features have known Year 2000 issues that have updates we recommend you apply. 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 software updates. In other cases, users are instructed to update a feature to a newer version of the feature to address known issues.

  • Please Note: Installation of Service Pack 4 for Terminal Server (TS SP4) must be performed with the system in "install" mode. This is performed automatically with the TS SP4 CD. Alternatively, at the command prompt, type: change user /install prior to installing TS SP4.

The steps identified below take a comprehensive approach to addressing known issues.

  • Step 1 prepares the target system for Terminal Server SP4 by addressing any updates that are needed before SP4 is applied.
  • Step 2 installs Terminal Server SP4 and any post-SP4 Year 2000 Updates to analyze the target system, remove versions that have known issues, and install updated versions that have no known issues.
  • Step 3 then audits the target system. To confirm all known issues have been addressed and steps 1 and 2 have been done correctly, the results of the audit should indicate that only those versions having a "compliant" rating (as identified on the tables below) remain on the target system after Steps 1 and 2 have been completed.

Step 1

TS SP4 itself will address most known Year 2000 issues. However, we recommend users update or upgrade certain features to newer versions, in addition to applying TS SP4.

Table 1A (below) lists the features that we recommend be updated or upgraded in addition to applying TS SP4, along with specific update/upgrade instructions.

Table 1B (below) lists the Terminal Server Optional features that we recommend 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 TS SP4 (which is outlined in Step 2).

Table 1A: System Components.

Feature Name

Version

Action Required Prior to Step 2

Microsoft Internet Explorer (IE)

Multiple Versions

Upgrade to IE4.01 SP2 including any applicable Year 2000 software Updates.

For information on additional Year 2000 Updates for IE, refer HERE.

IE 4.01 SP2 is included on the Terminal Server SP4 CD-ROM.

(Users who prefer to remain on IE 4.01 SP1 should refer to the IE4 Year 2000 Compliance document available HERE for appropriate actions. Additional software updates are recommended in addition to SP1.)

Table 1B: Optional Components.

Feature Name

Version

Action Required Prior to Step 2

Microsoft Data Access Components (MDAC)

Multiple Versions

Install MDAC 2.1 SP1 or newer including any applicable Year 2000 software Updates.

For information on additional Year 2000 Updates for MDAC, refer HERE.

Go Here for MDAC Downloads

Please note that the TSLicense service should be stopped before installing MDAC.

Microsoft FrontPage 97

"97"

Install FrontPage 97 Year 2000 Updates

 

Step 2

We recommend users apply SP4 for Terminal Server to the Target System. TS SP4 can be obtained by clicking here.

The installation of SP4 applies updates to the base Terminal Server product, features and installation options.

We recommend users also apply any Terminal Server Year 2000 updates that have been made available post-TS SP4.

When available, the post-TS SP4 year 2000 updates will be posted here.

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). A software update will be available in August 1999. Check back here then for further information.

2. License Server will not start on February 29, 2000. If users attempt to start the Terminal Server License Server on 2/29/2000, the following error message is displayed in the event log: "Can't load server's certificate. See Terminal Server Licensing help topic for more information. Event ID = 7 Type = error." Clients will still be allowed to connect, but will not be issued a license. A Knowledge Base article (Q236405) and software update will be available in August 1999. Check back here then for further information.

 

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.

  • Create a list of the Terminal Server 4.0 installation options and additional features installed on the target system
  • Review the compliance status of the installation options and features using Tables 2 & 3.
  • Confirm that only installation options and features having a "compliant" rating (as identified on the tables below) remain on the target system after Steps 1 and 2 have been completed.

Detail:

When users load the Terminal 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 the Terminal Server operating system itself and each of the options listed in Table 2 below should be updated after applying TS SP4.

Table 2

Option/Server Name

Compliance Rating

Gateway Services for NetWare

Compliant

Microsoft DHCP Server

Compliant

Microsoft DNS Server

Compliant

Microsoft TCP/IP Printing

Compliant

NetBEUI Protocol

Compliant

NetBIOS Interface

Compliant

Network Monitor Agent

Compliant

Network Monitor Tools and Agent

Compliant

NWLink IPX/SPX-Compatible Transport

Compliant

Point To Point Tunneling Protocol

Compliant

Remote Access Service

Compliant

SAP Agent

Compliant

Server

Compliant

Simple TCP/IP Services

Compliant

TCP/IP Protocol

Compliant

Windows Internet Name Service

Compliant

Windows Messenger Service

Compliant

Workstation

Compliant

 

The compliance ratings listed above are subject to change without notice. Please review this information frequently to assess whether there have been any changes to the compliance status of the installation option you have selected.

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. Microsoft has made these features available via Service Packs and the Windows NT Option Pack.

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

Feature Name

Version

Feature Compliance Rating

Notes

Distributed File Service

4.0

Compliant

Distributed File Service

4.1

Compliant

Imaging for Windows

Not Applicable

Compliant

Applies to all Versions that run on Windows NT Server 4.0

Microsoft Data Access Components(MDAC)

Multiple Versions

See Table 1B for Required Action

See Table 1B for Required Action

Microsoft Euro Currency Support for
Windows NT 4.0

Not Applicable

Compliant

Microsoft FrontPage 97

"97"

Not Compliant

See Note 2

Microsoft FrontPage 97

"97" with Updates

Compliant

To determine that Microsoft Front Page 97 updates are installed, verify the version number of the file named:
"(system directory)\system32\fp20tl.dll"
is at least 02.00.3002.23. See note 3 for instructions on verifying version numbers of .DLL files.

Microsoft FrontPage 97 Server Extensions

"97"

Not Compliant

See Note 1

Microsoft FrontPage 98 Server Extensions

"98"

Compliant

See Note 1

Microsoft Internet Explorer

Multiple Versions

See Table 1A for Required Action

See Table 1A for Required Action

Microsoft Internet Information Server

3.0

Compliant

Microsoft Internet Information Server

4.0

See Note 4

Microsoft Management Console

1.0

Compliant

Microsoft Message Queue Server

All Versions

See Note 5

Microsoft Virtual Machine

(Many Versions)

See Notes for Required Action

Some versions of the Microsoft Virtual Machine, including the versions that shipped with SP4 and with some versions of Internet Explorer, have known Year 2000 date-related issues. Please refer to the Microsoft VM year 2000 Product Guide at Microsoft Virtual Machine for details and recommendations to address known issues.

NetShow Services

1.0

Not Tested

NetShow Services

3.0

Compliant

Windows Media Player

6.0

Compliant

To verify that Windows Media Player 6.0 is installed, users should select "Help/About Windows Media Player" from within Windows Media Player and verify that the version number is 5.01.52.0701 or greater.

 

The compliance ratings listed above are subject to change without notice. Please review this information frequently to assess whether there have been any changes to the compliance status of the features you have installed.

 

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 Table 3, 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:

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. To verify the version number of a dynamic link library (DLL) file, users should:

  • Start Windows NT Explorer from the Start/Programs menu
  • Locate the DLL file to be verified
  • Select the file by pointing the mouse cursor at the file clicking the left mouse button once
  • Click the right mouse button once to display a menu
  • Select "Properties" from the menu by pointing the mouse cursor at the option and clicking the left mouse button once
  • Select the "Version" tab by pointing the mouse cursor at the tab and clicking the left mouse button once
  • Visually Locate the version number in the field labeled "File Version"

4. Internet Information Server 4.0 has not been tested for compatibility with Terminal Server 4.0. For additional IIS year 2000 compliance information, consult the Windows NT 4.0 Compliance Documents.

5. MSMQ has not been tested for compatibility with Terminal Server 4.0. For additional MSMQ year 2000 compliance information, consult the Windows NT 4.0 Compliance Documents.


Legend of Symbols:
*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  3.51   (Chinese - Simplified)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Chinese - Simplified OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 software update
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Chinese - Traditional)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Chinese - Traditional OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 software update
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Dutch)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Dutch OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and hot fix
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (English)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: English OS: Win NT Release Date: 30 May 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and a hot fix
Product Dependencies:
Clock Dependencies: System clock
Last Updated: 04 Oct 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (French)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: French OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows Nt 3.51 Service Pack 5 and hot fix
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (German)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: German OS: Win NT Release Date: 30 May 1998
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and a hot fix
Product Dependencies:
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Japanese)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996- - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and hot fix
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Korean)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Korean OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 software update and update
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Portuguese (Brazil))

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Portuguese (Brazil) OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and hot fix
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Spanish)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Spanish OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and hot fox
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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  3.51   (Swedish)

Product Summary
Product: Windows NT Server Version: 3.51 Category:Compliant*
Language: Swedish OS: Win NT Release Date: 30 May 1995
Operational Range: 01 Jan 1996 - 31 Dec 2036
Prerequisites: Windows NT 3.51 Service Pack 5 and hot fix
Product Dependencies: None
Clock Dependencies: System clock
Last Updated: 30 Sep 1999
Product Details

What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:

1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51

Brazilian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/351.sp5/

Chinese Simplified ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/chs/NT351/SP5/

Chinese Traditional ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/cht/NT351/SP5/

Dutch ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nld/351.sp5

English ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ussp5

French ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/frn/351.sp5/

German ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ger/351.sp5/

Japanese http://www.microsoft.com/japan/products/ntupdate/nt351postsp5/sp5.htm

Korean ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/kor/NT351/SP5/

Norwegian ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nor/351.SP5/

Spanish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/spa/351.sp5/

Swedish ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/sve/351.sp5/

2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.  

Brazilian

Chinese Simplified

Chinese Traditional

Dutch

French

English

German

Japanese

Korean

Norwegian

Spanish

Swedish

The software update addresses the following issues:

1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.

2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article 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.

3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another 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.

4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).

5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year."

6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000.

7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date.

8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values.

9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge 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.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the
Windows NT 4.0 Compliance Documents.

Description of how dates are handled in the product:

Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks.


What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.

Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.


Legend of Symbols:
*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

YEAR 2000 READINESS DISCLOSURE

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.