Exchange Server 2013 troubleshooting guide for administrators
Dear Exchange Experts,
I came across recently with a problem with my Exchange Server 2013 which could not send/receive mails.
I was searching for a solution using various blogs, microsofts support and EE.
It took me more than 4hours to find that the DB was dismounted and the Exchange Logs where responsible for this issue.
So I was wondering if anyone could suggest me a Troubleshooting book that covers the common failures of Exchange as well as the way that the components are interact each other.
Thanks,
Mamelas
I came across recently with a problem with my Exchange Server 2013 which could not send/receive mails.
I was searching for a solution using various blogs, microsofts support and EE.
It took me more than 4hours to find that the DB was dismounted and the Exchange Logs where responsible for this issue.
So I was wondering if anyone could suggest me a Troubleshooting book that covers the common failures of Exchange as well as the way that the components are interact each other.
Thanks,
Mamelas
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jeff Glover
I have to agree with the sentiments expressed here. There is no good "How to for Troubleshooting" out there. There are various experts who publish invaluable data on their websites and blogs but all in all, your best bet is this. Learn how it works and why. There are any number of good books out there that can explain how it works. Once you understand how it works, then it makes it easier to figure out why it isn't working. Exchange is not for the beginner or the faint of heart but it can be learned, either through self study or through classes. If you have the resources, I suggest you setup a test network and play with it. It is the best way to learn, by doing.
ASKER
Dear Experts,
I would say that you all agree each other.
Yes I usually follow the basic steps of checking the EventViewer, the Exchange Services, the Administrator's Console but...in the event of a production Environment there is no time for checking "possible" solutions on the net or waiting for a reply from EE.
It is also true that each time that something fails will help you to learn and understand things better but this is not professional in my opinion.
Every administrator should be one step ahead. Therefore I assume that the training is the keypoint.
Thank you all for your contribution.
I would say that you all agree each other.
Yes I usually follow the basic steps of checking the EventViewer, the Exchange Services, the Administrator's Console but...in the event of a production Environment there is no time for checking "possible" solutions on the net or waiting for a reply from EE.
It is also true that each time that something fails will help you to learn and understand things better but this is not professional in my opinion.
Every administrator should be one step ahead. Therefore I assume that the training is the keypoint.
Thank you all for your contribution.
Proactive monitoring is key for running healthy Exchange environment. There are several ways you can do it, First, by implementing good monitoring tool. Next writing few custom scripts, Which can give you detail overview about your environment every day.
As far as, troubleshooting during production hours. I agree, there is no time to check blogs etc. However, if you participate in blogs, you might know that issue well in advance.
Finally, key for troubleshooting any server issue, you should know the application flow. Like how you connect to your Exchange server, is there any HLB or TMG in between your Server. How your mail flow works. Is there any spam server etc.
Training also play key role, however almost with every service pack. Microsoft changes or adds new things. So, you need to keep yourself update by reading blogs like EHLO.
As far as, troubleshooting during production hours. I agree, there is no time to check blogs etc. However, if you participate in blogs, you might know that issue well in advance.
Finally, key for troubleshooting any server issue, you should know the application flow. Like how you connect to your Exchange server, is there any HLB or TMG in between your Server. How your mail flow works. Is there any spam server etc.
Training also play key role, however almost with every service pack. Microsoft changes or adds new things. So, you need to keep yourself update by reading blogs like EHLO.