Ubuntu – Evolution Error MAPI_E_LOGON_FAILED
KB ID 0000375 Problem Seen when trying to connect the Evolution mail client to a Microsoft Exchange server (via evolution-mapi). As soon as you hit authenticate you will see the following error. Authentication failed. MapiLogonProvider:MAPI_E_LOGON_FAILED Solution In my case it was a very quick fix, instead of using the DNS/Netbios name of the Exchange server put in the servers IP address. If all else fails, and you cannot rectify...
Exchange Mailbox Move Error”Property expression isn’t valid”
KB ID 0000238 Problem Seen when attempting to move a mailbox. Error: Property expression “username” isn’t valid. Valid values are: Strings that include ‘@’ where ‘@’ cannot be the last character During the move. When the move process has finished. Note: If your error says “Property expression “username” isn’t valid. Valid values are: Strings formed with characters from...
Is Exchange 2010 Supported on VMware?
KB ID 0000333 Problem At time of writing (30/09/10) it seems I cant get a definitive answer! My colleague tried to log a third line support call with Microsoft this week, as soon as they found out that Exchange 2010 was running in a VMware environment, they (literally) hung up on him. Solution Well Microsoft’s own documentation says it IS Reference: Fair enough Exchange 2010 is supported on a “Third party Hypervisor ONLY...
Connecting Evolution Mail Client to Exchange 2010 (and Exchange 2007)
KB ID 0000378 Problem Out of the box Evolution can only connect to Exchange 2000 and Exchange 2003, this is because it uses OWA to connect, when Exchange 2007 was released, the way OWA was presented changed a great deal. So if you try and connect to a newer version of Exchange it will error. (Before you email in, I know in 2010, its now called Web App not OWA). But there’s nothing to stop you connecting to Exchange 2007 and...
Exchange 2010 (c/w SP1) Install – Greenfield Site
(Installing on Server 2008 R2) KB ID 0000416 Problem Microsoft have not only slipstreamed the service pack into the install media, they have (Finally!) got the install routine to put in all the usual pre-requisites, roles, and features, that you had to do yourself before. (With the exception of the Microsoft 2010 filter pack, but even then you can do that after the install). The procedure below was done on a single server in a test...