Exchange Server Documentation Updates – June 2008


The Exchange Server documentation team is pleased to announce updates to the Exchange Server content.

To see what content has changed for Exchange Server 2007 with Service Pack 1, take a look at Exchange Server 2007 Documentation Updates.

To see what content has changed for Exchange Server Analyzer, take a look at Exchange Server Analyzer Topic Updates.

In particular, we would like to highlight the following new or updated topics:

You can see these articles and other Exchange Server documentation content in the Microsoft Exchange Server TechCenter.

The following downloads are also available for SP1 content:

BTW, if you haven’t noticed, all our topics in the Exchange Library now have a "Topic Last Modified" date at the top of the topic. And, if you wonder which topics apply to Exchange Server 2007 with Service Pack 1, we now have an "Applies to" tag for Exchange 2007 content.

You can now annotate topics in the Exchange Server 2003 and Exchange Server 2007 documentation. Scroll to the Community Content section at the end of any topic in the Exchange Server Library, and click Add Community Comment. You’ll be asked to sign in with your Windows Live ID and to register as a participant. Then, share your insights with the Exchange community.

Cathy Anderson, Content Release Manager, Exchange User Documentation


Share this post :

Comments (10)
  1. Lunik says:

    Very nice job!

    Thanks guys :)

  2. Jeff says:

    When will MSPress be releasing a Resource Kit book for Exchange 2007?

  3. tj says:

    very cool, thank you! ;)

  4. Exchange says:

    Hi Jeff, at this time, there are no plans to have a resource kit book for Exchange 2007. If there is some type of documentation you need, which is not met by the current help, please let us know

  5. dude says:

    All the documentation I´ve read about E2007 is written for server 2003. When will the documentation be fixed for implementation on Server 2008?

    I’m talking about stuff like this:

    "We recommend that you deploy a new, single-server Simple Exchange Organization only when you are using Microsoft Windows Small Business Server 2003."

  6. Jeff says:

    I don’t need any specific information, its just nice to be able to crack open my Exchange 2003 resource kit book to have a place where everything is easily accessible offline.

  7. Exchange says:

    Hi Jeff, I’d like to chat with you about offline access to Exchange info. Please contact me at your convenience. Thanks, alisonhATmicrosoft.com

  8. Paul says:

    Hi,

    in the above update "How to Configure Network Connections for Cluster Continuous Replication: Fixed incorrect configuration steps for the private network by specifying that Client for Microsoft Networks and File and Print Sharing need to be cleared." now sits at odds with http://support.microsoft.com/kb/258750 and specifically where it states:

    Note If the server is using a MNS quorum, you must have at least one network that has file-sharing capabilities for the MNS quorum to function. We strongly recommend that you have multiple networks on the cluster that have file sharing enabled to avoid a single point of failure for the quorum resource.

    We have seen issues whereby the cluster can fail if the only network with F&P sharing enabled is unavailable.  Microsoft updated this article to refect this.

    To me, the documentation was correct before and now appears incorrect.  It would be good if you could clarify this.

  9. Scott says:

    Hi Paul,

    We’re "un-fixing" the previous fix for "How to Configure Network Connections for Cluster Continuous Replication".  The original guidance is correct.  You do want File&Print Sharing and Client for Microsoft Networks enabled on the private network, as CCR uses an MNS quorum.  If you only have one NIC with these protocols, it becomes a single point of failure.  Thus we recommend having these protocols enabled on both NICs.

    Hope this helps.

  10. Paul says:

    Hi Scott,

    Thanks for the clarification on this and correcting the documentation.

Comments are closed.