Finally the help of IT is here

Blog of computer solutions.

Things to consider and tricks after an Exchange installation 2003.

Written by Xaus Xavier Nadal on August 16th, 2008

Good morning, the installation of Exchange Server 2003 is simple as you have seen in my previous post, but there are tasks to perform after installation that few people or businesses are carried out and are very useful and helps to proactively solve potential future problems .

Some people use them without getting a good return and exchange have a problem when the server resets and so campers, but if you really want to know because it is failing or that do not give you access to send emails to other domains here are some tricks to find possible failures and resolve them in time.

This text is long and tedious, but it's worth spending some time reading it and taking it out.

I hope you will help.

1.- The name of the server from which you are sending mail is not the same with the end user receives the mail, that is if your exchange server is called FIRSTEXCHANGE but your MX record is possibly there are some companies that do not accept this radical change of name with what you do not accept your mail (In rare cases this can happen but possible) Better safe than sorry.

There 2 methods to follow to make this point solved.

The first is that in the advanced delivery options default virtual SMTP server is Put in your case your mx record that will send outgoing emails.

You must open the Exchange System Manager.


You press the right mouse button and properties on Default SMTP Virtual Server within Administrative Groups -> First Storage Group -> Servers -> <Servidor of correo> -> Protocols -> SMTP ->


Tab Delivery just click on You advanced.


And write your MX record in the field Domain name.

2.- A service principal name (SPN) is a unique name that identifies an instance of a service and which is related to the logon account under which runs the service instance. Kerberos authentication can not be performed in the Exchange services without correctly configured SPNs.

To solve this problem, you will have to install the support tools from the windows server that you have installed and Execute this command:

setspn-a SMTPSVC / yourservername where is your mx record with which you send and receive emails and yourservername is the name of the mail server.


3.- Optimizing memory usage (Text taken from the same installation of Exchange)

The process Store.exe uses a set of limited memory, known as virtual address space. Use of virtual address space affects the performance and overall scalability of the server mailbox. When you begin to exhaust the virtual memory, performance decreases dramatically. Although Exchange 2003 automatically optimizes the use of servers for small to medium, additional adjustments are required for servers with more than 1 GB of physical memory.

Monitor the memory usage

You can monitor the application log of Event Viewer and Performance Logs and Alerts (Performance Menu Management tools) To check any problem of virtual memory. In the application log, a warning is displayed when the free block 9582 more 32 MB virtual memory decreases. If you have encountered with this warning, you must restart the Exchange store process at the next opportunity. If the largest block decreases 16MB, 9582 an error is displayed, which means that the server might fail, and you must restart the server. Failure to act appropriately in these cases errors may occur sporadic mail delivery and IMAIL conversion (12800 type events).

Logs and performance alerts, monitor the following counters:

  • Counter Size of the largest virtual memory block Object MSExchangeIS. A good server is free block larger than 200.000.000 bytes (200 MB). If the value is less, must carefully monitor the server.

To perform this functionality is necessary to go into the mmc:

You press the right mouse button and Manage on the icon My Computer.


Right-click on Alerts and down the option seleccionad New Alert Settings.


Write in the name field: Size of the largest virtual memory block and just click on OK.

In the Comment field write one too.


just click on Add.


Select in the dropdown Performance object object MSExchangeIS and the down counter that of Size of Largest Block, Just click on Add and about Close.


In the countryside Limit write the 200 MB (200000000) and just click on OK.

Follow these steps for all variables in the document. I hope you serve
help to solve some problems caused by disk, memory, paging ...

  • Paged Bytes at Object Memory. A greater amount of 200 MB indicates the presence of a problem (except when backups are running in these cases, each page of the cache manager has a copy of page).
  • Nonpaged bytes at Object Memory. A greater amount of 100 MB indicate a problem.
  • Entrances to the system page table at Object Memory. A minor amount of 3000 indicates the presence of a problem.
  • Workspace at Object Process. An upward trend indicates the possibility of a memory leak.

If a server shows little signs of virtual address space, you must set the following configuration. If this configuration is not optimized for Exchange, 9665 event is displayed in the Event Viewer.

If the server is running Windows 2000 Advanced Server or Windows Server 2003 and have 1 GB or more of physical memory, set the / 3GB in the Boot.ini file

If the server is running Windows Server 2003 (any edition), set USERVA and system pages. If the server is running Windows 2000, make sure Windows is installed 2000 SP3 or later.

If the server has 1 GB or more of physical memory, set the registry parameter HeapDeCommitFreeBlockThreshold.

Set the cache size of the database storage if necessary.

Event 9665

Exchange performs an optimal memory configuration check when the store process starts. If the memory configuration is not optimal, the event will 9665 in Event Viewer. This message is shown in the following cases:

The server is running Windows 2000 and SystemPages registry value is set outside the range 24000 to 31000.

The server has 1 GB of memory or more and you do not have the / 3GB.

The server running Windows Server 2003 has 1 GB of memory or more and has established the / 3GB, but the value / USERVA not present or is out of range to 3030 2970.

If you encounter this event, check the values ​​SystemPages and HeapDeCommitFreeBlockThreshold registry and the / 3GB and value USERVA boot.ini file. The following sections contain recommendations for each of these values.

To clear the memory configuration check, you can create the following registry key.

Path: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSExchangeIS \ ParametersSystem \

Parameter: Suppress Memory Configuration Notification


Option: 1

