Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Greek)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Hungarian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Italian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Japanese)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or WIndows NT 3.51 Service Pack 5 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2-digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2036.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2 digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2-digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4 digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any 2-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Korean)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Norwegian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Polish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Portuguese (Brazil))
| - | ||
| - | ||
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Portuguese)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Russian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Spanish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Swedish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Turkish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Chinese - Simplified)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Chinese - Traditional)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Czech)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Danish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Dutch)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (English)
| 01 Jan 1970 - 05 Feb 2036 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.0, Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. English version of the Exchange Server 5.0 Service Pack 2 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Sp2/English versions of the required Exchange Server 5.0 hot fixes are located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-STORE/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-CCM/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-MIG/French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors amessaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Finnish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (French)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. English version of the Exchange Server 5.0 Service Pack 2 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Sp2/English versions of the required Exchange Server 5.0 hot fixes are located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-STORE/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-CCM/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-MIG/French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors amessaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (German)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. English version of the Exchange Server 5.0 Service Pack 2 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Sp2/English versions of the required Exchange Server 5.0 hot fixes are located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-STORE/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-CCM/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-MIG/French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors amessaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Greek)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Hungarian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Italian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Japanese)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. English version of the Exchange Server 5.0 Service Pack 2 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Sp2/English versions of the required Exchange Server 5.0 hot fixes are located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-STORE/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-CCM/ ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.0/Post-SP2-MIG/French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors amessaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Korean)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Norwegian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Polish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Portuguese (Brazil))
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Portuguese)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Russian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Spanish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Swedish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.0 (Turkish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Chinese - Simplified)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Chinese - Traditional)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Czech)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Danish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Dutch)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (English)
| 01 Jan 1986 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.5 Service Pack 2 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.5 Service Pack 2 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.Note 1: For the entire product to Compliant Exchange 5.5 Service Pack 2 is required. However, if the following components are not installed, Microsoft Exchange Connector for Lotus cc:Mail, Microsoft Migration Wizard for cc:Mail, Microsoft Mail DirSync, then Exchange 5.5 Service Pack 1 is Compliant. Note 2: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.This document covers the products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. The components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? * Exchange 5.5 Service Pack 2 is required if any of the following components are used on the Exchange server.
Below are Knowledge Base articles that describe the problems in each component, not the fixes themselves. The fixes for the problems are contained in Service Pack 2. If any one of the above is installed on the user’s computer, then Service Pack 2 needs to be applied. Q193735 Q192595 XFOR: Incorrect Date on Message Sent Through cc:Mail ConnectorQ193745 XFOR: Dates Appear Incorrectly After cc:Mail MigrationQ171593 XGEN: List of Bugs Fixed in Exchange Server 5.5 Service PacksIf none of these components are used, then Exchange 5.5 Service Pack 1 is sufficient. Exchange 5.5 Service Pack 1 and Exchange 5.5 Service Pack 2 are located on:
Extensible Storage Engine (ESE) and the Exchange Server Database Engine use an internal date range in years from 1900 to 2156. ESE uses the JET_LOGTIME structure. Date/Time structures for ESE: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 – 2156.
Microsoft Exchange Information Store : Internally the Exchange Information Store stores year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2-digit year in those cases where other components hand the information store an Internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan. 1, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the 2 digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the information store has to do the year 2000 conversion and supports a range of 1986 – 2050. (Abbreviated years 86-99 = 1986-1999 and 00-50 = 2000-2050 as discussed above.)
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The dates used for the headers are 4 digits, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits CDONTS has to do the year 2000 conversion and supports a range of 1937 – 2038. (37-99 = 1936-1999 and 00-38 = 2000-2038)
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI use a 64-bit FILETIME. CDO or MAPI compliant applications that pass a correct 4-digit date will be stored correctly within Exchange. The internal date range in years for Exchange is from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): Dates stored internally within OWA are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of OWA is January 1, 1970 through January 19, 2038. The 4-digit dates are used throughout and passed back and forth through ASP and CDO. The user interface in OWA allows the users to enter the year for a date in 2 digits. When these dates are entered, OWA has a centralized JavaScript routine that normalizes the 2-digit years into 4-digit years for internal storage. The algorithm used to normalize the dates is as follows: if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA, other 2-digit numbers that are entered through the user interface within the range 39-69 result in an error message that alerts the user and the field reverts back to its last known recognized 4-digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, OWA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange Message Transfer Agent is a X.400 standard Message Transfer Agent. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems Message Transfer Agent converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Message Transfer Agent uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2-digit dates the Message Transfer Agent converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards, which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of DSA is January 1, 1970 through January 15, 2038. Exchange uses a 4-byte field that counts the number of seconds from 1/1/1970. The highest number that Exchange holds results in a maximum date of 1/19/2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99. However, due to X.500 standards that only support 2 digits, the DSA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in 2 digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to Internet and X.400 standards that only support 2 digits, the Administrator program converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The Microsoft Exchange Key Management Server explicitly uses 4 digits to represent years for storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours, the year digits as part of the date are not used. Encryption coding was tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The Microsoft Exchange Internet Mail Service stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the Internet Mail Service, are handled by IMAIL and the MDB. RFC 822 messages store date formats with 2-digits representing the year. See MDB for more information. When the IMC is setup as a connector it reads information from the GWART. See Message Transfer Agent for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the Microsoft Exchange Internet Mail Service converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Chat Server: The Chat Server only calculates time based on tick counts for real-time collaboration that does not span across a year period. When dates are stored, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits.
Microsoft Mail Connector Interchange (MSMI): Dates going to Exchange via Microsoft Mail Connector Interchange in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING, which is a string presentation of the ASN.1 UTC time syntax used by the Message Transfer Agent. UTC time is a 2-digit year and thus the Message Transfer Agent interprets the date into a 4-digit year. See the Message Transfer Agent for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2 digits, MSMI converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits, passed from cc:Mail, are the difference from 1900 (as defined by cc:Mail), which works only for 19xx years . When the Microsoft Exchange Server receives the dates, a conversion is done using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate results in expected behavior. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to cc:Mail only supporting 2 digits CCMC converts the date to four digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049.
Microsoft Exchange Connector for Lotus Notes: Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from Notes are mapped to/from the Notes date format; this is a 4-digit year format and is unambiguous. Date/Time structures Notes Connector uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055.
Microsoft Exchange SNADS Connector (SNADS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from SNADS are mapped to/from the SNADS date format; this is a 4-digit year format and is unambiguous. Date/Time structures SNADS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange IBM OfficeVision/Virtual Machine Connector (PROFS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. PROFS uses 2-digit year format. The PROFS connector converts this to and from the 2-digit year format using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures PROFS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to PROFS only supporting 2 digits, the PROFS connector converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. CCMS supports a range of 1970 – 2038.
Microsoft Exchange MIGRATION Dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. cc:Mail DB8: If the year number is greater than 60 then add 1900. If the year passed in is less than or equal to 60 then add 2000. Example: 10 is passed in for the year 2010. Collabra: Add 1980 to the year that is passed in from Collabra. Example: 30 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Notes: The year is passed in as 4 digits from Notes. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Also tested in Exchange 5.5 Service Pack 2: Microsoft Exchange InterOrg Replication Utility Microsoft Exchange InterOrg Move Server Utility Microsoft Exchange InterOrg Mailbox Cleanup Utility Two-digit shortcut handling: There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these cases, dates with the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Common date usage errors: Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure our customers of the compliance of the non-Microsoft receiving environment or the reliability of the date data being based to Microsoft Exchange Server. Testing guidelines and recommendations: Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use applications that may have been written to use the Exchange environment. These are workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Finnish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (French)
| 01 Jan 1986 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.5 Service Pack 2 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.5 Service Pack 2 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.Note 1: For the entire product to Compliant Exchange 5.5 Service Pack 2 is required. However, if the following components are not installed, Microsoft Exchange Connector for Lotus cc:Mail, Microsoft Migration Wizard for cc:Mail, Microsoft Mail DirSync, then Exchange 5.5 Service Pack 1 is Compliant. Note 2: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.This document covers the products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. The components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? * Exchange 5.5 Service Pack 2 is required if any of the following components are used on the Exchange server.
Below are Knowledge Base articles that describe the problems in each component, not the fixes themselves. The fixes for the problems are contained in Service Pack 2. If any one of the above is installed on the user’s computer, then Service Pack 2 needs to be applied. Q193735 Q192595 XFOR: Incorrect Date on Message Sent Through cc:Mail ConnectorQ193745 XFOR: Dates Appear Incorrectly After cc:Mail MigrationQ171593 XGEN: List of Bugs Fixed in Exchange Server 5.5 Service PacksIf none of these components are used, then Exchange 5.5 Service Pack 1 is sufficient. Exchange 5.5 Service Pack 1 and Exchange 5.5 Service Pack 2 are located on:
Extensible Storage Engine (ESE) and the Exchange Server Database Engine use an internal date range in years from 1900 to 2156. ESE uses the JET_LOGTIME structure. Date/Time structures for ESE: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 – 2156.
Microsoft Exchange Information Store : Internally the Exchange Information Store stores year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2-digit year in those cases where other components hand the information store an Internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan. 1, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the 2 digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the information store has to do the year 2000 conversion and supports a range of 1986 – 2050. (Abbreviated years 86-99 = 1986-1999 and 00-50 = 2000-2050 as discussed above.)
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The dates used for the headers are 4 digits, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits CDONTS has to do the year 2000 conversion and supports a range of 1937 – 2038. (37-99 = 1936-1999 and 00-38 = 2000-2038)
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI use a 64-bit FILETIME. CDO or MAPI compliant applications that pass a correct 4-digit date will be stored correctly within Exchange. The internal date range in years for Exchange is from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): Dates stored internally within OWA are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of OWA is January 1, 1970 through January 19, 2038. The 4-digit dates are used throughout and passed back and forth through ASP and CDO. The user interface in OWA allows the users to enter the year for a date in 2 digits. When these dates are entered, OWA has a centralized JavaScript routine that normalizes the 2-digit years into 4-digit years for internal storage. The algorithm used to normalize the dates is as follows: if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA, other 2-digit numbers that are entered through the user interface within the range 39-69 result in an error message that alerts the user and the field reverts back to its last known recognized 4-digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, OWA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange Message Transfer Agent is a X.400 standard Message Transfer Agent. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems Message Transfer Agent converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Message Transfer Agent uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2-digit dates the Message Transfer Agent converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards, which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of DSA is January 1, 1970 through January 15, 2038. Exchange uses a 4-byte field that counts the number of seconds from 1/1/1970. The highest number that Exchange holds results in a maximum date of 1/19/2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99. However, due to X.500 standards that only support 2 digits, the DSA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in 2 digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to Internet and X.400 standards that only support 2 digits, the Administrator program converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The Microsoft Exchange Key Management Server explicitly uses 4 digits to represent years for storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours, the year digits as part of the date are not used. Encryption coding was tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The Microsoft Exchange Internet Mail Service stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the Internet Mail Service, are handled by IMAIL and the MDB. RFC 822 messages store date formats with 2-digits representing the year. See MDB for more information. When the IMC is setup as a connector it reads information from the GWART. See Message Transfer Agent for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the Microsoft Exchange Internet Mail Service converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Chat Server: The Chat Server only calculates time based on tick counts for real-time collaboration that does not span across a year period. When dates are stored, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits.
Microsoft Mail Connector Interchange (MSMI): Dates going to Exchange via Microsoft Mail Connector Interchange in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING, which is a string presentation of the ASN.1 UTC time syntax used by the Message Transfer Agent. UTC time is a 2-digit year and thus the Message Transfer Agent interprets the date into a 4-digit year. See the Message Transfer Agent for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2 digits, MSMI converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits, passed from cc:Mail, are the difference from 1900 (as defined by cc:Mail), which works only for 19xx years . When the Microsoft Exchange Server receives the dates, a conversion is done using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate results in expected behavior. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to cc:Mail only supporting 2 digits CCMC converts the date to four digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049.
Microsoft Exchange Connector for Lotus Notes: Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from Notes are mapped to/from the Notes date format; this is a 4-digit year format and is unambiguous. Date/Time structures Notes Connector uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055.
Microsoft Exchange SNADS Connector (SNADS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from SNADS are mapped to/from the SNADS date format; this is a 4-digit year format and is unambiguous. Date/Time structures SNADS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange IBM OfficeVision/Virtual Machine Connector (PROFS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. PROFS uses 2-digit year format. The PROFS connector converts this to and from the 2-digit year format using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures PROFS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to PROFS only supporting 2 digits, the PROFS connector converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. CCMS supports a range of 1970 – 2038.
Microsoft Exchange MIGRATION Dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. cc:Mail DB8: If the year number is greater than 60 then add 1900. If the year passed in is less than or equal to 60 then add 2000. Example: 10 is passed in for the year 2010. Collabra: Add 1980 to the year that is passed in from Collabra. Example: 30 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Notes: The year is passed in as 4 digits from Notes. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Also tested in Exchange 5.5 Service Pack 2: Microsoft Exchange InterOrg Replication Utility Microsoft Exchange InterOrg Move Server Utility Microsoft Exchange InterOrg Mailbox Cleanup Utility Two-digit shortcut handling: There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these cases, dates with the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Common date usage errors: Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure our customers of the compliance of the non-Microsoft receiving environment or the reliability of the date data being based to Microsoft Exchange Server. Testing guidelines and recommendations: Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use applications that may have been written to use the Exchange environment. These are workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (German)
| 01 Jan 1986 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.5 Service Pack 2 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.5 Service Pack 2 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.Note 1: For the entire product to Compliant Exchange 5.5 Service Pack 2 is required. However, if the following components are not installed, Microsoft Exchange Connector for Lotus cc:Mail, Microsoft Migration Wizard for cc:Mail, Microsoft Mail DirSync, then Exchange 5.5 Service Pack 1 is Compliant. Note 2: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.This document covers the products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. The components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? * Exchange 5.5 Service Pack 2 is required if any of the following components are used on the Exchange server.
Below are Knowledge Base articles that describe the problems in each component, not the fixes themselves. The fixes for the problems are contained in Service Pack 2. If any one of the above is installed on the user’s computer, then Service Pack 2 needs to be applied. Q193735 Q192595 XFOR: Incorrect Date on Message Sent Through cc:Mail ConnectorQ193745 XFOR: Dates Appear Incorrectly After cc:Mail MigrationQ171593 XGEN: List of Bugs Fixed in Exchange Server 5.5 Service PacksIf none of these components are used, then Exchange 5.5 Service Pack 1 is sufficient. Exchange 5.5 Service Pack 1 and Exchange 5.5 Service Pack 2 are located on:
Extensible Storage Engine (ESE) and the Exchange Server Database Engine use an internal date range in years from 1900 to 2156. ESE uses the JET_LOGTIME structure. Date/Time structures for ESE: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 – 2156.
Microsoft Exchange Information Store : Internally the Exchange Information Store stores year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2-digit year in those cases where other components hand the information store an Internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan. 1, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the 2 digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the information store has to do the year 2000 conversion and supports a range of 1986 – 2050. (Abbreviated years 86-99 = 1986-1999 and 00-50 = 2000-2050 as discussed above.)
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The dates used for the headers are 4 digits, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits CDONTS has to do the year 2000 conversion and supports a range of 1937 – 2038. (37-99 = 1936-1999 and 00-38 = 2000-2038)
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI use a 64-bit FILETIME. CDO or MAPI compliant applications that pass a correct 4-digit date will be stored correctly within Exchange. The internal date range in years for Exchange is from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): Dates stored internally within OWA are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of OWA is January 1, 1970 through January 19, 2038. The 4-digit dates are used throughout and passed back and forth through ASP and CDO. The user interface in OWA allows the users to enter the year for a date in 2 digits. When these dates are entered, OWA has a centralized JavaScript routine that normalizes the 2-digit years into 4-digit years for internal storage. The algorithm used to normalize the dates is as follows: if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA, other 2-digit numbers that are entered through the user interface within the range 39-69 result in an error message that alerts the user and the field reverts back to its last known recognized 4-digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, OWA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange Message Transfer Agent is a X.400 standard Message Transfer Agent. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems Message Transfer Agent converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Message Transfer Agent uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2-digit dates the Message Transfer Agent converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards, which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of DSA is January 1, 1970 through January 15, 2038. Exchange uses a 4-byte field that counts the number of seconds from 1/1/1970. The highest number that Exchange holds results in a maximum date of 1/19/2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99. However, due to X.500 standards that only support 2 digits, the DSA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in 2 digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to Internet and X.400 standards that only support 2 digits, the Administrator program converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The Microsoft Exchange Key Management Server explicitly uses 4 digits to represent years for storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours, the year digits as part of the date are not used. Encryption coding was tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The Microsoft Exchange Internet Mail Service stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the Internet Mail Service, are handled by IMAIL and the MDB. RFC 822 messages store date formats with 2-digits representing the year. See MDB for more information. When the IMC is setup as a connector it reads information from the GWART. See Message Transfer Agent for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the Microsoft Exchange Internet Mail Service converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Chat Server: The Chat Server only calculates time based on tick counts for real-time collaboration that does not span across a year period. When dates are stored, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits.
Microsoft Mail Connector Interchange (MSMI): Dates going to Exchange via Microsoft Mail Connector Interchange in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING, which is a string presentation of the ASN.1 UTC time syntax used by the Message Transfer Agent. UTC time is a 2-digit year and thus the Message Transfer Agent interprets the date into a 4-digit year. See the Message Transfer Agent for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2 digits, MSMI converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits, passed from cc:Mail, are the difference from 1900 (as defined by cc:Mail), which works only for 19xx years . When the Microsoft Exchange Server receives the dates, a conversion is done using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate results in expected behavior. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to cc:Mail only supporting 2 digits CCMC converts the date to four digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049.
Microsoft Exchange Connector for Lotus Notes: Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from Notes are mapped to/from the Notes date format; this is a 4-digit year format and is unambiguous. Date/Time structures Notes Connector uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055.
Microsoft Exchange SNADS Connector (SNADS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from SNADS are mapped to/from the SNADS date format; this is a 4-digit year format and is unambiguous. Date/Time structures SNADS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange IBM OfficeVision/Virtual Machine Connector (PROFS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. PROFS uses 2-digit year format. The PROFS connector converts this to and from the 2-digit year format using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures PROFS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to PROFS only supporting 2 digits, the PROFS connector converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. CCMS supports a range of 1970 – 2038.
Microsoft Exchange MIGRATION Dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. cc:Mail DB8: If the year number is greater than 60 then add 1900. If the year passed in is less than or equal to 60 then add 2000. Example: 10 is passed in for the year 2010. Collabra: Add 1980 to the year that is passed in from Collabra. Example: 30 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Notes: The year is passed in as 4 digits from Notes. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Also tested in Exchange 5.5 Service Pack 2: Microsoft Exchange InterOrg Replication Utility Microsoft Exchange InterOrg Move Server Utility Microsoft Exchange InterOrg Mailbox Cleanup Utility Two-digit shortcut handling: There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these cases, dates with the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Common date usage errors: Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure our customers of the compliance of the non-Microsoft receiving environment or the reliability of the date data being based to Microsoft Exchange Server. Testing guidelines and recommendations: Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use applications that may have been written to use the Exchange environment. These are workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Greek)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Hungarian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Italian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Japanese)
| 01 Jan 1986 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.5 Service Pack 2 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Enterprise 5.5 Service Pack 2 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.Note 1: For the entire product to Compliant Exchange 5.5 Service Pack 2 is required. However, if the following components are not installed, Microsoft Exchange Connector for Lotus cc:Mail, Microsoft Migration Wizard for cc:Mail, Microsoft Mail DirSync, then Exchange 5.5 Service Pack 1 is Compliant. Note 2: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.This document covers the products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. The components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? * Exchange 5.5 Service Pack 2 is required if any of the following components are used on the Exchange server.
Below are Knowledge Base articles that describe the problems in each component, not the fixes themselves. The fixes for the problems are contained in Service Pack 2. If any one of the above is installed on the user’s computer, then Service Pack 2 needs to be applied. Q193735 Q192595 XFOR: Incorrect Date on Message Sent Through cc:Mail ConnectorQ193745 XFOR: Dates Appear Incorrectly After cc:Mail MigrationQ171593 XGEN: List of Bugs Fixed in Exchange Server 5.5 Service PacksIf none of these components are used, then Exchange 5.5 Service Pack 1 is sufficient. Exchange 5.5 Service Pack 1 and Exchange 5.5 Service Pack 2 are located on:
Extensible Storage Engine (ESE) and the Exchange Server Database Engine use an internal date range in years from 1900 to 2156. ESE uses the JET_LOGTIME structure. Date/Time structures for ESE: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 – 2156.
Microsoft Exchange Information Store : Internally the Exchange Information Store stores year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2-digit year in those cases where other components hand the information store an Internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan. 1, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the 2 digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the information store has to do the year 2000 conversion and supports a range of 1986 – 2050. (Abbreviated years 86-99 = 1986-1999 and 00-50 = 2000-2050 as discussed above.)
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The dates used for the headers are 4 digits, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits CDONTS has to do the year 2000 conversion and supports a range of 1937 – 2038. (37-99 = 1936-1999 and 00-38 = 2000-2038)
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI use a 64-bit FILETIME. CDO or MAPI compliant applications that pass a correct 4-digit date will be stored correctly within Exchange. The internal date range in years for Exchange is from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): Dates stored internally within OWA are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of OWA is January 1, 1970 through January 19, 2038. The 4-digit dates are used throughout and passed back and forth through ASP and CDO. The user interface in OWA allows the users to enter the year for a date in 2 digits. When these dates are entered, OWA has a centralized JavaScript routine that normalizes the 2-digit years into 4-digit years for internal storage. The algorithm used to normalize the dates is as follows: if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA, other 2-digit numbers that are entered through the user interface within the range 39-69 result in an error message that alerts the user and the field reverts back to its last known recognized 4-digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, OWA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange Message Transfer Agent is a X.400 standard Message Transfer Agent. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems Message Transfer Agent converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Message Transfer Agent uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2-digit dates the Message Transfer Agent converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards, which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte integer counting the number of seconds since January 1, 1970. Thus the date range of DSA is January 1, 1970 through January 15, 2038. Exchange uses a 4-byte field that counts the number of seconds from 1/1/1970. The highest number that Exchange holds results in a maximum date of 1/19/2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99. However, due to X.500 standards that only support 2 digits, the DSA converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in 2 digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (2-digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to Internet and X.400 standards that only support 2 digits, the Administrator program converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The Microsoft Exchange Key Management Server explicitly uses 4 digits to represent years for storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours, the year digits as part of the date are not used. Encryption coding was tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The Microsoft Exchange Internet Mail Service stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the Internet Mail Service, are handled by IMAIL and the MDB. RFC 822 messages store date formats with 2-digits representing the year. See MDB for more information. When the IMC is setup as a connector it reads information from the GWART. See Message Transfer Agent for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to Internet standards that only support 2 digits, the Microsoft Exchange Internet Mail Service converts the date to 4 digits and supports a range of 1970 – 2038.
Microsoft Exchange Chat Server: The Chat Server only calculates time based on tick counts for real-time collaboration that does not span across a year period. When dates are stored, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits.
Microsoft Mail Connector Interchange (MSMI): Dates going to Exchange via Microsoft Mail Connector Interchange in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING, which is a string presentation of the ASN.1 UTC time syntax used by the Message Transfer Agent. UTC time is a 2-digit year and thus the Message Transfer Agent interprets the date into a 4-digit year. See the Message Transfer Agent for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99. However, due to X.400 standards that only support 2 digits, MSMI converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits, passed from cc:Mail, are the difference from 1900 (as defined by cc:Mail), which works only for 19xx years . When the Microsoft Exchange Server receives the dates, a conversion is done using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate results in expected behavior. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to cc:Mail only supporting 2 digits CCMC converts the date to four digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049.
Microsoft Exchange Connector for Lotus Notes: Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from Notes are mapped to/from the Notes date format; this is a 4-digit year format and is unambiguous. Date/Time structures Notes Connector uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055.
Microsoft Exchange SNADS Connector (SNADS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Dates going to/from SNADS are mapped to/from the SNADS date format; this is a 4-digit year format and is unambiguous. Date/Time structures SNADS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange IBM OfficeVision/Virtual Machine Connector (PROFS): Dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. PROFS uses 2-digit year format. The PROFS connector converts this to and from the 2-digit year format using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures PROFS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. However, due to PROFS only supporting 2 digits, the PROFS connector converts the date to 4 digits using the 1950 rule. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. CCMS supports a range of 1970 – 2038.
Microsoft Exchange MIGRATION Dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. cc:Mail DB8: If the year number is greater than 60 then add 1900. If the year passed in is less than or equal to 60 then add 2000. Example: 10 is passed in for the year 2010. Collabra: Add 1980 to the year that is passed in from Collabra. Example: 30 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Notes: The year is passed in as 4 digits from Notes. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Also tested in Exchange 5.5 Service Pack 2: Microsoft Exchange InterOrg Replication Utility Microsoft Exchange InterOrg Move Server Utility Microsoft Exchange InterOrg Mailbox Cleanup Utility Two-digit shortcut handling: There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these cases, dates with the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Common date usage errors: Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure our customers of the compliance of the non-Microsoft receiving environment or the reliability of the date data being based to Microsoft Exchange Server. Testing guidelines and recommendations: Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use applications that may have been written to use the Exchange environment. These are workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Korean)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Norwegian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Polish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Portuguese (Brazil))
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Portuguese)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Russian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Spanish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Swedish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 5.5 (Turkish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Chinese - Simplified)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Chinese - Traditional)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Czech)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Danish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Dutch)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (English)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or Windows NT 3.51 Service Pack 5 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (French)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or Windows NT 3.51 Service Pack 5 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (German)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT Service Pack 4.0 (see Note 1) or Windows 3.51 Serrvice Pack 5 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Greek)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Hungarian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Italian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Japanese)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or Windows 3.51 Service Pack 5 (see note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Korean)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Norwegian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Polish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Portuguese)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Russian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Spanish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Swedish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 4.0 (Turkish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Chinese - Simplified)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Chinese - Traditional)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Czech)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Danish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Dutch)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (English)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Standard 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19th, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Finnish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (French)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Standard 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19th, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (German)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Standard 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19th, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Greek)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Hungarian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Italian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Japanese)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 5.0 SP2 and current hot fixes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NT System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Exchange Server-Standard 5.0 Service Pack 2 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.Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This includes Windows NT Server Service Pack 3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and the way they work together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition or that can be purchased separately or the individual components that can be added to the Exchange Standard edition. In this document all components combined together are referred to as Exchange. There are individual components that may be called out to give more details of how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange Server 5.0 is year 2000 compliant when using it with Exchange 5.0 SP2 and the current hot fixes. ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/
How the product handles dates: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database: Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store : Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information storeaccepts a 2 digit year in those cases where other components hand the information store an internet standard RFC 822 message. In this case the the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, it will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the information store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Collaboration Data Objects for Windows NT (CDONTS): CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2-digits to represent the year within the date header information. All date properties exposed by CDONTS are read only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the OS system clock. The date used for the headers are 4 digits and year 2000 compliant, but the RFC 822 message headers only use the last 2 digits for the year date. Date/Time structures CDONTS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits CDONTS has to do the correct year 2000 conversion and supports a range of 1900 – 2038.
Collaboration Data Objects (CDO) and MAPI: CDO and MAPI uses a 64-bit FILETIME. Any CDO or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Outlook Web Access (OWA): All dates stored internally within OWA are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of OWA is January 1st, 1970 through January 19th, 2038. The 4 digit dates are used through out and passed back and forth through ASP and CDO. The UI in OWA allows the users to enter the year for a date in 2 digits. When these date are entered OWA has a centralized JavaScript routine that normalizes the 2 digit years into 4 digit years for internal storage. The algorithm used to normalize the dates is if the year entered is in the range 70-99, the year will be converted to 1970-1999. If the year entered is in the range 00-38, it is converted to 2000-2038. In the case of OWA all other 2 digit numbers that are entered through the UI within the range 39-69 result in an error that alerts the user and the field reverts back to its last known recognized 4 digit value. Date/Time structures OWA uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits, OWA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4 byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however, due to internet and X.400 standards that only support 2 digits, the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant.
Microsoft Exchange Internet Mail Service (IMS): The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMS, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2-digits representing the year. See Microsoft Exchange information store for more information. When the IMC is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMS uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2 digits the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMIin the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Connector for Lotus cc:Mail (CCMC): All dates going to/from Exchange in the content of a message are mapped to/from MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. All dates going to/from cc:Mail use the cc:Mail IMPORT/EXPORT format. This is a 2-digit year format. Currently CCMC does assume that the 2-digits are a delta from 1900 which is incorrect. In testing conducted by Microsoft, cc:Mail and Exchange inter-operate correctly. Date/Time structures CCMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055, however due to cc:Mail only supporting 2 digits CCMC has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Migration All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2 digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. GroupWise: The year is passed in as 4 digits from GroupWise. Example: 2010 is passed directly to Migration. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2 digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion?
Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any two-digit dates received from and/or expected by those non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the non-Microsoft environment, however Microsoft can not assure our customers of the compliance of the non- Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Korean)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Norwegian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Polish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Portuguese (Brazil))
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Portuguese)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Russian)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Spanish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Swedish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.0 (Turkish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Standard 5.5 (Chinese - Simplified)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Itemized List of products in each Volume
|
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA. ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
||
|
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.  | ||