That is the way it is designed. The catch is that OCS allows for more than one client to access it at the same time. If you've ever logged in to Yahoo or MSN Messenger when already logged on from a different computer, you will be logged off on the original computer with an explanation message, this doesn't happen with MOC. This is important from the standpoint that you might have your computer locked in your office, but at the same time be logged in from your WM device or a kiosk or a laptop, etc. I do not believe it to be a design flaw if you think of it from an IM point of view. "In a Meeting" implies that you are there, but may not respond immediately due to being busy. (There are also different levels of Access you can set based on groups and these availability settings.) Away implies that you are not at any computer so there is no way for you to see IM's that might be received. If your computer is locked (even if you are sitting in front of it), you cannot see any incoming IMs, making it impossible for you to reply. Therefore as a sender, I know not to expect a reply any time soon. If you lock one computer, but are still logged into OCS via another means, then your status will stay at "In a Meeting". You have to keep in mind that IM presence is really made available for the sender, not for the receiver. It is all about setting expectations for reply times.
PS - I know this because I just had to run a number of training classes here on MOC/OCS with our users, many of whom didn't get it at first either. From: Tim Evans [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2008 12:14 PM To: NT System Admin Issues Subject: RE: OCS questions I agree that it seems like a design flaw. I usually am away from my computer when I'm in a meeting. ...Tim From: Kevin Lundy [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2008 10:11 AM To: NT System Admin Issues Subject: Re: OCS questions If that is the way the presence is supposed to work, I believe that is a design flaw (opinion). If I have a meeting scheduled, it should say "in a meeting" whether I'm at my computer or not. So based on the statistically invalid response of one, looks like we do have something to research on the random authentication. No, we aren't rolling out the voice part. We are fully Cisco VoIP. I've got Unity and CM upgrades to do and a IPIP gateway to purchase and install before I can integrate the two. And that is a low priority for us. On Fri, Oct 10, 2008 at 12:59 PM, Tim Evans <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Oh, cool! Someone else is going thru the same thing I am 1. I believe that's the way presence is supposed to work, at least that's the way it does here. Actually, if I have something on my calendar and I lock my PC, my jelly bean turns half red/half yellow. 2. I don't get prompted to authenticate to read the address book (from a PC that is a domain member), but we've been having some issues some users getting random prompts for authentication to the MB server or the CAS server (Ex 07 here). I figure that's a problem with Exchange configuration that I'm still chasing Did you set up the enterprise voice and everything? That's pretty sweet. ...Tim From: Kevin Lundy [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Friday, October 10, 2008 8:35 AM To: NT System Admin Issues Subject: OCS questions We just installed OCS Enterprise. Currently pre-production. Exchange 2003. Native 2003 AD. Couple of questions: 1) It appears to be reading info properly from Exchange for calendar. The presence is not showing as I would have expected. If I have a meeting scheduled, the presence shows as "in a meeting" to team members as long as I'm at my desk during that time. However, if I lock my computer (such as for a meeting in a conference room), the presence changes to "away". So is this working as designed or do we have some trouble shooting to do? 2) Twice in the past 2 days, OCS has prompted me for my credentials to read the address book. This has happened long after I'm logged into XP and into Communicator, and while I'm actively working, but not using Communicator. So again, is this working as designed, or another problem for us to investigate? Thanks Kevin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
