[EX2013] CoExistence URLs

Client Connectivity in an Exchange 2013 Coexistence Environment

From <http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx>

Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

From <http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx>

Install Exchange 2013 in an Existing Exchange 2007 Organization

From <https://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx>

Exchange 2007 And 2013 Outlook Anywhere Co-Existence

From <http://blogs.technet.com/b/rmilne/archive/2014/03/19/exchange-2007-2013-outlook-anywhere-coexistence.aspx>

Disabling IPv6 On Exchange 2007

Before you install Exchange 2013, you might need to disable IPv6 on some of your Exchange 2007 servers. Some connections between Exchange 2007 and Exchange 2013 don't work correctly when IPv6 is enabled and an Exchange 2007 server has both the Mailbox and Client Access server roles installed.

From <http://blogs.technet.com/b/rmilne/archive/2014/03/19/exchange-2007-2013-outlook-anywhere-coexistence.aspx>

"Make sure that when you enable Outlook Anywhere on the Client Access Server, choose NTLM for IIS authentication."

From <https://technet.microsoft.com/en-us/library/bb123741(v=exchg.150).aspx#coexistence>

Part 1: Step-by-Step Exchange 2007 to 2013 Migration

Part 2: Step-by-Step Exchange 2007 to 2013 Migration

Part 3: Step-by-Step Exchange 2007 to 2013 Migration

Exchange 2010/2007 to 2013 Migration and Co-existence Guide

From <http://msexchangeguru.com/2013/05/10/exchange2013-migration/>

****************************************************************************

****************************************************************************

****************************************************************************

EXAMPLE

Exchange 2007

Ex2007.domain.com

Exchange 2007 SP3 RU10

192.168.100.10

Exchange 2013

Ex2013.domain.com

Exchange 2013 RU3

192.168.100.20

• Prior to Exchange 2013

Virtual Directory	Current 2007 Values (Prior to Exchange 2013)
OWA	internalURL: https://webmail.domain.com/owa externalURL:https://webmail.domain.com/owa
ECP	N/A
ActiveSync	internalURL: https://webmail.domain.com/Microsoft-Server-ActiveSync  externalURL: https://webmail.domain.com/Microsoft-Server-ActiveSync
Outlook Anywhere	externalHostName: webmail.domain.com IISAuthenticationMethods: Basic ClientAuthenticationMethods: Basic
Exchange Web Services	internalURL: https://webmail.domain.com/EWS/Exchange.asmx externalURL:https://webmail.domain.com/EWS/Exchange.asmx
AutoDiscover	AutoDiscoverServiceInternalURI:https://autodiscover.domain.com/Autodiscover/Autodiscover.xml

…and DNS was configured as follows:

A Record	IP Address
webmail.domain.com	192.168.100.10
autodiscover.domain.com	192.168.100.10

• After:

Virtual Directory	2007	2013
OWA	internalURL: https://legacy.domain.  com/owa  externalURL: https://legacy.domain.  com/owa	internalURL:  https://webmail.domain.com/owa  externalURL:  https://webmail.domain.com/owa
ECP	N/A	internalURL:  https://webmail.domain.com/ecp  externalURL:  https://webmail.domain.com/ecp
ActiveSync	internalURL:  https://legacy.domain.com/Microsoft-  Server-ActiveSync  externalURL: $null	internalURL:  https://webmail.domain.com/Microsoft-Server-ActiveSync  externalURL:  https://webmail.domain.com/Microsoft-Server-ActiveSync
Outlook Anywhere	externalHostName:  webmail.domain.com  IISAuthenticationMethods:  Basic,NTML  ExternalClientAuthenticationMethods:  Basic	externalHostName:  webmail.domain.com  IISAuthenticationMethods:  Basic,NTML  ExternalClientAuthenticationMethods:  Basic
Exchange Web Services	internalURL:  https://legacy.domain.com/EWS/Exchange.asmx  externalURL:  https://legacy.domain.com/EWS/Exchange.asmx	internalURL:  https://webmail.domain.com/EWS/  Exchange.asmx  externalURL:  https://webmail.domain.com/EWS/  Exchange.asmx
AutoDiscover	AutoDiscoverServiceInternalURI:  https://autodiscover.domain.com/  Autodiscover/Autodiscover.xml	AutoDiscoverServiceInternalURI:  https://autodiscover.domain.com/  Autodiscover/Autodiscover.xml

…and DNS will look like this:

A Record	IP Address
legacy.domain.com	192.168.100.10
webmail.domain.com	192.168.100.20
autodiscover.domain.com	192.168.100.20

OWA – (Redirect) Should be pretty straight forward.  When a user whose mailbox still resides on 2007, accesses OWA via the 2013 CAS, they will be redirected back to 2007 via externalURL value:https://legacy.domain.com/owa

