[Donkey9]

I have two BES (Exchange 2010) set up for HA. Upgraded both of them with no issue. I'm trying to get OCS working and it's driving me mad!

So I followed the documantation that I can find. Got a Web cert, installed OCS Core, UCMA Runtime, Added user account to RTCUniversalServerAdmins and Components, etc. So here are my questions:

1) My OCS Server has an Internal and External address for CWA. Which do I use?

2) Do I really have to manually add the BBIM to trusted applications? I keep seeing this in the event viewer "<2011-05-11 15:42:33.415 EDT>:[93]:<BBIM_RSSRV-ITBES2_BBIM_1>:<ERROR>:<LAYER = BBIM, [OCSC] Error creating Trusted Application pool: Object reference not set to an instance of an object.>"

Any ideas....

[ebanger]

Hi Have you solved the problem?

[RadHaz75]

you dont use the CWA address, you use the address of your front end pool. also, make sure the ports you specify in BAS are 5061 and 65061 for the listening port.

also for the cert, make sure the subject name is your BES server FQDN that you have the collaboration service (not the OCS server name) and that the friendlt name is "OCSConnector". finally, make sure the cert is installed on the Computer personal store and not the user personal store.

[ebanger]

Thank you very much. He said the four error, an error is solved now.

<2011-06-01 14:37:03.918 PDT>: [108]: <BBIM_MOBILMAIL_BBIM_1>: <ERROR>: An item with the same <LAYER = BBIM, [OCSC] Error: added.> key has already been

What can I do.

[Azmere]

I'm also having loads of issues with getting this to work. I have a job in with RIM on this one and going around in circles. I have it pointing to the pool address and we use TLS with the standard ports. This should have been stright forward but its not.

The 1st issue found was the duplicate AD entry mentioned in KB25416.

The 2nd issue was a certificate one and was resolved with KB24960. The interesting thing here is requesting the cert seems to work fine and it all works. If we restart the collaboration service though the certificate is deleted. Not sure whats going on here. Still we were able to progress to the next step.

The next fault is the show stopper the client software is unable to login. refer KB26429. This is error we are seeing in our logs. Except our users are in the same domain! Has anyone else gotten this to work?

[Donkey9]

Okay so I never got OCS R2 working and now we've moved to Lync. So I reconfigured everything for Lync, got a new cert, and installed the client on my handheld. It's timing out. I'm going to start a new thread as this is now Lync and not OCS R2. Hopefully someone can help there. Thanks anyways.