To display the W3C logging folders, Start, Run, Logfiles
Exchange Server 2007 is a complex topic, do you need practical hands on training? As an MCT trainer, I can thoroughly recommend
TrainSignal. In particular, I like the way
that TrainSignal cover all learning methods, instructor lead, video and of course text
material. You can either take one module, for example Exchange 2007 or go for a combination of modules.
Learn more about Microsoft Exchange Server 2007 here
Proactive Tips
If you have more than 50 mailboxes, invest in the Enterprise version of Exchange 2000. That standard version has a 16 GB limit on the mailstore.
Build Exchange Server 2003 on a Windows 2003 member server. Not on Windows 2000, and not on a domain controller of any kind.
Assess the Tools folder in general, and the Notification sub-folder in
particular. Check out Resource Monitoring
Make sure that 'Keep Deleted Items' is set on the server. This is a safety net for the users to recover their own deleted email from Outlook.
If you deploy Front-end / Back-end servers, investigate which services to disable on the Front-end servers. E.G. Information Store.
Microsoft Exchange System Manager does not display the security tab unless you add this registry
DWORD:
ShowSecurityPage. See more here
Apply SP2 (or the latest Service Pack for Exchange 2003).
Schedule a time to defrag the mailstore databases with eseutil /d.
Instead of a reboot, stop and restart services, for example, System Attendant. Rapid Reboot Script.
If you have to restart IIS, remember iisreset at the command prompt.
Another variation, dismount and then mount individual Mailbox store. This saves stopping and starting the Store service. For example if you are defragging priv1.edb.
Disable the BadMail folder with SP1. Or move it? Get utility. See more on BadMail
Guy Recommends:
The SolarWinds Exchange Monitor
Here is a
free tool to monitor your Exchange Server. Download and
install the utility, then inspect your mail queues, monitor the Exchange
server's memory, confirm there is enough disk space and check the CPU
utilization. This is the real deal - there is no catch. SolarWinds
provides this fully-functioning product for free, as part of their commitment to
supporting the network management community.
Get into the habit of checking the Application Event Log weekly if not daily. In particular, look for errors, which indicate problems with Exchange 2003 server.
Enable Protocol logging for Troubleshooting. Remember to it turn off when you finish logging. Your server will notice the difference.
To stop NDRs from former employees - Create a Dead Letter account, then add each SMTP addresses as an alias.
Check out ExMerge.exe (SUPPORT folder on CD). Copy the ExMerge files to the Exchsrvr\bin folder.
When you launch ExMerge to recover individual mailboxes, make sure that you have Send As permissions on those mailboxes.
When you look up Event IDs in TechNet use 'near' in the search. For example, Event NEAR 7001. What NEAR does is in this example is return all occurrences of Event within 8 words of 7001.
.
Summary of Exchange Troubleshooting Tips.
Spend time with Exchange System Manager. Keep a list of handy Exchange tips for troubleshooting. If you have a time-saving tip, then I would love to add it to my list.
The
extra features you get in your eBook include: 'How to...' sections
with screen shots. Checklists to prepare your migration plan.