Set-OwaVirtualDirectory –Identity “ex2013\owa (Default Web Site)” –InternalUrlhttps://webmail.domain.com/owa –ExternalURL https://webmail.domain.com/owa

Set-OwaVirtualDirectory –Identity “ex2007\owa (Default Web Site)” –InternalUrlhttps://legacy.domain.com/owa –ExternalURL https://legacy.domain.com/owa

ActiveSync – (Proxy) I prefer to force ActiveSync to proxy from 2013 to 2007 as some ActiveSync devices don’t handle the redirect correctly.  In order to force a proxy scenario, the externalURL value for 2007 is set to $null.  The internalURL on 2007 should be configured with https://legacy.domain.com/Microsoft-Server-ActiveSync

Set-ActiveSyncVirtualDirectory –Identity “Ex2013\Microsoft-Server-ActiveSync (Default Web Site)” –InternalURL https://webmail.domain.com/Microsoft-Server-ActiveSync –ExternalURLhttps://webmail.domain.com/Microsoft-Server-ActiveSync

Set-ActiveSyncVirtualDirectory –Identity “Ex2007\Microsoft-Server-ActiveSync (Default Web Site)” –InternalURL https://legacy.domain.com/Microsoft-Server-ActiveSync –ExternalURL $null

Outlook Anywhere – (Proxy) All OA connections, both 2007 mailboxes and 2013 mailboxes will now connect via the 2013 CAS.  2013 will proxy connections back to 2007 for legacy mailboxes.  The externalHostName for both 2013 and 2007 should be the same, (webmail.domain.com).  Exchange 2007 does not support “Negotiate” authentication (See image below).  Therefore the externalClientAuthenticationMethods should be configured to match whatever is configured for 2007, either Basic or NTLM.  For OA to proxy from 2013 to 2007, the IISAuthenticationMethods on 2007 must be reconfigured to support both Basic and NTLM.  By default, Exchange 2007 IISAuthenticationMethods is set to just Basic.  NTLM must be added for the proxy to work.

Set-OutlookAnywhere –Identity “Ex2013\Rpc (Default Web Site)” –InternalHostname webmail.domain.com –ExternalHostName webmail.domain.com –ExternalClientAuthenticationMethod Basic –IISAuthenticationMethods Basic,NTLM

Set-OutlookAnywhere –Identity “Ex2007\Rpc (Default Web Site)”  –IISAuthenticationMethods Basic,NTLM

Exchange Web Services – (AutoDiscover) Autodiscover is used to retrieve the EWS configuration for the 2007 users.

Set-WebServicesVirtualDirectory –Identity “Ex2013\EWS (Default Web Site)” –InternalURLhttps://webmail.domain.com/EWS/Exchange.asmx –ExternalURLhttps://webmail.domain.com/EWS/Exchange.asmx

Set-WebServicesVirtualDirectory –Identity “Ex2007\EWS (Default Web Site)” –InternalURLhttps://legacy.domain.com/EWS/Exchange.asmx –ExternalURLhttps://legacy.domain.com/EWS/Exchange.asmx

AutoDiscover – Both the 2007 and 2013 SCP locator can be configured to point to the Autodiscover URLhttps://autodiscover.domain.com/Autodiscover/Autodiscover.xml.  DNS must be updated however so that the A record for Autodiscover.domain.com resolves to the 2013 CAS.

Set-ClientAccessServer –Identity Ex2013 –AutoDiscoverServiceInternalUrihttps://autodiscover.domain.com/Autodiscover/Autodiscover.xml

ECP –  Exchange 2007 did not have an ECP virtual directory.  Therefore, only the 2013 ECP virtual directory needs to be configured.

Set-EcpVirtualDirectory –Identity “Ex2013\ecp (Default Web Site)” –InternalURLhttps://webmail.domain.com/ecp –ExternalURL https://webmail.domain.com/ecp

From <http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/> 

[EX2013] Calendar Sync Issues

Plano de ação para analisarmos os problemas de sincronismo de calendário com dispositivos iOS.

Plano de Ação:

=============

* Antes de reproduzir o problema:

1)    Habilitar o ActiveSync Mailbox logging para a conta afetada;

Set-CASMailbox <user> -ActiveSyncDebugLogging:$true

* Depois de reproduzir o problema:

2)    Recuperar o log de ActiveSync na caixa de correio afetada;

Get-ActiveSyncDeviceStatistics -Mailbox <user> -GetMailboxLog:$true –NotificationEmailAddresses jfeitosa.solve@suzano.com.br

3)    Exportar um dump das propriedades do usuário afetado;

Get-Mailbox <user> | fl

4)    Exportar os dispositivos na conta afetada;

