In your Exchange environment, whether it is Exchange 2010 or 2013, you might come across an error that when you
Advertisements
Category: Exchange 2013
Exchange 2013 – OWA/ECP defaults to Exchange 2010
Here is a quick tip for Exchange Admins working in an Exchange 2010/2013 Coexistence Environment. When you launch the Exchange
Exchange 2013 – ECP Login Error 400
In your Exchange 2013, you have setup everything and now you want to start administering your new environment, upon launching
Exchange 2013 – Mailbox Migration Error
In your Exchange 2010/2013 environment, you might start moving mailboxes, however when you try creating a batch and then click
Exchange 2016: Check forwarders set on mailbox
As an Exchange Admin, you probably receive requests to set forwarding on a mailbox. This could be for many reasons,
Exchange 2010/2013: The Internal Transport Certificate Cannot be Removed
In Exchange 2010 or 2013, you might have issued a renewal of your SSL certificate. In the Exchange Management Console
Exchange 2010 – Event ID 108 Outlook Web App couldn’t connect Exchange Web Services due to a configuration error. Response code = “500”
In Exchange 2010, the following error logs quite often in the application log but no noticeable impact to users. The
Exchange (All Versions) – Bulk update Accepted Domains
In Exchange, you might have a number of accepted domains and manually editing the information can be a daunting task.
Kernel Migrator for Exchange
Many attempts have been there to simplify the Exchange migration process. That is why many Exchange migration solutions are there
Exchange 2016 – Mailbox: Inbox Rules
In any Exchange Environment, your users will create Inbox Rules on there mailboxes. For them it is like a filing
Exchange – My top most used PowerShell commands
As an Exchange Admin, you might have your saved list of commands you use on a daily or weekly basis.
Exchange 2010/2013 – Setting POP/IMAP X509CertificateName when using a WildCard Certificate
Many organizations make use of a WildCard Certificate in their Exchange Environment. This makes sense when you have quite a
Exchange 2016 – Why you cannot add an Exchange 2013 Server to an Exchange 2016 DAG
Many times the question has been asked, can I not add my Exchange 2010 Server to my Exchange 2013 DAG
Exchange 2016 – Back Pressure
In Exchange, be it Exchange 2010, Exchange 2013 or Exchange 2016, you might have come across back pressure alerts or
Exchange 2013 – IPv6 (To disable or not)
This is an interesting topic. Some believe that it is best to disable IPv6 on an Exchange 2013 Server where
Exchange 2016 – Disabling vs deleting a mailbox
In Exchange, whether it is Exchange 2010, Exchange 2013 or Exchange 2016, there is always some sort of confusion when
Exchange 2013 – The Object has been corrupted and is in an inconsistent state
In your Exchange 2013 environment, you may come across the following error below when working in the EAC when you
Exchange 2013 – IP Less DAG vs DAG with IP
In Exchange, you are probably familiar with creating DAG’s and assigning a DAG IP. All DAG’s running Windows Server 2008
Exchange 2016 – Failover Active Mailbox Database to another Server
In my previous post we looked at redistributing the active databases and copies in a DAG. Today we will be
Exchange 2010 – Redistribute DAG’s
In your Exchange 2010 environment you will need to re-balance your DAG’s after you perform maintenance or if you had