Microsoft Messenger for Mac 6.0.2 release - logging clarification
Microsoft Messenger for Mac 6.0.2, released Jan 30, 2007
I would like to let you know that the logging paragraph, included below, implies unfortunately that the logging is logging everything. Sadly this is not true and the logging will only work with the Personal (MSN) sessions. To be clear the Microsoft Messenger for Mac client is a multiple stack (2) client similar to Windows Messenger. This allows you to use one client UI to sign-in to multiple services. In this case you sign in to MSN (Personal) and LCS (SIP protocol Corporate tab).
So you were hopping to deploy this new client for your LCS deployment and resolve the lack of logging issue? Well thankfully one customer has said that to be true and I have worked with the Mac team to put in a tracking request that the next version include that. Most of us not running the client are ok with that, but for those deploying it, why do I have to wait? Well don't... send me in email (toml at microsoft dot com) your company name, your total number of LCS seats and how many of those are MAC clients. Be honest when you say what the impact is - can you deal with LCS server side logging, if not why not? Can you deploy LCS using TCP over port 5060 and install Wireshark on your Mac workstation? Annoyance sure, but any reason why you can't? I am not minimizing the problem or effort what I am doing it making sure I don't put in a request that would cause the team to over prioritize this request over another, remember decisions have to be made as time and money are not endless even for the Microsoft empire :)
Additionally, Messenger for Mac 6.0.2 includes logging. Log files can help troubleshoot various problems in Messenger such as connection problems, status failures, and other issues. Enabling logs saves a file containing personal information to ~/Documents. Anyone with access to this directory can open this file. By default, Messenger logging is turned off. For more information about how to enable logging for troubleshooting problems, contact support
Tom