With Exchange 5.5 you would normally run Performance Optimizer during the last phase of an installation. After this is done, Performance Optimizer is rarely heard of again. As we know, Performance Optimizer allows you to configure the Exchange Server memory usage, resource allocation, public information store options and database paths. Resources for both the Exchange Server system's hardware and user-configured options are automatically configured. Therefore, apart from running an offline defrag, it is recommended running the Performance Optimizer:
- After every new installation or upgrade.
- After adding components to a server, such as connectors.
- When hardware changes are made such as adding RAM or changing hard disk configurations
You may also want to run Performance Optimizer when mailbox activity or the number of users significantly changes. For example, if you were to remove a couple of mailboxes with varying sizes you will then perform an offline defrag to reclaim hard disk space. Running Performance Optimizer afterwards not only ensures that the databases paths are set properly but also improves the overall health of the Exchange Server. Please note that when running the Performance Optimizer all services will be stopped, therefore users will not be able to access the Exchange server. If you are not sure when you last ran Performance Optimizer, perform the following:
Go to C:WINNTSystem32.
Open the Perfopt.log using notepad.
The information in this log file will tell you time and date Performance Optimizer last ran.
Adesh Rampat has 10 years experience with network and IT administration. He is a member of the Association Of Internet Professionals, the Institute For Network Professionals, and the International Webmasters Association. He has also lectured extensively on a variety of topics.
