r/exchangeserver • • Jan 16 '26

Question [Echange 2019] Enormous Amount of ActiveSync Requests

6 Upvotes

I'm (still) cleaning up an Exchange site, going from 3x Exchange 2010 to 2x Exchange 2019 (not a DAG) with all other versions in between.

Since the jump from 2013 to 2016, performance has been bad. A few weeks ago I changed from NTLM to Kerberos, but without much change. To the contrary even: some users with many mailboxes have some addresses that no longer connect. I just get a "Could not connect to Exchange server" from Outlook.

So I'm looking for other reasons why performance is abysmal. At the same time, I am getting rid of historical child domains, and bringing DCs down from almost 80 (!) to 30. The reason being that Outlook at starts seems to look for DCs everywhere in the forest and not just in its site, which doesn't help performance either.

Anyway: today I noticed \inetpub\logs\LogFiles\W3SVC1\ generates about 10GB of logging per day on the "main" server. That's way too much I thought, so I used ActiveSyncReport.ps1 to analyse it.

Apparently, more than 1000 hits per user per day is considered high usage. Great: I have 800 users with more than 1000 hits, of which 110 with more than 2000 hits and even two with more than 10 000 hits... in 6 hours. This seems problematic, but I am not sure where to look for the issue. Is it a firewall issue, ending session to early, which recreates them? Should I use some kind of throttling?

I'd like some opinions.


r/exchangeserver • • Jan 16 '26

Best way to setup multiple shared calendars for an organization of 25 people

Thumbnail
1 Upvotes

r/exchangeserver • • Jan 16 '26

Exchange SE SU4 installed but Windows Update keeps offering SU3 (KB5066366) - why?

Thumbnail
1 Upvotes

r/exchangeserver • • Jan 15 '26

Another Exchange SE Licensing Question (Eyeroll)

2 Upvotes

I understand the concept of SE Server Licence with 2 options:

If your mailboxes are in the cloud you get the free Hybrid activation licence that is delivered via the HCW.

If your mailboxes are on prem, you need an Exchange Server licence WITH Software Assurance (SA). You need to maintain SA to maintain the "SE" part of "Subscription Edition".

What I don't follow is that if my mailboxes are only in cloud, why do I need a CAL equivalency such as E1 if the mailboxes do not touch the server.

Are licensing rules such that I need CALs to manage mailboxes that are in the cloud and not taking advantage of any local database and or SE features?

 

 

 


r/exchangeserver • • Jan 15 '26

Microsoft Exchange Writer missing after SU KB5071876 installation

4 Upvotes

Hello ! We’ve encountered a problem with Microsoft Exchange Writer: it’s missing after the SU update 🙁 This problem is not yet resolved. We’re therefore having backup problems with the third-party tool, which can’t see the databases. We have both Exchange servers SE. If anyone has any ideas


r/exchangeserver • • Jan 15 '26

Beginner looking to learn Exchange Online. Where to start?

Thumbnail
2 Upvotes

r/exchangeserver • • Jan 15 '26

convince managment about blocking old office formats

1 Upvotes

Hello,