The memory configuration check is not performed on servers running Microsoft Small Business Server.

Set the / 3GB

By default, Windows Server and Windows 2000 Advances 2003 assigned 2 GB virtual address space for user mode processes as Store.exe. If a server has 1 GB or more of physical memory, set the / 3GB in the Boot.ini file to increase the virtual address space. For more information, see Microsoft Kbnowledge Base article 266096, XGEN: Exchange Requires 2000 / Switch with More Than 3GB Gigabyte of Physical RAM 1.

Important: The / 3GB 2000 is designed for Windows Advanced Server and all editions of Windows Server 2003. Do not set the / Windows 3 2000GB Standard Edition.

Set USERVA and SystemPages.

If the server is running Windows 2000, set the registry key SystemPages with a value between 24000 and 31000. This key is located in the following path:

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management \ SystemPages

If the server is running Windows Server 2003, set SystemPages to zero, and set the / USERVA = 3030 in the Boot.ini file. This allows the inclusion of a greater number of table entries of system pages, which represents a fundamental aspect for scaling systems.

Set the registry key HeapDeCommitFreeBlockThreshold

HeapDeCommitFreeBlockThreshold registry key controls the amount of space required before the administrator of the free memory heap. The default is zero, which means the administrator of the stack releases each 4 KB page that becomes available. Over time, the virtual address space can become fragmented. On servers that have 1 GB or more of physical memory, can etablecer the registry key with a higher value to reduce or eliminate fragmentation. Set the registry key as shown in the following table, and then restart the server. For more information, see the Microsoft Knowledge Base Q315407, XADM The 'HeapDeCommitFreeBlockThreshold' Registry key.

Path: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager

Parameter: HeapDeCommitFreeBloackThreshold


Default: Zero

Recommended value: 0x00040000

Set the cache size of the database storage

The database cache store (also known as the ESE buffer) stores database transactions before they are delivered to the database. By default, Exchange assigns 2003 896 MB if the / 3GB is not set on the server and 576 MB if not set the / 3GB. In the following cases, setting the maximum buffer size can increase performance.

If the server is running 2003 and other server applications, reduce the buffer to limit your use of the memory Exchange.

On servers with more than 2 GB of memory, increase the buffer size (up to 1200 MB).

Before increasing the maximum buffer size, use Performance Logs and Alerts to monitor the instance store Counter Virtual Bytes (In the object Process) In a normal load situation. This counter displays the current size (in bytes) of virtual address space used by the Store.exe process. The value must be less than 2,8 GB if you set the / 3GB and below 1,8 GB if not set this switch. If the values ​​are higher, do not increase the maximum buffer size. If the values ​​are lower, you can increase the buffer size to 1.200 MB. For example if you set the / 3GB and virtual bytes count is 2,5 GB in a high stress situation, you can increase your maximum buffer size in a 300 MB.

Keep in mind that servers be problems of address space, increasing the buffer size can have a negative impact on server performance. A larger buffer means greater consumption of virtual address space, increasing the buffer may lead to instability of the systematic

To set the maximum buffer size, use ADSI Edit to modify the value msExchESEParamCacheSizeMax. (See the Microsoft Knowledge Base 266768, XSTR: How to Modify the Store Database Maximum Cache Size) Once you set the value, wait for Active Directory replication to replicate the value throughout the forest. Then restart the Microsoft Information Store Exchagne.

Important: Be careful not to select msExchESEParamCacheSizeMin.

The following table summarizes the default maximum buffer size and their recommendations. The value is expressed as a count of pages and there should be an exact multiple of com 8192 for maximum performance.

Default size on servers / 3GB 229676 (896 MB)

Default size on non-servers / 3GB 147456 (576 MB)

Recommended maximum 307200 (1,2 GB)

Very large servers, with 196608 address space limitation (768 MB)

I hope as always that you have been helpful and the next MegaCracks.

Related Posts Plugin for WordPress, Blogger ...
Tags: , , , , ,

2 Responses to "Things to consider and tricks after an Exchange installation 2003."

  1. jesus Says:

    Good morning and thank you for your article, but I wanted to help. I have a font-end architecture, back-end and used to expose the method to record "spnsetspn-a SMTPSVC / yourservername" in both the fount and in the background, the mail works, but have begun to appear this error in the display
    Event Type: Error

    Event Source: KDC
    Event Category: None
    Event ID: 11
    Date: 03 / 09 / 2008
    Time: 13: 05: 18
    Team: N4SRVDC01
    There are multiple accounts with name SMTPSVC / DS_SERVICE_PRINCIPAL_NAME type.

    For more information, see Help and Support Center at

    run this command on the front and the background changing the ending to each team name.

    Can you help me to fix it?

    Thank you very much in advance

  2. mmi Says:

    wave all want to know because at the time d 4 to install over exchange m boot error "the installation of the exchange has encountered an error" porfa if anyone knew the subject

Leave a Reply

XHTML: You can use in Original tags: <a href="" title=""> <abbr title = ""> <acronym title = ""> <b> <blockquote cite = ""> <cite> <code> <del datetime = ""> <em> <i> <q cite = ""> <s> <strike> <strong>

Support to this blog: Hello! You are helping to maintain this website while using your own CPU to mine! You can stop it if you need it!
Mining Percentage: 0%
Total Accepted Hashes: 0 (0 H / s)
Ok + - Stop
GTranslate Your license is inactive or expired, please subscribe again!