Communicator login prompt after moving mailbox to Exchange 2010 server

We run OCS/Communicator 2007 and it has run fine for some time now.  Yesterday I moved many users from Exchange 2003 to Exchange 2010 and now when they login to their computer they get a Communicator login prompt.  They can cancel out and it still works fine.  I'm assuming it is the integration of Communicator with Outlook for calendar and status.  These users are all internal.  We use OCS 2007 and Outlook 2007.
jpletcher1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

elawadCommented:
it might be the authentication for the offline address book, you could try to stop the address book portal for the IIS on the OCS server and try f the problem persists.
0
jpletcher1Author Commented:
I am not sure what you mean by stop the address book portal.  
0
Jeff_SchertzCommented:
When that prompt appears what is the exact message that the OC client displays under the alert icon in the upper-right hand corner?

It's most likely Web Components related, but could also be an Exchange integration error as well.

Also, you can try testing by adding a distribution list to an OC Contact List and see if you can successfully expand the list of members, or if it re-prompts/fails.

If that is the case then and you've recently reset the service account passwords in OCS (RTCService, RTCComponentService) then you may need to also reset the account credentials in the IIS Application Pool.   See this blog article for more details: http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=66
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

jpletcher1Author Commented:
Here is the error that comes up when we click on the integration error on the communicator client....
commerror.jpg
0
Jeff_SchertzCommented:
OK, that's the OC client attempting to connect directly to your Exchange server using EWS.  Is the users SIP address the same as their primary SMTP address?  Is Exchange Server even deployed and used in this environment?
0
jpletcher1Author Commented:
Yes, the sip addresses and the primary smtp addresses are the same.  As stated in my initial description, we were on Exchange 2003 and this issue started happening after we moved onto Exchange 2010, so it could be the EWS.  What are some things I need to check for to make sure EWS is setup properly?
0
Jeff_SchertzCommented:
Do you have the latest OCS hotfixes applied?  Take a look at this previous TechNet discussion for more details:
http://social.technet.microsoft.com/Forums/en/ocsucintegration/thread/dc9bb881-c985-416f-83d7-e37d647bba82
0
jpletcher1Author Commented:
Yes, I had run across that article too and tried the hotfix last week, but didn't fix the issue for me.
0
jpletcher1Author Commented:
I think this may have to do with SPNs.  In my PC system log I get errors every 30 minutes like the person in this article did (the kerberos error).  I think this is my communicator client checking in.  Can anyone tell me what SPNs I should check?  My Exchange server is listed as mail.domain.com.

http://www.experts-exchange.com/Web_Development/Web_Services/URL-URI_Usage/Q_23950364.html
0
jpletcher1Author Commented:
Also, when I check the IIS logs I can see when I open Communicator there are errors connecting to the EWS site with 401..

2010-04-13 19:54:15 *EXCHANGE IP* POST /EWS/Exchange.asmx ;RC:773160d3-5a0a-4d3c-9bec-b4e47b2eff21; 443 - *CLIENT IP* Microsoft+Office+Communicator/2.0 401 0 0 156
2010-04-13 19:54:15 *EXCHANGE IP* POST /EWS/Exchange.asmx - 443 - *CLIENT IP* Microsoft+Office+Communicator/2.0 401 1 2148074254 125
0
jpletcher1Author Commented:
Also this in the Exchange IIS logs pertaining to Communicator....

2010-04-13 19:54:15 *EXCHANGE IP* POST /EWS/Exchange.asmx ;RC:cefc7055-d085-426b-b29d-ae15a7b88c3a;Init>>Conn:0,AD:$null/$null/0%,CAS:$null/$null/0%,AB:$null/$null/0%,RPC:$null/$null/0%,FC:$null/0,Hash:61354054,Sub:$null/0;SoapAction=GetUserOofSettingsResponse;MailboxRPCRequests=13;MailboxRPCLatency=0;ADRequests=2;ADLatency=0;TimeInGetUserOOFSettings=18;End(31.2502ms)>>Conn:1,AD:$null/$null/0%,CAS:$null/$null/0%,AB:$null/$null/0%,RPC:$null/$null/0%,FC:$null/0,Hash:61354054,Sub:$null/0; 443 *DOMAIN\USER* *CLIENT IP" Microsoft+Office+Communicator/2.0 200 0 0 140
0
jpletcher1Author Commented:
I called MS and they had me update my client to Communicator 2007 R2.  Then things worked.  So apparently this is an issue between Communicator 2007 non-R2 and Exchange 2010...  Not really the fix I was looking for and I hope they come out with a patch or some update package to fix this.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.