Exchange 2013: When the DAG NIC Affects Transport, That Can't Be Good

In my on-premises Exchange 2013 lab, there was a queue built up to a mailbox:   Get-TransportService | Get-Queue | Where{$_.MessageCount -gt 0} | FT -AutoSize   Identity      DeliveryType          Status MessageCount Velocity RiskLevel OutboundIPPool NextHopDomain ——–      ————          —— ———— ——– ——— ————– ————- Stromkarlen\3 SmtpDeliveryToMailbox Retry  15           0        Normal    0              emea-sweex15-01 store 001   What’s interesting about the queue is…

1

O365: CDN Change Causes OWA Client Error

Recently, we've seen a pattern of escalations wherein users are no longer able to access OWA. Specifically, the error will be similar to the following: In the details, we'll see the error we're concerned with: X-OQA-Error: ClientError;exMsg=’_g’ is undefined; file=https://pod51048.outlook.com/owa/:362 If we use Network Tracing (F12 in Internet Explorer) [or Fiddler] we'll see a failure…


Exchange 2013: Recipient Filtering Agent (More Lessons in Proxy)

With the arrival of Exchange 2013 came some design changes and, with those changes, inevitably something was bound to catch us off-guard. To help explain this better, enter the proxy from the CAS Frontend to the Mailbox backend. All SMTP connections (we’re focusing on SMTP for this post) utilize the proxy of the Frontend Transport…

4

O365: Accessing Another Mailbox via OWA URL

It may become necessary for an admin or delegate to access a mailbox (other than their own) in OWA. There's two ways to do this and most people are familiar with the change in the URL method, which is what I'll be covering in this post. In Wave14 (Exchange 2010), you merely had to append…

6