We implemented Openfire in March for internal communication and the business LOVES it. It's got a plugin for message archival. We use Pidgin as the client (with all the protocols besides xmpp removed - just remove the dlls). We tried Spark as the client for a while but the resource usage was crazy (90+ MB at times, whereas Pidgin hovers around 16 MB).
- Andy O. >-----Original Message----- >From: Kurt Buff [mailto:[email protected]] >Sent: Thursday, February 18, 2010 2:44 PM >To: NT System Admin Issues >Subject: IM raises its ugly head again... > >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/> ~
