IIRC it's the other way around - AOL is free and Yahoo still needs PIC CALs
Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: Steven Peck [mailto:[email protected]] Sent: Monday, May 10, 2010 4:58 PM To: NT System Admin Issues Subject: Re: log Windows Live Messenger conversations OCS with Archiving and federation. Otherwise some network logging appliance but i fthe clients are using something like SimpLite then you are out of luck http://www.secway.fr/us/products/simplite_msn/home.php Get OCS2007r2. Connecting with MSN and Yahoo Public IM (PIC) networks now does not require a license. Just block AOL or pay for licenses. Steven On Mon, May 10, 2010 at 2:54 PM, Brian Desmond <[email protected]> wrote: > Bill- > > > > You need an appliance. I know Symantec makes one as a previous > employer imposed this upon us. Depending on your FW/Proxy environment > that vendor might also make a plugin or have a 3rd party addin to it for this. > > > > A better solution would be something like OCS with Archiving and > Federation w/ MSN, etc., IMO. > > > > Thanks, > > Brian Desmond > > [email protected] > > > > c - 312.731.3132 > > > > From: Bill Songstad [mailto:[email protected]] > Sent: Monday, May 10, 2010 4:52 PM > To: NT System Admin Issues > Subject: log Windows Live Messenger conversations > > > > My office uses WLM for communication to supplement email and telephones. > That battle is lost. But the next battle is to log communications > through that medium for legal purposes. My Google Fu has been less > than encouraging as the popular opinion is that since there are no > GPOs for WLM and since the reg keys needed are encrypted and > unpredictably variable, it wouldn't be possible to turn on logging with Group > Policy. > > > > So what I am asking is: Does anybody know how to, or have a strategy > to administratively turn on logging for Windows Messenger? Or will I > just have to disable it if we ever become involved in a lawsuit? > > > > What I need to do is turn on message history and prevent users from > turning it off. Ideally this would be something I could turn on or off as > needed. > > > > Any insight would be appreciated, > > > > -Bill > > > > > > > > ~ 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/> ~
