Yeah leave /3GB switch its actually recommened by MS.
Other Memory optimizations for exchange 2003
http://www.msexchange.
Hi,
I recently upgraded our IBM XSeries 346 running Windows Exchange Server 2003 SP with extra RAM as it was performing poorly. We have over 500 mailboxes, users frequently send large attachments and our mail store is about 42GB! We previously had 2GB of PC-3200 installed but i repaced it with 4GB or PC5300.
We currently have a 2GB page file. The previous boot.ini file included the following switches
/noexecute=optout /fastdetect /3GB /USERVA=303
I had added the /3GB /USERVA=3030 switches a few weeks ago but they didn't improve performance. We had a very large page file and I noticed that % Disk Time and also Current Disk Queue Length would climb very high at peak times. I also reduced the page file to 2GB(equaling the physical memory size of 2 GB).
Since I have added 4GB of RAM tonight, I noticed BIOS recognized 4096MB RAM but Windows only recognized 3.25GB of RAM as I would expect. I did some research and confirmed that in normal operation 32-bit operating system will only address 3.2GB max.
I added the switch to the boot.ini to force the server address 4GB /PAE, rebooted and and sure enough it found the 4GB! Happy days.
The current switches now as of tonight are as follows
/noexecute=optout /fastdetect /3GB /USERVA=3030 /PAE
I'm wondering what experienced exchange users would recommend setting the page file for this setup to (currently 2GB) ?
Also would you recommend keeping the /3GB /USERVA=3030 switches?
Thanks,
Paddy
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yeah leave /3GB switch its actually recommened by MS.
Other Memory optimizations for exchange 2003
http://www.msexchange.
The current switches now as of tonight are as follows /noexecute=optout /fastdetect /3GB /USERVA=3030 /PAE - This is good ....
To check if Exchange would run fine or not run the
EXBPA - www.exbpa.com ----- very important as many Admins run this once 2 weeks or a month to keep a check that Exchange is not having any issues after any changes in AD or DNS or anywhere :) :)
This would check the Exchange and configuration that Exchange and other Role server should have for better performance .....
Check the error and take care of them and all should be good ????
The additional RAM likely won't help a lot with Exchange specfically, as Exchange 2003 cannot take advantage of RAM above 4GB anyway. I found this out from the Exchange Best Practices Analyzer mentioned by Rancy.
Disk configuration also plays a part. Ideally, the server should have this configuration if possible:
Hi all,
Thanks for your feedback and help. unfortunately since last nights changes exchange is running as slow as ever, even after the memory upgrade.
% Disk Time is still really hight. I have run the best practice analyzer tool and that has recommended two registry changes in particular which im hopeful will make the difference.
First recommendation was to set the SystemPages registry entry to 0 which I have done.
I have also set msExchESEParamLogBuffers to 9000. I will not know how these affect performance until a I reboot which I will do tonight so hopefully they will make the difference.
Any body have any other ideas or what else should i be looking at?
Hi Rancy,
The top 5 processes are store.exe(1026MB), inetinfo.exe(40MB), mad.exe(28MB), svchost.exe(27MB) and uptmagnt.exe(26MB).
We are running Exchange Standard Edition SP2. We have one mail store which come to 41GB in size.
We are running 3 applications on the Email server, a HR app, a payroll app and a recruitment app.
I have disabled the Symantec AV but unfortunately still no joy.
To give you some further background on the issue. This issue first appeared 6 weeks ago when one of the help desk staff accidentally installed MS Office 2007 on Exchange. This caused a MAPI issue. We were only running SP 1 on the machine, so instead of re-install SP1 we upgraded to SP2. Which appeared to fix the MAPI issue. The exchange server itself though still runs chronically slow. Is there many server settings that should change solely because of an upgrade to SP2?
I have attached a screenshot which shows some counters which I'm hoping will be useful in resolving the issue
I have been working on the premise that this is a virtual memory issue which is bottlenecking when reading/writing to physical disk.The slowness users experience when using the hosted apps or email seems to correlate exactly to when the %Disk Time goes above 100. As you can see from the screenshot it regularly goes far above 100. Could it simply be a issue with the RAID performance or one or more of the hard disks? Anybody any ideas on how I can ascertain this and measure it?
Thanks,
You also show give the Exchange Best Practices Analyzer a whirl on your mail server. You can find it here: http://www.microsoft.com/d
Business Accounts
Answer for Membership
by: Raheem05Posted on 2009-11-04 at 18:47:46ID: 25746331
Please review the below regarding page file for exchange servers
smwhelan/a rchive/200 6/12/12/ ex change-200 3-and-conf iguring-th e-page-fil e.aspx
Exchange 2003 and configuring the page file
This question has come up in the last hour or so with one of my customers and I thought it was worth mentioning as a reminder.
The recommend page file size for an Exchange server is 1.5x memory up to a maximum size of 4095Mb. For example, if you have 1Gb RAM, we would recommend a page file size of 1.5Gb.
If you have the maximum RAM that Exchange can utilize (4Gb), the page file size should be 6Gb. As we have a limitation on the page file size, you will need to create a second page file on a different volume.
From a performance perspective, it is recommend to have each page file on a seperate physical volume.
http://blogs.msdn.com/jame