01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
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=1430Testing guidelines and recommendations:
|
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
13 Sep 1999 | ||
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 CreationDateIn 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. |
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. |
- | |||||||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
14 Oct 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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
Table 2: Windows NT Embedded 4.0 – embedded-enabling features
|
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. |
- | |||||||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
04 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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
Table 2: Windows NT Embedded 4.0 – embedded-enabling features
|
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. |
- | |||||||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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
Table 2: Windows NT Embedded 4.0 – embedded-enabling features
|
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
- | ||
Windows NT 4.0 Service Pack 4 or higher plus any necessary post-service pack updates. | ||
20 Oct 1999 | ||
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. |
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. |
01 Jan 1980 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT4 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT Server 4.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
18 Oct 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
|
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. |
01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 3 Year 2000 Update (see below) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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:
An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either: http://www.microsoft.com/ntserver/all/downloadsor ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/
1. WINS/DHCP Admin show Expiration Dates incorrectly . (Q193371) Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). This is a display issue only.2. Custom date properties in .DOC property dialog box . (Q207807) When a Word 97 file is selected on the desktop and the user right clicks on the file, selects "Properties", selects the "custom" tab, and then enters a date with a 2-digit year value of "01", this issue may cause the date to automatically decrement by 1 day when the "Add" button is clicked. This issue only manifests if time zone is set to Far East region time zone (Greenwich Mean Time (GMT)+8 or Greenwich Mean Time (GMT)+9).3. BIOS Date Value does not Immediately Update on January 1, 2000. ( Q216913) When the Window NT System Time value rolls over from the year "1999" to "2000", the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. This behavior may cause unexpected behavior under two conditions:
4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the 5. Incorrect Date Displayed when viewing a saved System Info Report. ( Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".6. Four-Digit Year Format for Non-English Regional Settings. ( Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring 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.
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.
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.
Notes: http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.
|
The 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. |
01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 3 Year 2000 Update (see below) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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:
An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either: http://www.microsoft.com/ntserver/all/downloadsor ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/
1. WINS/DHCP Admin show Expiration Dates incorrectly . (Q193371) Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). This is a display issue only.2. Custom date properties in .DOC property dialog box . (Q207807) When a Word 97 file is selected on the desktop and the user right clicks on the file, selects "Properties", selects the "custom" tab, and then enters a date with a 2-digit year value of "01", this issue may cause the date to automatically decrement by 1 day when the "Add" button is clicked. This issue only manifests if time zone is set to Far East region time zone (Greenwich Mean Time (GMT)+8 or Greenwich Mean Time (GMT)+9).3. BIOS Date Value does not Immediately Update on January 1, 2000. ( Q216913) When the Window NT System Time value rolls over from the year "1999" to "2000", the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. This behavior may cause unexpected behavior under two conditions:
4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the 5. Incorrect Date Displayed when viewing a saved System Info Report. ( Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".6. Four-Digit Year Format for Non-English Regional Settings. ( Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring 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.
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.
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.
Notes: http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.
|
The 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. |
01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 3 Year 2000 Update (see below) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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:
An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either: http://www.microsoft.com/ntserver/all/downloadsor ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/
1. WINS/DHCP Admin show Expiration Dates incorrectly . (Q193371) Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). This is a display issue only.2. Custom date properties in .DOC property dialog box . (Q207807) When a Word 97 file is selected on the desktop and the user right clicks on the file, selects "Properties", selects the "custom" tab, and then enters a date with a 2-digit year value of "01", this issue may cause the date to automatically decrement by 1 day when the "Add" button is clicked. This issue only manifests if time zone is set to Far East region time zone (Greenwich Mean Time (GMT)+8 or Greenwich Mean Time (GMT)+9).3. BIOS Date Value does not Immediately Update on January 1, 2000. ( Q216913) When the Window NT System Time value rolls over from the year "1999" to "2000", the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. This behavior may cause unexpected behavior under two conditions:
4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the 5. Incorrect Date Displayed when viewing a saved System Info Report. ( Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".6. Four-Digit Year Format for Non-English Regional Settings. ( Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring 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.
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.
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.
Notes: http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.
|
The 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. |
01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 3 Year 2000 Update (see below) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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:
An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either: http://www.microsoft.com/ntserver/all/downloadsor ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/
1. WINS/DHCP Admin show Expiration Dates incorrectly . (Q193371) Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). This is a display issue only.2. Custom date properties in .DOC property dialog box . (Q207807) When a Word 97 file is selected on the desktop and the user right clicks on the file, selects "Properties", selects the "custom" tab, and then enters a date with a 2-digit year value of "01", this issue may cause the date to automatically decrement by 1 day when the "Add" button is clicked. This issue only manifests if time zone is set to Far East region time zone (Greenwich Mean Time (GMT)+8 or Greenwich Mean Time (GMT)+9).3. BIOS Date Value does not Immediately Update on January 1, 2000. ( Q216913) When the Window NT System Time value rolls over from the year "1999" to "2000", the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. This behavior may cause unexpected behavior under two conditions:
4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the 5. Incorrect Date Displayed when viewing a saved System Info Report. ( Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".6. Four-Digit Year Format for Non-English Regional Settings. ( Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring 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.
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.
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.
Notes: http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.
|
The 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. |
01 Jan 1996 - 31 Dec 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 3 Year 2000 Update (see below) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
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:
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:
An update for this language version of Terminal Server version 4.0 SP3 can be obtained at either: http://www.microsoft.com/ntserver/all/downloadsor ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/
1. WINS/DHCP Admin show Expiration Dates incorrectly . (Q193371) Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). This is a display issue only.2. Custom date properties in .DOC property dialog box . (Q207807) When a Word 97 file is selected on the desktop and the user right clicks on the file, selects "Properties", selects the "custom" tab, and then enters a date with a 2-digit year value of "01", this issue may cause the date to automatically decrement by 1 day when the "Add" button is clicked. This issue only manifests if time zone is set to Far East region time zone (Greenwich Mean Time (GMT)+8 or Greenwich Mean Time (GMT)+9).3. BIOS Date Value does not Immediately Update on January 1, 2000. ( Q216913) When the Window NT System Time value rolls over from the year "1999" to "2000", the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. This behavior may cause unexpected behavior under two conditions:
4. OLE Automation. In locales where there are other calendars in addition to the Gregorian calendar, application functionality that depends on OLE Automation to interpret 2-digit years does not properly use the date window as set in Control Panel, Regional settings. The result is that the maximum value for the sliding date window is not properly read for Gregorian dates in those locales causing it to fall back to the default value of 2029. This problem would occur only if the date window had been changed from the default value of 1930-2029. See the 5. Incorrect Date Displayed when viewing a saved System Info Report. ( Q218877) Programs that use the COleDateTime function from MFC40.dll may incorrectly parse a date after the year 2000 (02/05/2000 may become 2/05/100). The function assumes that any year passed to it as 2 digits is relative to 1900 and adds 1900 to it. If a 4-digit year is passed, this function results in the correct 4-digit year. For example, if "02" is passed (for 2002) to the function, it will return a date of "102".6. Four-Digit Year Format for Non-English Regional Settings. ( Q218941) When certain locale settings (such as Hebrew or Japanese) are used in configuring 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.
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.
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.
Notes: http://www.microsoft.com/support/winnt/default.htm. Click on Begin the Download Process, Select Encryption Level, and Accept the License agreement. The following page allows the user to download the updated Content Analyzer.
|
The 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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 4 Year 2000 Update; IE 4.01 SP2 updates | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 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. The steps identified below take a comprehensive approach to addressing known issues.
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.
Table 1B: Optional Components.
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.
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
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
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:
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. |
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 4 Year 2000 Update; IE 4.01 SP2 updates | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 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. The steps identified below take a comprehensive approach to addressing known issues.
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.
Table 1B: Optional Components.
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.
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
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
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:
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. |
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post-Service Pack 4 Year 2000 Update; IE 4.01 SP2 updates | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
None | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Relative date queries are resolved using current system time | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows NT Server 4.0 Service Pack 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. The steps identified below take a comprehensive approach to addressing known issues.
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.
Table 1B: Optional Components.
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.
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
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
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:
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. |
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 software update | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 software update | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and hot fix | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
System clock | |||||||||||||
04 Oct 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows Nt 3.51 Service Pack 5 and hot fix | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and a hot fix | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996- - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and hot fix | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 software update and update | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and hot fix | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and hot fox | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
01 Jan 1996 - 31 Dec 2036 | |||||||||||||
Windows NT 3.51 Service Pack 5 and hot fix | |||||||||||||
None | |||||||||||||
System clock | |||||||||||||
30 Sep 1999 | |||||||||||||
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 2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5. Brazilian Chinese Simplified Chinese TraditionalDutchFrench English German Japanese Korean Norwegian Spanish Swedish The software update addresses the following issues :
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:
|
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. |
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. |