Link to home
Start Free TrialLog in
Avatar of paclaiborne
paclaiborne

asked on

Exchange 2010 Client Access Role Installation Error

The image below shows the installation error I am getting when trying to install the CAS role for Exchange 2010, any help would be greatly appreciated.

I have had Exchange 2010 installed successfully before when it was beta, I used the same name "MCC-EXCHANGE-01" as i'm trying to use now if that helps solve this error.

Thank You!!
9-16-2010-10-49-44-AM.jpg
Avatar of endital1097
endital1097
Flag of United States of America image

make sure IPv6 is enabled on the server
Avatar of paclaiborne
paclaiborne

ASKER

IPv6 is enabled
do you have any exchange 2007 or 2010 server in your environment?
if not:
launch adsiedit
right click and connect to
connect to configuration partition
then browse to configuration - services - microsoft exchange - exorg name - administrative groups

check if there is an exchange administrative group FYDBO
We have our live Exchange 2007 server, but before I did the 2010 installation I went into Administrative Groups in ADSI and deleted the prior MCC-EXCHANGE-01 under Servers, not sure if there is something else in another location that should have been deleted also?

Thanks
ASKER CERTIFIED SOLUTION
Avatar of endital1097
endital1097
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It's a pretty large .txt file so I attached it to this post.

Thanks
ExchangeSetup.log
I found the solution, since I had a previous installation of Exchange 2010 in my organization I had to open ADSI Edit and go to Configuration, Services, Microsoft Exchange, Your Organization, Administrative Groups, Exchange Administrative Group, CN=Databases and delete the old database references out of the container, once I did this the installation ran successfully!!

I'll give you the points anyway endital1097, thanks for helping :)
thanks, i was preparing for a datacenter move this weekend
i would have said to look at the databases container since 2010 moved the location