Microsoft Lync Server 2010 Workshop–Day 2

And here is the summary for Lync Workshop Day 2:

Options to Deploy Enterprise Voice

Note: Check : http://technet.microsoft.com/en-us/lync/gg131938.aspx to view a list of certified telephony products. If your vendor is not on the list, you may need to contact the vendor and request them to get certified for Lync:

Vendor Process for Microsoft Unified Communications Open Interoperability Program:

http://technet.microsoft.com/en-us/lync/gg294187

1) Deploy a sip trunk ( There are many different types of SIP Trunk, some sip trunk can connect directly to Mediation Server)

Note: Check with your Sip Trunk Provider before making the final decision on how to link the devices.

Mediation Server——SIPTRUNK(Certified)—–> PSTN Provider

2) Deploy an E1 line or T1 line

If there is currently an existing E1 line to the organization connected to a PBX. Check if the IP-PBX is a certified Lync IP-PBX.

If the PBX is not on the certification list, a Lync Certified Media Gateway is required to link the Lync Mediation Server to the IP-PBX.

Note: Check with your Media Gateway Vendor before making the final decision on how to link the devices.

Possible Configuration:

Mediation Server—–LAN——>Media Gateway(Certified) —– E1orT1——->IPPBX — E1orT1 —-> PSTN Provider

Mediation Server—- LAN ——>Media Gateway(Certified) — E1orT1 —-> PSTN Provider

Mediation Server—- LAN ——>IPPBX(Certified) — E1orT1 —-> PSTN Provider

Mediation Server—- LAN ——>IPPBX(Certified) ——- E1orT1———->Media Gateway —-E1orT1—–> PSTN Provider

Mediation Server—- LAN ——> Media Gateway(Certified) <——- E1orT1———- IPPBX

E1 or T1

PSTN Provider

Virtual IP PBX (recommended, good for testing)

http://www.trixbox.com/products/trixbox-ce/

Physical VOIP Gateway for test environments

AudioCodes MP114 FXO 4 port Analog VoIP Gateway

Reverse Proxy Requirement

For Lync clients to access HTTPS services from the internet, You need to publish web addresses on the reverse proxy.

Some *examples* include:

Lync external web service url for every pool (Download Address Book, Download meeting contents, Lync Mobility) (to Front End pool(s))
Dial-in url (to Director, if director is deployed, else Front end)
Meet url (to Director, if director is deployed, else Front end)
Autodiscover exchange url (to Exchange CAS)
Exchange external web service url (to Exchange CAS)
Lync discover url (For Lync Mobility) (to Director, if director is deployed, else Front end)
TMG is one of the reverse proxies that is supported for use with Lync. It is recommended to use TMG.

http://technet.microsoft.com/en-us/library/gg195814.aspx

Address book phone numbers not showing in Lync

Lync address book will only reflect E.164 numbers in the contact information of the users. As a best practice, all numbers of the users (in Active Directory as well) needs to be in E.164 format. Instead of changing all the values in Active Directory, a workaround is available to normalize numbers to E.164 so that they will show up on the address book. Research on the following term : “Lync Address Book Normalization” for more information.

Load Balancing:

http://technet.microsoft.com/en-us/library/gg398634.aspx

You still need HLB to load balance HTTPs traffic on Enterprise Front End pools or Director pools (when there is more than 1 server in the pool), The hardware load balancers need to support “cookie based persistence” feature if you intend to deploy lync mobility:

http://technet.microsoft.com/en-us/library/hh690030.aspx

DNS Load Balancing Overview

http://blogs.technet.com/b/nexthop/archive/2011/05/25/dns-load-balancing-in-lync-server-2010.aspx

Before you can use DNS load balancing, you must:

1. Override the internal web services pool FQDN.

2. Create DNS A host records to resolve the pool FQDN to the IP addresses of all the servers in the pool.

To override internal web services FQDN
From the Lync Server 2010 program group, open Topology Builder.
From the console tree, expand the Enterprise Edition Front End pools node.
Right-click the pool, click Edit Properties, and then click Web Services.
Below Internal web services, select the Override FQDN check box.
Type the pool FQDN that resolves to the physical IP addresses of the servers in the pool.
Below External web services, type the external pool FQDN that resolves to the virtual IP addresses of the pool, and then click OK.
From the console tree, select Lync Server 2010 , and then in the Actions pane, click Publish Topology.

http://blogs.technet.com/b/ucedsg/archive/2010/10/12/lync-dns-load-balancing-and-server-draining.aspx

Voice Polices

They can be imported / export to VCFG file for backup and restoration purpose. In order to call a PSTN number, the user needs a Voice Policy containing the correct PSTN usage with the correct route. Least Cost Routing can be implemented if there are multiple sites with PSTN media gateways or IPPBXs.

Dial Plan (change number OR perform number matching)
Voice Policy ( Voice policy needs to contain correct PSTN Usage)
Voice PSTN Usage (PSTN Usage needs to contain correct routes)
Voice Route (Routes need to be pointed to the media gateways or ip pbx)

Overview of Installation

1) Active Directory Pre Requisites: 2003 Native Mode (Forest Functional Level, Domain Functional Level), Prepare Schema, Forest, Domain

2) Server Pre-Requisites :

Microsoft .NET Framework 3.5 with SP1 (to be installed using Server Manager)
Microsoft Visual C+ 2008 Redistributable (can be installed automatically by Lync Server 2010, if not already installed on the computer)
Windows Media Format Runtime (can be installed automatically by Lync Server 2010, if not already installed on the computer)
Windows PowerShell version 2.0 (is already installed on some Windows operating systems)
Windows Installer version 4.5

Sample command to install pre-requisites for front end servers:

Import-module servermanager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Static-Content,Web-Default-Doc,Web-Http-Errors,Web-Http-Redirect,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,Web-Windows-Auth,Web-Client-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools –Restart

Note: The above cmdlet should be tweaked, Only Directors and Front End servers require “Web” services. For other servers, it is not required to install “Web” services.

http://technet.microsoft.com/en-us/library/gg398686.aspx

3) If installing Standard Edition Server: Prepare the SE server, if installing Enterprise edition skip this but ensure the SQL server is properly installed.

4) Install Topology Builder: Define your topology. Ensure to type in correct FQDN(s) or installation will fail.

5) Publish the topology.

6) Start Installation

There is no install order required. Front End server will be the first server to be deployed.

1) Front End (STD, ENT) (SQL server is required if deploying enterprise edition fe pool) (Topology Builder)

If remote access is required:

2) Edge (If no TMG, TMG installation is required)

3) Director Etc.

Certificates

Generally, internal servers do not need a public certificate, However, You can use external certificate even for internal server.

Edge Server:

External NIC Card – Highly recommend to have a public SAN cert

Internal NIC Card – Internal SAN Certificate is fine.

TMG:

External NIC Card – Highly recommend to have a public SAN cert

Internal Nic Card(if there is an internal nic card) – Internal SAN Certificate is fine.

Director

If mobility is deployed, Public Certificate is recommended , use internal certificate for small deployments or when mobility is not required

Front End(Mediation and AV collocated)

Internal Certificate, if there is no director and mobility is required, Public Certificate is recommended. Use internal certificate for small deployments or when mobility is not required or when there is a director

SBS

Internal Certificate

Mon/Arc

Do not need certificate.

Bandwidth figures

http://technet.microsoft.com/en-us/library/gg413004.aspx

Bandwidth Calculator