Viral Rathod Exchange Server 2016 Blog

Microsoft Exchange Server Blog

  • Click here to Register for Experts-Exchange Account

  • My Experts Exchange Profile

  • Disclaimer

    All information is provided "AS IS" with no warranties, and confer no rights, and as such you perform at your own risk.

    NOTE: You should always make a backup of your server or export the registry before making any changes to it.

Archive for the ‘Exchange Server 2013 Posts’ Category

Outlook 2016 taking an extremely long time for the autodiscover to detect the account settings

Posted by viralr on December 5, 2016

Outlook 2016 taking an extremely long time for the autodiscover to detect the account settings,

Outlook 2016 for Windows will attempt to resolve https://autodiscover.yourdomain.com/autodiscover/autodiscover.xml 11 times with a 30 second+ wait time between each attempt before discovering the CNAME record configured on your domain, which points to autodiscoverredirect.yourdomain.com. This causes the initial autodiscover process to take 20-30 minutes.

Unlike previous versions of Outlook, Outlook 2016 does not allow manual configuration of server settings, and is instead solely dependent on the autodiscover process.

There are two workarounds available:

1. Wait 20-30 minutes for the autodiscover process to complete.

2. Add the below registry key, The below registry settings will force Outlook to go directly to the HTTP redirection method and allow the account to be setup nearly instantly.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover]
“ExcludeHttpsRootDomain”=dword:00000001
“ExcludeHttpsAutoDiscoverDomain”=dword:00000001

Hopefully Microsoft will provide an update to resolve this issue soon.

Please feel free if you have any question and I will be happy to help.

Advertisements

Posted in Exchange Server 2013 Posts | Leave a Comment »

Exchange 2013 Database Removal Error: “This mailbox database contains one or more mailboxes”

Posted by viralr on December 5, 2016

Exchange 2013 Database Removal Error: “This mailbox database contains one or more mailboxes”

During exchange 2013 Uninstallation : The following error appears when uninstalling:

Error:Uninstall can’t continue. Database Mailbox Database 2067414591 : This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all public folder mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -PublicFolder. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>. It was running the command ‘Remove-MailboxDatabase ‘CN=Mailbox Database 2067414591,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=UnitedBagSales,DC=local’ -whatif’.For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnwillingToRemoveMailboxDatabase.aspx

Cause :

The Exchange Installations creates several “System Mailboxes” (Arbitration,Monitoring and Discover) during installation that you need to delete before you can uninstall your last Exchange 2013 Server.This are,

DISCOVERY MAILBOX
DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}

MONITORING MAILBOXES
HealthMailbox62256620620346798029c55bfe0fcc5d
HealthMailboxb67c72c285f54c30bad37dd37eec361a
HealthMailbox721771958fa64a53aa78527c02caf55b
HealthMailbox995793b82c2c4a14b6173e54371179ec
HealthMailboxc8603cb9bb41442e8b402db42f93dc16

ARBITRATION MAILBOXES
SystemMailbox{1f05a927-c403-4250-9f07-c5e43605c1ac}
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
Migration.8f3e7716-2011-43e4-96b1-aba62d22913

Solution :

Since you cannot see these in the Exchange Admin Center, you need to launch Exchange Management Shell (EMS) the commands are,

For Discovery Search Mailbox :

To find discovery search mailbox,

Get-Mailbox -Resultsize Unlimited -Filter {RecipientTypeDetails -eq ”DiscoveryMailbox”

OR

Get-Mailbox-Filter { RecipientTypeDetails -eq “DiscoveryMailbox” }

Run the following command to delete the default discovery mailbox.

Remove-Mailbox “DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}”

To find arbitration system mailbox,

Get-Mailbox -Arbitration

OR
Get-Mailbox -Arbitration -Database DataBase1

(-database option to check specific database for arbitration mailbox)

To remove arbitration mailbox,

Get-Mailbox -Arbitration -Database DataBase1| Remove-Mailbox -Arbitration -RemoveLastArbitrationMailboxAllowed

