Showing posts from 2012

Lync/ Exchange Certificates CRL Check (Proxy Servers)

In Exchange, as well as in Lync in always have some customers using proxy server. Due to nature of proper certificate validation processes, windows server need to validate the CRL (Certificate Revocation List). Since the CRL is a normal file, which we can download from CA provider, we need to ensure the accessibility of those files. in some customer environments we also find a mysterious behavior and we need to modify the WINHTTP proxy settings manually. there are two ways how to do so, if the normal IE setting will not work: netsh winhttp import proxy ie or netsh winhttp set proxy proxy-server=" " bypass-list="*,<local>" while with the bypass-list we need to play around till it fits. Also happened, especially in Exchange, I had to reboot the server before the settings got activated. Also don't forget about the IE Setting: for installation purposes (also for service packs), you should disable t

Lync Server 2013 for IT pros

Since is always an hassle finding the right Information on Microsoft Webpage about Lync 2013, there is an entry point where you are able to step into as portal. Microsoft has listed all important Links, sorted and well documented, so it's easy to navigate to the necessary Information quickly. Lync 2010: Lync 2013: As well as the Interoperability Program: Author: Thomas Pött Managing Consultant Microsoft UC

Lync Server 2010 on Windows Server 2012 (it works)

Windows Server 2012 (copied from Microsoft Support Webpage) Lync Server 2010 server roles are compatible with Windows Server 2012. For this to be supported, you must install the October 2012 cumulative updates for Lync Server. For more information about these updates, click the following article number to view the article in the Microsoft Knowledge Base: 2493736   ( )      Updates for Lync Server 2010 Important After you install Lync 2010 Server on Windows Server 2012, the Lync Server 2010 application pools are configured to use the Microsoft .NET Framework 4.0. However, the Lync Server 2010 application pools use the .NET Framework 2.0. For information about how to change the version of the .NET Framework that is used by the Lync Server 2010 application pools, click the following article number to view the article in the Microsoft Knowledge Base: 2777747   ( )      "404.17 -

Lync Mobile Client 2013 VoIP

Now it's official The new Mobile Client will be released first for WM7/8, than iPhone and at last for Android. Regarding the question we all had was about VoIP, well 100% true Voice will be integrated. Release date is expected around April 2013. Good to hear this. But don't think you can use VoIP features with Lync Server 2010 as backend. You have to have Lync Server 2013. I have updated this article with more detailed information and new features, as well as client feature sets: please visit Author: Thomas Pött Managing Consultant Microsoft UC

All Lync 2013 Client Version (comparision)

Microsoft has mutliple client version for Lync 2013 available. Not only 32/64 bit versions, we differentiate here more regading the featuresets: Available Verisons: Full Version Client: Part of Office 2013 Profession Plus (32/64bit) Windows 8 App Store : Lync 2013 App Windows 7/8 Phone Edition Client: Windows Phone App Lync 2013 Basic Version: downloadable in 32bit: 64bit: VDI Client: 32bit: 64bit: other Clients: Lync Phone Edition, Lync for Mac 2011 If you see the huge comparision list of all features across all clients: Author: Thomas Pött Managing Consultant Microsoft UC

Lync 2013 VDI Plug-In

LYNC 2013 Virtual Desktop Infrastructure Plug-In The following are requirements for the virtual machines running on the data center computer: Virtual machines must be configured with Windows 8, Windows 7, or Windows Server 2008 R2 with the latest service packs. The following are requirements for the user’s local computer: The local computer must be running Windows Embedded Standard 7 with SP1, Windows 7 with SP1, or Windows 8. If you are using Remote Desktop Services, the Lync VDI plug-in bitness (that is, whether the application is 32-bit or 64-bit) must match the local computer’s operating system bitness. The bitness of the operating system on the local computer and the operating system on the virtual machine do not need to match. If you are using another virtualization solution or platform, refer to guidance from your virtualization solution provider about bitness requirements. The local computer must be running the latest version of the remote desktop client. Install the

Lync 2013 Documentation

Lync 2013 Server documentation is available online. Soon the download version will be released. Getting Started View online: Getting Started Planning View online: Planning View online: Planning Primer: Planning for Your Organization View online: Determining Your Infrastructure Requirements View online: Planning for High Availability and Disaster Recovery View online: Planning for Front End Servers, Instant Messaging, and Presence View online: Planning for Conferencing View online: Configuring Video View online: Planning for External User Access View online: Planning for Enterprise Voice View online: Planning for Archiving View online: Planning for Persistent Chat Server View online: Planning for Clients and Devices in Lync Server 2013 View online: Planning for Remote Call Control View online: Planning for Mobility Supportability View online: Supportability

