Showing posts from October, 2012

System Center Operation Manager with Lync

System Center 2012 Operation Manager is the preferred choice fro Lync Monitoring. Please don't confuse yourself with Lync Monitoring Server, which actually monitors the call and conferences, as well as the QoE data . 1. With Lync 2013 you still need the NEW UCMA 4.0 (for Lync 2010 UCMA 3.0 was sufficient) and make sure you have the latest Windows Updates installed. And the Lync and SCOM Server need to be in the same AD Domain or a trusted domain. 2. In SCOM 2012 you need a dedicated Notification Action Account (NAA). if you don't have already configured on, make sure its and AD enabled normal user account. 3. After the NAA is replicated through AD, you have to enable this user for Lync. Follow your normal procedure as you do for normal Lync users too. you can do so from the Control Panel or from PowerShell (Enable-Cs-User command) Next it's part working on SCOM site: Still you need a SCOM Console and a user who is Operation Manager Administrator. 4. After you logged

RTM Office 2013 + Lync, Exchange available

Just the fast info for everybody who is waiting since weeks and was guessing when the RTM is public. Since yesterday night, RTM for Office 2013, Lync 2013 and Exchange 2013 is downloadable via MSDN. Have fun and check it out Author: Thomas Pött Managing Consultant Microsoft UC

Secured, SIP Secured and Unsecured Voice integration Exchange

In Exchange 2007/ 2010/ 2013, you are able to set different security configuration for your SIP Traffic. Therefore special configuration between Gateway, Lync (via Exchange Dial Plans) and Server-to-Server Communication can be defined. Let talk about Exchange 2013 and Lync 2013 UM integration, especially for your configuration in your live environment.   With Exchange Administration Center (EAC) or the Set-UMDialPlan cmdlet in PowerShell you can define your SIP Security configuration. When you configure the UM dial plan to use SIP secured* ( [-VoIPSecurity <SIPSecured | Unsecured | Secured>]) or Secured mode, Client Access and Mailbox servers will encrypt the SIP signaling traffic or the RTP media channels or both. For Lync, you need the special SIP Secured Mode (described below) VoIP security mode, can be configured as: -           SIP secured (SIP Secured setting only protect SIP traffic using TLS while RTP traffic would be transmitted over TCP) -