In Exchange 2010 Beta is client throttling is __introduced. With client throttling policy you are able to limit the bandwidth used per user. Besides this, you are able to keep an eye on the resources consumed per user.
It’s time for the 3rd article about Exchange 2010 Beta, in this article we will have a closer look Outlook Web Access Mailbox Policies. In Exchange 2007 configuring which features you want to activate in OWA could only be done per user or global on the OWA itself, in Exchange 2010 Beta there’s a new features called: Outlook Web Access Mailbox Policies. With this policies you can deactivate items for users. When selecting the CAS server under the Organization Configuration you will see two tabs instead of one tab, just as in Exchange 2007.
In Exchange 2007 you could only enable most of the logging via Powershell. In Exchange 2010 Beta this has changed back to configuring it via the GUI just as in Exchange 2003.
Enabling the logging can be done via a simple press on the button and specifying the correct log and level of logging.
Exchange 2010 beta has been released for several days and of course I have installed it myself. The coming weeks I will publish several articles about the changes in Exchange 2010 Beta. Ofcourse it is a beta so it could be that some features will not be available in the final version.
During one of my forum visits I found a really interesting issue. Someone tried to remove his old Exchange 2003 cluster but received the following error when trying to dit it:
Organizational forms were used in Exchange 2003 by several applications and were very easy to implement. In Exchange 2007 this is a bit more complicated to configure organizational forms.
When starting to troubleshoot smtp issues you can do this easily via telnet, below a hosrt description on how to perform the test:
Via one of my colleagues I received a pretty nice site with an overview of all ports used for communication between the Exchange 2007 server roles. Below the overview:
Virusscanners may not have the result you wanted always, especially on databases and log files they can cause strange issues. Below an overview of folders you will need to exclude from virusscanning when a virusscanner is running on your Exchange 2007 server:
