Released: Exchange Server 2013 RTM Cumulative Update 1

Hey,

I'm supporting Ex2010SP3 environment with 1500+ GALs. GALs and Address books are segregated using Address Book Policies introduced in 2010SP2. Multi-tenancy hosting guide for 2010SP2 also says that that GAL limit also was lifted by making linked attributes.

-=-=-

It is no longer necessary to run the makegallinked.exe tool or change the schema definition properties of the GlobalAddressList attribute in Active Directory to enable you to create more than 1000 GALs. Once you reach the default limit of the GlobalAddressList attribute (approximately 1250 with the Windows Server 2008 Active Directory schema) you will receive a warning that the GAL you are attempting to create will only be accessible by users with a mailbox on Exchange 2010 SP2.

NOTE: It is not supported (nor is it necessary) to run the makegallinked.exe tool or change the schema definition properties of the GlobalAddressList attribute in Active Directory in a new Exchange Server 2010 SP2 installation, you simply need to ensure the Active Directory is operating at the correct forest functional level and you use only the 2010 versions of the New-GlobalAddressList cmdlet.

-=-=-

And this makes sense.. I still can create GALs in Ex2010 even I'm way above 1250 limit...

Unfortunately it is not the case with Exchange 2013. I introduced Ex2013 into this organization. installation went smoothly. I have working coexistence. What doesn’t work is GALs.. I CANNOT create any new GALs. I receive weird error:

WARNING: One or more global address lists were missing from the Active Directory attribute. This is likely caused by using legacy Exchange management tools to create global address lists.

and it is failing with statement that "One or more attribute entries of the object "CN=Mincrosoft Exchange,CN=..." already exists.

Looks like Ex2013CU1 "forgot" about removed GAL limitation in Ex2010SP2. It seems that it is missing some GALs (we I have ~300 GALs on top of official 1250 limit) and it cannot create new one because it thinks that it already exists, but it is not..

Has anyone else ran into this issue. Is there a potential workaround or fix?  Is there quick fix to enable linked attrobute for GlobalAddressList and GLobalAddressList2?