Tag Archives: Lync 2013

Lync Server reporting url error


Lync monitoring reports deployment is a key part of the management & administration of Lync server. Sometimes, it is simple to configure and use but some time you can face some problems. You can get this common error “An error occurred during report processing.” While accessing report url.

Sometimes this error can occur because of database stored procedure. If reporting url was working fine earlier you can follow below steps only for LcSCDR & QoEMetrics databases.

  • Open SQL Server studio manager.
  • Go to the LcSCDR / QoEMetrics
  • Go to the Programmability

  • Go to the Stored Procedures under Programmability
  • Select and right click on dbo.RtcGenerateSummaryTables
  • Click on New Stored Procedure

  • You will see the result with return value 0.

 

Now, another case comes in picture while you are deploying new reporting servers. This issue can be faced in both the cases while monitoring services are deployed on SQL Mirror or SQL Cluster. To resolve this issue, open reporting services url and go the CDRDB & QMSDB under report content and modify the connections string.

  • You can find “data source=(local)\instancename;intial catalog=QoEMetrics
  • Change (local) with real sql server name and apply the changes.

Follow the same steps for LcSCDR also via updating CDRDB and enjoy J

 

Advertisements

Remove Lync Server Standard Edition from existing Lync infrastructure


Business critical applications such as Exchange and Lync are very tightly integrated with Active Directory. Many preparation steps are required to introduce these application or even when you’re migrating to the newer version. Most of the times professionals see, few changes like installation or removal are required frequently for small branch site deployments. Let’s start with removal process of Lync server Standard Edition deployment from existing Lync infrastructure. There are few pre-requisites for uninstallation of Lync server required which should be performed before uninstallation process.

Below is the step by step process for Lync Standard Edition Server uninstallation:

1. Move/Disable/Remove all Lync users from existing Lync Standard Edition Server.

2. Delete/Move Conference directories.

Open Lync Management Shell

Run Get-CsConferenceDirectory and note down the Identity which are associated with Lync SE pool.

To remove run Remove-CsConferenceDirectory –Identity <Identity Number>

3. Remove other components which are associated

  • Delete all Contact objects enabled for Lync Server Enterprise Voice features by using Lync Server Management Shell.
    • If the Lync Server 2010 response groups have been migrated to a Lync Server 2013 deployment, do not remove the contact objects of the migrated response groups. If response groups have been migrated, skip the document “Remove Response Group Service Workflow Contact Objects” that is listed in the “Documentation” column. For more information, see http://technet.microsoft.com/en-us/library/jj204854.aspx.
  • Remove Enterprise Voice routes by using Lync Server Control Panel.
  • Remove all Call Park orbits by using Lync Server Control Panel.
  • Remove all tables for Enterprise Voice unassigned phone numbers.
  • Back up the Location Information service database.
  • Back up the custom music on hold file.
  • Delete Enterprise Voice routes.
  • Reassign the public switched telephone network (PSTN) gateway.

 

4. Cross verify, Lync Standard Edition server which you are going to uninstall is empty.

5. Open Lync Topology builder and delete the server from topology.

6. Delete the Lync site if there is no Lync server or other components are not associated with existing deployment.

7. Publish the topology.

8. Open Lync server 2013 deployment wizard and run “Install or Update Lync Server System”

9. Run “Setup or Remove Lync Server Components”.

10. Once components are uninstalled successfully then remove associated certificates.

11. Cross verify the uninstallation.

12. Open SQL server studio manager and remove all the databases from all three instances RTC, RTCLOCAL & LYNCLOCAL.

13. Uninstall SQL Server Express Edition from control panel.

14. Uninstall Lync Server components and other pre-requisites.

 

I hope you have enjoyed the uninstallation process. Please feel free to write you views or any observation which you find at the time of uninstallation process.

 

Lync Server 2013 – Location Based Routing


