Lync Server 2013Comments (0)

Lync, a word taken from Link and Sync is Microsoft's successor to the Office Communications Server. Now in version 2013, it has been a much appreciated tool amongst the employees around the world.
With features as presence, chat, audio, video and enterprise voice, it has become a must have service.

Comments

You need sign in to comment! Sign up today!

Lync Pre-requirementsComments (0)

Operating Systems
- Windows Server 2008 R2 SP1 or latest service pack
- Windows Server 2012
- Windows Server 2012 R2

Additional Software
- Windows PowerShell 3.0
- Microsoft .NET Framework 4.5
- Windows Identity Foundation for Edge Servers

Windows Server 2012 Prerequisities
Lync Server 2013 Front-Ends:
Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client, BITS -Source D:\sources\sxs

Comments

You need sign in to comment! Sign up today!

Install CUComments (0)

This guide will help you to install a CU on your Lync Environment.

Verify status
First we need to verify the status of the pool, this is to prevent upgrading an environment that is not 100% ok:
Get-CsPoolUpgradeReadinessState

Run installation
LyncServerUpdateInstaller.exe

Apply back-end database updates
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn sql01.company.com -Verbose

Apply updates to Persistent Chat databases
Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn sql01.company.com -SqlInstanceName "DBInstance" -Verbose

Apply updates to Monitoring/Archiving/Persistent Chat databases
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn sql01.company.com -Verbose

Enable the mobility service
Enable-CsTopology

Enable the Unified Communications Web API
D:\Program Files\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe

Comments

You need sign in to comment! Sign up today!

Move the Central Management Database (CMS)Comments (0)

This guide will help youmove the CMS database to a new location and uninstall the CMS on the legacy server.

Prepare CMS to the new pool
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn sql01.company.com -Verbose

Middle Tier
Enable-CsTopology

Move-CsManagementServer
Move-CsManagementServer

Verify Status
Get-CsManagementStoreReplicationStatus

Start the process
Lync Server Master Replicator Agent
Invoke-CSManagementStoreReplication

See status
Get-CSManagementStoreReplicationStatus

Uninstall CMS from legacy server
Uninstall-CsDatabase -CentralManagementDatabase -SqlServerFqdn sql01.company.com -SqlInstanceName rtc

Comments

You need sign in to comment! Sign up today!

Lync 2013 client cannot connect to the lync pool!Comments (0)

When the Lync 2013 client cant connect to a Lync 2013 Front-End server running on top of a Windows Server 2012 there might be some issues with the TLS protocol.
The following events will appear in the log:

EventID: 36874
TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.

EventID 36888
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 1205.

Disable TLS 1.2 by following the below steps:
- On the Lync 2013 server open the registry and browse to the following location: HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols
- Create the following Key under Protocol: TLS 1.2
- Create the following two Keys under TLS 1.2: Client and Server
- Create the following DWORDs under both the Client and Server Key: DisabledByDefault and Enabled
- Under both Client and Server set the following: DisabledByDefault=1 and Enabled =0
- Reboot the server.

Comments

You need sign in to comment! Sign up today!

Understanding and activating the Unified Contact Store in Lync Server 2013!Comments (0)

Unified Contact Store (UCS) is a new feature between the Office 2013 products. It basically store all contact information in the users mailbox and it's shared across Lync, Exchange, Outlook and Outlook Web App.

After both Exchange Server 2013 and Lync Server 2013 has been deployed one have to configure server-to-server authentication between the two products.

Requirements for Unified Contact Store
- Users must be running Lync Server 2013 and Exchange Server 2013
- Users must use Lync 2013 to initiate the migration process of contacts from Lync Server 2013 to Exchange Server 2013
- User mailboxes must have been migrated to Exchange Server 2013
- The server-to-server authentication must have been configured between Lync Server 2013 and Exchange Server 2013

How to enable users for Unified Contact Store

To enable UCS globally for all Lync Users:
Set-CsUserServicesPolicy -Identity global -UcsAllowed $True

To enable UCS for users at a specific site:
New-CsUserServicesPolicy -Identity site:'SiteName' -UcsAllowed $True

To enable unified contact store for specific users:
New-CsUserServicesPolicy -Identity 'PolicyName' -UcsAllowed $True
Grant-CsUserServicesPolicy -Identity 'DisplayName' -PolicyName 'PolicyName'

When the UCS policy is enabled (it is by default) and users have logged in with Lync 2013 once, the process should be started.

To verify if the contacts has been migrated:
Test-CsUnifiedContactStore -UserSipAddress 'sip:fredrik.tornell@contoso.com' -TargetFqdn 'pool01.contoso.com'

Comments

You need sign in to comment! Sign up today!

Outlining the server roles in Lync Server 2013!Comments (0)

This topic shall outline the information regarding servers and it's roles.

The following list describes the roles:
- Standard Edition Server
- Front-End Server and Back-End Server
- Edge Server
- Mediation Server
- Director
- Persistent Chat

Standard Edition Server
This server is designed for small organizations or pilot projects. Almost all features can be enabled on a single server which make this a popular choice at a lower cost without the high availability solution.

Front-End Server
A Front-End Server is the core server role in an Enterprise Pool. Along with a Back-End Server (SQL) it creates a functional topology.
Front-End Servers are the choice if looking for a high availability solution by pooling a set of servers together.

The Front-End pools are the primary storage for user and conference data. Information about each user is replicated among three Front-End Servers in the pool and backed up on the Back-End (SQL) server(s).

Back-End Servers
The Back-End Servers are the database layer, which means that it runs Microsoft SQL to provide database services for the Front-End pool.
One can have a single Back-End Server but for high availability solutions, Microsoft recommends using SQL mirroring for database failover. This Back-End Server(s) do not run any Lync Server software.

