Instant Translation with Lync 2013

I was wondering if my Lync Client can translate my IM messages when i send the messages to other colleagues in their local language. I found the below work around to achieve my goal.

Open a Notepad and copy the below code and save it as Translate.Reg

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\MicrosoftOffice\15.0\Lync\Addins\{2b26edf9-92e0-4d9c-9d7a-f772fcd4f31b}]
"Name"="Lync Conversation Translator"
"Parameters"=""
"ExtensibilityApplicationType"=dword:00000000
"ExtensibilityWindowSize"=dword:00000001
"DefaultContextPackage"=dword:00000000
"InternalURL"="http://go.microsoft.com/fwlink/?LinkID=68810&Lync=y"
"ExternalURL"="http://go.microsoft.com/fwlink/?LinkID=68810&Lync=y"


[HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\Security]

[HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\Security\Trusted Sites]

[HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\Security\Trusted Sites\conversationtranslator.cloudapp.net]
"http"=dword:00000001
"https"=dword:00000001

Right Click on the Translate.Reg and Click Merge and Click OK to update the registry entries

Exit and Restart Lync Client 2013

Once you start Lync 2013 you will find ... in the IM Conversation window, now you need to do the settings of yours and other user language. If you don't do then you will get below error

Once you provide the correct settings, you will be able to modify the language of your or others to which you are sending the IM message

Note: You must have Silverlight installed in your system

Modify the SIP address of an Enabled Lync User

For various reasons you may need to modify the SIP address for eg if you have acquired a new company and you want them to use the existing domain name in their SIP address.

For a Single User, you can run the below command:

Set-CsUser -Identity "Anil Kumar Nudurupati" -SipAddress "anilkumar.nudurupati@newsipdomain.com"

If the same task if you have to do for multiple users, then it will be a tedious task if you perform via Control Panel or by running above powershell command. For this you need to use the below PowerShell Script.

For Bulk Users

$users=Import-Csv .\users.csv
foreach ($user in $users)
    {
        $oldAddress = $user.SipAddress
        $newAddress = $oldAddress -replace "@oldsipdomain.com", "@newsipdomain.com"
        Set-CsUser -Identity $user.Identity -SipAddress $newAddress
    }

Introduction to Lync Server 2013

Lync Server 2013 and its client software, such as Lync 2013 enables users to connect in new ways and to stay connected regardless of their physical location.

IM and Presence: Instant Messaging (IM) and presence help users to find and communicate  with one another efficiently and effectively. 
IM provides an instant messaging platform with conversation history, and supports public IM connectivity with users of public IM networks such as MSN/Windows Live, Yahoo!, AOL, and Google Talk.

Note: An end of life date of June 2014 for AOL and Yahoo! has been announced.

 Conferencing: Lync Server includes support for IM conferencing, audio conferencing, web conferencing, video conferencing and application sharing, for both scheduled and ad-hoc meetings. All these meeting types are supported with a single client. Lync Server also supports dial-in conferencing so that users of public switched telephone network (PSTN) phones can participate in the audio portion of conferences.

Enterprise Voice: Enterprise Voice is the Voice over Internet Protocol (VoIP) offering in Lync Server. It delivers a voice option to enhance or replace traditional private branch exchange (PBX) systems. 

Support for Remote Users: You can provide full Lync Server functionality for users who are currently outside your organization's firewall by deploying servers called Edge Servers to provide a connection for these remote users. These remote users can connect to conferences by using a personal computer with Lync 2013 installed, the phone or a web interface.

Mobile Client Support: With Lync mobility services, users can access Lync functionality when using supported Apple iOS, Android, Windows Phone or Nokia mobile devices and platform such as send/receive instant messages, view contacts, view presence.

Integration with Other products: Meeting tools are integrated into Outlook to schedule a meeting or start an ad-hoc conference with a single click and make it just as easy for attendees to join. Presence information is integrated with Outlook and SharePoint.

Simple Deployment:  To plan and deploy servers and clients Lync provides the Topology Builder. Topology Builder is an installation component of Lync Server. Topology Builder used to create, adjust and publish your planned topology.

Simple Management: 

1. Central Configuration Management, which enables you to manage changes centrally and have them replicated quickly to the entire deployment.
2. Lync Server Control Panel, a web-based graphical user interface for administrators. With this web-based UI, Lync Server administrators can manage their systems from anywhere on the corporate network, without needing specialized management software installed on their computers.
3. Lync Server Management Shell command line management tool, which is based on the Windows PowerShell command line interface. It provides a rich command set for administration of all aspects of the product, and enables Lync Server administrators to automate repetitive tasks.

Microsoft Lync Federation

                                              Lync 2010 Federation 

What is Federation?

Basically federation is the process of connecting our Lync/OCS/LCS environments with other Lync/OCS/LCS environments, such as our partner companies.  This connection allows users to easily communicate with users in other companies utilizing all the same modalities they have with users in their own environment (IM, Audio, Video, Desktop Share, etc….).

Type of Federation

In Lync 2010 there are 3 types of federation supported, those are Dynamic, Enhanced and Direct. Let us discuss each type in detail.

Dynamic Federation

