MSGINA.DLL driver update available
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2006-08-21
The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine the version of Microsoft Windows® running on the server that is running Exchange Server:
A CurrentVersion value of 4.0 indicates that the Exchange server is running Microsoft Windows NT® Server 4.0. A value of 5.0 indicates that the Exchange server is running Windows 2000 Server. A value of 5.2 indicates that the Exchange server is running Windows Server™ 2003.
The Exchange Server Analyzer also examines the Win32_OperatingSystem Microsoft Windows Management Instrumentation (WMI) class to determine the value for the ServicePackMajorVersion key.
A ServicePackMajorVersion key value of 1 indicates the server has Service Pack 1 (SP1) installed.
Finally, the Exchange Server Analyzer queries the CIM_Datafile WMI class to determine the value of the Version key for the Msgina.dll file.
The Exchange Server Analyzer displays an error if the following conditions are true:
The server is running Windows Server™ 2003 SP1.
The build number of the Msgina.dll file is less than 5.2.3790.2525.
This error indicates that the version of Msgina.dll installed on the server may cause excessive page file activity and a decrease in performance.
To resolve this problem, obtain the update referenced in Microsoft Knowledge Base article 905865, "The sizes of the working sets of all the processes in a console session may be trimmed when you use Terminal Services to log on to or log off from a computer that is running Windows Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=905865).