Edge Server
This role enables users to communicate and collaborate with users outside of the organizations firewalls. External users can consist of the organizations own employees working offsite, users from federated organizations or other users that have been invited to conferences.

Mediation Server
For Enterprise Voice and dial-in implementations this role is a necessary component. The Mediation Server translates signaling and sometimes media between the Lync Server infrastructure and the PSTN Gateway, IP-PBX or SIP trunk.

Director
Directors is an additional layer of security where it authenticates requests before sending them on to internal servers. In case of a denial-of-service attack the requests ends at the Director and are not affecting the Front-End servers.

Persistent Chat
Persistent chat help users to participate in multiparty chat-rooms that persist over time. This is perfect for discussions where people come and go.

Comments

You need sign in to comment! Sign up today!

Lync Server Monitoring Dashbord generates errorComments (0)

Error message:
Report processing stopped because too many rows in summary tables are missing in the call detail recording (CDR) database. To resolve this issue, run dbo.RtcGenerateSummaryTables on the LcsCDR database.
Report processing stopped because too many rows in summary tables are missing in the Quality of Experience (QoE) database. To resolve this issue, run dbo.RtcGenerateSummaryTables on the QoEMetrics database.

To solve this issue, logon to the SQL Server Management Studio
Browse to Databases > QoEMetrics > Programmability > Stored Procedures
Rightclick dbo.RtcGenerateSummaryTables and choose Execute Stored Procedure...

Do this steps for both the QoEMetrics and LcsCDR databases.

Comments

You need sign in to comment! Sign up today!

Lync Certificate assignment won't find your certificateComments (0)

When importing a certificate and it does not assign the private key to the certificate the coulde be some corruption with the store.

The solution is to repair the certificate store

Identify the serialnr
certutil.exe -store

This will display the certificates and it's corresponding serialnumber. This can also be done through the mmc and cert snap-in.

Next step is to repair the store, it's done using the following command:
certutil.exe -repairstore my 'serialnr'

Comments

You need sign in to comment! Sign up today!

How to uninstall Lync Server 2013Comments (0)

This guide will help you to remove Lync from front-end servers, edge servers as well as removing the topology from the environment. As always I recommend doing this in a controlled manner in a test-environment prior to doing this in production.

Step 1: Remove all users that are homed at the pool:
Get-CsUser | Disable-CsUser

Step 2: Remove all conference directories that belongs to the pool:
Get-CsConferenceDirectories

Look at the ID's of the directories and remove all that belongs to the pool using:
Get-CsConferenceDirectories -Identity 'id' | Remove-CsConferenceDirectory

Step 3: Remove all servers from the topology using Topology builder and publish the topology

Step 4: Run the Remove Deployment Wizard from the Topology builder and publish the topology

Step 5: On each Lync server run the setup wizard and the Setup or Remove Server Components step
Then use Stop-CsWindowsService to stop all Lyncrelated services.

Step 6: Export and Import cleantopology to any edge server from any Front-End server:
Export-CsConfiguration -FileName c:\LyncCleanConf.zip
Import-CsConfiguration -FileName c:\LyncCleanConf.zip -LocalStore

Step 7: Bootstrap each Lync server using:
C:\Program Files\Microsoft Lync Server 2013\Deployment\bootstrapper.exe /scorch

Step 9: Uninstall Microsoft SQL Server 2012 (64-bit) from Programs and Features, follow the wizard and remove all Lyncrelated databases
After Microsoft SQL Server 2012 (64-bit) has been removed, run the uninstall process for all other SQL related programs, Lync Server components and Admin tools, Windows Fabric and Microsoft Visual C++.

Step 10: Remove any folders that still exist. Otherwise Lync and SQL has been removed from the topology and you're done!

Comments

You need sign in to comment! Sign up today!

How to integrate Exchange Server 2013 OWA and Lync Server 2013!Comments (0)

This post will cover the steps needed for owa integration between Exchange Server 2013 and Lync Server 2013.

Step 1: The certificate
All traffic between Exchange Server 2013 and Lync Server 2013 is encrypted using SSL.
To list Thumbprint and Subject Name of the certificate, type:
Get-ExchangeCertificate | fl
The Thumbprint will be used to identify which certificate to use for the connection. the subject Name will be used to create the Trusted Application.

To activate the web service integration:
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory-InstantMessagingEnable $ True-InstantMessagingType OCS

To configure the access policy and enable the OWA IM features for all users:
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy-InstantMessagingEnabled $ true-InstantMessagingType OCS

Now we need to edit the OWA file named web.config (C:\Program Files\Microsoft\Exchange Server\V15\Client Access\Owa):
Open the file and locate section. Add these two lines located here:
[add key="IMCertificateThumbprint" value="Thumbprint"/]
[add key="IMServerName" value="lyncpool01.contoso.com" /]

Note that the first and last [ ] shall be replaced as the other lines there, I cannot post them here due to PHP rewrites

Next step is to apply the changes in OWA:
C:\Windows\System32\Inetsrv\Appcmd.exe AppPool recycle / apppool.name: "MSExchangeOWAAppPool"

Step 2: Configure Lync Server 2013
Create an application pool:
New-CsTrustedApplicationPool -Identity 'SubjectName' -Register 'LyncServerFQDN' -Site 'SiteID' -RequiresReplication $False

Create a trusted application for OWA:
New-CsTrustedApplication -ApplicationId 'OutlookWebAccess' -TrustedApplicationPoolFqdn 'SubjectName' -Port 8081

Publish the topology:
Enable-CsTopology

Comments

You need sign in to comment! Sign up today!