Office 2016 Outlook and Exchange Server, without Autodiscovery

Create a local XML redirect file:

<?xml version="1.0" encoding="utf-8" ?>
<Autodiscover xmlns="">
  <Response xmlns="">

Create registry key:


Name, with value: C:\Autodiscover\autodiscover.xml (path to xml file)

It only works if Outlook Anywhere and Outlook Web App has already been published to the Internet. And of course, you must replace URL with your own.

Renewing SBS2011 Exchange Self-Signed Certificate

In SBS2011:

  1. Open Exchange Management Console > navigate to Server Configuration and review the Certificates in the right panel
  2. Identify the certificate that has expired (take note of the subject name and the services)
  3. Start ExMngmtnShell as Administrator
  4. type Get-ExchangeCertificate to list the installed certificates
  5. Match the certificate to the expired certificate (using subject the name and services) from the Console then copy the associated thumbprint
  6. Type Get-ExchangeCertificate –Thumbprint INSERTTHUMBPRINTHERE | New-ExchangeCertificate
  7. Remove the old expired certificate either from the Console or from the Shell using Remove-ExchangeCertificate -Thumbprint INSERTTHUMBPRINTHERE

Note: I had to restart the server for the certificate to take effect.

Exchange 2010: 923372036854775766 copy queue lenght and orphaned mailbox server

An error occurred while trying to validate the specified database copy for possible activation:

Move-ActiveMailboxDatabase DAG-OFFICE -ActivateOnServer DAG-200

Database copy ‘DAG-OFFICE’ on server ‘’ has a copy queue length of 9223372036854725486 logs, which is too high to enable automatic recovery. Try this:

Move-ActiveMailboxDatabase DAG-OFFICE -ActivateOnServer DAG-200 -SkipHealthChecks -SkipActiveCopyChecks -SkipClientExperienceChecks -SkipLagChecks -MountDialOverride:BESTEFFORT

Exchange 2010 (after SP3): OWA error, exppw.dll, event ID 2280

I would suggest you perform the following steps to troubleshoot this issue:

  1. Remove the exppw.dll entry from applicationhost.config (c:\windows\system32\inetsrv\config)

Then registered the exppw.dll by following the below steps:

  1. IIS Manager -> Select the Server Name in the left Pane -> Open Modules in the middle pane
  2. Click on ‘Configure Native Modules’ in the right pane -> Click the button ‘Register’ -> Type the name as ‘exppw’
  3. Browse and select the path of above file as: c:\Programme Files\Microsoft\Exchange Server\V14\Client Access\OWA\Auth\exppw.dll

After registered:

  1. Made sure that the ‘exppw.dll’ is only present at OWA level and not at any of the top hierarchy
  2. Then ensured for this module in OWA (VDir), ‘Module Type’ is set to ‘Native’ and ‘Entry Type’ is ‘Local’
  3. Run IISreset /noforce

SBS POP3 connector error: invalid header fields

If you are using the POP3 Connector on Windows SBS 2008, you may encounter this error in the event log:

One or more (5) e-mail messages in the POP3 mailbox account ‘’ on the POP3 server ‘’ have invalid header fields. Because of this, the messages cannot be delivered to the Exchange Server mailbox ‘’ in Windows Small Business Server. The messages are still on the POP3 server. To resolve this issue, connect to the POP3 mailbox account, and then manually retrieve or delete the messages.

By default the POP3 connector will stop processing new messages after 5 protocol errors so once this happens, you will not receive any email.

Increase the MaxProtocolErrors from 5 to something bigger:

Set-ReceiveConnector -identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -MaxProtocolErrors 300

Next step: remaining messages to be downloaded, but the messages with invalid headers will still not be downloaded.
To fix this:

Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain