I frequent the Lync TechNet forums: http://social.technet.microsoft.com/Forums/en-US/category/lync and was recently asked how one would get a report for all users that have Desktop Sharing enabled.
I took the script from here: http://blogs.technet.com/b/nexthop/archive/2010/06/07/scriptuserpolicyassignments.aspx
Modified it to run for all users, detect only the Conferencing policy and write a line when EnableAppDesktopSharing is equal to Desktop for the user.
Sample output:
Jay Pritchett / Conferencing Policy: Global policy / Sharing: Desktop
While browsing TechNet I noticed the Lync 2013 downloads and updates pages has been redesigned, now including items for Lync 2010 and OCS 2007 R2. http://technet.microsoft.com/en-us/lync/dn146015.aspx
Old Layout:
New Layout:
Some missing items:
Microsoft Lync Connectivity Analyzer: http://technet.microsoft.com/en-us/library/jj907302.aspx and the Microsoft Remote Connectivity Analyzer: https://www.testexchangeconnectivity.com/ are not listed under “Tools”. Lync 2013 for Android: https://play.google.com/store/apps/details?id=com.microsoft.office.lync15&hl=en is not under “Mobile platform clients”. Rollout and Adoption Success kit: http://technet.microsoft.com/en-us/lync/jj879331 No links to Lync Basic 2013 client (32bit: http://www.
I came across an issue where a fresh install of the Lync Connectivity Analyzer ( http://technet.microsoft.com/en-us/library/jj907302.aspx ) on Server 2012 wouldn’t launch. Looking in the Event Viewer I found the following errors.
Event: ID 1026
Source .Net Runtime
Application: LyncConnectivityAnalyzer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Event: ID 1000
Source: Application Error
Faulting application name: LyncConnectivityAnalyzer.exe, version: 5.0.8308.289, time stamp: 0x5113842c
When deploying an Office Web Apps Server (WAC/OWAS) the default allow list contains no domains, meaning OWAS will allow file requests to hosts in any domain.
This could allow unauthorized use of your server/farm if the Office Web Apps Server is accessible from the Internet (deployed in DMZ or Reverse Proxy to Internal). An external party could define the Office Web Apps Server pointing to your OWAS URL and start using your server for their workloads.
With SNOM’s Enhanced Better Together being demonstrated at WPC 2013: http://www.snom.com/en/news/archive/article/2013/en/snom-to-demonstrate-pc-pairing-%E2%80%9Cbetter-together%E2%80%9D-features-on-its-microsoft-lync-qualified-desktop-phones-at-wpc-2013/ and availability being most likely end of 2013. I figured it would be a good time to post my review of the Call Via Phone Advanced. A 3rd party Better Together type application for Lync and SNOM phones which is currently available.
The Call Via Phone application comes in two editions (free and paid) and works with Lync 2010 and 2013.
Incoming calls from the PSTN to an unassigned number within the unassigned number range on Lync 2013, the call fails. The same number called from the Lync client completes successfully, and is routed to either the Announcement service or Exchange Attendant depending on configuration. In Snooper the call trace shows a “486 Busy Here” or “403 forbidden” or “404 not found” depending on your Gateway/PSTN provider.
Looking into the 403 forbidden message, I came across VOIPNorm’s Call Park Retrieval Issues From CUCM 8.
On each Lync 2013 Front End the Data MCU will attempt to connect to the Lync Web App Reach URL over TCP/8061 every thirty minutes, this poke event uses the server FQDN. If the External Lync Web Services is using a certificate that doesn’t contain the server FQDN, a 41029 will be recorded to the Event Log every poke.
Server FQDN is not included by default when requesting a separate certificate for the Lync External Web Services.
When applying Lync Server (2010/2013) Cumulative Updates, one step that is often overlooked is updating the Monitoring Server Reports hosted on SQL Server Reporting Services (SSRS).
Looking at TechNet for both 2010/2013 there is no reference to update Lync Monitoring Server Reports:
Cumulative Updates for Lync Server 2013: February 2013 Cumulative Updates for Lync Server 2010: March 2013 Lync Server 2013 Monitoring Reports RTM Version: 5.0.8308**.0**:
After applying the Lync 2013 CU1 update, I noticed some oddities with the Test-CsDatabase –LocalService. All databases showed Expected Version and Installed Version matching, except for:
Localrtclocal: rtcdyn – Expected Version 125.6.2 / Installed Version 0.0.0 Localrtclocal: xds – Expected Version BLANK / Installed Version 10.13.2 Status:
Known issue and can be safely ignored.
With the recent announcement: Snom IP Phones Deliver Out-of-the-Box Provisioning Speeds and Simplify Microsoft Lync Voice Deployments. I decided to setup Lync Device Update service for my Snom 760.
A quick check on the Lync Interop Programs shows the Snom 760 as compatible with Lync 2013 and Managed Updates supported:
Downloaded the snom760-8.8.2.10.cab firmware, imported and approved the update:
I found the 760 registered to our Lync 2013 environment via the Edge server but refused to attempt the firmware update, where as my Lync phone edition devices (Polycom cx600 and Aastra 6735) had no issue.