Dynamic federation often called open federation is a method where a partner company’s edge server is discovered by looking up an SRV record (_sipfederationtls._tcp.domain.com).  Dynamic federation is perfect for an environment where users may need to add contacts from other companies quickly and without administrative intervention.  The firewall will have to allow inbound connections to the access edge server on port 5061 from any potential partners, typically most companies who use open federation, they allow traffic from everywhere on this port to prevent needing administrative assistance.

There are a couple of limitations on Dynamic federation, first when a partner is discovered via dynamic federation; limitations are put on how many SIP messages (20) can be received per second by that partner.  Also, there is a limit of 1000 contacts per federated contact.  Last, but not least, if you discover a partner via dynamic federation, the A record and certificate for their federated access edge must match the sip domain of the user.

Enhanced Federation

Enhanced Federation requires that you add your partners SIP domain to the “Federated Domains” list in the Lync control panel.  However, you do not need to add the FQDN of their access edge server.  Enhanced federation is not limited like dynamic federation so you will no longer have a cap on the number of messages or users. Below is a sample screen shot of how to configure enhanced federation configuration will look like

Direct Federation

Direct Federation just like enhanced federation, has no limit on the number of messages or users, but there is one big difference.  If your partner company has an access edge server with an FQDN that doesn’t match the SIP domain, you can still federate.  You will just need to put the FQDN of the access edge server and the domain name as shown in the screen shot below.

So, how do we know if we have an open federation? Simply open your Lync Control Panel, then Federation and External Access -> Access Edge Configuration and double click Global:

If Enable partner domain discovery is checked, it means the federation is open. You can also check the same using PowerShell, check if the EnablePartnerDiscovey is set to True with:

Get-CsAccessEdgeConfiguration

To close the federation you need to remove the Enable partner domain discovery checkbox in the Lync Control Panel or run the cmdlet:

Set-CsAccessEdgeConfiguration  -UseDnsSrvRouting  -EnablePartnerDiscovery $False

Enable or Disable Federation for an Organization

Follow the steps below to enable or disable federation for an Organization

1.  From a user account that is a member of the RTCUniversalServerAdmins group (or has equivalent user rights), or is assigned to the CsAdministrator role, log on to any lync server in your internal deployment.

2.  Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

3.  In the left navigation bar, click External User Access, and then click Access Edge Configuration.

4.  On the Access Edge Configuration page, click Global, click Edit, and then click Show details.

5.  In Edit Access Edge Configuration, do one of the following:

        To enable federated user access for your organization, select the Enable communications with      federated user’s   check box.

        To disable federated user access for your organization, clear the Enable communications with federated user’s   check box.

6.  If you selected the Enable communications with federated user’s check box, do the following:

        If you want to support automatic discovery of partner domains, select the Enable partner domain discovery check box.

    If your organization supports archiving of external communications, select the Send archiving disclaimer to federated partners check box.

7.  Click Commit.

Change LIS from Mumbai to Bangalore

1. From Lync Management Shell execute the below command

Remove-CsLisSubnet –Subnet 10.10.10.1

2. Set-CsLisSubnet –Subnet 10.10.10.1 –Location Bangalore –CompanyName “Company” –HouseNumber 1 –StreetName “Gandhi Street” –State Karnataka –PostalCode 5002 –Country IND
3. Publish-CsLisConfiguration

Lync 2010 Implementation Plan

1. Requirement

a.       Pre-requisites on the Server:
      Windows Powershell 2.0

                 Microsoft .Net Framework 3.5 with SP1

         Windows Installer Version 4.5

   Internet Information Services (IIS)

Static Content

Default Document

HTTP Errors

ASP.NET

.NET Extensibility

Internet Server API (ISAPI) Extensions

ISAPI Filters

HTTP Logging

Logging Tools

Tracing

Windows Authentication

Request Filtering

Static Content Compression

IIS Management Console

IIS Management Scripts and Tools

Anonymous Authentication (This is installed by default when IIS is installed.)

Client Certificate Mapping Authentication

     Windows Media Format Runtime

     Microsoft Silverlight

     Messaging Queue (MSMQ)

               Software Automatically Installed by Lync Server 2010

Microsoft Visual C++ 2008 Redistributable

Microsoft Visual J# version 2.0 Redistributable

URL Rewrite Module version 2.0 Redistributable

SQL Server 2008 Express SP1

SQL Server 2008 Native Client

    b.  DNS Requirements

We need to edit DNS record for the Lync pool to include the new servers. We need to add DNS A records point to our new FE servers (Testlyncfe01 & Testlyncfe02) for the FQDN of our Lync pool (TestLyncPool01.heiway.net) and DNS A records for Microsoft Lync Server 2010 client auto configuration point to new FEs under SIP zone in internal DNS. Also update the records with new Lync Front End Server’s IPs on sip.domain.local and sip.domain.com as well.

c. Certificate Requirements

Add 2 more SAN Entries “Testlyncfe03 and Testlyncfe04” on the Certificate (TestLyncPool01.heiway.net) from Existing Frontend Server (Testlyncfe01 & Testlyncfe02). Install the new certificate on the all the Front End Servers (Testlyncfe01, Testlyncfe02, Testlyncfe03 and Testlyncfe04)

