Microsoft Exchange Server 2013

Exchange 2013 Client Access Server Configuration
Configure Mail Flow and Client Access
Exchange 2013 Cmdlets
Exchange Server 2013 Management Pack Guide
TechNet Wiki - Exchange Server 2013 and Cumulative Updates (CU’s) Build Numbers
TechNet Wiki - How to Configure SSL Offloading in Exchange 2013 shows that SSL Offloading is not (yet) supported.
Default Settings for Exchange Virtual Directories

Exchange 2013 storage configuration options

Microsoft Download Center - Multi-Tenancy and Hosting Guidance for Exchange Server 2013
Microsoft Download Center - Multi-Tenant Scalability Guidance for Exchange Server 2013

Microsoft Support - Description of Exchange Server 2013 Service Pack 1 (KB2926248)

Microsoft Support - Cumulative Update 5 for Exchange Server 2013 (KB2936880)
The Exchange Team Blog - Released: Exchange Server 2013 Cumulative Update 5
Tony Redmond's Exchange Unwashed Blog > Exchange 2013 CU5 - the totally unremarkable update (in a good way)

Microsoft Support - Cumulative Update 6 for Exchange Server 2013
The Exchange Team Blog - Released: Cumulative Update 6 for Exchange Server 2013
Tony Redmond's Exchange Unwashed Blog > Exchange 2013 CU6 hybrid and co-existence bugs cause administrators to despair
Tony Redmond's Exchange Unwashed Blog > Yet another co-existence bug in Exchange 2013 CU6 causes ActiveSync failures for Exchange 2007 users

Microsoft Support - Cumulative Update 7 for Exchange Server 2013
The Exchange Team Blog - OAB Improvements in Exchange 2013 Cumulative Update 7

Tony Redmond's Exchange Unwashed Blog - Microsoft pulls Exchange updates to fix installer problem
The Exchange Team Blog - On-Premises Legacy Public Folder Coexistence for Exchange 2013 Cumulative Update 7 and Beyond

Microsoft Support - Cumulative Update 8 for Exchange Server 2013
The Exchange Team Blog - Announcing Cumulative Update 8 for Exchange Server 2013

Michael Van Horenbeeck - A closer look at the changes in the Client Access Infrastructure in Exchange Server 2013
The Exchange Team Blog - Exchange 2013 Server Role Architecture
The Exchange Team Blog - Exchange 2013 Client Access Server Role
The Exchange Team Blog - Publishing Exchange Server 2013 using TMG
Danny Wong's Blog - Exchange 2013 – Client Access Server Role – Proxying
Tony Redmond's Exchange Unwashed Blog - Exchange 2013 is a resource hog - no surprise there
ExchangeServerInfo - TROUBLESHOOTING OAB IN EXCHANGE 2013
The Exchange Team Blog - Address Book Policies, Jamba Jokes and Secret Agents
The Exchange Team Blog - Server Component States in Exchange 2013

Intermedia Knowledge Base:
Known OWA Issues In Exchange 2013
OWA 2013 Browser Compatibility Chart

JaapWesselius.com - Load Balancing in Exchange 2013
Pro-Exchange,Lync & Office 365 - Load Balancing Exchange 2013 - part 1
Exchange for the Working Man - How to Use Managed Availability in Exchange 2013 with your Load Balancer

bcTechNet - Exchange 2010/2013 Co-Existence Experience
TechTalk Live Blog - Issues with Exchange 2013 and Exchange 2010 Coexistence
Troubleshooting Exchange - Legacy Public Folder remnants in Exchange 2013 cause “The Microsoft Exchange Administrator has made a change…” prompt

MSExchangeGuru.com - Exchange 2013: Configuring Outlook anywhere
MseXchangeTeam - Outlook Anywhere in Exchange Server 2013 – What’s New
4sysops - Outlook Anywhere for Exchange 2013
Ilantz's Weblog - Exchange 2013 Outlook Anywhere Considerations
Sysadmin Lab - Outlook Anywhere Basic vs. NTLM Authentication explained

MSExchange.org - Planning and migrating a small organization from Exchange 2007 to 2013 (Part 8)

The Exchange Team Blog - Ask the Perf Guy: Sizing Exchange 2013 Deployments

Microsoft TechNet - Exchange Server 2013 - Managed Store
TechNet Blogs » Richard Schwendiman's Blog » Exchange 2013: Store, FAST, and ESE Cache Demystified…Hopefully!
Thoughtsofanidlemind's Blog - New Store, new memory tuning techniques required

Exchange Server Tools Documentation
Microsoft Download Center - Microsoft Exchange 2013 Public Folders Migration Scripts

