Get-Mailbox does not reflect the correct Server name for Mailboxes on databases for a DAG

We got notified from customers, that the powershell commandlet get-mailbox in Exchange 2010 (see http://technet.microsoft.com/en-us/library/bb123685(v=exchg.141).aspx) and in Exchange 2013 (see http://technet.microsoft.com/en-us/library/bb123685(v=exchg.150).aspx) do not always return the correct ServerName  or ServerLegacyDn for the given mailbox. Those customers often rely for their backups or customized mailbox processes on the information, on which server a given mailbox is currently located….


BRANCHCACHE for Exchange 2010 OAB Download How-To:

BRANCHCACHE for Exchange 2010 OAB Download How-To: Requirements for BranchCache Following is a list of operating systems that support BranchCache content server or BranchCache client computer functionality. To successfully deploy BranchCache in a test lab environment, you must use operating systems that support BranchCache. General Requirements to Server and Client Server and Clients must be…


How to link existing AD accounts to the correct organization in a Microsoft Exchange Server 2010 SP1 multi-tenant environment

With Microsoft Exchange Server 2010 SP1 there is a built-in multi-tenant support feature available that replaces many features of HMC. A good overview about the features, limitations, installation and configuration is available at Technet article: Multi-Tenant Support http://technet.microsoft.com/en-us/library/ff923272.aspx  The hosting solution available for Exchange 2010 SP1 includes most of the features and functionality available in…


Winmail.dat received with a Lotus Notes Client

When an Exchange based email organization sends out an email to a non Exchange based organization (Lotus Notes or other systems for example web mailers) it could happen, that a non mapi client receives an empty email with a winmail.dat file attachment. The client is unable to open the winmail.dat file and so the email…


Messages sent from Exchange 2007 to Non-Exchange Recipients through an Exchange 2003 Connector are NDRed by the first Hub/Transport Server

In a mixed Exchange 2007/2003 environment with a Connector to a Non-Exchange System on an Exchange 2003 Server you cannot send messages from Exchange 2007 to a recipient in the Non-Exchange System if the following two conditions are true: 1) the Connector contains an Address Space with an underscore (“_”) in it, like in the following example:…


How to control routing from your own routing agent

With the release of Microsoft Exchange Server 2007 Service Pack 1 you can programmatically override the default routing for message recipients on a per-recipient basis. This can be done by using the SetRoutingOverride method on the recipient for which you want to override the default routing. Let’s assume that you have an Exchange 2007 server…


Proxying CAS HTTP Cross Forest availability requests

Some of you may want to configure Cross Forest availability with your CAS Servers, but don’t necessarily want to open additional paths through your firewalls or networks for the CAS Servers to be able to talk directly with one another.   In this case, if you have an HTTP Web Proxy (obviously we like to…


Microsoft Exchange Web Services Managed API 1.0 Beta released

Yesterday the Exchange DEV Team announced the Release of the EWS Managed API Beta. Some basic documentation is available at the the MSDN Site for the Microsoft Exchange Web Services Managed API 1.0 Beta SDK April 2009. The main object of the API is the ExchangeService. In the Getting started section You can see a basic code example for…