Please feel free to get back if you have any questions and i will be happy to help.

 

 

Posted in Exchange Server 2013 Posts | Leave a Comment »

Powershell command to track emails sent to specific user email address

Posted by viralr on December 5, 2016

Suppose you have an end user saying that he is missing a message from an external sender in this case what you will do to track email from exchange server for that user ?

Well you can use following PowerShell command to track emails sent to your end user

Condition 1 – Get all failed/undeliverable emails:

Get-Messagetrackinglog -Recipients: team@microsoft.com -EventID “FAIL” -Start “5/4/2011 9:00:00 AM” -End “5/10/2011 5:00:00 PM” |ft Timestamp, Source, Sender, Recipients, MessageSubject >>C:output.txt

Condition 2 – Get all success emails

Get-Messagetrackinglog -Recipients: team@microst.com -EventID “RECEIVE” -Start “5/4/2011 9:00:00 AM” -End “5/10/2011 5:00:00 PM” |ft Timestamp, Source, Sender, Recipients, MessageSubject >>C:output.txt

This will give you the output in the form:
Timestamp Source Sender Recipients MessageSubject

Source “SMTP” means it’s an external email and “STOREDRIVER” means processed internally

Hope this help you to track your user email, if any question get back to me and I will be happy to help.

Posted in Exchange Server 2007 Posts, Exchange Server 2010 Posts, Exchange Server 2013 Posts | Leave a Comment »

Exchange 2013- Blank ECP / OWA screen, event ID 15021 HttpEvent in system event log

Posted by viralr on February 20, 2015

Exchange 2013- Blank ECP / OWA screen, event ID 15021 HttpEvent in system event log : An error occurred while using SSL configuration for endpoint 127.0.0.1:443 :

When you log in to OWA or EMC using a browser, you may see a blank screen after you enter your credentials. You may also notice that the event log shows event 15201:

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

empty page

This can be caused by an incorrect certificate being assigned to the port. To fix this error,

  • Open the Command Prompt
  • Run – netsh http show sslcert

InvalidCert

  • Copy and save content on notepad or take a screenshot of port 443’s certificate hash and application ID because we will need it.
  • export content
  • Delete the certificate causing errors (Given on Screen Shot)
  • netsh http delete sslcert ipport=0.0.0.0:444
  • delete-certificate-causing-errors
  • Read out the certificate hash from the certificate

certificate-hash

  • Assign new certificate: netsh http add sslcert ipport=0.0.0.0:444 certhash=XXXXXX  appid=”{XXXXXXX}”

    add cert

  • Do IISRESET OR REBOOT the server
  • Good luck!

Posted in Exchange Server 2013 Posts | Leave a Comment »

This message is too large to send. To be able to send it, make the message smaller, for example, by removing attachments.

Posted by viralr on May 29, 2014

Unable to send large attachments and get this bounce back:

From: postmaster@MYDOMAIN.LOCAL [mailto:postmaster@MYDOMAIN.LOCAL]
Sent: Wednesday, May 28, 2014 4:14 PM
To: Mathews, John
Subject: Undeliverable: FW: Re: Remaining
Delivery has failed to these recipients or groups:
user@mydomain.com
This message is too large to send. To be able to send it, make the message smaller, for example, by removing attachments.

Diagnostic information for administrators:
Generating server: EXCHANGESERVER.MYDOMAIN.LOCAL
user@mydomain.com
#< #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization> #SMTP#

To troubleshoot this issue use the following steps:-

The email size restriction for user mailbox will be applied in the following order

  1. Global Transport configuration settings
  2. Send connector size restriction
  3. Receive connector size restriction
  4. In the user mailbox properties of send and receive size limit

Please use the below command to check the limts,

To verify global transport settings all Hub Transport servers in the Exchange Organization :-

Get-TransportConfig | ft MaxSendSize, MaxReceiveSize

To modify the sending and receiving email message size to 100 MB in the global Tranport configuration

