We've had an internal LCS solution for years. We have a restricted pilot to Public IM for a subset of users. We are transitioning to OCS2007r2 currently. Out of all users with IM accounts we have 3/4 logged on during business hours. I consider this a rather high buy in rate for an instant messaging product. We do not have a company mandate that requires people to be logged in.
The transition is to add archiving capabilities. However the actual policy is being debated now. What I suspect will happen is what we do with laptops. If you have a business need to use IM communications you will sign a document saying you have read and understood the business rules and agree to abide by them (which really can be summed up to: don't be stupid, this isn't your property and can be audited). PIM users will probably have their communications automatically archived, the rest will not. This is a guess. As most executives will be the primary recipients for this, I suspect the archives will be accessed only when there is a question or issue (we have email archival as well). We fall under HIPAA rules. We do not fall under SOX but are considering working under them just because the laws will probably eventually cover us. (Not for profit insurance) We are not using the live meeting subset of features due to licensing but will probably trial it and possibly implement it later. We have trialed VOIP through LCS2005 which was well received but Communicator 2005 had client UI issues (which MS said it would) that did not make it suitable for corporate use. I suspect that we will be trialing VOIP again with OCS2007r2. I would love to do conference lines with it and offload the dozens of external conference lines we currently pay for primarily internal only use. Steven Peck On Thu, Feb 18, 2010 at 12:43 PM, Kurt Buff <[email protected]> wrote: > Anyone out there care to share their policy and (very) general > implementation info on IM and personal video conferencing usage? > > Does your company, for instance, allow users to install and use any of > the major consumer IM/video apps and communicate directly to the major > public IM/video providers such as MSN, AOL, Yahoo! and Google? > > If your company does allow it, what does the company consider to be > the cost/benefit tradeoff WRT security and not using a centralized > IM/video server with gateways to public IM/video services? > > Also, what security concerns were looked at before implementation and > what measures, if any, were taken to mitigate them? > > If direct access to public IM/video services isn't allowed, is an > IM/video service provided for business purposes, and if so, what are > you using - MSFT OCS, or Openfire, or something else? > > If you can't comment on-list, but don't mind doing so off-list, I'd > certainly appreciate it. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
