While this might not qualify as light summer reading, Microsoft Press’s newest book sure will help with that, um, summer working. It offers up the very best practices for use of Exchange Server 2010. Be warned, proper use of the techniques held in this book could send your business into the stratosphere.

Microsoft Exchange Server 2010 Best Practices is available now and tackles a variety of subjects to help you get over some initial migration hurdles. It’s also good for folks completely new to Exchange. Here is a small sample to get you in the mood for learning:

Chapter 3  Exchange Environmental Considerations

This chapter describes all the basic components surrounding Exchange Server 2010 that need to be considered to plan a solid Exchange implementation. These components provide the basis to build Exchange on a solid foundation and to identify potential issues.

It provides a basis for other chapters in this book by describing some of the technologies that will be discussed later. For example, this chapter includes a discussion on namespace design as well as a review of certificate requirements, which are then taken to the next level in Chapter 4, “Client Access in Exchange 2010.” Of particular importance when using this book is the “Planning Naming Conventions” section, which explains the names that are used throughout the entire book.

Evaluating Network Topology

Evaluating the network topology through which Exchange Server 2010 will communicate is crucial during the Delivery Phase, Step 2: Assess, as described in Chapter 2, “Exchange Deployment Projects.” Often, making changes in the network infrastructure can take a considerable amount of time because the Exchange team isn’t necessarily responsible for making changes to the network, and communication and negotiation are often required before network changes can be made, especially in large organizations that support heterogeneous operating systems.

Identifying any required changes and making sure that the execution of the change can occur without any difficulties early in the design process can save time later when you are implementing Exchange Server 2010.

Want more? Buy it now!