On Address List Segregation with Exchange 2010…


We have started getting more and more questions (as well as some support cases) around Address List Segregation with Exchange 2010. Some of our customers have also assumed that the existing Exchange 2007 documentation on the subject would just apply to Exchange 2010 also and have tried to configure this, usually with bad results.

Dave Goldman – one of people who worked on the Exchange 2007 document – has just posted a blog post detailing the status of the existing document and it’s use with Exchange 2010. In short: DON’T DO IT. There is a new document in works for Exchange 2010 and we will definitely let you know when it releases, but trying to apply Exchange 2007 document to Exchange 2010 leads to Bad Things.

You can see Dave’s blog post here.

Nino Bilic


Comments (4)
  1. pesos says:

    Well this is timely…  We have had address list segregation in place since 2003…  It was a mess when moving to 2007 and we worked with PSS to get things all sorted again.  Luckily our 2010 migration did not squawk at all and everything has been working fine – HOWEVER!  I just tried to create a new address list for the first time since moving to 2010, and I get: Active Directory operation failed on dc2.tvo.local. This error is not retriable. Additional information: Access is deni

    ed.

    Active directory response: 00000005: SecErr: DSID-031521D0, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

       + CategoryInfo          : NotSpecified: (0:Int32) [New-AddressList], ADOperationException

       + FullyQualifiedErrorId : D9F75077,Microsoft.Exchange.Management.SystemConfigurationTasks.NewAddressList

    I am guessing this is due to custom ACLs.  A 2010 document carefully and explicitly outlining what permissions need to be where will be much appreciated.

    thanks,

    Wes

  2. dordurden@yahoo.com says:

    Nice informative post and thanks for sharing.

  3. Leon says:

    Any Approximate  Time when the Doc will be Released  ? ?

  4. Daniel says:

    Isn’t it right that this should be able with the Hosted Exchange version of Exchange 2010 witch release 1 year after the ‘normal’ Exchange 2010?

Comments are closed.