Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

May 19, 2004 12:00 AM

Q. I have an Exchange Server 2003 server that runs on Windows Server 2003 and has more than 1GB of memory. What settings should I add to the boot.ini file to optimize virtual-memory usage?

Windows IT Pro
InstantDoc ID #42688
Rating: (6)

A. On pre-Windows 2003 systems that have more than 1GB of memory, it was common to add the /3GB setting to the boot.ini file to optimize Exchange Information Store virtual memory usage. On a Windows 2003 system, you must specify an additional setting in boot.ini: /USERVA=3030. The /USERVA=3030 setting splits the virtual memory allocation between user mode and kernel mode. This memory allocation lets Exchange allocate an additional 40MB of memory to the kernel for page table entries, which improves an Exchange 2003 server's scalability. The following sample boot.ini entry shows the use of the /3GB and /USERVA=3030 settings:

multi(0)disk(0)rdisk(0)partition(1)
\WINDOWS="Microsoft Windows Server 2003"/fastdetect
/3GB /USERVA=3030

(The listing is shown on three lines because of space constraints.)

Related Content:

ARTICLE TOOLS

Comments
  • CATHERINE
    7 years ago
    Jul 18, 2005

    Please reading the following update , very important.

    http://bink.nu/Article4438.bink

  • Anonymous User
    7 years ago
    Jul 11, 2005

    /3GB
    Increases the size of the user process address space from 2 GB to 3 GB (and therefore reduces the size of system space from 2 GB to 1 GB). Giving virtual-memory- intensive applications such as database servers a larger address space can improve their performance. For an application to take advantage of this feature, however, two additional conditions must be met: the system must be running Windows XP, Windows Server 2003, Windows NT 4 Enterprise Edition, Windows 2000 Advanced Server or Datacenter Server and the application .exe must be flagged as a 3-GB-aware application. Applies to 32-bit systems only

  • Anonymous User
    7 years ago
    Jan 22, 2005

    PAE is a physical extension and has nothing to do with virtual memory. To address issues with VM fragmentation if you are running Win2k advanced or datacenter you can use /3GB switch, if you are running standard your best bet is reducing the RAM to around 1 GB and implementing tewaks per follwing KBs. 325044 How to troubleshoot virtual memory fragmentation in Exchange Server 2003
    http://support.microsoft.com/?id=325044
    317411 How to gather data to troubleshoot Exchange virtual memory issues
    http://support.microsoft.com/?id=317411
    317411 How to gather data to troubleshoot Exchange virtual memory issues
    http://support.microsoft.com/?id=317411
    315407 XADM: The "HeapDecommitFreeBlockThreshold" Registry Key
    http://support.microsoft.com/?id=315407

  • Anonymous User
    7 years ago
    Jan 22, 2005

    Exchange and PAE is not a good idea. Exchange is not built to understand anything over 4GB. The /PAE (Physical Addressing Extensions) switch is a parameter that is set in Boot.ini. The /PAE switch enables a computer to access more than 4 GB of physical memory (RAM). Exchange Server cannot use more than 4 GB of physical memory, and there is no benefit to installing more than 4 GB of RAM on a computer that is dedicated to running Exchange Server. This switch may have been incorrectly set an OEM Setup program.
    If the server is running another memory-intensive application (such as SQL Server 2000), this switch may have been intentionally set by an administrator to use more than 4 GB of RAM. If you are running multiple applications that require the additional memory, you can run a Windows hotfix that will help prevent Exchange store failures that might occur when there is more than 4 GB of RAM available. Note that the recommended best practice is to dedicate a computer to run Exchange Server only. For more information about the hotfix, see Microsoft Knowledge Base article 834628, "Data is corrupted when PAE is enabled on a Windows Server 2003-based computer" ().If the computer where this warning was generated is a dedicated Exchange Server computer, remove this switch from the Boot.ini file.

  • Philippe GODINHO
    8 years ago
    Jun 02, 2004

    Can I use this settings on Windows 2000 Server with Exchange 2000 Server ?
    Because, I have some problem with Virtual Memory Fragmentation.

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.