Acknowledgments

One of the funny things about technical writing is that there is a certain mythology behind the writing process. This is the 10th book I have authored, coauthored, or contributed to, and people seem to think that a single author or one or two people wrote every single word of the book. Further, readers seem to think that this process happens quickly.

By the time you are able to walk into your neighborhood bookstore and pick up this book, at least a year will have passed. During that time, what the book will contain and how it should be used are tossed back and forth between the author, the publisher, and Exchange gurus. Decisions are made about important topics, target audience, and page count restrictions. Wiley Acquisitions Editor Tom Cirtin puts the project together and maps out a plan to get the book out the door, and Wiley Editorial Manager Pete Gaughan monitors the schedule and helps keep the entire book development and editorial process on track.

And then the slowest part of all, the actual writing, begins. A typical chapter takes between 10 days and 2 weeks to write, though this can vary depending on my schedule and whether and how familiar I am with the topic.

I have never worked on any book in which the content was written exclusively by me. Always there are individuals that contribute ideas, bullet points, paragraphs, or even entire chapters, and this book was no exception. Ben Craig jumped in early in the development of this book and helped me catch up when ...

Get Microsoft® Exchange Server 2007: Implementation and Administration now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.