Exchange 2010 has the concept of internal and external URL's for various virtual directories for the Client Access Server (CAS role).

You must correctly specify values for URLs because of potential issues with certificates and discoverability of Exchange services for your users.

Here are commandlets in powershell to control all virtual directories URLs in Exchange 2010 (most or all of them are also will work in Exchange 2013):

You can expect the following errors while running Get-MailBox, New-MoveRequest and many other commanlets in Powershell in EMS (Exchange Management Shell):

The requested search root domain is different from the scope root domain.

or

The requested search root domain.local/Users’ is not within the scope of this operation. Cannot perform searches outside the scope ‘child.domain.local’.

I had a problem yesterday with my hybrid Exchange 2010 + 2013 installation. One user set up out-of-office message but it does not sending. Nor in internal domain neither external users.

• We have checked if user forwarding emails to some other users. All good forwarding was net set.
• Also we have disabled all Inbox rules (there was one rule that forwarded messages).
• We have tried to move mailbox to other database (in case corrupted data).
• We tried to disable and enable reply messaging.
• We have reviewed mail flow rules on transport servers.

All these actions didnt give answer.

Exchange 2010 and 2013 partially managed with Exchange Control Panel (ECP). It's a web-service running on IIS on Client Access Server. There is a problem: when you publish OWA in the Internet, you automatically publish ECP to the Internet too. And this is a security issue.

If you use IIS ARR as Reverse Proxy for publishing Exchange to the Internet, you can create rule that will block access to URLs like https://owa.domain.com/ecp/.

How to find all mailboxes in Exchange 2010/2013 with mail forwarding enabled?

It's just a string in Powersehll:

As soon as all messages of Exchange users are stored in database, we can perform search and, if needed, delete operations against messages. It is needed in some cases for example, when employee sent message with confidentional information to the wrong recipient or you just need to find some message and look into it... there can be a lot of options.

What Exchange 2010/2013/2016 can offer to us in such cases? We can search mailboxes (all or any specific) in database and copy search results into some other mailbox. If needed, we also can delete search results from the source mailboxes.