Notlarım…
Exchange Server 2013 Cu10 ve üzeri olması gerek. Exc 2010 sp3 Rr11 olması gerek. Exc 2007 varsa 2007 yi ortamdan kaldırmak gerek.
Get-ExchangeServer | fl ile Exchange versiyonları kontrol edilir.
Sistem gereksinimleri aşağıdaki gibidir.
Coexistence of Exchange 2016 with earlier versions of Exchange Server
| Exchange version | Exchange organization coexistence |
| Exchange 2007 and earlier versions | Not supported |
| Exchange 2010 | Supported with Update Rollup 11 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers. |
| Exchange 2013 | Supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
| Mixed Exchange 2010 and Exchange 2013 organization | Supported with the following minimum versions of Exchange:
|
Supported hybrid deployment scenarios
Exchange 2016 supports hybrid deployments with Office 365 tenants that have been upgraded to the latest version of Office 365. For more information about specific hybrid deployments, see Hybrid deployment prerequisites.
Network and directory servers
The following table lists the requirements for the network and the directory servers in your Exchange 2016 organization.
Network and directory server requirements for Exchange 2016
| Component | Requirement |
| Domain controllers | All domain controllers in the forest need to be running one of the following:
|
| Active Directory forest | The Active Directory forest functionality level needs to be at Windows Server 2008 or higher. |
| DNS namespace support | Exchange 2016 supports the following domain name system (DNS) namespaces:
For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces. |
| IPv6 support | In Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 support in Exchange 2013. |
Directory server architecture
The use of 64-bit Active Directory domain controllers increases directory service performance for Exchange 2016.
 Note: |
