D(one) IT

IT Tips, Tricks & Such

Lync Phone Edition Trusted Authorities Cache update – Jan 2014

Certificates for Lync Phone Edition TechNet article was updated Jan 7,2014 (http://technet.microsoft.com/en-us/library/gg398270). The Trusted Authorities Cache now includes DigiCert and a few more 2048-bit (Key Length) Root certificates.

ta1

The January 2014 Lync Phone Edition (LPE) CU includes the updated list of trusted public certificates.
January 2014 CU for LPE (Aastra 6721ip/6725ip)
January 2014 CU for LPE (HP 4110/4120)
January 2014 CU for LPE (Polycom CX500/CX600/CX3000)
January 2014 CU for LPE (Polycom CX700 and LG-Nortel IP Phone 8540)

Prior to the January update, certificates issued from DigiCert had to be requested in the Legacy format to work with LPE. Jaap Wesselius’ blog post details this issue: http://www.jaapwesselius.com/2013/12/01/polycom-cx600-fail-to-login-after-certificate-renewal-on-lync-2013-edge-server/

Lync 2013 SBA Front-End service fails to start

During a recent project deploying SBAs for Lync 2013, I came across an issue where the Lync Front-End service would not start.

The SBA was an AudioCodes Mediant 1000 SBA running version 1.1.12.0

Going through the Deployment Web GUI, the error would occur at “Start MCS Services”

sba1

Looking at the Deployment Log, the Front-End (RTCSRV) service would timeout.

sba2

Connecting to the SBA using RDP and reviewing Event logs showed:

  • System Event Log with Event ID: 7024

    sba3

  • Lync Server Event Log with Event ID: 50006

    sba4

  • Application Event Log with Event ID: 1000

    sba5

  • Windows Fabric Admin Event Log with Event ID: 2564

    sba6

The root issue was the Windows Fabric service would not stay running and seemed to be corrupt in the SBA image.

To Repair the Window Fabric Component:

  1. Stop Lync Services
    sba7
  2. Remove Windows Fabric application
    sba8

    sba9

    sba10

    sba11

  3. Don’t Restart
  4. Install Windows Fabric *** C:\Sources\WindowsFabric
    sba12

    sba13

    sba14

    sba15

    sba17

    sba16

    sba18

  5. Restart Windows
  6. Confirm Windows Fabric Service starts
    sba19
  7. Confirm all the Lync Services start *** Lync Server Front_end will take a while to go from Starting to Start
    sba20

Looking at TechNet, the same issue was reported with an OfficeMaster SBA from Ferrari Electronic: http://social.technet.microsoft.com/Forums/en-US/81699c3a-969b-4e2a-acc5-2148537928d3/windows-fabric-host-service-and-rtcsvc-not-starting-on-lync-2013-sba?forum=lyncdeploy

Event Zero – Dossier for Lync IM (Part 4)

This is a multi-part article that goes through the Dossier for Lync product suite from Event Zero. If you would like to read the other parts in this series please go to:

The Dossier for Lync product suite allows environments using Microsoft Lync to gain in depth insight into the way Lync is being used in real time within an organization. https://www.eventzero.com/Dossier/

Dossier for Lync IM (Instant Messaging) extends the default reporting in Lync by providing true “Operational Awareness” to an organization with data about IM volume and use to advanced analytics. https://www.eventzero.com/Dossier/DossierforLyncIM/

di1

  • Dashboard:

    di2

    di3

    di4

    di5

  • Recent IM Log:

    di6
  • View All IM Conversations:

    di7
  • View All IM Users:

    di8
  • View All Power Lists for IM Conversations:

    di9
  • View All Power Lists for IM Users:

    di10
  • IMs In The Last 30 Days:

    di11
  • Screen Shares In The Last 30 Days:

    di12
  • File Shares In The Last 30 Days:

    di13
  • Lync IM Power View:

    di15
  • Report Center:

    di14
  • Search:

    di16
  • Lync 2013 – High Performance App Sharing

    After installing Lync Server 2013 Cumulative Update 3 – October 2013 (http://support.microsoft.com/kb/2809243), the CSClientPolicy now exposes two new parameters for High Performance Application Sharing.

    hpas-1

    Looking at the Parameters for Set-CSClientPolicy on TechNet (http://technet.microsoft.com/en-us/library/gg398300.aspx)

    • EnableHighPerformanceP2PAppSharing: “When set to True, allows a peer-to-peer application sharing session to exceed the maximum frame rate of 2.5 frames per second. The default value is False.”
    • EnableHighPerformanceConferencingAppSharing: “When set to True, enables high performance application sharing in conferences. This improves the performance of application sharing, but, at the same time, means fewer resources are available to other processes.”

    Enable High Performance functionality:

    hpas-2

    Testing:

    Peer to Peer Desktop sharing of a YouTube video, both clients external via Edge (start both videos below at the same time to compare).

    • EnableHighPerformanceP2PAppSharing: False (Default)
    • EnableHighPerformanceP2PAppSharing: True

    Observations:
    With High Performance enabled the frame rate differences were noticeable, video playback was more fluid. Keep in mind bandwidth implications with turning on High Performance Application Sharing. Our internal testing saw client bandwidth fluctuate between 2 and 7 Mbps.

    Event Zero – Dossier for Lync Essentials (Part 3)

    This is a multi-part article that goes through the Dossier for Lync product suite from Event Zero. If you would like to read the other parts in this series please go to:

    The Dossier for Lync product suite allows environments using Microsoft Lync to gain in depth insight into the way Lync is being used in real time within an organization. https://www.eventzero.com/Dossier/

    Dossier for Lync Essentials assists organizations to understand usage patterns and costs from the use of Microsoft Lync by providing an organization wide, real time, continuously updated usage database for Lync activity, insight and cost accounting. https://www.eventzero.com/Dossier/DossierforLyncEssentials

    de1

  • Dashboard:

    de2

    de3

    de4

    de5

    de6

  • Session Overview:

    de7
  • Quality:

    de8

    de9

    de10

    de11

    de12

    de13

    de14

    de15

  • Adoption:

    de16
  • Modality Usage:

    de17
  • Active Calls Wallboard:

    de18
  • Recent Call Log:

    de19
  • Recent Conference Log:

    de20
  • View All Voip Calls:

    de21
  • View All Conferences:

    de22
  • View All Phone Numbers:

    de23
  • Response Code:

    de24
  • View All Power Lists for Voip Calls:

    de25

    de26

    de27

    de28

    de29

  • View All Power Lists for Phone Numbers:

    de30
  • View All Power Lists for Phone Numbers:

    de31
  • Report Center:

    de32
  • Lync Voice Power View:

    de33

    de34

    de35

    de37

    de38

  • Call Summary Details:

    de36
  • Search:

    de39
  • Dossier for Lync Essentials videos:

    • Call Statistics:
    • Overview:
    • Communications Timeline:
    • Advanced Call Flow Analysis:
  • Snom Lync Call Park support 7xx

    Integrating the Lync Call Park service on a Snom 7xx series phone.

    Snom phones allow you to capture a screenshot of the device’s LCD screen by browsing to: http://phoneIP/screen.bmp

    • LCD Screen:
      screen

    The 710 I received was shipped with 8.8.2.8 UC firmware, which didn’t include the Call Park+Orbit Function:

    8.8.2.8

    Looking at the New Features & Fixes list (http://www.snom.com/en/your-personal-menu/snom-uc-edition-firmware-center/snom-uc-edition-front-desk/snom-uc-edition-88216-snom-7xx-only/), Call Park support on the 7xx phones was added in 8.8.2.13 and improved upon in 8.8.2.14.

    The 8.8.3.X Beta (BToE) firmware site doesn’t show a 710 version available for download, but there is a “snom710-UC-8.8.3.201309090236-SIP-r.bin” on the download site. The 8.8.3.X firmware requires the Park+Orbit to be assigned to a function key.

    8.8.3.x

    • Call comes in:
      8.8.3.x-ring
    • Call is answered:
      8.8.3.x-con
    • Function key is pressed and Orbit info is displayed on screen:
      8.8.3.x-park
    • Note: To retrieve a parked call the Orbit number must be dialed, repressing the function key will not retrieve the call.

    I decided to deploy the current release version and found that the 8.8.2.16 firmware adds the Park+Orbit to the LCD call handling options and does not require a programmed function key.

    • Call comes in:
      8.8.2.16-ring
    • Call is answered (Park O is shown on the LCD):
      8.8.2.16-con
    • Park option is selected and Orbit info is displayed on screen:
      8.8.2.16-park
    • Call is retrieved by keying in the Orbit number and displays who retrieved the call:
      8.8.2.16-unpark
    • The display is updated if caller hangs up:
      8.8.2.16-hung

    Event Zero – Dossier for Lync Installation (Part 2)

    This is a multi-part article that goes through the Dossier for Lync product suite from Event Zero. If you would like to read the other parts in this series please go to:

    The Dossier for Lync product suite allows environments using Microsoft Lync to gain in depth insight into the way Lync is being used in real time within an organization. https://www.eventzero.com/Dossier/

    Dossier for Lync has two components the Connector and the Server. The Server comes in two formats: On-Premises (Hyper-V, VMware or Xen appliance) or On-Demand (Cloud). I’m a fan of the Cloud solution due to the vast number of enhancements released by Event Zero for the Dossier product suite and not having to manage the server appliance. The Connector is a small ~6MB application that is installed on each Front End, SBA and SQL Server hosting RGS/monitoring/archiving databases. Communication between each Connector and the Server is compressed to minimize bandwidth consumption and uses multiple layers of encryption.

    Installation:

    • To request a trial fill out the Dossier for Lync Pilot Request form: https://www.eventzero.com/Dossier/DossierforLyncEssentials/?view=Contact&notype=Pilot%C2%A0Request
    • Once the pilot is provisioned you will receive a Welcome email. This email provides specific service information for your pilot, links to download software and product documentation.
      dossier1
    • Cloud Control: Enables the ability to view/change service and account related information. I found changing the background would set to Beach1 no matter the option selected.
      dossier2

      dossier3

    • Enterprise Commander: Dashboard for the Dossier product suite
      dossier4b
      dossier4
    • Licensing: Located under the Global Setup tab. Detailing activated modules, expiry dates and endpoint licenses.
      dossier5
    • Account creation and password changes is located under the System Settings in Global Setup. This is also the location to configure Active Directory authentication later on.
      dossier7
    • Prerequisites
      • Archiving and Monitoring configured in the Lync Topology and databases deployed.
      • Administrative access to:
        • all Lync Enterprise Front End servers
        • any Lync Standalone servers
        • any SBA servers
        • SQL Servers hosting RGS (rgsconfig/rgsdyn), Archiving (LcsLog) and Monitoring (LcsCDR/QoEMetrics) Databases
      • Settings and policies configured for both Archiving and Monitoring, example:
        dossier8a

        dossier8b

        dossier8c

        dossier8d

    • Connector Installation:
      The Connector download link in the Welcome email was redirecting to the main page, use the following instead: https://www.eventzero.com/Download/?view=Connectors
      dossier6

      dossier9a

      I found that clicking the “Commander Connectors Documentation” button during the installation went to an error page, use the documentation links in the Welcome email or the following instead: https://eventzero.atlassian.net/wiki/display/HOME/Home
      dossier9b

      dossier9c

      The Connector service can run as Network Service or an Active Directory account. Leaving the default “run as Network service” is recommended and simplifies installation.
      dossier9d

      Commander Server Location can use one of two methods for discovery. Use Service Discovery looks to DNS for the SRV record: _ezentcom._https._tcp. using port 443 and the host offering this server is the FQDN of the Server. I prefer to specify the Server location manually during pilots and key in the Server FQDN from the Welcome email in the text field.
      dossier9e

      dossier9f

      dossier9g

      dossier9h

      dossier9i

    • Connector Configuration: Connectors try to communicate to the server after installation but need to be authorized and components configured before data will flow. This is done from Enterprise Commander.
      1. Authorize:
        dossier10a

        dossier10b

        dossier10c

        dossier10d

        dossier10e

      2. Components: After authorizing the Connector page will now show the Components section.
        The SQL Server Connectors should have the Lync 2013 Archive and Lync RGS Configuration sections configured. Enable State components and modify the Database Connection Strings to match what is deployed in the environment. For my installation I had to append the SQL Server instance name after localhost (\LYNC). For more details on the Database Connection Strings see: https://eventzero.atlassian.net/wiki/display/Lync/Installation+Guide
        dossier11a

        The Lync Front End Connectors should have the Lync RGS Realtime and Lync SIP State components enabled. This registers a service on the Front End server to collect additional information that is not stored in the Archiving or Monitoring databases.
        dossier11b

    • SQL Server Login: The run as Service account used in Connector installation needs to have a login account created on the SQL Server and DB_datareader permissions to the rgsconfig, rgsdyn, LcsLog, LcsCDR and QoEMetrics Databases. This is done using SQL Server Management Studio, for more details see: https://eventzero.atlassian.net/wiki/display/Lync/How+to+create+a+SQL+Server+Login+for+Dossier+for+Lync+Essentials

      dossier12a

      dossier12b

      DB_datareader needs to be check for each database individually.
      dossier12c

    • Data will start showing in the Dashboards.
      dossier14
    • Trouble Shooting:
      Live Errors is available on the Connector page, with detailed messages.
      dossier13a

      Capturing logs to send to Event Zero support is available on the Connector page.
      dossier13aa

      Connector log files can be viewed locally from c:\ProgramData\Event Zero\Connectors\
      dossier13c

      Windows Application Event Log will highlight any SQL Server permission issues.
      dossier13b

    Event Zero – Dossier for Lync Overview (Part 1)

    This is a multi-part article that goes through the Dossier for Lync product suite from Event Zero. If you would like to read the other parts in this series please go to:

    The Dossier for Lync product suite allows environments using Microsoft Lync to gain in depth insight into the way Lync is being used in real time within an organization. Dossier for Lync is available in 2 different formats: On-Premises and On-Demand (Cloud). https://www.eventzero.com/Dossier/

    The product suite contains the following modules:

    System Compatibility:

    1. Client Software:

      • Windows Lync Client 2010
      • Windows Lync Client 2013
      • Lync Phone Edition (LPE)
      • Lync for Android
      • Lync for iPhone
      • Lync for OSX
      • Lync for Windows Mobile
      • Lync for WindowsRT

    2. Lync Server Environment

      • Microsoft Lync Server 2013
      • Microsoft Lync Server 2010
      • Microsoft Lync Monitoring SQL Databases (LcsCDR & QoEMetrics)
      • Microsoft Lync Archiving SQL Database (LcsLog)
      • Microsoft Lync Response Group SQL Databases (RGSConfig & RGSDYN)

    3. On-Demand (Cloud)

      • Internet Access

    4. On-Premises Environment

      • Microsoft Hyper-V 2012 and above
      • VMWare ESXI 4.1 and above

    CyberData VoIP v3 Paging Server

    The CyberData VoIP v3 Paging Server allows a single SIP phone extension to access up to a 100 multicast zones and to connect to an analog overhead paging system. The VoIP paging server is powered via Power over Ethernet (PoE) or a power adapter (not included) with a MSRP of $499.

    Features:

    • Web-based Administration
    • Voice prompting
    • Password-controlled zones
    • Supports 600 Ohm output
    • Page start relay contacts
    • Remote amp fault sensor
    • SIP RFC 3261 compatible
    • Multicast output
    • Two SIP endpoints (one for Night Ringer)
    • DTMF control of zone selection
    • Delayed Page Support
    • Line-In connection for music
    • Line-out connection to support analog Amps

    Resources:

    Device:

    • Front
      cyber-1
    • Back
      cyber-2

    Quick Setup:

    1. Connect Paging Server to Power source and Network
    2. Find/Change IP: Paging Server uses DHCP by default. CyberData provides a Discovery Utility (http://www.cyberdata.net/support/voip/VoIP_Discovery_Utility.zip) to help locate the device on the network and statically set the IP.
      Cyber-3
    3. Use Discovery Utility or web browser to connect to the Administration page (Default user: admin, Default password: admin)
      Cyber-4a
    4. Update Firmware: v7.0.0
      1. Download Firmware Update (ZIP): http://www.cyberdata.net/products/voip/digitalanalog/pagingserverv3/drivers/700-uImage-pserver_nosig.zip
      2. Unzip file
      3. Apply Update: Upgrade Tab in the Web Administration, Click “Choose File” and locate the extracted firmware file and click “Submit”
        Cyber-5
      4. Paging Server will reboot when upload is complete

    Paging with Lync

    Web Administration

    • Home: Allows you to change the Device Name, Username, Password, lists Current Settings and allows for the Import or Export of the Configuration.

      Cyber-6a

    • Device Config: Assign Device’s Multicast Address, Miscellaneous Settings and the Ability to Test Audio, Multicast and Relay.
      Cyber-6b
      ***Note: Device’s Multicast Address cannot be used for a Paging Group***
      Cyber-7
    • Networking: Static or DHCP IP settings.
      Cyber-6c
    • SIP Config: SIP registration information.
      Cyber-6d
    • Nightringer: Secondary SIP registration information.
      Cyber-6e
    • Fault Detection: Triggers during a fault.
      Cyber-6f
    • PGROUPs Config: Configure Paging Group’s (0-99) Zone Number, Name, Multicast Address, Port, Security Code, TTL and enabled or disable Lineout port. ***Note: Paging Groups 0-24 (first page) has the Lineout box checked by default, to enable this feature the check had to be removed.***
      Cyber-6g
    • Audio Config: Upload custom audio files.
      Cyber-6h
    • Event Config: Send HTTP POST events to a remote server when actions occur.
      Cyber-6i
    • Autoprovisioning: Paging Server get its configuration from a remote server on startup or schedule.
      Cyber-6j
    • Update Firmware: Upgrade Device Firmware.
      Cyber-6k

    DCOM Error When Attempting To Move Lync Users

    Working with a client to move users between a Lync 2010 pool and a new Lync 2013 pool, a collegue of mine came across the following error:

    Unable to connect to some of the servers in pool “poolname” due to a Distributed Component Object Model (DCOM) error. Verify that Front End service is running on servers in this pool. If the pool is set up for load balancing, verify that load balancer is configured correctly.

    DCOM-1

    Trying the same move from the Lync Management Shell had the following error:

    Cannot find Registrar pool. Verify that “poolname” is a valid registrar pool.

    dcom3

    Searching the net for the error yielded fixes if the pool was behind a hardware load balancer or messing with the dcomcnfg tool.



    Unfortunately neither solution work in our scenario. To resolve the error, the Local Security Policy of the servers reported in the error needed to be modified.

    Fix:

    1. Click “Start” -> “Run” -> Type “secpol.msc” -> Click “OK”
    2. Expand “Local Policies” -> Click on “Secuirty Options”
    3. Double Click “DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax” Policy
    4. On the “Template Secuirty Policy Setting” Click “Edit Security”
    5. Click “Add” -> Type “RTCUniversalServerAdmins” -> Click “OK”
    6. Check all the Allow boxes for the RTCUniversalServerAdmins account -> Click “OK”
    7. Log off and on
    8. DCOM-2

    All credit goes to Korbyn for finding the fix.

    Follow

    Get every new post delivered to your Inbox.

    Join 78 other followers