Location Based Routing is an impressive feature of Lync Server 2013 which distinct Lync Server 2013 from other UC solutions. LBR allows full fledge Lync 2013 Enterprise Voice deployment for those enterprises who are doing business in regulated countries such as India, UAE, Egypt etc. Lync enterprise voice deployment with LBR requires well-versed planning and designing as your one wrong step can disturb entire voice setup. Now, questions come to every Lync professional if LBR requires planning & designing; it means LBR is not enabled by default or in other ways, LBR configuration part comes later.

Question: If LBR is not enable by default and needs additional configuration, which methodology Lync Server uses by default?

Answer: LCR

Many Exchange professional who are reading this blog, can assume LCR means Local Continuous Replication which was introduced in Exchange Server 2007.

By default Lync server uses Least Cost Routing methodology. Least cost routing can reduce the call rates by minimizing toll charges and maximizing WAN uses, which can benefit to the enterprises but in another ways it is a revenue loss for PSTN service providers.

LBR Benefits:

  • Comply with regulations that restricts IP-to-PSTN routing in pre-defined cases.
  • Routes PSTN calls based on caller’s location to prevent toll bypass.
  • Scoped to specific locations, gateways, and users based on Network configuration.
  • Route call to the gateway closest to the calling party which increase QoS & QoE.
  • Minimize use of WAN which result in better QoS & QoE.

LBR Capabilities:

  • Route outgoing calls to a PSTN gateway local to the caller’s location.
  • Prevent incoming calls if the Lync client is not in the PSTN gateway’s location.
  • Route outgoing calls through international PSTN gateways when there is no local gateway.
  • Ensures that conferences do not have a mix of users from different locations and PSTN dial-out.

Outbound routing:

Trunk-to-trunk routing:

Inbound routing:


There are many test cases involve in LBR implementation which need to be tested. Implementation steps and test cases is explained in the next part of this article.

Courtesy: Lync Conference 2014.

A trusted server….. error while publishing Lync Server 2013 topology


You may see “A trusted server….” error while publishing Lync Server 2013 topology.

In my case, I was adding Archiving and Monitoring role in existing Lync environment and had never faced this issue before.

After searching and looking into the error, I observed this error is occurring because of some existing entries in Active Directory.

To resolve this issue, I followed the below steps.

Note: Please take your AD backup before playing with ADSI Edit or ask your AD expert to perform the same activity.

  1. Open ADSI Edit (adsiedit.msc)
  2. Open Configuration partition and navigate to CN=Services>CN=RTC Service>CN=Trusted Services.

  1. Go to the properties of each entry under “CN=Trusted Services”.
  2. Type “msrtc” to search the Lync attributes in the property.

  1. Cross verify “TrustedServiceType” and “TrustedServerFQDN” with the error.
  2. Close the property and delete the entry.
  3. Publish the topology.
  4. If you get the same error again with different TrustedServiceType, follow the same procedure one more time.

Finally, publish the topology 🙂

Lync Server 2013 Brick Model


Messaging is a business critical application for any enterprise. To increase the productivity, instant or real-time communication is very much required. Lync has become a more suitable option for business productivity which serves all real-time workloads such as IM/Presence, Audio/Video & Web conferencing, Group/Persistent Chat, Application & Desktop sharing and Enterprise Voice.

While enterprises are moving towards an application for real-time communication, services availability is concern for IT decision makers. To avoid complexities and provide more availability Microsoft came up with brick model architecture for Lync 2013. It allows scaling out your Lync FE servers from 1 to 12 and each server can support up to maximum 6666 concurrent users. Lync Server 2013 is loosely coupled with Lync Back End SQL server and use lazy writes feature to write data in SQL Back End server.

Lync Server 2013 divides users in a group and each group is dynamically assigned to three Front End Server, primary secondary and tertiary. Once user logs in, primary server serves the services and replicate the data across secondary and tertiary using synchronous replication as well as update the SQL backend server using asynchronous replication known as lazy writes. In case of primary server failure secondary server serves the services.

In Lync server 2013, Front End server keeps rtc, rtcdyn and xds database in local sql express store. To know more about Lync 2013 databases please go through Lync Server 2013 databases.

Now, we should talk about how brick model works. Basically, brick model is based on windows fabric and it consider nodes majority for availability. That’s why you need minimum three Front End servers to achieve high availability. The majority is considered when n/2 or n+1/2 Front End servers are alive.