Get-MobileDeviceStatistics -Mailbox <user> | fl DeviceId, DeviceType, DeviceModel, DeviceOS, DeviceFriendlyName, Name, LastS*

5)    Salvar uma cópia dos eventos de Application em formato *csv de todos os servidores CAS que atendem o tráfego do ActiveSync;

6)    Salvar os logs de IIS e IIS http err de todos os servidores CAS que atendem o tráfego do ActiveSync;

a.     IIS logs (Default: C:\inetpub\logs\LogFiles\W3SVC1)

b.     IIS HTTP error logs (Default: C:\Windows\System32\LogFiles\HTTPERR)

Artigos Relacionados:

=============

# Known calendaring issues with iOS 8.x and iOS 7.x devices

https://support.microsoft.com/en-us/kb/3015401

# Current issues with Microsoft Exchange ActiveSync and third-party devices

https://support.microsoft.com/en-ph/kb/2563324

[EX2013] Content Index

Reseed the content index catalog if the mailbox database is part of a DAG


• Reseed the content index catalog from any source


Update-MailboxDatabaseCopy -Identity DB1\MBX1 -CatalogOnly


• Reseed the content index catalog from a specific source


Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2 -CatalogOnly




Reseed the content index catalog if there is only one copy of the mailbox database


• Stop-Service MSExchangeFastSearch
• Stop-Service HostControllerService
• Delete, move, or rename the folder that contains the Exchange content index catalog.
• Start-Service MSExchangeFastSearch
• Start-Service HostControllerService


• Get-MailboxDatabaseCopyStatus | FL Name,*Index*


** ResetSearchIndex.ps1 **


Content Index status of all or most of the mailbox databases in the environment shows "Failed"


1. Create a new Active Directory group that is named "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group. This is a dummy group and should be used as a placeholder only. You might want to add a description so that the group is not removed.
2. Force or wait for Active Directory replication.
3. Restart the following services:
• Microsoft Exchange Search
• Microsoft Exchange Search Host Controller


De <http://support.microsoft.com/kb/2807668/en-us>  

[EX2013] Mailbox Move Limits

LIMITS

<Exchange Installation Path>\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config

In Exchange 2013 the file has the same name and is located in the same folder, but now in the Mailbox server role.

MaxActiveMovesPerSourceMDB

MaxActiveMovesPerTargetMDB

MaxActiveMovesPerSourceServer

MaxActiveMovesPerTargetServer

[EX2013] Update Disconnected Mailboxes

This example updates the mailbox state for all mailboxes on the mailbox database MDB02.

Get-MailboxStatistics -Database MDB02 | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid -Confirm:$false }

This example updates the mailbox state for all disconnected mailboxes on the mailbox database MDB03.

Get-MailboxStatistics -Database MDB03 | Where { $_.DisconnectReason -ne $null } | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid -Confirm:$false }

Update-StoreMailboxState

From <http://technet.microsoft.com/en-us/library/jj860462(v=exchg.150).aspx>

Remove-StoreMailbox

From <http://technet.microsoft.com/en-us/library/ff829913(v=exchg.150).aspx> 

[EX2013] Simplify the Outlook Web App URL

1. Start IIS Manager.
2. Expand the local computer, expand Sites, and then click Default Web Site.
3. At the bottom of the Default Web Site Home pane, click Features View if this option isn't already selected.
4. In the IIS section, double-click HTTP Redirect.
5. Select the Redirect requests to this destination check box.
6. Type the absolute path of the /owa virtual directory. For example, type https://mail.contoso.com/owa.
7. Under Redirect Behavior, select the Only redirect requests to content in this directory (not subdirectories) check box.
8. In the Status code list, click Found (302).
9. In the Actions pane, click Apply.
10. Click Default Web Site.
11. In the Default Web Site Home pane, double-click SSL Settings.
12. In SSL Settings, clear Require SSL.



Note:

If you don’t clear Require SSL, users won’t be redirected when they enter an unsecured URL. Instead, they’ll get an access denied error.



13. For the new settings to take effect, open a Command Prompt window, and then type iisreset /noforce to restart IIS.


From <http://technet.microsoft.com/en-us/library/aa998359.aspx>  

[EX2013] Database is mandatory on Arbitration Mailboxes

1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
1. Click Start, click Run, type adsiedit.msc, and then click OK.
2. Locate the Default Naming Context node, and then locate to the CN=Users container.
3. Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, clickDelete.
1. Rerun the Exchange Server 2010 Mailbox role setup application.
2. Create a new federated e-mail account by using the following command:
   New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>


From <http://support2.microsoft.com/kb/978776/en-us>




setup /PrepareAD [/OrganizationName:]
Enable-Mailbox -Arbitration -DomainController  -Identity "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}"




Set-Mailbox “SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}” -Arbitration -Database “YourDatabaseNameHere”