?
Solved

Adding second Exchange 2010 server, error installing CAS role.

Posted on 2011-09-19
3
Medium Priority
?
335 Views
Last Modified: 2012-06-22
Hello!

I currently have an Exchange 2010 server setup and running well.  I need to add in a second Exchange server that will become my main exchange server while the current will have exchange removed.  

I can install all roles except the CAS role.

I have tried installing it with the external address filled in and without.  Each time the error that states it cannot find the Public Folder Database, which lives on the other exchange server, and to check that I typed it correctly.  It's strange because I never get to specify where the database is located.  The two servers seem to be communicating just fine.  I even went as far as mapping a drive directly to where the Public Folder Database is located.

I'm not sure what else to try.  I've looked into IIS and dont see anything unusual there and both servers are Domain Controllers with current copies of the GC.

Any advice you have will be much appreciated.
0
Comment
Question by:CYSAdmin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 16

Expert Comment

by:The_Kirschi
ID: 36566522
Actually I do not know why CAS role asks for the PF database but may you can solve it if you assign a default pf database to the mailbox database on the new server if it is not assigned already. Go to EMC -> Organzation Configuration -> Mailbox. Select the database management tab, then right-click the desired mailbox database, select Properties and go to the Client settings tab. Here you can browse for the PF database you want to use for mailboxes in that mailbox database.

I think CAS asks for a PF database when you tell the installer that you will use Outlook 2003 or something because it requires PF.

Hope this helps.
0
 

Accepted Solution

by:
CYSAdmin earned 0 total points
ID: 36576355
Unfortunately your idea did not work.  It was already assigned the public folder database.  What I found out was that there were some remnants leftover from the switching from Exchange 2003 to Exchange 2010.  Apparently the Folder Hierarchy folder (which contains the Public Folders entry) was never transfered.  I had to recreate it and change the msExchangePFTree attributes.

I tried many things before figuring this out, but what seemed to finally fix it was following this guide in recreating the Folder Hierarchy entry and disabling the old Hierarchy.

http://exchangemaster.wordpress.com/2010/01/02/165/
0
 

Author Closing Comment

by:CYSAdmin
ID: 36597800
Fixed it myself using the guide posted in the previous comment.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question