Set-TransportConfig –MaxSendSize 20MB –MaxReceiveSize 100MB

To verify and modify the send connector size,Send connector are used to send emails out of the exchange organization and the default size is 10 MB.

Get-SendConnector | ft name, MaxMessageSize

Set-SendConnector <Connector Name> –MaxMessageSize 50MB

To verify and modify the receive connector size,Receive connector are used to receive emails from the internet or application and the default size is 10 MB.

Get-ReceiveConnector | ft name, MaxMessageSize

Set-ReceiveConnector <Connector Name> –MaxMessageSize 50MB

The send and receive email message size can be granular controlled in the user mailbox properties. To verify the and modify the size

Get-mailbox | ft Name, MaxSendSize, MaxReceiveSize

Set-Mailbox “test” –MaxSendSize 20MB –MaxReceiveSize 20MB

 

——————————————————————————————————————————————-

There are various error message which is listed below will occur if the value is not configured as per the above rule.

Error 1:

The following recipient(s) could not be reached:

test@test.com on 01/15/2014 3:54 PM

This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.

<mail.com #5.2.3 smtp;450 5.2.3 Msg Size greater than allowed by Remote Host>

Error 2:

The following recipient(s) could not be reached

test@test.com  on 01/15/2014 3:54 PM

This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.

<mail.com #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender>

Error 3:

Delivery has failed to these recipients or distribution lists:

administrator@mail.com
This message exceeds the maximum message size allowed. Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller — by removing attachments, for example — and try sending it again, or provide the following diagnostic text to your system administrator.

Diagnostic information for administrators:
Generating server: MBX01.mail.com
administrator@mail.com
#550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender ##

Error 4

OWA Error – The request filter module is configured to deny a request that exceeds the request content length”

Error 5

EWS Error –   Email is goes in drafts or never leaves the outbox and the client receives an “exceeded the size limit”

Posted in Exchange Server 2013 Posts | Leave a Comment »

Internet Explorer 11 Only Allows “Use the light version of Outlook Web App”

Posted by viralr on February 17, 2014

If you upgraded to Windows 8.1 and tried to access Outlook Web App with the new Internet Explorer 11, you probably noticed that the “Use the light version of Outlook Web App” checkbox is checked and disabled on the login page:

owa-light

That means that IE11 is willing to render only the basic version of OWA which was originally designed to target legacy browsers. This is quite embarassing, because IE11 is a really modern browser even in the preview! The solution is to force IE to render OWA in compatibility mode. You can add the site to the compatibility list in the Tools –> Compatibility View Settings dialog: Click Add button

Compability

compatibility-view-settings

IF the above settings didn’t resolve the issue then try to add your OWA URL to the list of sites in the Intranet Zone in the Tools –> Internet Options –> Security –> Local intranet –> Sites –> Advanced dialog.

According to some forum posts, the same issue arises with Office 365 and some popular websites like GitHub as well.

Ref : http://gyorgybalassy.wordpress.com/2013/07/05/use-owa-in-full-version-with-ie11/

Posted in Exchange Server 2010 Posts, Exchange Server 2013 Posts | Leave a Comment »

Exchange Server 2013

Posted by viralr on September 14, 2013

What’s New In Exchange 2013 –

What’s New In Exchange 2013 Video From Trainsignal :-

Installing Exchange Server 2013 –

Exchange 2013 Installation Training Video From Trainsignal :-

Transition from Exchange 2003 to Exchange 2010 to Exchange 2013 –

Transition from Exchange 2003 to Exchange 2010 to Exchange 2013 Video from Trainsignal :-

Exchange 2010 to Exchange 2013 Migration Docs from petenetlive :-

Migration From Exchange 2010 to Exchange 2013 Part 1

http://www.petenetlive.com/KB/Article/0000788.htm

Migration From Exchange 2010 to Exchange 2013 Part 2

http://www.petenetlive.com/KB/Article/0000789.htm

Posted in Exchange Server 2013 Posts | Leave a Comment »