Office communicator not updating my status boy boy como dating encontrar in seattle
They all run the same client (which I guess must be 32bit - I'm not aware of a native 64bit Office Communicator build).
I'm kind of at my wits end now - I've run out of things to try.
” So many users are using Busy as their “Available” that we’ve all started just IMing Busy people anyway. So many of us are now simply ignoring Busy status that we’re affecting our coworkers to who use Busy as a real indication of their availability to communicate.
Here’s an example: A friend who runs a large Lync deployment shared with me that people at his company are afraid to use Available status because they don’t want to be bombarded with IMs. On the other end of the spectrum we have the people who are always Available, meaning A as their presence indicator, you might have IMed them anyway!
Remember when presence was an indicator of your availability to communicate?
It was empowering to know that you could control interruptions and be ready to collaborate with others if they needed you. I am not really sure how it came to be, but a growing number of people are manually setting their presence to Busy and leaving it there all day long.
This also wasn't a problem on the previous install of OCS. EDITS So installing Communicator on the Front End Server itself works.
I'm guessing based on your description that the CDP has an HTTP url for the CRL (okay, the acronyms are ridiculous, sorry) and that either the CRL wasn't actually put in that location, which has to happen manually, or that location isn't available since as you've pointed out, it doesn't have an HTTP server on it.
You can work through this issue; however, I think you'll be better off if you just publish the cert to AD and call it good enough.
Whilst looking for solutions to this issue, most of my googling has turned up issues with certificates as the root cause, but I'm nigh on positive this isn't the problem here.
I'm able to surf to the URL being sent from the OCS server to Communicator as the Address book URL, and I get no issues reported by Internet Explorer at all.
The Galcontacts.db/files are downloaded immediately. Also - the MAPI Error (Outlook Integration Error) has now disappeared too (although I'm really not bothered about this).