1. When moving an e-mail with HTML layout from one mailbox to another mailbox or exporting to .pst, inline pictures and part of the HTML layout disappears.
   1. Fixed in: SP1
   2. Workaround:
      1. When the mail needs to be moved to another mailbox: forward the email.
   3. Sources:
      1. Exchange Server Forums - Move Message with Attachment from one Mailbox to another problem
      2. Microsoft Support - Images are missing using Outlook in online mode with Exchange 2013
2. After migrating a mailbox from Exchange 2010 with an active ActiveSync partnership to Exchange 2013 the ActiveSync device stops synchronizing until 1-8 hours have passed.
   1. Fixed in: Supposed to be fixed in CU5, but the fix is not in CU5. See “Update 3” at the bottom of: Tony Redmond's Exchange Unwashed Blog > Exchange 2013 CU5 - the totally unremarkable update (in a good way)
   2. Workaround: recycle the IIS application pool worker processes.
   3. Sources:
      1. The EXPTA {blog} - Fix for Exchange ActiveSync Failures After Migration to Exchange 2013
3. POP/IMAP clients unable to Authenticate
   1. Fixed in: CU2
   2. Sources: MSExchangeGuru.com - Exchange 2013: Pop/Imap clients unable to Authenticate
4. You can't disable Outlook Web App access for users in on-premises Exchange Server
   1. Fixed in: CU2
   2. Sources:
      1. KB 2835562
      2. Tony Redmond's Exchange Unwashed Blog - Blocking OWA access for a user is a problem for Exchange 2013 CU1
5. Beware Full OAB Downloads After Installing 1st Exchange 2013 Server in Existing Exchange 2007/2010 Environment
   1. Workaround: Make sure all of your Exchange 2007/2010 Mailbox Databases have an actual value populated for their Offline Address Book. If they are currently blank, then populate them with your current Default OAB.
   2. Sources:
      1. Troubleshooting Exchange - Beware Full OAB Downloads After Installing 1st Exchange 2013 Server in Existing 07/10 Environment
      2. The Exchange Team Blog - Released: Exchange Server 2013 RTM Cumulative Update 1
         
6. “Exchange Server 2013 introduced separate internal and external client settings for Outlook Anywhere connectivity. Outlook uses the external namespace to connect to alternate mailboxes, even though Outlook is located on the internal network. Alternate mailboxes include auto-mapped mailboxes and public folders.”
   1. Fixed in: Outlook 2007/2010/2013 hotfix package of July/August 2013. See KB2839517 link below.
   2. Sources:
      1. Outlook is unable to connect to Exchange 2013 public folder or auto-mapped mailbox (KB2839517)
      2. Internal Outlook ask password after settings external Outlook Anywhere to Basic auth [Exchange 2013]
7. Users cannot access mailboxes in OWA or EAS when mailbox database is removed
   1. Fixed in: CU6
   2. Workaround: “For now, the solution is simple: don’t remove old databases from Exchange 2007 or Exchange 2010 after you move the mailboxes to Exchange 2013 SP1. Leave them alone and make sure that they remain available until every moved mailbox has successfully logged on to Exchange 2013 SP1. Once that happens, you should be able to remove the old database.”
   3. Sources:
      1. Windows IT Pro - Tony Redmond's Exchange Unwashed Blog - Cherish old Exchange databases to avoid the pesky DatabaseGuidNotFound error
      2. Microsoft Support - Users cannot access mailboxes in OWA or EAS when mailbox database is removed (KB2958434)
      3. Microsoft Support - Cumulative Update 6 for Exchange Server 2013
8. Migrated mailboxes have duplicate folders
   1. Fixed in: CU6
   2. Sources:
      1. Microsoft Support - Duplicate mailbox folders after migration to Exchange Server 2013(KB2991934)
      2. Microsoft Support - Cumulative Update 6 for Exchange Server 2013
9. Exchange 2013 CU6 can't proxy ActiveSync connections to Exchange 2007
   1. Fixed in: KB2997847 hotfix (contact support)
   2. Sources:
      1. Tony Redmond's Exchange Unwashed Blog > Yet another co-existence bug in Exchange 2013 CU6 causes ActiveSync failures for Exchange 2007 users
      2. Microsoft Support - You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6 (KB2997847)
10. Exchange Server 2013 CU6 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
    1. Fixed in: KB2997209 hotfix (contact support)
    2. Sources:
       1. Microsoft Support - Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007 (KB2997209)

See also:
Jason (Izzy) Sherry's Blog - Exchange 2013 RTM CU2 released (Again on 7/29) & Known Issues
Jason (Izzy) Sherry's Blog - Exchange 2010 SP3 RU3 and 2013 CU3 Released & Known Issues
Jason (Izzy) Sherry's Blog - Known Issues with Exchange 2013 SP1
Jason (Izzy) Sherry's Blog - Exchange 2013 CU6, 2010 SP3 RU7, & 2007 SP3 RU14 released & Known Issues

