Access your Pro+ Content below.
Why it's important to document your Exchange installation
This article is part of the Exchange Insider issue of November 2010, Vol. 7
As an experienced Exchange administrator, I've never found documenting an Exchange installation to be particularly exciting. Not only can it be repetitive, trying to decipher handwritten changes and knowledgebase articles isn't much fun either. But administrators have an obligation to document, explain and provide guidance for others who will work with the system. Exchange architects often leave sites when an installation is complete, so providing proper documentation is essential. There are a few principles of good documentation that you should follow. Consider using this structure and some of these methods when creating your own Exchange Server installation documentation. Identify your audience From the beginning, establish who will read the documentation. It's easy to assume that the people who will benefit from your work are devout Exchange admins. But since Exchange 2007 split management of user mailboxes and accounts between the Exchange Management Console, Exchange Management Shell and Active Directory users and computers...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
Virtualizing Exchange 2010 servers is a smart move, and the steps involved are fairly simple. The actual virtualization process begins long before you create a VM.
When Outlook Web App’s default settings just won’t do, it’s time to tweak. Certain configuration changes will help OWA run more efficiently and securely.
After you've installed Exchange Server for a client, it's time to write the installation documentation. Providing consistent and easy-to-understand documentation is vital for both Exchange administrators and users. These three principles of good documentation writing can help.