Tagged: exchange

Exchange 2013: Exchange Admin Center (EAC) blank

Recently we have extra servers in our environment idling for quite sometime and since I’m also have some extra time that I can squeeze out of my day, I decided to test Exchange 2013. Sadly, after almost 18 months it was released I’m able to test it fully.

The installation is a breeze since Microsoft have simplified the Exchange 2013 server roles as in Exchange 5.5 – 2003 with only 2 roles, CAS & Mailbox. Anyway, installation part will be in another post.

One of the major changes in Exchange 2013 is that there is no more EMC (Exchange Management Console) and that’s really a good news for me as I have always hated using EMC due to the time it takes to present the information and lack of filtering feature as well as details information. It has been replaced with Exchange Admin Center or EAC.

I believe the most common issue for someone who testing Exchange 2013 is, you don’t know how to access EAC and when you have the address you are getting a blank screen.

How to access EAC



if you are getting a blank screen

open your Exchange Management Shell (EMS) and run this command

Get-EcpVirtualDirectory | FL *URL*


Look for the InternalURL and copy and paste into your browser. Viola! You will get the the interface as in the 1st screenshot!

Hope this helps people who have the same problem like mine.


Exchange 2010: Check Exchange Service and Start/Stop Service

We had an issue yesterday where some of our exchange services was stopped. You can easily check this using these command from Exchange Management Shell (EMS)  for Exchange 2010.


Screenshot of the command from CAS/Hub Transport servers
Screenshot of the command from Mailbox servers
Take note on the “ServicesNotRunning”.

Here is the command you need to start/stop any of the Exchange Services. If you want to properly restart Exchange Service without rebooting the servers, copy and paste this in Powershell console/Exchange Management Shell. Make sure you its in the same order of the one listed below.

Stop-Service MSExchangeAB
Stop-Service MSExchangeADTopology
Stop-Service MSExchangeAntispamUpdate
Stop-Service MSExchangeEdgeSync
Stop-Service MSExchangeFBA
Stop-Service MSExchangeFDS
Stop-Service MSExchangeIS
Stop-Service MSExchangeMailboxAssistants
Stop-Service MSExchangeMailboxReplication
Stop-Service MSExchangeMailSubmission
Stop-Service MSExchangeProtectedServiceHost
Stop-Service MSExchangeRepl
Stop-Service MSExchangeRPC
Stop-Service MSExchangeSA
Stop-Service MSExchangeSearch
Stop-Service MSExchangeServiceHost
Stop-Service MSExchangeThrottling
Stop-Service MSExchangeTransport
Stop-Service MSExchangeTransportLogSearch

Start-Service MSExchangeAB
Start-Service MSExchangeADTopology
Start-Service MSExchangeAntispamUpdate
Start-Service MSExchangeEdgeSync
Start-Service MSExchangeFBA
Start-Service MSExchangeFDS
Start-Service MSExchangeIS
Start-Service MSExchangeMailboxAssistants
Start-Service MSExchangeMailboxReplication
Start-Service MSExchangeMailSubmission
Start-Service MSExchangeProtectedServiceHost
Start-Service MSExchangeRepl
Start-Service MSExchangeRPC
Start-Service MSExchangeSA
Start-Service MSExchangeSearch
Start-Service MSExchangeServiceHost
Start-Service MSExchangeThrottling
Start-Service MSExchangeTransport
Start-Service MSExchangeTransportLogSearch

Hope this helps someone. Ping me


Exchange 2010: Allow Anonymus Receive Connector for in-house application

If you are working or doing some migration work for a 40 years old company, chances are you bump into one or few legacy applications that don’t support SMTP authentication but it is still being used and will not be retired any soon. These application sends out email for notifcation.

To resolves this, we need to allow Exchange Receive Connector to allow relay without any form of authentication. Here’s how to do it form Exchange Management Shell(EMS).

Get-ReceiveConnector -Identity “Anonymous Relay Connector” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “Ms-Exch-SMTP-Accept-Any-Recipient”

As a best practice, make sure that you only allow connection from specific IP address. This can be done from Exchange Management Console (EMC) > Microsoft Exchange On-premises (your server name) > Server Configuration > Hub Transport > Receive Connectors


source: http://www.cgoosen.com/2012/01/exchange-2010-anonymous-relay-receive-connector/