Exchange 2010 SP1 beta: install and configure UM role

In Exchange 2010 SP1 beta you will find a lot of changes. In this tutorial I will have a closer look at the Unified Messaging Role from Exchange 2010 SP1. 

MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

During a migration of a mailbox from one forest to a new Exchange Forest I encountered the following problem:

Exchange 2007 Service Pack 3: changing your password

One of the new features in Exchange 2007 Service Pack 3 is the ability for users to change their password before logging in. Before service pack 3 a user who’s password had expired needed to call the helpdesk to reset their password or use another solution. With this new feature a user will be redirected to another page where he/she can change the password.

MapiExceptionInvalidParameter: Unable to set properties on object. (hr=0x80070057, ec=-2147024809)

During a cross-forest migration from Exchange 2003 to Exchange 2010 I found a nasty issue while migration a mailbox. The first 10% of the move request went OK but after that it failed. In the first 10% the mailbox is created, the folder structure is created and permissions are set on the folders.

MapiExceptionNotFound: Unable to delete mailbox

During a cross-forest test migration from Exchange 2003 to Exchange 2010 I got the following error:

Open another users calender via OWA

Opening a calender from another user using OWA is not a very hard proces, when you have enough permissions you can easily open the other users calender. But what if you would like to do this via OWA?  This depends on the Exchange version you are using, let’s start with Exchange 2003:

Microsoft releases security updates for Exchange

Microsoft has released security updates for Exchange 2000 SP3, Exchange 2003 SP2, Exchange 2007 SP1/SP2 and Exchange 2010. For both Exchange 2007 and 2010 this security fix is  included in a rollup. For Exchange 2007 SP1 this is the 10th rollup, for Exchange 2007 the 4th and for Exchange 2010 the 3rd.

Get-owavirtualdirectory does not return all CAS servers

By accident I found a bug in Exchange 2010. The issue only occurs in Exchange 2010 and if you have multiple CAS servers which are located in different sites and can’t communicate to eachother. Till now I only saw the issue with Exchange 2010 where an extra CAS server was added to the mainoffice. In this case this is the 3rd CAS server in the Exchange 2010 environment

Move-mailbox fails with strange error

During the conversion of a pilot to production environment I found a nice issue. The mailboxes needed to be moved from the old mailbox server to the new mailbox server. Normally not a very exciting proces which can be done both by using the Exchange Management Console as Exchange Management Shell. But the move from the old Exchange 2010 mailbox server to the new Exchange 2010 mailbox server failed with a strange error. So first I had a look in the event log of the server and found the following error:

Why the use of PST, OST and PAB files is unsupported over LAN/WAN Links

Sometimes you may have the discussion if it is supported to place these files on fileserver so they can be accessed via a LAN/WAN connection. The answer for this is no, it isn’t officially supported by Microsoft. But when you will try it in your environment it will work, so what are the reasons it isn’t supported?