d. HLB Requirements

Add the new Front End Servers on the Hardware Load balancer and update the new certificate on HLB  

e. Firewall Requirements

Ports needs to be open between new Front End Servers and Edge Servers.

2. Deployment Process

Actions	Responsible Team
Installation of Pre-requisites on the Server
DNS A and SRV Records creation and modification
Server Certificate
Hardware Load Balancer Configuration

Installation of Lync Server Application
Firewall Configuration
OPCO Firewall configuration

    3. Steps to add the New FEs to the existing pool

   f . Define the New Server in Lync Topology Builder

                                            I.            Log on to the server (TestLyncfe01/TestLyncfe02) where you installed Topology Builder.

                                          II.            Open “Lync Server Topology Builder” from the Microsoft Lync Server 2010 menu.

                                        III.            On the Welcome page, click Download Topology from Existing Deployment. Click OK.

                                         IV.            A “Save Topology As” box will come up. Choose a location, name the file and save it. (Keep the “.tbxml” extension.)

                                          V.            In Topology Builder, click to expand the Server Role tree view.

                                        VI.            Right-click “Enterprise Pool (TestLyncPool01)”.

                                        VII.            Click New Server.

                                        VIII.            On the “Define the Server” page that comes up. Enter your Lync New FE FQDN (TestLyncfe05.domain.com), Enter IP address (xx.xx.xx.xx) on Primary IP address & PSTN IP Address and click OK.

Notes: Repeat the above for TestLyncfe06 with FQDN as TestLyncfe05.domain.com and IP Address as xx.xx.xx.xx

g.       Publish the Edited Topology

                                                                    I.            Right-click the Lync Server 2010 node.

                                                                  II.            Click Publish Topology.

                                                                III.            Click Next on the first “Publish the Topology” page.

                                                                IV.            Next, you have the “Create Databases” page. Select the databases you want to publish.

Click OK once you have selected an option. Then click Next

                                                                   V.            Select a Front End pool on the “Select Central Management Server” page.
Click Next to complete the publishing process.

                                                                  VI.            When it is done, click Finish. Now the new server needs a local configuration store.

h.       Install the Local Configuration Store on the New Server

                                                                    I.            Take the Lync Server installation media. Load it on the new server (TestLyncfe05.domain.com).

                                                                  II.            Browse to setupamd64Setup.exe and click OK.

                                                                  III.            Click OK on the “Lync Server 2010 Installation Location” page. Accept the license terms.

                                                                  IV.            Click Install or Update Lync Server System on the Deployment Wizard page.

                                                                  V.            Click Next until you get to “Step1: Install Local Configuration Store”. Click Run. Make sure the “Retrieve Configuration Automatically from the Central Management Store” option is selected on the configuration page. Then click Next.

                                                                VI.            Click Finish when the install is done.

                                       Notes: Repeat the above steps on TestLyncfe05.domain.com

i.       Install Lync Server 2010 on the New Server

                                                                    I.            On TestLyncfe05, On the “Microsoft Lync Server 2010 – Deployment Wizard” page, click Next until you get to “Step 2: Setup or Remove Lync Server Components”.

                                                                  II.            Click Run.

                                                                III.            Click Next on the “Setup Lync Server Components” page.

                                                                IV.            Click Finish when the task status completes.

                                      Notes: Repeat the above steps on TestLyncfe05.domain.com

j.       Configure a Default Certificate for the New Server

                                                                    I.            On the “Microsoft Lync Server 2010 – Deployment Wizard” page, click Next to get to “Step 3: Request, Install or Assign Certificates”.

                                                                  II.            Click Run.

                                                                III.            Click Import on the “Certificate Wizard” page.

                                                                IV.            Once the imported Certificate is assigned. click Close on the “Certificate Wizard” page

k.      Start the New Server

                                                                    I.            Once again on the “Microsoft Lync Server 2010 – Deployment Wizard” page, click Next to get to “Step 4: Start Services”.

                                                                  II.            Click Run.

                                                                  III.            Click Next to start the new Lync Server's services.

                                                  IV         Once all services start up, click Finish

   4. Test Plan

We will check the Lync Services on TestLyncfe05 and TestLyncfe06 by performing below tests,

1.       Check the Lync Services

2.       Telnet the required ports

3.       Check the Event Viewer for error logs

1.       Stop the services on TestLyncfe01, TestLyncfe02, TestLyncfe03 and TestLyncfe04 to check the traffic.

5.     Impact and Risk

N   Impact and risk associated with this change as the existing Lync Front End Servers will be install with new certificate one by one

Lync Delegation Access

RBAC roles used to define the management tasks that users allowed to carry out, and to determine the scope in which users will be allowed to perform these tasks.

Perform the following command from Lync Management Shell:

New-CsAdminRole -Identity "BLR-LyncUserAdmins-IND" -ConfigScopes "site:1" -UserScopes "OU:ou=Blr,dc=Domain,dc=com" -Template CSUserAdministrator

CSUserAdministrator: - Administrator Security group that provide required permission to perform activities. Command will automatically create this group.