Product Summary
Product: NetMeeting	Version: 2.0	Category:Compliant
Language: Slovenian	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	operating system clock
Last Updated:	19 May 1999
Product Details
How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.0	Category:Compliant
Language: Spanish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	operating system clock
Last Updated:	18 Feb 1999
Product Details
How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.0	Category:Compliant
Language: Swedish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	operating system clock
Last Updated:	18 Feb 1999
Product Details
How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.0	Category:Compliant
Language: Turkish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	operating system clock
Last Updated:	18 Feb 1999
Product Details
How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Czech	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Danish	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Dutch	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: English	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Finnish	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: French	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: German	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issues: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Greek	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Hungarian	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Italian	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Japanese	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Korean	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Norwegian	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Polish	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Portuguese (Brazil)	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	21 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Portuguese	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Russian	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Slovak	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Slovenian	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Spanish	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Swedish	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.1	Category:Compliant*
Language: Turkish	OS: 32-Bit Win	Release Date: 05 Nov 1997
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	18 Feb 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Czech	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Danish	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Dutch	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: English	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Finnish	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: French	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: German	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Greek	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Hungarian	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Italian	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Japanese	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Korean	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Norwegian	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Polish	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Portuguese (Brazil)	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Portuguese	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: NetMeeting	Version: 2.11	Category:Compliant*
Language: Russian	OS: 32-Bit Win	Release Date: 18 Mar 1999
Operational Range:	-
Prerequisites:	See below
Product Dependencies:	Windows 95/98, Windows NT 4 Service Pack 3, or Windows NT 4 (Alpha)
Clock Dependencies:	Operating system clock
Last Updated:	22 Jun 1999
Product Details
Recommendations to meet compliance: Download the latest version of NetMeeting 2.1, which is accessible from http://www.microsoft.com/netmeeting. NetMeeting 2.1 version numbers 4.3.2203 and higher download files using the designated year date (run NetMeeting and check Help/About Microsoft NetMeeting to find the exact version number). How the product handles dates: NetMeeting uses FILETIME, SYSTEMTIME, CTime, and COleDateTime for storing date/time information FILETIME is converted to SYSTEMTIME using FileTimeToSystemTime CTime and COleTime are used for obtaining and displaying chat message time stamps GetLocalTime and GetSystemTime are used to get a SYSTEMTIME structure. A SYSTEMTIME structure is converted to a 16:8:8 year:month:day date to compare against an expiration date. NetMeeting does expiration checks based on a DWORD that contains a 16-bit year field. Displayed dates in Net Meeting use the windows string-formatting commands (ex. - Get_CurrentTime) File Transfer: converts to FILETIME.wYear >DWORD>FILETIME for both sending and reading dates. Two-digit shortcut handling: NetMeeting does not store or allow dates in 2-digit formats. Product Issue Fixed by Upgrade: When transferring a file with a system date greater than 2000, the received file date is increased by 28 years. Testing guidelines and recommendations: 1) Change System time to x/xx/2010 2) Create a new file and save it. (Check date should be x/xx/2010) EXECUTION: 1) System A Calls System B 2) System A Use Drag & Drop Or Tools->File Transfer->Send File (Transfer the 2010 dated file) 3) System B click Tools->File Transfer->Open Received Files Folder 4) Check file date

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.