Microsoft Exchange and Active Directory Blog
Exchange 2013 is already available to MSDN subscribers for download. However, it is not yet possible to migrate from previous Exchange versions. Service Pack 3 for Exchange 2010 and an update rollup for Exchange 2007 SP3 (announced for the first quarter of 2013) are still missing. A direct migration from Exchange 2003 will not be possible. ... Read more
Although it is an "old" tool, it also works quite well under Exchange 2010, although there are a few limitations (it does not check the web-based publication of the OAB). Nevertheless useful to check the creation process of the OAB and especially to compare the OAB against the Active Directory. OABINTEG can be downloaded here ... Read more
A script for detecting Active Sync problems has been published on the Exchange Team Blog. Troubleshooting Active Sync problems is a tedious task. This script can help, have a look at it: http://blogs.technet.com/b/exchange/archive/2012/01/31/a-script-to-troubleshoot-issues-with-exchange-activesync.aspx
Microsoft has published a document which describes the Exchange schema extensions to the Active Directory. The Word document (packaged in an MSI file) can be downloaded here. The document also shows that Exchange Server 2010 Service Pack 2 makes changes to the schema. The document contains the schema changes for Exchange Server 2003, 2007 and 2010. http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5401
More and more companies now want to migrate to Exchange 2010. In my opinion, the most common case is the migration from Exchange 2003 to Exchange 2010. Exchange 2007 was left out by many companies. In this article I describe how Exchange 2003 is migrated to Exchange 2010. The test environment FWDC01 is a Windows Server 2003 R2, this server ... Read more
When migrating from Exchange 2003 to Exchange 2010, the e-mail address policies must be converted to the current Exchange version so that they can be edited from the Exchange 2010 Management Console. If the policies have not yet been converted, you will receive this error message "The specified email address policy could not be edited. Email address policies that were created with a previous version ... Read more
In some cases, Exchange is not to blame if something does not work. Problems also occur on the client. Finding these is not always easy, as there are often many different programs installed on the client. Plug-ins or other software can affect communication with Exchange, but often there is nothing to be found in the event logs. ... Read more
If you want to quickly find out the Exchange version in use, you can compare the build numbers and version numbers with the table here: http://social.technet.microsoft.com/wiki/contents/articles/exchange-server-and-update-rollups-builds-numbers.aspx This allows you to quickly find out the patch level and the service pack version in use.
Here is a list of the maximum database sizes for the various Exchange versions. Starting with Exchange 2003 up to the current version Exchange 2010. Exchange version Maximum database size Exchange 2003 16 GB Exchange 2003 Service Pack 2 75 GB (see below) Exchange 2007 250 GB Exchange 2010 2 TB The information refers to a single ... Read more
A white paper on Jetstress has been published in the Exchange Team Blog. The document describes how Jetstress can be used to determine and test the performance of mailbox servers. In my opinion, the white paper is well worth reading and contains useful information about the Jetstress tool. Here is the link to the document: http://msexchangeteam.com/files/12/attachments/entry456925.aspx
