This failover allows services to remain available to users.īy maintaining service availability in the case of a failure, clustering gives you time to diagnose and fix the problem. When a single server fails, clustering moves Exchange 2003 resources from the failed server to another server in the cluster. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SystemPagesįor additional information about the /Userva switch, see Microsoft Knowledge Base Article "XADM: Using the /Userva Switch on Windows 2003 Server-Based Exchange Servers" ( /?kbid=810371).Ĭlustering provides a mechanism for moving resources between cluster nodes when problems occur. The location of the SystemPages registry key is as follows: If the server is running Windows 2000, set the SystemPages registry key to a value between 2400. These settings allow for more system page table entries on the server, which is critical for scale-up systems.
#R1soft exchange public folder windows#
If the server is running Windows Server 2003, set the SystemPages value to zero, and set the /Userva=3030 parameter in the Boot. Do not set the /3GB switch if you are running Windows 2000 Server. Important The /3GB switch is designed for all editions of Windows Server 2003 and for Windows 2000 Advanced Server. ini file to increase the virtual address space.įor more information about the /3GB switch, see Microsoft Knowledge Base Article "XGEN: Exchange 2000 Requires /3GB Switch with More Than 1 Gigabyte of Physical RAM" ( /?kbid=266096). If a server has 1 GB or more of physical memory, set the /3GB switch in the Boot. For information about the settings that must be removed, see "Removing Exchange 2000 Tuning Parameters" in the book Exchange Server 2003 Deployment Guide (Setting the /3GB Switchīy default, Windows Server 2003 and Windows 2000 Advanced Server allocate 2 GB of virtual address space to user mode processes, such as the Exchange store process (Store.
#R1soft exchange public folder manual#
If you have since upgraded that server to run Exchange 2003, that server no longer needs those manual tuning changes, and you should manually remove them from the server. If a server in your cluster previously ran Exchange 2000, you may have performed the manual tuning changes that were recommended by previous Exchange documentation.
In fact, Exchange 2003 performs most necessary tuning automatically. Exchange 2003 requires much less manual tuning than Exchange 2000. In the Extended Logging Properties dialog box, on the General Properties tab, in Log file directory, change the SMTP log file location to a folder on a shared disk.Įven with thoughtful management and attentive monitoring, it may become necessary to tune the servers in your clusters to maintain high availability. In the Default SMTP Virtual Server Properties dialog box, on the General tab, click Enable logging, and then click Properties.ĥ. In the console tree, right-click Default SMTP Virtual Server, and then click Properties.Ĥ. In the console tree, expand Protocols, and then expand SMTP.ģ. In Exchange System Manager, in the console tree, expand Servers, and then expand the server on which you want to enable IIS logging for SMTP.Ģ. To enable SMTP logging and log the files to a shared diskġ. To reliably configure SMTP logging in a clustered environment, you need to change the default location of the log files (that is, the local computer) to a folder on a shared disk. When enabled, Internet Information Services (IIS) creates SMTP log files on the system drive of the local computer (for example, C:\Winnt\System32\Logfiles, where C is the location of your Windows Server 2003 or Windows 2000 installation). Unless you are troubleshooting or in need of statistical data, you should disable logging (the default setting). However, be aware that enabling SMTP logging reduces Exchange performance. If you want to gather statistical data about server usage, you can enable logging of the SMTP resource. In the Default Microsoft Exchange Services dialog box, select Microsoft Exchange MTA Stacks, and then click Remove. On the Monitoring tab, select Default Microsoft Exchange Services from the list of services, and then click Details.Ĥ. In the Properties dialog box, click the Monitoring tab.ģ.
In Exchange System Manager, in the console tree, expand Servers, right-click the appropriate Exchange Virtual Server, and then click Properties.Ģ. To disable MTA monitoring on an Exchange Virtual Serverġ.
0 kommentar(er)
