Hello I am trying to install ex2K7 in a simple domain environment with one Windows 2003 R2 (32 bit) server as DC running ex2k3.ex2k7 server is 64 bit R2 of windows. Both servers have all the latest SPs and patches. I have installed all the ex2k7 pre-requisite software components and managed to start the actual installation. However, the install fails during the organization preparation, complaining that the global adress list already exists: *************************************************************************************** Active Directory operation failed on <server>.<domain>. The object 'CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>' already exists. *************************************************************************************** and I just can't get rid of it or find any info on this on the web. I get the same error when I run "setup /preparead". The only error message in event viewer is the lovely ambigous error message 2152 from MSExchangeADAccess as below. Can anybody help pleeeeeeeeeeeease!!! ******************************************************************************* The description for Event ID ( 2152 ) in Source ( MSExchange ADAccess ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ExSetup.exe, 2900, 1753, Error 6d9 from HrGetServersForRole. *******************************************************************************

This is a bump to this message. I have also experienced this problem and so have many others (just look at Google Groups). The only solution I found, and it seemed to work for me (i.e. I have not seen any problems so far), I went into ADSIEDIT and renamed these objects to <object name> Old. This allowed Exchange to create its own, identically named objects in Active Directory, which seems to have made Exchange happy. While this seemed to work, it is a horrendous work around, and also is something I would like a Microsoft representative to verify.