Dave Goldman blogged about address list segretation in Exchange Server 2003 in his blog site (http://blogs.msdn.com/dgoldman/default.aspx).

Over the last few months a great number of people have asked if we would be putting out a white paper on how to segregate address lists for Exchange 2003. We put a massive amount of time and effort into getting the Exchange 2007 version of this document ready and it is now released. There are no future plans to publish or create a 2003 version of this document.

There are a few things to note here:

1. If you are in need of address list segregation functionality, we highly recommend that you consider moving forward to Exchange 2007 to meet this need.
2. All older Exchange (address list segregation / hosting white papers)have been pulled and are no longer valid.
3. All older Exchange (address list segregation / hosting KB Articles) have been pulled and are no longer valid.
4. The only valid address list segregation document that is supported is the Exchange 2007 address list segregation document that is now hosted on the Microsoft Technet web site and is located here: http://technet.microsoft.com/en-us/library/bb936719.aspx

Outside using the Exchange HMC solution there will be no support for Exchange 2003 address list segregation.

Read more at source: http://blogs.msdn.com/dgoldman/archive/2008/02/19/...t.aspx

Microsoft has released Update Rollup 6 for Microsoft Exchange Server 2007. This article contains the following information about the update rollup:

More information at: http://support.microsoft.com/default.aspx?scid=kb;...=10926

David Goldman who is the author of Exchange Server 2007 Address List Segregation document blogged about some questions that were made since that document was released.

Read more at source: http://blogs.msdn.com/dgoldman/archive/2008/02/17/...s.aspx

This is a follow-up to an earlier post: Single-label Domain Names and Exchange Server 2007 SP1. Please refer to it for background information on this issue.

After investigating Exchange 2007 Service Pack 1 installed in an Active Directory domain with a Single-label Domain (SLD) name, Microsoft has changed the Setup prerequisite rule for SLDs from an Error to a Warning, thereby allowing Service Pack 1 installation to continue in SLD environments.

There are a few items that I want to point out:

• Not a recommended configuration
  While Exchange 2007 SP1 is supported with SLDs, the Exchange product team’s view is that SLDs are not a recommended configuration. While we will allow installation of Exchange 2007 SP1 in an SLD, we strongly recommend that you take step to move your organization out of this configuration.
• Not fully tested
  Exchange 2007 and Exchange 2007 SP1 have not been fully tested in SLDs. The Exchange team investigated known issues and determined that there were sufficient workarounds to safely allow installation of SP1 to continue; however, there may be unknown issues that could arise from operating Exchange 2007 in an SLD environment.
• Deprecated in the next version of Exchange
  The next version of Exchange will not support Active Directory domains with single-label domain names. Similarly, upgrades of Exchange servers currently deployed in single-label domains will not be supported. In this case, “next version” means the next major release of Exchange Server. Customers that intend to deploy the next version of Exchange must use fully qualified domain names.
• Documentation being updated
  Currently, the existing TechNet documentation states that SLDs are not supported in Exchange 2007. We are working to change the documentation to reflect that SLDs are supported but not recommended configurations. The updated documentation is expected to be published on TechNet as part of the March 2008 document refresh in early March.
• Exchange 2007 does not support Domain Rename, and there are currently no plans for a Domain Rename Fixup Tool for Exchange 2007
  The possibility of creating a domain rename fixup tool for Exchange 2007, similar to the one that was written for Exchange 2003, was discussed internally. The decision is that there will not be a similar tool written for Exchange 2007. The Domain Rename Fixup tool written for Exchange 2003 is not compatible with Exchange 2007, and should not be used in Exchange 2007 environments.

Read more at source: http://msexchangeteam.com/archive/2008/02/15/448140.aspx

Technorati : Exchange 2007 SP1, setup changes, single-label domain names

The Autodiscover service for Microsoft Exchange Server 2007 provides automatic profile configuration for Microsoft Office Outlook 2007 clients that are connected to your Exchange messaging environment.

When you install the Client Access server (CAS) role on a computer running Exchange 2007, a new virtual directory is created under the Default Web Site in Internet Information Services (IIS). In the Active Directory a Service Connection Point (SCP) object is created that allows all domain-connected clients running Outlook 2007 to query the Active Directory and configure the Outlook profile automatically.

Many organizations have complex topologies with multiple forests where the Exchange is running in a resource forest and an accounts forest which contains the user accounts for the organization. In the multiple trusted forest scenario, the user accounts and Microsoft Exchange are deployed in multiple forests. Exchange 2007 features such as the Availability service and Unified Messaging rely on the Autodiscover service to access user accounts across forests. In this scenario, the Autodiscover service must be available to users across multiple trusted forests.

The intention of this post is not to explain how Autodiscover works, how to implement it for multiple forests, or troubleshoot every scenario. It is a brief, practical list of tips for use during the deployment and covers some common examples and methods to resolve issues.

Read more at source: http://msexchangeteam.com/archive/2008/02/13/448127.aspx

Technorati : Autodiscover service, SCP object, multiple forests
Del.icio.us : Autodiscover service, SCP object, multiple forests
Ice Rocket : Autodiscover service, SCP object, multiple forests
Flickr : Autodiscover service, SCP object, multiple forests

There are many scenarios in Exchange 2007 Server which requires parsing, monitoring, and analyzing Message Tracking logs. For example, in transaction log file and / or Database growth scenarios, Server got hit with spam messages, Looping message scenario, Transport queue backup scenarios, and Server performance scenarios, and many other administrative, monitoring, and troubleshooting scenarios - it absolutely becomes necessary to review and analyze Message Tracking Logs. The amount of fields and tremendous amount of data present in message tracking logs, and the amount of extremely high messaging traffic that Exchange servers process these days ( i.e. the sheer size of message tracking log files ) makes it extremely difficult, if not impossible, to analyze these message tracking logs manually. The task is further complicated when you have to review message tracing logs from multiple servers, and especially on a pretty regular basis.

Read more at source: http://msexchangeteam.com/archive/2008/02/07/448082.aspx

Amir told me that he posted a two part series that covers new features of Entourage 2008 on his blog. Part 2 talks quite a bit about Exchange integration too so I figured people would be interested:

Entourage 2008 - New Features (Part I)

Entourage 2008 - New Features (Part II)

Read more at source: http://msexchangeteam.com/archive/2008/02/06/448063.aspx

System Center Capacity Planner 2007 is a pre-deployment capacity planning and post-deployment change analysis solution for Exchange Server 2007.

Get it here: http://www.microsoft.com/downloads/details.aspx?Fa...ang=en

Technorati : Exchange Server 2007, System Center Capacity Planner 2007
Del.icio.us : Exchange Server 2007, System Center Capacity Planner 2007
Ice Rocket : Exchange Server 2007, System Center Capacity Planner 2007
Flickr : Exchange Server 2007, System Center Capacity Planner 2007

How to recreate the sync relationship on mobile devices synchronizing with Microsoft Exchange Server

Read more at source: http://msexchangeteam.com/archive/2008/01/30/447971.aspx

One of the most common questions I’m asked is if we have any resources that document the default settings for the Exchange-related virtual directories in Exchange 2007 - specifically with regards to the authentication and SSL settings. This aims to address that need should you find yourself in a situation where these settings have been inadvertently modified with the end result being an undesirable behavior in Exchange 2007. These settings hold true for both Exchange 2007 RTM and Service Pack 1.

Read more at source: http://msexchangeteam.com/archive/2008/02/01/447989.aspx