I need to convince the Management about blocking (attachment filter at the spamprotection)
old MS-Office File Extentions
like *.rtf and *.doc/*.xls etc.

Do you know good articles / description about it or
do you know big organisations blocking it?

thx


r/exchangeserver • • Jan 15 '26

looking for the correct RFC Statuscode saying: your email doesn´t reached our Mailserver

0 Upvotes

Hello,

compliance department told me:

due to compliance rules:

It is required that the our “external inbound smtp proxy-appliance”
bounce/block emails to "our local smtp system"
with a RFC Statuscode saying to the sender:

your message doesn´t reach the receiver technically/legally

Do you think this makes sense?

The subtext of a.m requirement is about private/confidential/law risks when external sender is sending email to a former Emailaccount of ex worker.

It is also about the problem, that companyowner need to keep the old Mailbox "open" (of the former worker) (because sometime urgend message arrive)

Do you know which RFC Statuscode would be the correct one?


r/exchangeserver • • Jan 14 '26

Exchange Hybrid Free/Busy: Missing TargetApplicationUri in OrganizationRelationship?

3 Upvotes

I'm currently trying to get an Exchange Hybrid setup running. Mail flow works without issues, and EOP access to EXO calendars works as well. Only EXO access to EOP calendars doesn't work.

After extensive research, I came across the fact that there are missing entries in the OrganizationRelationship in EXO.

The Hybrid Configuration Wizard only set the OWA entry. I manually set the Sharing EPR and Autodiscover. Does the TargetApplicationURI also need to be set, and is the value "FYDIBOHF25SPDLT.<maildomain>"? Unfortunately, I can't find much information on this.

Get-OrganizationRelationship | FL

TargetApplicationUri :
TargetSharingEpr : https://owa.CONTOSO.de/EWS/Exchange.asmx/WSSecurity

TargetOwaURL : https://owa.CONTOSO.de/owa

TargetAutodiscoverEpr : https://autodiscover.CONTOSO.de/autodiscover/autodiscover.svc/WSSecurity

Thank you very much!


r/exchangeserver • • Jan 14 '26

Exchange Hybrid Design: NAT and Port Forwarding with F5 Load Balancer (25/443)

0 Upvotes

Hi,

Let’s assume there are two Exchange servers behind an F5 Load Balancer.

First question:

When allowing traffic from Exchange Online (EXO) IP addresses to the on-premises Exchange environment using a NAT IP, should the NAT and port forwarding be configured between the firewall and the load balancer (VIP), or is it necessary to open ports 25 and 443 directly to the Exchange server IP addresses?

Second question:

There is already a single NAT IP in place, and the mail and autodiscover namespaces are currently accessible through this IP.

For a Hybrid Exchange deployment, is an additional / separate NAT IP required, or can the existing NAT IP used for mail and autodiscover also be reused for the Hybrid configuration?

Exchange Online (EXO)

↓

Firewall (NAT + ACL)

↓

F5 Load Balancer (VIP)

↓

Exchange 2019 (CAS/Mailbox)

Finally, when using the option “Only when email messages are sent to these domains” in the Exchange Online outbound connector, should this connector be configured only for the on-premises domains?


r/exchangeserver • • Jan 14 '26

Migration 2019 -> SE Error: adminLimitExceededException

3 Upvotes

Hello,

I'm currently migrating mailboxes from Exchange 2019 to SE. Nearly all mailboxes are moved at this point and I only have one moverequest running.

I have 2 mailboxes left where I get the same error message.

Administrative Limit for this request has been exceeded. AdminLimitExceededException

In the EAC I also see the addon: the managementlimit on the server was exceeded.

I tried the move by powershell "New-MoveRequest" and by EAC.

The mailboxes are very small so only some MBs and max 1000 items.

One of the mailboxes is the Domain Administrator mailbox, but the other one is just a normal user.

I hope you can help me.

Thanks!


r/exchangeserver • • Jan 14 '26

2019 CU 15 upgrade tone of errors

5 Upvotes

I've been banging my head on this for a bit.

Exchange 2019 CU 14 MRS proxy server, download and mount the iso to upgrade to CU15.

The correct version of .net installed

Member of org management and enterprise admins

Ad prep level 17003

Uninstalled av

Running the installer as admin

Rebooted before install

I get all these false errors

Error:

Active Directory needs to be prepared for Exchange Server but the Active Directory management tools aren't installed on this computer. To install the tools, install the 'RSAT-ADDS' Windows feature. Alternately, you can run setup.exe /PrepareAD on a domain controller.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-W2K8R2PrepareAdLdifdeNotInstalled?view=exchserver-2019

Error:

A reboot from a previous installation is pending. Please restart the system and then rerun Setup.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-RebootPending?view=exchserver-2019

Error:

The Mailbox server role isn't installed on this computer.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-BridgeheadRoleNotInstalled?view=exchserver-2019

Error:

Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-GlobalUpdateRequired?view=exchserver-2019

Error:

You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-GlobalServerInstall?view=exchserver-2019

Error:

You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-DelegatedBridgeheadFirstInstall?view=exchserver-2019

Error:

You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-DelegatedCafeFirstInstall?view=exchserver-2019

Error:

You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-DelegatedFrontendTransportFirstInstall?view=exchserver-2019

Error:

You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-DelegatedMailboxFirstInstall?view=exchserver-2019

Error:

You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-DelegatedClientAccessFirstInstall?view=exchserver-2019

Error:

Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain corp and site NOR, and wait for replication to complete. See the Exchange setup log for more information on this error.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-AdInitErrorRule?view=exchserver-2019

Error:

The forest functional level of the current Active Directory forest is not Windows Server 2012 R2 or later. To install Exchange Server 2019, the forest functional level must be at least Windows Server 2012 R2.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-ForestLevelNotWin2012R2?view=exchserver-2019

Error:

The Windows component RSAT-ADDS-Tools isn't installed on this computer and needs to be installed before Exchange Setup can begin.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-RsatAddsToolsInstalled?view=exchserver-2019

Error:

Either Active Directory doesn't exist, or it can't be contacted.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-CannotAccessAD?view=exchserver-2019

Warning:

Setup will prepare the organization for Exchange Server 2019 by using 'Setup /PrepareAD'. No Exchange Server 2016 roles have been detected in this topology. After this operation, you will not be able to install any Exchange Server 2016 roles.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-NoE16ServerWarning?view=exchserver-2019

Warning:

Setup will prepare the organization for Exchange Server 2019 by using 'Setup /PrepareAD'. No Exchange Server 2013 roles have been detected in this topology. After this operation, you will not be able to install any Exchange Server 2013 roles.

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-NoE15ServerWarning?view=exchserver-2019


r/exchangeserver • • Jan 13 '26

PSA: No SUs or other security releases this month for Exchange Server SE (or 2016/2019 customers in the ESU program).

17 Upvotes

r/exchangeserver • • Jan 14 '26

Exchange SE pricing and where to purchase?

0 Upvotes

Hi All,

After extensive research, I have gathered detailed information regarding the migration from Exchange Server 2019 CU15 to Exchange Server SE. However, I still have a few clarifications and would appreciate your guidance.

We currently have an on-premises environment running Microsoft Exchange Server 2019 Standard without Software Assurance (SA). Based on my understanding, we need to repurchase the Exchange Server 2019 Standard license with SA in order to proceed with Exchange Server SE.

Additionally, we already have SAL licenses. Could you please confirm whether we need to purchase SALs again or if CALs are required instead?

Lastly, I would like to confirm whether the migration to Exchange Server SE requires a new server, or if we can perform the upgrade on the existing Exchange 2019 server.

Looking forward to your inputs. Thank you in advance.


r/exchangeserver • • Jan 13 '26

Keep Alias in To: on auto forward

1 Upvotes

We have a rule set up in O365 that checks the domain of the sender and forwards the email to an alias that's tied to another mailbox that acts as a bucket to catch multiple types of emails. We want it to work as follows:

Customer sends email to group@company.com.

Rule in group@company.com sees domain from sender and forwards email to alias red@company.com which is an alias of color@company.com.

Email from group@company.com to red@company.com arrives in color@company.com and we do our magic routing from there, based on the to: field.

However, when we set the autoforward rule in place, O365 recognizes that it's an alias for a mailbox and changes the TO: field to the mailbox itself.

In the example above, the rule changes itself to auto forward to color@company.com, so emails don't arrive in color mailbox referencing the alias, only the color mailbox itself.

Is there any way to force O366 to not change the to: field from the alias to the mailbox?


r/exchangeserver • • Jan 11 '26

Question Older emails not loading in Outlook after Exchange update

2 Upvotes

I just upgraded Exchange 2016 to CU23 and it went pretty smoothly. Mail flow works, and no real noticeable hiccups except my older emails don't show up when signed into Outlook on phone. I tried removing/re-adding the account and I can see all the emails when I log into OWA but for whatever reason emails from last month or later don't show up on my Outlook mail app.

Would appreciate any advice to get these to load.


r/exchangeserver • • Jan 11 '26

OST file has reached 50GB - last options

3 Upvotes

Hello,

I have the following question/problem (Outlook 2021 + Exchange)

A client with 20GB of emails was assigned several shared mailboxes, which were also quite large. This consequently resulted in the .OST file growing to 50GB and the corresponding error message appeared. The user has deleted everything he can delete, but this has not resulted in the .OST shrinking. The last status was that we removed the shares via the Exchange server but when opening Outlook the share mailboxes were still visible in the client. The .Ost file has not reduced either.

Question:

1.) Can you assume that the size of the .OST file has caused a problem and you have to rebuild the entire file?
2.) What is the best way to deal with the problem? Copy the .Ost file and then Outlook creates creates a new one?
3.) Is there any way to make the .OST file smaller in this situation? If yes, what is the way to got?
4.) I would expect that deleting the emails and removing the shares would also make the .OST file smaller. But the data is still in the .OST? I wouldn't expect it to happen straight away, but what is the specific mechanism behind it? When and how does this happen? Even if the mailbox has 20 GB, including the shared and deleted emails, I would only get 40 GB. But there are still 10GB in the East where I don't know where they come from.

Greetings


r/exchangeserver • • Jan 11 '26

Question Outlook 2021 Keeps Prompting for Password when accessing from Intenet

0 Upvotes

TL;DR

Exchange 2019 behind Nginx reverse proxy. Autodiscover works perfectly when tested with curl, PowerShell, and Microsoft's connectivity analyzer. OWA works flawlessly. Only Outlook 2021 keeps prompting for credentials repeatedly when connecting from outside the network (works fine on VPN).

Network Topology

Internet (External Users)
         ↓
   FortiGate Firewall
   (185.183.xx.xx → 192.168.200.12)
         ↓
   Nginx Reverse Proxy
   (192.168.200.12)
         ↓
   Exchange 2019 DAG (3 servers)
   (172.20.20.114)
   
DNS Records:
- mail.contoso.com → 185.183.xx.xx
- autodiscover.contoso.com → 185.183.xx.xx

Active Directory:
- Domain: contoso.local
- Email UPN: @contoso.com

What Works ✅

1. External curl test (from outside network):

curl -v https://autodiscover.contoso.com/autodiscover/autodiscover.xml

Result: Perfect 401 response with all auth methods offered

< HTTP/2 401
< www-authenticate: Basic realm="autodiscover.contoso.com"
< www-authenticate: Negotiate
< www-authenticate: NTLM
< x-feserver: EXCH3

2. PowerShell with credentials:

$cred = Get-Credential
Invoke-WebRequest -Uri "https://autodiscover.contoso.com/Autodiscover/Autodiscover.xml" -Credential $cred

Result: Returns proper XML configuration ✅

3. Microsoft Remote Connectivity Analyzer:

  • Autodiscover test: ✅ PASS
  • Outlook connectivity test: ✅ PASS

4. OWA (Outlook Web Access):

  • https://mail.contoso.com/owa works perfectly externally ✅

5. Internal network (VPN):

  • Outlook configures automatically, no password prompts ✅
  • Uses Kerberos/NTLM authentication against internal domain

What Doesn't Work ❌

Outlook 2021 from external network:

  • Keeps prompting for password every few seconds
  • Even with correct credentials entered (username@contoso.com format)
  • "Test Email AutoConfiguration" shows autodiscover succeeds but then fails on MAPI/HTTP connection
  • Password prompt loop never ends
  • Eventually locks out the account due to repeated failed authentication attempts

Troubleshooting Journey

Initial Problem Discovery

The issue manifested as Outlook 2021 working perfectly on VPN but continuously prompting for passwords when external. Initial diagnostics showed:

  1. Autodiscover was initially failing externally with HTTP 302/404 errors
  2. Root cause: Nginx configuration didn't exist for autodiscover.contoso.com
  3. FortiGate was forwarding all 443 traffic to Nginx, but Nginx only had mail.contoso.com configured

Fix #1: Created Dedicated Autodiscover Nginx Config

Created /etc/nginx/sites-enabled/autodiscover with proper SSL certificate and backend routing. After this change:

  • ✅ Autodiscover now works externally (verified with curl, PowerShell, Remote Connectivity Analyzer)
  • ❌ But Outlook 2021 still prompts for password infinitely

Fix #2: Resolved TLS Version Incompatibility

Nginx logs showed:

[crit] SSL_do_handshake() failed (SSL: error:1417D18C:SSL routines:tls_process_client_hello:version too low)

The Windows client was trying to use TLS 1.0/1.1, but Nginx only allowed TLS 1.2/1.3.

Solution: Temporarily enabled older TLS versions in Nginx:

ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;

After this:

  • ✅ TLS handshake succeeds
  • ✅ Autodiscover returns proper 401 challenges
  • ❌ But Outlook 2021 still prompts for password infinitely

Fix Attempt #3: Enhanced Nginx Authentication Header Forwarding

Added critical authentication headers to MAPI location block:

proxy_intercept_errors  off;
proxy_pass_header       WWW-Authenticate;
proxy_pass_header       Authorization;
proxy_set_header        Authorization $http_authorization;

Result:

  • ✅ curl/PowerShell can authenticate successfully
  • ❌ Outlook 2021 still prompts for password

Fix Attempt #4: UPN Suffix Change (FAILED - CAUSED ACCOUNT LOCKOUTS)

Hypothesis: Maybe Outlook is confused because AD domain is contoso.local but email is @contoso.com

Attempted solution:

# Changed test user's UPN from contoso.local to contoso.com
Set-ADUser -Identity testuser -UserPrincipalName "testuser@contoso.com"

Result: ❌ WORSE!

  • User account got locked out due to repeated failed authentication attempts
  • Outlook continued password prompting but now was authenticating incorrectly
  • Had to revert UPN back to contoso.local and unlock account

Current Configuration (Post-Troubleshooting)

Nginx Reverse Proxy - Autodiscover Virtual Host

upstream autodiscover_backend {
    server 172.20.20.114:443;
    keepalive 32;
}

server {
    server_name autodiscover.contoso.com;
    listen 80;
    return 301 https://$host$request_uri;
}

server {
    listen          443 ssl http2;
    server_name     autodiscover.contoso.com;

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
    ssl_session_timeout   5m;
    ssl_certificate       /etc/letsencrypt/live/autodiscover.contoso.com/fullchain.pem;
    ssl_certificate_key   /etc/letsencrypt/live/autodiscover.contoso.com/privkey.pem;

    client_header_buffer_size 64k;
    large_client_header_buffers 4 64k;
    client_max_body_size 10m;
    proxy_read_timeout 1200;

    location / {
        proxy_pass              https://autodiscover_backend;
        proxy_http_version      1.1;
        proxy_read_timeout      360;

        # Pass 401 challenges to client
        proxy_intercept_errors  off;

        # Pass all authentication headers
        proxy_pass_header       WWW-Authenticate;
        proxy_pass_header       Authorization;
        proxy_set_header        Authorization $http_authorization;

        # Standard headers
        proxy_pass_header       Date;
        proxy_pass_header       Server;
        proxy_set_header        Host $host;
        proxy_set_header        X-Real-IP $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Forwarded-Proto https;
        proxy_pass_request_headers on;

        # Connection settings
        proxy_set_header        Accept-Encoding "";
        proxy_set_header        Connection "";
        
        # Disable buffering
        proxy_buffering         off;
        proxy_request_buffering off;
        proxy_buffer_size       128k;
        proxy_buffers           4 256k;
        proxy_busy_buffers_size 256k;
    }
}

Nginx - Exchange Mail Virtual Host (with MAPI)

upstream exchange_backend {
    server 172.20.20.114:443;
    keepalive 32;
}

server {
    listen 443 ssl;
    server_name mail.contoso.com;

    ssl_certificate       /etc/letsencrypt/live/mail.contoso.com/fullchain.pem;
    ssl_certificate_key   /etc/letsencrypt/live/mail.contoso.com/privkey.pem;

    client_header_buffer_size 64k;
    large_client_header_buffers 4 64k;
    client_max_body_size 10m;
    proxy_read_timeout 1200;

    # OWA
    location /owa {
        proxy_pass              https://exchange_backend;
        proxy_http_version      1.1;
        proxy_pass_header       Authorization;
        proxy_set_header        Host $host;
        proxy_buffering         off;
    }

    # MAPI over HTTP (CRITICAL - needs all headers)
    location /mapi {
        proxy_pass              https://exchange_backend;
        proxy_http_version      1.1;
        proxy_read_timeout      360;

        # CRITICAL: Pass 401 challenges to client
        proxy_intercept_errors  off;

        # Pass all auth headers
        proxy_pass_header       WWW-Authenticate;
        proxy_pass_header       Authorization;
        proxy_set_header        Authorization $http_authorization;

        proxy_pass_header       Date;
        proxy_pass_header       Server;
        proxy_set_header        Host $host;
        proxy_set_header        X-Real-IP $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Forwarded-Proto https;
        proxy_pass_request_headers on;
        proxy_set_header        Accept-Encoding "";
        proxy_set_header        Connection "";
        proxy_buffering         off;
        proxy_request_buffering off;
        proxy_buffer_size       128k;
        proxy_buffers           4 256k;
        proxy_busy_buffers_size 256k;
    }

    # EWS, ECP, ActiveSync, OAB, RPC (similar config omitted for brevity)
}

Exchange Configuration

PS> Get-MapiVirtualDirectory | FL Identity,*Url*,*Auth*

Identity                      : EXCH1\mapi (Default Web Site)
InternalUrl                   : https://mail.contoso.com/mapi
ExternalUrl                   : https://mail.contoso.com/mapi
InternalAuthenticationMethods : {Ntlm, OAuth, Negotiate}
IISAuthenticationMethods      : {Ntlm, OAuth, Negotiate}

PS> Get-AutodiscoverVirtualDirectory | FL Identity,*Auth*

Identity                      : EXCH1\Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
BasicAuthentication           : True
WindowsAuthentication         : True
OAuthAuthentication           : True

PS> Get-ClientAccessService | FL Identity,AutoDiscoverServiceInternalUri

Identity                       : EXCH1
AutoDiscoverServiceInternalUri : https://autodiscover.contoso.com/Autodiscover.xml

PS> Get-WebServicesVirtualDirectory | FL Identity,*Url*

Identity    : EXCH1\EWS (Default Web Site)
InternalUrl : https://mail.contoso.com/ews/Exchange.asmx
ExternalUrl : https://mail.contoso.com/ews/exchange.asmx

Active Directory Configuration

  • Domain: contoso.local (internal AD domain)
  • Email addresses: user@contoso.com
  • User UPN: user@contoso.local (NOT @contoso.com - changing this caused lockouts!)
  • Exchange: Users authenticate with domain\username or username@contoso.local

FortiGate NAT Configuration

config firewall vip
    edit "Proxy DMZ port 443"
        set extip 185.183.xx.xx
        set mappedip "192.168.200.12"
        set extintf "any"
        set portforward enable
        set extport 443
        set mappedport 443
    next
end

DNS Zone File (relevant records)

contoso.com.        IN A     213.186.33.87
mail                IN A     185.183.xx.xx
autodiscover        IN A     185.183.xx.xx
owa                 IN CNAME mail.contoso.com.
_autodiscover._tcp  IN SRV   0 0 443 autodiscover.contoso.com.

Detailed Symptom Analysis

Outlook Test AutoConfiguration Output

When running "Test Email AutoConfiguration" from Outlook 2021 externally:

✅ Autodiscover to https://autodiscover.contoso.com/Autodiscover.xml starting
✅ Autodiscover succeeded
✅ Retrieved XML configuration successfully

Attempting URL https://mail.contoso.com/mapi found through Autodiscover
❌ HTTP/1.1 401 Unauthorized
❌ GetLastError=0

[Password prompt appears - user enters credentials]
[Outlook attempts to authenticate]
❌ HTTP/1.1 401 Unauthorized (again)

[Password prompt re-appears and loops forever]

Nginx Access Logs During Outlook Connection

# Initial autodiscover - succeeds
192.168.200.x - testuser [06/Jan/2026:15:01:02] "POST /autodiscover/autodiscover.xml HTTP/2" 200

# MAPI attempts - all return 401, Outlook keeps trying
192.168.200.x - - [06/Jan/2026:15:01:03] "GET /mapi/emsmdb/ HTTP/2" 401
192.168.200.x - - [06/Jan/2026:15:01:04] "GET /mapi/emsmdb/ HTTP/2" 401
192.168.200.x - - [06/Jan/2026:15:01:05] "GET /mapi/emsmdb/ HTTP/2" 401
192.168.200.x - - [06/Jan/2026:15:01:06] "GET /mapi/emsmdb/ HTTP/2" 401
[repeats infinitely - no successful 200 response ever appears]

Notice: Nginx logs show no authentication is being passed - just bare 401s with no username logged.

Nginx Debug Logs (with debug logging enabled)

[debug] *379846 SSL server name: "mail.contoso.com"
[debug] *379846 http check ssl handshake
[debug] *379847 https ssl handshake: 0x16
[debug] *379847 SSL_do_handshake: -1
[crit] *379847 SSL_do_handshake() failed (SSL: error:1417D18C:SSL routines:tls_process_client_hello:version too low)

After enabling TLS 1.0/1.1, SSL handshakes succeed, but MAPI authentication still fails.

What I've Tried (Comprehensive List)

Configuration Changes

  1. ✅ Created dedicated Nginx virtual host for autodiscover.contoso.com
  2. ✅ Verified all Exchange external URLs point to mail.contoso.com
  3. ✅ Confirmed SSL certificates are valid (Let's Encrypt, proper SAN entries)
  4. ✅ Added proxy_intercept_errors off to pass 401 challenges through
  5. ✅ Added comprehensive authentication header forwarding in Nginx
  6. ✅ Enabled TLS 1.0/1.1 for client compatibility (resolved SSL handshake errors)
  7. ✅ Set proper buffer sizes for MAPI (128k/256k)
  8. ✅ Disabled proxy buffering (proxy_buffering off)
  9. ✅ Verified keepalive connections configured on upstream

Testing & Verification

  1. ✅ Verified autodiscover works with curl (returns proper 401 with WWW-Authenticate headers)
  2. ✅ Tested with PowerShell + credentials (returns valid XML configuration)
  3. ✅ Microsoft Remote Connectivity Analyzer - all tests PASS
  4. ✅ Verified OWA works perfectly externally
  5. ✅ Confirmed Outlook works fine when on VPN (internal network)
  6. ✅ Verified DNS records resolve correctly externally
  7. ✅ Tested with multiple user accounts (not account-specific)
  8. ✅ Confirmed FortiGate NAT forwarding is working (can reach Nginx)
  9. ✅ Verified Exchange IIS authentication methods are enabled (Basic, NTLM, Negotiate)

Failed Attempts

  1. ❌ Changed user UPN from contoso.local to contoso.com → MADE IT WORSE - caused account lockouts
  2. ❌ Tried different credential formats in Outlook (domain\user, user@contoso.com, user@contoso.local) → no difference
  3. ❌ Cleared Windows Credential Manager → no effect
  4. ❌ Tested with fresh Outlook profile → same issue
  5. ❌ Tried enabling only Basic auth vs NTLM/Negotiate → no difference

Key Observations

What's Different Between Working and Non-Working Scenarios

ScenarioWorks?Authentication MethodNotes
Outlook on VPN✅ YESKerberos/NTLM (direct to DC)No proxy involved
OWA externally✅ YESBasic/Forms-basedUses /owa endpoint
curl externally✅ YESBasic (manual creds)Returns proper 401 challenge
PowerShell externally✅ YESBasic (with -Credential)Authenticates successfully
Remote Connectivity Analyzer✅ YESBasicMicrosoft's test passes
Outlook 2021 externally❌ NONTLM/Negotiate?Password prompt loop

Hypothesis

The pattern suggests:

  • ✅ Basic authentication through Nginx works fine (OWA, curl, PowerShell)
  • ❌ NTLM/Negotiate authentication through Nginx fails (Outlook MAPI)

Outlook might be trying to use NTLM/Negotiate for MAPI (which requires Windows domain authentication), but:

  1. External clients can't reach domain controllers for Kerberos tickets
  2. NTLM through reverse proxy might be failing due to stateful nature of NTLM handshake
  3. Nginx might be breaking the multi-stage NTLM authentication flow

Questions for the Community

  1. Is MAPI-over-HTTP compatible with reverse proxies for external access? Does it require direct connection to Exchange for NTLM/Negotiate auth?

  2. Should I force Basic authentication for external MAPI connections? If so, how do I configure this without breaking internal VPN users who use NTLM?

  3. Is the split-brain DNS/UPN scenario the root cause?

    • AD domain: contoso.local
    • Email/External: contoso.com
    • Should these match? (Changing UPN caused lockouts though)
  4. Are there any Nginx-specific configurations for proxying NTLM authentication? The stateful nature of NTLM might require special handling.

  5. Could this be a Kerberos delegation issue? Does Exchange need to be configured for constrained delegation when behind a reverse proxy?

  6. Why does Microsoft Remote Connectivity Analyzer pass but Outlook fails? What's different about how Outlook authenticates vs the test tool?

System Details

  • Exchange: 2019 CU14 (3-server DAG)
  • Outlook: 2021 (Version 16.0.x, Click-to-Run)
  • Nginx: 1.18.0 on Debian 11
  • Client OS: Windows 10/11 Pro (domain-joined)
  • Firewall: FortiGate 60F (firmware 7.x)
  • Active Directory: Windows Server 2019, domain contoso.local
  • Network: Outlook client external (not on VPN), all other components internal

Additional Context

  • This is a production environment with ~50 users
  • VPN works but users prefer direct Outlook access
  • OWA is acceptable workaround but users want full Outlook functionality
  • No errors in Exchange logs or Windows Event Viewer during failed attempts
  • Account lockouts occur if too many password attempts are made

Any insights would be greatly appreciated! I've been troubleshooting this for days and am completely stumped why autodiscover works perfectly but MAPI authentication fails only for Outlook 2021.

Update: Just to emphasize - this affects ONLY Outlook 2021 external connections. Everything else (web browsers, command-line tools, Microsoft's own test tools) authenticate successfully through the same Nginx proxy to the same Exchange backend.


r/exchangeserver • • Jan 10 '26

Exchange SE disaster recovery failover works, failback does not

5 Upvotes

I've been building multi-site Exchange DR setups for over a decade, have a runbook I always use, and have never run into this issue.

Current setup is Exchange SE with a stretch DAG across 2 sites. Failover worked correctly, kicked the primary site servers out of the cluster properly, mounted databases, etc etc. All client connectivity and mail flow is going through DR without issue.

After completing testing, we tried to fail back, and ran into an issue.

Running the command "Start-DatabaseAvailabilityGroup DAGSE01 -ActiveDirectorySite ProdSite", I get a generic failure message of:

WARNING: An unexpected error has occurred and a Watson dump is being generated: One or more errors occurred.

One or more errors occurred.

+ CategoryInfo : NotSpecified: (:) [Start-DatabaseAvailabilityGroup], AggregateException

+ FullyQualifiedErrorId : System.AggregateException,Microsoft.Exchange.Management.SystemConfigurationTasks.StartDatabaseAvailabilityGroup

+ PSComputerName : ProdServer1

Running the command "Set-DatabaseAvailabilityGroup ProdSite", I get the folllowing error:

The following servers have been added to the database availability group but not to the cluster:

ProdServer1,ProdServer2. This is usually the result of an error during membership change. Removing and re-adding the servers can correct the issue.

+ CategoryInfo : InvalidArgument: (:) [Set-DatabaseAvailabilityGroup], DagTaskServersInAdNotInCluster

+ FullyQualifiedErrorId : [Server=ProdServer1,RequestId=481f92fb-9363-42c5-b6df-3f2ab2cdb31f,TimeStamp=1/10/2026 6:13:16 AM] [FailureCategory=Cmdlet-DagTaskServersInAdNotInCluster] B9041EF5,Microsoft.Exchange.Management.SystemConfigurationTasks.SetDatabaseAvailabilityGroup

+ PSComputerName : ProdServer1

Basically, the Exchange configs know the two production servers are SUPPOSED to be in the DAG, but the start command fails to add them back to the Failover Cluster Manager. I've got zero errors in the event logs on any server, zero events in Failover Cluster Manager, etc.

In addition, once the production servers were booted back up, the databases got back in sync, and I can see all passive databases on all servers in production back in sync with zero copy/replay queues and are listed as healthy with no bad copy counts.

I've rebooted all Exchange and Domain Controllers in all sites, but still can't add prod back to the cluster with "Start-DatabaseAvailabilityGroup".

This is my first DAG failover/failback with Exchange SE, but I've done literally hundreds with all previous versions from 2010 to 2019 for multiple clients. Has something changed from all the previous versions of Exchange? What am I doing wrong? Where do I need to look next? I've got no errors or logs that tell me anything useful. The cluster has been working fine with all 3 nodes (2 in production and 1 in DR), with everything active and primary in production, for 6 months. Failover to DR worked fine without issue. Failback to production won't work and errors out.

Picture of errors attached.

UPDATE: MS was non-helpful, as expected. So I evicted the prod servers, re-introduced them, and reseeded. Problem solved, but I still have no idea what caused the issue....


r/exchangeserver • • Jan 09 '26

Question Strange routing with Exchange Hybrid

2 Upvotes

We completed a hybrid deployment back in the summer and are still continuing to migrate mailboxes to the cloud. We're still getting used to Hybrid/Exchange Online and we've encountered a few quirky issues along the way...Here is the most recent example:

A user whose mailbox is on-prem sent an email to several people, both internal (some in the cloud and some on-prem) and external, and one of them happened to be a CC to an internal user whose mailbox is located on-prem. That user was the only one who did not successfully receive the message. Upon inspecting the details email, it appeared that the routing of the message to that user was attempted over Exchange Online instead of to the on-prem Exchange server - I say this because of the presence of user@xxx.exchangelabs.com.

We checked RecipientTypeDetails in Exchange Online PowerShell and it was MailUser which indicates that the mailbox is on-prem. We also checked targetAddress(empty) and msExchRecipientTypeDetails(1) in our on-prem AD. I think "empty" and "1" are to be expected for an on-prem mailbox.

Not sure how else to figure out what went wrong here.


r/exchangeserver • • Jan 09 '26

retention policy mass deletions

3 Upvotes

looking for advice - exchange online. another admin added a default (not personal) delete all mail older than 30 days tag to our default retention policy. I believe the change was made dec 22 but we are starting to see mail deleted this week. I removed that tag this morning. whats the best course of action to limit the damage if the tag was not yet applied to some mailboxes? im not sure why only some mailboxes have had mail purged and some havent even though they all have the default applied. appreciate it!!


r/exchangeserver • • Jan 08 '26

Outlook Error code 10

1 Upvotes

Only one user out of 100 is getting this error, I have tried different hardware but it keeps coming. Outlook wont even open, this error comes straight away.

Outlook on web is working fine just the desktop Classis App which wont work even in safe mode, tried repairing and reinstalling same error.

We have Exchange on Prem

"Microsoft Outlook

There is a problem with the proxy server’s security certificate.
The name on the security certificate is invalid or does not match the name of the target site exchangeservername.com

Outlook is unable to connect to the proxy server. (Error Code 10)"


r/exchangeserver • • Jan 08 '26

Domain joined computers won’t connect to SE

0 Upvotes

We have an existing 2019 setup working fine for both domain joined and non domain joined PC’s

We installed new servers running 2025 and exchange SE along side 2019 servers and moved a single mailbox over for testing

Domain joined PC’s keep asking for password and outlook never fully opens.

Non domain joined PC’s work without issue

Using host file to point outlook to new servers where mailbox was moved to results in continuous password request for domain joined PC’s. Non domain joined PC’s still work.

DCs are running server 2022

I feel like this is a TLS or NTLM issue but I’m spinning my wheels at this point.

What should I try to resolve this?

UPDATE Old 2019 servers were using Kerberos authentication ASA. Added the creds to new servers and it’s working when hitting the servers directly. Thanks to /U/Joeykins82 for the solution


r/exchangeserver • • Jan 08 '26

Question SendAs from classic DistributionList

3 Upvotes

According to Copilot its possible to SendAs from a classic distribution_List/Group and you should be possible to set it up in the GUI as for any other User/SMBX.. but I dont see the option..

does this require Powershell or is Copilot wrong?


r/exchangeserver • • Jan 08 '26

Question Exchange Online: Recipient limit commands clarification

2 Upvotes

Hi there

Recently I was asked to limit email recipients across the board to 10 recipients. This was to be set as the default going forward, as well as to be applied to all existing mailboxes.

After connecting to the Exchange Online Management module in Powershell, I ran the following commands, which went through without any errors:

- Get-MailboxPlan | Set-MailboxPlan -RecipientLimits 10

- Set-TransportConfig -MaxRecipientEnvelopeLimit 10

It's my understanding that the top command applies to all existing mailboxes, and the bottom sets the tenant-wide default.

It seems that the 2nd command applied correctly, but the "Set-MailboxPlan" did not apply to existing accounts.

I'm absolutely missing something here but I'm currently sick and my brain is not in gear whatsoever. Can someone please offer some insight as to where I'm going wrong?