| In multi-domain environments, on Windows Server 2008 domain controllers that have the Active Directory language locale set to Japanese (ja-jp), your servers may not receive some attributes that are stored on an object during inbound replication. For more information, see Microsoft Knowledge Base article 949189, A Windows Server 2008 domain controller that is configured with the Japanese language locale may not apply updates to attributes on an object during inbound replication. |
Installing Exchange 2016 on directory servers
For security and performance reasons, we recommend that you install Exchange 2016 only on member servers and not on Active Directory directory servers. To learn about the issues you can face when installing Exchange 2016 on a directory server, see Installing Exchange on a domain controller is not recommendedAfter Exchange 2016 is installed, changing its role from a member server to a directory server, or vice versa, isn’t supported.
Hardware
For information about deploying Exchange in a virtualized environment, see Exchange 2016 virtualization.
Hardware requirements for Exchange 2016
| Component | Requirement | Notes |
| Processor |
|
For more information, see Sizing Exchange 2016 Deployments.
See the “Operating system” section later in this topic for supported operating systems. |
| Memory | Varies depending on Exchange roles that are installed:
|
For more information, see Sizing Exchange 2016 Deployments. |
| Paging file size | The page file size minimum and maximum must be set to physical RAM plus 10MB, to a maximum size of 32,778MB (32GB) if you’re using more than 32GB of RAM. | None |
| Disk space |
|
For more information, see Sizing Exchange 2016 Deployments. |
| Drive | DVD-ROM drive, local or network accessible | None |
| Screen resolution | 1024 x 768 pixels or higher | None |
| File format | Disk partitions formatted as NTFS file systems, which applies to the following partitions:
Disk partitions containing only the following types of files can optionally be formatted as ReFS:
|
None |
Operating system
The following table lists the supported operating systems for Exchange 2016.
| Important: |
We don’t support the installation of Exchange 2016 on a computer that’s running Windows Server Core or Nano Server. The Windows Server Desktop Experience feature needs to be installed. To install Exchange 2016, you need to do one of the following to install the Desktop Experience on Windows Server prior to starting Exchange 2016 Setup:
|
Supported operating systems for Exchange 2016
| Component | Requirement |
| Mailbox and Edge Transport server roles |
|
| Management tools | One of the following:
|
*Requires Exchange Server 2016 Cumulative Update 3 or later.
Supported Windows Management Framework versions for Exchange 2016
Exchange 2016 only supports the version of Windows Management Framework that’s built in to the release of Windows that you’re installing Exchange on. Don’t install versions of Windows Management Framework that are made available as stand-alone downloads on servers running Exchange.
Installing other software on an Exchange 2016 server
We don’t support the installation of Office client or Office server software, such as SharePoint Server; Skype for Business Server; Office Online Server; or Project Server, on Exchange 2016 servers. Other software that you want to install on Exchange 2016 servers needs to be designed to run on the same computer as Exchange.
.NET Framework
We strongly recommend that you use the latest version of .NET Framework that’s supported by the release of Exchange you’re installing.
| Important: |
| Releases of .NET Framework that aren’t listed in the table below are not supported on any release of Exchange 2016. This includes minor and patch-level releases of .NET Framework. |
| Exchange version | .NET Framework 4.6.2 | .NET Framework 4.6.1 | .NET Framework 4.5.2 |
| Exchange 2016 CU5 or later | X | ||
| Exchange 2016 CU4 | X | X3 | X3 |
| Exchange 2016 CU3 | X | X | X |
| Exchange 2016 CU2 | X1,2 | X | |
| Exchange 2016 RTM or CU1 | X |
1 .NET Framework 4.6.1 requires post-release fixes if you want to install it on a server running Exchange 2016 CU2. For more information. see Exchange 2016 prerequisites.
2 If you’re upgrading to Exchange 2016 CU4 from Exchange 2016 RTM, CU1, or CU2, we strongly recommend that you install Exchange 2016 CU4 before .NET Framework 4.6.2 or .NET Framework 4.6.1 and its related post-release fixes.
3Starting with Exchange 2016 CU5, .NET Framework 4.6.1 and 4.5.2 will no longer be supported with Exchange 2016. While those versions of .NET Framework are supported by Exchange 2016 CU4, we strongly recommend that you upgrade servers running Exchange 2016 to .NET Framework 4.6.2.
Enterprise admin, Schema Admin ve Local Admin olan bir account ile domaine member sunucuda ön gereksinimleri tamamlayarak kuruluş öncesi hazırlıklar tamamlanması gerekmektedir.
Microsoft .NET Framework 4.5.2 (Offline Installer)
https://www.microsoft.com/en-us/download/details.aspx?id=42642
Windows Management Framework 4.0
https://www.microsoft.com/en-us/download/details.aspx?id=40855
Unified Communications Managed API 4.0 Runtime
https://www.microsoft.com/en-us/download/details.aspx?id=34992
Aşağıdaki features ların kurulması gerekmektedir. Kurmayıp bu kuruluşu Exchange e de yaptırabiliriz.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation,RSAT-ADDS
Exchange server ı kurarken en son exc cu ile kurulum yapılabilir. Exc cu nun içerisinde exc setup ı da mevcuttur Bu nedenle önce exc sonra günce exc cu kurmaya gerek yoktur.
Kuruluştan sonra Get-ExchangeServer komutu ile server kontrol edilir.
Domain ve Forest Level ler 2003 te ise önde domain sonra forest 2008 u çıkarılır.
Exchange 2016 kuruluşu sınra domaine join olmuş bilgisayarlardaki outlook lar sertifika hatası almaması için ad deki scp yi exc kuruluşundan sonra hemen düzenlemek gerek.
Set-ClientAccessServer -Identity exc2016sernername -AutoDiscoverServiceInternalUri https://mail.domain.com/autodiscover/autodiscover.xml
Exc 2013 cas Proxy olarak çalıştığı için cas tarafında bir işlem yapmadan mailbox ları exc 2016 move edilebilir.
Exc 2013 ten sertifika psk ile export edilip exc 2016 ya import edilip servislere atanır.
Virtual directory olarak kullanılan mail.domain.com posta.domain.com gibi record ların tutulduğu dns lerde posta mail webmail vs kaydı ve autodiscover kaydı yeni exc2016 sunucusuna point edecek şekilde internal dns lerde düzenleme yapılır.
Exc web servislerinin düzenlenmesi
Outlook Anywhere
Get-OutlookAnywhere -Server exc2016servername | Set-OutlookAnywhere -InternalHostname mail.domain.com -InternalClientAuthenticationMethod Ntlm -InternalClientsRequireSsl $true -ExternalHostname mail.domain.com -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $true -IISAuthenticationMethods Negotiate,NTLM,Basic
ECP
Get-EcpVirtualDirectory -Server excserver2016name | Set-EcpVirtualDirectory -InternalUrl https://mail.domain.com/ecp -ExternalUrl https://mail.domain.com/ecp
WebService
Get-WebServicesVirtualDirectory -Server excserver2016name | Set-WebServicesVirtualDirectory -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -ExternalUrl https://mail.domain.com/EWS/Exchange.asmx
OWA
Get-OwaVirtualDirectory -Server exc2016servername | Set-OwaVirtualDirectory -InternalUrl https://mail.domain.com/owa -ExternalUrl https://mail.domain.com/owa
ActiveSync
Get-ActiveSyncVirtualDirectory -Server exc2016srv | Set-ActiveSyncVirtualDirectory -InternalUrl https://mail.domain.com/Microsoft-Server-ActiveSync -ExternalUrl https://mail.domain.com/Microsoft-Server-ActiveSync
OAB
Get-OabVirtualDirectory -Server exc2016servername | Set-OabVirtualDirectory -InternalUrl https://mail.domain.com/OAB -ExternalUrl https://mail.domain.com/OAB
MapioverHTTP
Get-OrganizationConfig | fl *mapi* ile mapioverhttp nin enable edilip edilmedği kontrol edilir.
Exc 2007 veya 2010 varsa mapioverhttp bağlantıda Outlook clientları sunucuda bağlanamayabilir.
Mapi bağlantıda sorunlu clientlar için https://support.microsoft.com/en-us/help/3101488/november-10-2015-update-for-outlook-2013-kb3101488 güncellemesi yüklenmelidir.
Mapi gerçmeden çnce Outlook 2013 sp1 i ve Outlook 2010 lar sp2 li olmalı.
Exc 2013 sp1 ve üzeri olmalı cas ve mbx ler
Outlook lar mapi sonrası exc e bağlanırken sorun yaşarsa aşağıdaki makaledeki işlemler gerçekleştirilir.
Set-OrganizationConfig -MapiHttpEnabled $true ile enable edilir. Aşağıdaki komutu 2013 ve 2016 sunucular için tek tek çalıştır.
Get-MapiVirtualDirectory -Server excserver2016name | Set-MapiVirtualDirectory -InternalUrl https://mail.domain.com/mapi -ExternalUrl https://mail.domain.com/mapi
Değişikliklerin hemen uygulanması için MSExchangeAutodiscoverAppPool app pool u resetle veya iis i resetle. İis resetlenince Outlook lar gidip gelebilir.
Firewall üzerinden 443 ncü port exc 2016 ya yönledirilir ve external dan erişimler 2016 ya alınmış olur.
autodiscover.domain.com ve mail.domain.com kayıtlarını internet dns ten yeni exc2016 sunucu olarak değiştir.
Exc 2016 kurulunca default db nin rename edilmesi
Get-MailboxDatabase -Server exc2016srvname
Set-MailboxDatabase -Identity “defauldbname” -Name newdbname
Arbitration mb taşıma
Get-Mailbox –Arbitration
Get-Mailbox -Arbitration | New-MoveRequest -TargetDatabase exc2016dbname
Get-MoveRequest | Get-MoveRequestStatistics
PF Taşıma
Get-Mailbox -Server exc2013srvname -PublicFolder
New-MoveRequest PublicFolders1 -TargetDatabase exc2016dbname
Move Mailbox
New-MoveRequest Administrator -TargetDatabase exc2016dbname
Get-Mailbox -Database “excsrv2013dbname” | New-MoveRequest -TargetDatabase exc2016srvname ile 2013db sindeki tüm kullanıcılar taşınmaya başlanır
Get-MoveRequest | Get-MoveRequestStatistics ile taşıma durumu takip edilir.
Get-MoveRequest -movestatus completed | remove-moverequest iel move requestte bulunan mailbox lar taşınamayacağu için bu request ler silinir.
Var olan send connector de exchange 2013 çıkarılıp exchange 2016 eklenerek internete yeni exc 2016 üzerinden mail gönderili başlanır.
Relay için receive connector oluşturmak gerekebilir. Receive connector ü de oluştur. İlk kuruluştan sonra her iki server da bir birinden sorunsuz mail alması için karşılıklı olarak bir receive connector oluşturulur.
New-OfflineAddressBook -Name “AddressBook” -AddressLists “\Default Global Address List” -VirtualDirectories $Null -GlobalWebDistributionEnabled $True ile exc 2016 için bir OAB oluşturulur ve db lerin kullanması için gerekli ayar yapılır.
Tüm işlemler sorunsuz bittiyse Exchange 2013 ortamdan uninstall edilebilir durumdadır.