Lync 2013 Server Prerequisit in Nutshell

Since I always had a problem finding my PreRequisit installation scripts, I decided posting it here. So, even I will from now on find my links and script. If like to read the Technet Article: Link to prerequisit Information Have fun with it: For Windows Server 2008 R2 and Windows Server 2012: Silverlight (opt) Windows Identity Foundation 3.5 (Server 2012 as Role, in W2k8 R2) download for 2008 R2: . -------------------- Windows 2008 R2 Server PowerShell 3.0 PowerShell 3.0 is not a standalone product, it's part of the Windows Framework 3.0 .Net Framework 4.5 Windows Identity Foundation Import-Module ServerManage r Add-WindowsFeature RSAT-ADDS # if Persistent Chat is r

Lync OAuth Protocol and Confgiuration

What is Server-to-Server/ OAuthentication Protocol? OAuth2 is an open standard for authorization used by Microsoft Office 2013 Servers. It allows users to access their private resources (e.g. Lync Contact List, IM Archiving) stored on Servers without having to hand out their credentials, typically supplying username and password tokens instead. Each token grants access to a specific service for specific resources and for a defined duration OAuth2 standard-based server-to-server trust across all Office 2013 servers Lync, Exchange, Microsoft Office SharePoint®, Active Directory In Lync scenarios enabled for: Unified Contacts, IM Archiving, OWA meeting scheduling Hybrid Model: On-Premise Model: Prerequisites: Certificate: token issuer certificate (OAuthTokenIssuer) must be request able on PKI - TIP: every Web Server Certificate that includes the name of the SIP Domain in the Subject Field can be used as OAuthTokenIssuer Certificate Configuration Steps for On-Pr

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) -        

Location Information Service (LIS) Lync 2010/ 2013

Lync 2010 with CU1 introduced the LIS for identifying the Users Location for E-9-1-1 call and internal information too. The E-9-1-1 Service must be supported by a) SIP Trunk Provider or/and b) Law. What does Law mean?   Simply explained, if you are for example in Germany, so need to ensure you can make Emergency Calls also during Power Interruption. This cannot be done with Computer based Systems. A PABX is different, there are service ensuring the phones availability. So let look into LIS itself: The information will be stored in the LIS Database for Lync, which is the same for Lync 2010 and 2013. Lync identifies 4 different Location Types: 1.      Switch Ports 2.      Switches 3.      IP Subnets 4.      Wireless Access Points All associated commands here are: Get-CsLisSubnet Set-CsLisSubnet Remove-CsLisSubnet Get-CsLisWirelessAccessPoint Set-CsLisWirelessAccessPoint Remove-CsLisWirelessAccessPoint Get-CsLisSwitch Set-CsLisSwitch Remove-CsLi

LYNC Device Configuration (DHCP) - Step by Step

New feature Lync 2013: Differences between Lync 2010 and Lync 2013 is in the DHCP Option 43. Lync 2013 support with it's devices a dedicated VLAN deployment.     Todo's before configuring DHCP: Before we are starting the DHCP Server Option, we need to make Lync 2010/ 2013 aware of the DHCP enbaled devices. Turn on this functionality by using this Lync Server Management Shell command as follows: set-CsRegistrarConfiguration -EnableDHCPServer $true In addition, ensure that broadcast packets from the client can reach the DHCP server(s) on the Registrar. This may mean configuring DHCP relay agents to forward DHCP packets to DHCP servers on the Registrar.   DHCP Options which are requred: Option 120 (SIP Servers) is defined in RFC 3361. It is used to return a list of SIP servers. Option 55 is used by the device to ask the DHCP server for the values of specific options (in our case 120 and 43). Option 60 is used by the client to specify the vendor f

Lync Server 2013 Enterprise Server Setup (Step-by-Step)

Now it's time for the for the fir Lync 2013 site. I'm following up with the Topology blog i released earlier. I prepare the first Enterprise Server Lync 2013. Just in the Test Lab, I don't have the Load Balance yet, so what I did was, I gave the only EE Server two IP addresses. The second one is for the POOLLEFT, this is a supported scenario if you only have single pool server in place. First we need all the Pre-Requisites for the new EE Server in place, which I have listed here: PowerShell 3.0 PowerShell 3.0 is not a standalone product, it's part of the Windows Framework 3.0 .Net Framework 4.5 Windows Identity Foundation IIS Windows Desktop Experience SilverLight 4 Visual C++ 11 x64 Active Directory Management tools IIS: Static Content Def