Introduction
Exchange 2003 requires specific memory tuning to function optimally. This flash outlines Windows 2003 boot.ini configuration settings for Exchange 2003 and highlights recent changes...
Updated Jul 01, 2019
Version 2.0
Blog Post
Item #1, basicially we don't need to worry about using /PAE or /NOPAE anymore, if the motherboard can use it, the system turns it on, otherwise, just leave it alone.
Item #2, I did find an issue and reported it to MS that Windows 2003 SP1 with DEP/PAE enabled on an Cluster, the Exchange SMTP services didn't function correctly. On one node the server wouldn't start, on the other node the service couldn't stop. Once I replaced the /noexecute switch with /Execute, service returned to normal. /Execute btw, is the only way to shut off both PAE and DEP.
Item #3, I found changing the userva to 2970 didn't improve my free PTE's any on my clustered Exchange servers which are varying between 3800 and 5100. and these boxes are tuned to the max, and am wondering if PAE would help out. They all currently have the /NOPAE switch in, and we haven't gone to production with SP1 for Windows 2003.
Item #2, I did find an issue and reported it to MS that Windows 2003 SP1 with DEP/PAE enabled on an Cluster, the Exchange SMTP services didn't function correctly. On one node the server wouldn't start, on the other node the service couldn't stop. Once I replaced the /noexecute switch with /Execute, service returned to normal. /Execute btw, is the only way to shut off both PAE and DEP.
Item #3, I found changing the userva to 2970 didn't improve my free PTE's any on my clustered Exchange servers which are varying between 3800 and 5100. and these boxes are tuned to the max, and am wondering if PAE would help out. They all currently have the /NOPAE switch in, and we haven't gone to production with SP1 for Windows 2003.