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.

Best anti spam filtering software for Microsoft Exchange Server 2016

Posted by viralr on January 8, 2017

Best anti spam filtering software for Microsoft Exchange Server 2016,

tmp_3430-fusion-logo-h200-1975917006

I would recommend you to try, Vamsoft ORF Fusion which is a great piece of Anti-Spam software and in this software, you can set the Sender Blacklist to Blacklist ALL Addresses except the ones you specify, which will be the list of the 520 domains that you want to accept.

Once Blacklisted, the emails can be rejected (or whatever you choose to do with them) but the ones that pass the Blacklist check will be allowed through.

You can install a 42-day trial of the software to see if it does what you want it to do and then if you’re happy with it, it’s a relatively low-cost purchase and you don’t have to renew it annually, although you can to keep the software up-to-date with new releases, but it won’t stop working if you don’t renew.

Reference :-
https://vamsoft.com/

Posted in Exchange Server 2003 Posts | Leave a Comment »

Exchange server 2016 / Exchange server 2013 error OWA / ECP :-( something went wrong

Posted by viralr on December 28, 2016

Issue :-

You have successfully installed Microsoft Exchange Server 2016 or Microsoft Exchange Server 2013. The installation process may have failed or been interrupted at some stage and then resumed and finally completed successfully. However, when you try to access Exchange Control Panel (ECP) or Outlook Web App (OWA), you receive the following error message:

“500 : – ( something went wrong”
The server operation timed out. Please try again later.

3103337

Cause :-
This issue occurs if SharedWebConfig.config is missing from either of the following locations:

C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess

Resolution:

Copy sharedWebConfig.config file from C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy directory.
Past sharedWebConfig.config file to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess directory

OR Vice Versa
after copy do IISreset /noforce

Reference:

https://support.microsoft.com/en-us/kb/3099532

Posted in Exchange Server 2003 Posts | Leave a Comment »

How to Disable IPv6 autoconfiguration in Windows servers

Posted by viralr on December 28, 2016

How to Disable IPv6 autoconfiguration in Windows server (Disabling IPv6 Stateless Autoconfiguration) :-

Stateless autoconfiguration of IPv6 allows the client device to self configure it’s IPv6 addreess and routing based on the router advertisements.

So to Disable auto configuration of IPv6 address execute following command,

First to check the network interface on which ipv6 is autoconfiguration execute following command,

netsh interface ipv6 show interface

Then finally to Disable ipv6 auto configuration execute following command
netsh interface ipv6 set interface “Local Area Connection” routerdiscovery=disabled

Please refer following article if you need more information about Disabling Stateless configuration.

http://www.excaliburtech.net/archives/192

Posted in Exchange Server 2003 Posts | Leave a Comment »

Exchange 2016 install Error: Database is mandatory on User Mailbox

Posted by viralr on December 16, 2016

Exchange 2016 install Error: Database is mandatory on User Mailbox

Error:
The following error was generated when “$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
{
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
}
” was run: “Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.

Resolution: The above error “Database is mandatory on UserMailbox” states that “one of the system mailbox on the server is not having a Database” so to check which system mailbox is not having database please use below command

Get-mailbox -Arbitration | Format-Table Name, ServerName, Database -Auto

tmp_3325-3-1-1719779036

As you can see ,The command will display orphand mailbox which does not have database

Also see the below command which shows system mailbox on decommissioned server ‘viral-mbx02’

[PS] C:\Windows\system32>Get-Mailbox -Arbitration |ft Name, Servername

Name ServerName

—- ———-

SystemMailbox{1f05a927-0695-4348-bb62-d2369dcb23d5} viral-mbx01

FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 viral-mbx01

SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} viral-mbx02

SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} viral-mbx02

Migration.8f3e7716-2011-43e4-96b1-aba62d229136 viral-mbx02

Now we will disable all of those mailboxes which present on viral-mbx02 server since viral-mbx02 server is already decommisioned long ago.

Now to disable that mailbox use below command

Disable-Mailbox “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” -Arbitration -DisableLastArbitrationMailboxAllowed
tmp_3325-image0022108351992

Now to remove database from server which is already decommissioned use following commands,

Get-MailboxDatabase -Server viral-mbx02

Name Server Recovery ReplicationType

—- —— ——– —————

Mailbox Database 0912423282 viral-MBX02 False None

[PS] C:\Windows\system32>Remove-MailboxDatabase “Mailbox Database 0912423282”

 
Following article contains more info and fix to disable arbitration mailboxes.
http://msexchangeguru.com/2013/01/02/exchange-2013-error/

 

 

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

Posted in Exchange Server 2016 Posts | Leave a Comment »

Don’t Install Exchange Server 2016 on Windows Server 2016 For Now Due to Stability Issues

Posted by viralr on December 11, 2016

Don’t Install Exchange Server 2016 on Windows Server 2016 For Now Due to Stability Issues,

Since the release of Exchange Server 2016 Cumulative Update 3 (CU3), which added support for installing Exchange 2016 onto Windows Server 2016 servers, there’s been a series of reports in support forums and blog comments about errors that customers are seeing.

Now Microsoft has acknowledged that there is in fact a known issue, and there is no current workaround for it.

Please refer following article for more information about this bug.

http://exchangeserverpro.com/dont-deploy-exchange-server-2016-windows-server-2016-now-due-stability-issues/

 

 

Posted in Exchange Server 2016 Posts | Leave a Comment »

How to reset forgot administrator password in Hyper-V Server 2012 R2 ( bare metal)

Posted by viralr on December 5, 2016

How to reset forgot administrator password in Hyper-V Server 2012 R2 ( bare metal)

Please try steps given on following article, this trick works on all versions of Windows ,the same is tested on windows 10 / winows server 2016.

It hardly takes 5 minutes.

http://richsitblog.com/index.php/2015/06/21/resetting-forgotten-windows-admin-password/

Posted in Exchange Server 2003 Posts | Leave a Comment »

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.

Posted in Exchange Server 2013 Posts | Leave a Comment »

SBS Failed to start listening (Error: 10049). Binding: 10.100.1.10:143.

Posted by viralr on December 5, 2016

After Migration to Exchange 2013 you have some errors in eventlog.

Event ID : 1019
Failed to start listening (Error: 10049). Binding: 10.100.1.10:143

Solution :
SBS only supports 1 NIC at a time. Exchange was trying to communicate with both NIC’s thus it could not start listening on the 2nd one.

So basically this issue occurs if the IMAP service is not configured to listen on a local IP address or if the receive connectors for the Transport service cannot bind to an IP address.
The IMAP Service needs to bind itself to one of the local Adapters on the exchange server.

To resolve this issue, configure the IMAP service to listen on a local IP address, and configure the receive connector to listen on all IP addresses.

“netstat -a” will show you current listening ports bound to IP/interface.
This example sets the IP address and port for communicating with Exchange by using IMAP4 with no encryption or TLS encryption.

Set-ImapSettings -UnencryptedOrTLSBindings IPaddress:Port

After you’ve set the IP address and port settings for IMAP4, you must restart the IMAP4 service for the settings to take effect.

The fix available on following article

https://technet.microsoft.com/en-us/library/dd789669(v=exchg.80).aspx

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

Posted in Exchange Server 2003 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 »