Presence can factor location and device so, let's streamline some of this stuff and make it easy for the user.
From a Communicator Mobile experience perspective, Single Number Reach is mandatory for enterprise organizations, but I also want to be able to walk into the office, have my presence pick-up and update my Communicator account to take calls in the office and as soon as I walk out of the office with my mobile device, allow me to automatically pickup office and personal calls on my mobile and bridge the office calls through the OCS server, WITHOUT EVER HAVING TO CONFIGURE ANYTHING.
In my opinion, there is not one mobile device or platform that truly fits the needs of the individual so hopefully Microsoft is working on something that is device agnostic in which the user can customize their own mobile experience and for heaven's sake, please incorporate a media experience that accepts iTunes and Windows Media. For more information on the Windows Mobile release and the Single Number Reach feature, check out the following link:įrom my perspective, I hope to see a much different design by the next Worldwide Partner Conference. With mobile platforms like the iPhone now in its second release, you would think that Microsoft would have something really cool and efficient to show as the company is trying to change its "coolness" factor to consumers. While Single Number Reach is a huge feature for enterprise organizations to keep track and accounting of corporate mobile user's communications and to provide seamless office/mobile communications through the power of OCS 2007 R2 saving on mobile communications costs, I have to say I was not blown away. In normal usage we should disable the logs since it will continuously generate log files filling the hard disk with unnecessary files.While having a blast in New Orleans at the Microsoft Worldwide Partner Conference, I had only one product that was of any interest for me to see an update of Windows Mobile 6.5 and the improvements made for the Microsoft Office Communicator Mobile client for Microsoft Office Communications Server 2007 R2. The trace logs in Communicator/Client are really useful but, in my opinion, we should only enable them when trying to troubleshoot an issue.
Now we can choose from 3 trace log levels. In the previous versions logging was disabled by default. As in Lync 2010, we can access options using the gear/cog.Īnd also use the drop down menu, “Tools-> Options”.īy default logging is enabled (Full level) in Lync 2013 Client. This time we’ve got another makeover in Lync client.
Interestingly, Microsoft Lync is not just restricted to Microsoft products like Windows based operating systems, Windows 8 tablets or Windows Phone, but is also available for competitor devices including Mac, Android, iPhone and iPad. To enable Trace log tick “Turn on logging in Lync” check-box. Microsoft Lync is a famous application from the Microsoft Office suite which provides some very impressive video conferencing features. The “General” tab is default in the “Options” window. Or select the drop down menu next to the gear and then “Tools ->Options”.
Now to access options we select the gear/cog directly: In Lync 2010 the client changed the graphical interface but the “Options” window is similar to the one in Communicator. In the “Options” window we select the “General” tab and finally activate logging by ticking the option “Turn on logging in Communicator”.
Or we can select “Tools -> Options”, from the drop down menu. To access the options we can click on the presence indicator and select “Options”. The new release, version 7.0, supports Microsoft Office Communications Server (OCS) 2007 and its enhanced presence model. Trace logs are important in troubleshooting because most of the problems related to failure in instant messages or video/audio calls can be detected in Communicator/Lync Trace logs. I created the following steps to help to enable logging.
One thing that I’m always looking for is how to enable Trace Logs in Communicator/Lync.