It's always MY problem - Exchange 2013 and Bugcheck 0x000000ef
Exchange Server forums > Exchange Server 2013 - General Discussion - BSOD after creating DAG
Tony Redmond's Exchange Unwashed Blog - Trauma for Exchange 2013 servers when Managed Availability goes bad
Microsoft Support - Exchange Server 2013 restarts frequently after CU2 is installed

1. Outlook Exchange Proxy Settings dialog box always displays the internal host name as the Proxy server in an Exchange Server 2013 environment
   1. Sources:
      1. KB 2754898
2. Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
   1. Sources:
      1. KB 2834139

On an Exchange Server 2013 CU23 server the Microsoft Exchange services have the following start type:

DisplayName                                                   StartType  Status
-----------                                                   ---------  ------
Microsoft Exchange Active Directory Topology                  Automatic Running
Microsoft Exchange Anti-spam Update                           Automatic Running
Microsoft Exchange DAG Management                             Automatic Running
Microsoft Exchange Diagnostics                                Automatic Running
Microsoft Exchange EdgeSync                                   Automatic Running
Microsoft Exchange Frontend Transport                         Automatic Running
Microsoft Exchange Health Manager                             Automatic Running
Microsoft Exchange IMAP4                                         Manual Stopped
Microsoft Exchange IMAP4 Backend                                 Manual Stopped
Microsoft Exchange Information Store                          Automatic Running
Microsoft Exchange Mailbox Assistants                         Automatic Running
Microsoft Exchange Mailbox Replication                        Automatic Running
Microsoft Exchange Mailbox Transport Delivery                 Automatic Running
Microsoft Exchange Mailbox Transport Submission               Automatic Running
Microsoft Exchange POP3                                          Manual Stopped
Microsoft Exchange POP3 Backend                                  Manual Stopped
Microsoft Exchange Replication                                Automatic Running
Microsoft Exchange RPC Client Access                          Automatic Running
Microsoft Exchange Search                                     Automatic Running
Microsoft Exchange Search Host Controller                     Automatic Running
Microsoft Exchange Server Extension for Windows Server Backup    Manual Stopped
Microsoft Exchange Service Host                               Automatic Running
Microsoft Exchange Throttling                                 Automatic Running
Microsoft Exchange Transport                                  Automatic Running
Microsoft Exchange Transport Log Search                       Automatic Running
Microsoft Exchange Unified Messaging                          Automatic Running
Microsoft Exchange Unified Messaging Call Router              Automatic Running

The services overview was created with the following PowerShell command:

Get-Service | Where-Object {$_.DisplayName -match "^Microsoft Exchange"} | Sort-Object DisplayName | Select-Object DisplayName,StartType,Status

Outlook can't connect to a mailbox.
The Exchange Control Panel (ECP) shows blank page after logging in.

The Exchange Management Shell shows error:

VERBOSE: Connecting to ex.intern.local.
New-PSSession : [ex.intern.local] Connecting to remote server ex.int.wordworkers.nl failed with the following err
or message : [ClientAccessServer=EX,BackEndServer=ex.intern.local,RequestId=GUID,
TimeStamp=6-12-2021 08:41:26] [FailureCategory=Cafe-SendFailure]  For more information, see the about_Remote_Troublesho
oting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed

The System event log shows multiple messages like:

Log Name:      System
Source:        Microsoft-Windows-HttpEvent
Date:          6-12-2021 09:37:57
Event ID:      15021
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EX.intern.local
Description:
An error occurred while using SSL configuration for endpoint 0.0.0.0:444.  The error status code is contained within the returned data.

When checking the 444 binding on the “Exchange Back End” site in IIS Manager the certificate that should be there instead shows as “Not selected”.

Unclear.

1. Select the internal certificate with friendly name “Microsoft Exchange Server” on the 444 binding on the “Exchange Back End” site in IIS Manager.
2. Open an elevated command prompt.
3. Restart IIS with:

   iisreset

Source: Bluebook - An error occurred while using SSL configuration for endpoint 0.0.0.0:444

See also:

• Microsoft Docs - Unable to open OWA, ECP, or EMS after a self-signed certificate is removed from the Exchange Back End website
• Gareth Harris | Technical Blog - Event ID 15021 HttpEvent Exchange 2013
• evotec - Exchange 2013 powershell errors out, and Exchange 2013 ECP doesn’t work correctly
• vcloudnine.de - Microsoft Exchange 2013/ 2016/ 2019 shows blank ECP & OWA after changes to SSL certificates

See Ammar Hasayen – Blog - Exchange 2013 Certificate Revocation Failed.