For maintenance, you should restart/down one server at a time. If all Front End servers go down due to the power outage or any other reasons, please make sure you are starting all Front End servers at the same time.

Configure DHCP Server options for Lync Phones


Setting up entire Lync Infrastructure is fun for Lync Professionals but real fun always come at last moment when end users start enjoying Lync services from their end user devices. To setup Lync soft client is quite easy while configure Lync phone devices are tricky one.

Trick comes with automate process of Lync phone devices which start from getting an IP address from DHCP server and end with user specific configuration such as selecting Time zone. Most of the companies use DHCP server to provide IP address to the client machine, simply Lync Phone devices can get an IP address from same DHCP server but it needs more to complete the entire configuration.

First of all, we have to understand any Lync client can only login if time is synchronized between Lync Server and Client. To meet this requirement starts with DHCP option 42.

If you have time server in your existing environment, specify the same in DHCP configuration option 42.

Let’s take an example if you don’t have time server in your existing environment then you can configure domain controller (PDC) as a time server.

  1. Create a record as shown below.

  1. Create service record as shown below.

Once you are done with this, specify same server address in DHCP option 004 & 042 and domain name in option 119.



Rest all the options you can see below need to be configured. But 🙂 you’ll not get any option with specific vendor by default in your DHCP server.

To make it simple MS provide dhcputil.exe in Microsoft Lync Server 2013 Front End / Standard Edition Servers.

 

Just copy this dhcputil.exe file in DHCP server and run below command

DHCPUtil.exe -SipServer <Lync Server Pool FQDN > -WebServer <Lync Server Internal Web FQDN> -RunConfigScript

In my case, I have copied dhcputil.exe in c drive of dhcp server.

C:\> DHCPUtil.exe -SipServer se01.insidemstech.com -WebServer sewebint.insidemstech.com –RunConfigScript

Once you will run the above cmdlet, it will add & configure all the required option as shown below

If you want to verify your dhcp configuration, run DHCPUtil.exe –EmulateClient from client computer.

If it doesn’t give any errors. It means you are done.

Now you can set pin for your Lync users and get logged in through Lync Phone Edition devices.

I hope it helped 🙂

 

How does Lync Federation work?


Lync federation also known as external connectivity which allows a lync user to connect with users in other organization as well as public IM domains and XMPP. Lync support two kinds of federation open and close. When an organization allow open federation that means the organization has enabled automatic discovery while closed means the organization has disabled automatic discovery and added specific domain to allow federation.

Lync federation can be configured from Lync Control Panel as well as from Lync Management Shell.

It is time to know “how does lync federation work?” Let’s take an example of two organizations contoso.com and fabrikam.com. Both organizations have open federation.

Below is the step by step procedure:

  1. UserA (sipuri:usera@contoso.com) is looking for UserB (sipuri:userb@fabrikam.com)
  2. First of all it will check the access edge configuration for federated domain.
  3. As UserA request for sipuri: userb@fabrikam.com and in my case both domain is configured for open federation, the request will go to Access Edge Server and Access Edge Server will do lookup for domain name fabrikam.com.
  4. If fabrikam.com domain exists then it will look for the SRV record _sipfederationtls._tcp.fabrikam.com.
  5. Once it will get the destination address of fabrikam.com access edge server then it will try to establish the SIP/MTLS:5061 connection.
  6. Once Fabrikam.com will receive the request from contoso.com, fabrikam.com will check the access edge configuration to verify allow/block federated domains.
  7. Once the connection will be establish between both Lync Front End Pools / Lync Standard Edition Servers via Access Edge Server, UserA and UserB will talk to each other.

 

Note:

  1. All the required ports should be open in both ends.
  2. SRV record entry should exist in External Certificate.
  3. Federated domain should be allowed in both ends.
  4. XMPP doesn’t use SIP/MTLS:5061. It use XMPP/TCP:5269 to connect access edge server from public network and XMPP/MTLS:23456 to connect Front End Pool.