Exchange Server 2003 relies on a complex but detailed and strict access control hierarchy. This means that you as an administrator have to check whether any users will have any access to the Exchange Organization itself.
Effective troubleshooting requires knowledge of the processes taking place. By knowing the process taken when a user attempts to logon, troubleshooting Outlook Web Access (OWA) logon issues becomes a whole lot easier.
In my previous article we had a closer look at the new Sender ID feature included in Exchange 2003 SP2, in this article I’ll show you how to configure and take advantage of the new database size limit increase in Exchange 2003 SP2.
We would like to welcome Rodney Buike to our team of authors as he presents his first article to MSExchange.org readers. The Information Store is the heart and soul of Exchange Server 2000 and 2003. Understanding the fundamentals of the Information Store is important for anyone managing an Exchange server.
In the last 2 parts or this article series I covered the process of sizing the hardware for an Exchange Server. Now it’s time to validate the results, using some stressing tools and monitor software. You’ll also be glad to know that there are some tools that really can help and ease the sizing process.
Featured Links*
Receive all the latest articles by email!
Receive Real-Time & Monthly MSExchange.org article updates in your mailbox. Enter your email below! Click for Real-Time sample & Monthly sample
Become an MSExchange.org member!
Discuss your Exchange Server issues with thousands of other Exchange experts. Click here to join!