Archive for the ‘Lync 2010’ Category

Lync 2010 mobile client sign-in fails

January 23, 2016 Leave a comment

This is a very common issue and comes with a multiple errors, I spoke in my previous article  about one of this errors. Today we have the same error but with a little different symptom.


Lync Mobile users get the following Error message “can’t connect to the server. It may be busy or temporarily unavailable” while trying to connect, in addition the S4B mobile clients have the same symptom as we have a hybrid deployment with Skype for Business Online,and the new in this issue is that this problem occurs at irregular intervals  




Quite simply the first thing we should think about it when we find that this problem is repeated irregularly, is to review the (Autodiscover and MCX) directories settings over IIS web component on the Frontend servers in case you have a multiple frontend servers.

In my case I have two frontend servers one of them has lost the autodiscover and MCX directories.

you need to rebuild the autodiscover and MCX directories on defected server by the following steps;

  1. Log on to the computer as a user who is a member of the CsAdministrator group.

  2. Download the latest installation package from the Microsoft Download Center and extract it to the hard disk.

  3. Copy McxStandalone.msi to C:\ProgramData\Microsoft\Lync Server\Deployment\cache\4.0.7577.0\setup.

  4. Open the command prompt: Click Start, click in the search box, type cmd, and then press ENTER.

  5. At the command prompt, run C:\Program Files\Microsoft Lync Server 2010\Deployment\Bootstrapper.exe.


If you run Bootstrapper.exe from Lync Server Management Shell, you must prepend the path with a period (.) and enclose the path in quotation marks ("). For example: ."C:\Program Files\Microsoft Lync Server 2010\Deployment\Bootstrapper.exe".



Categories: Lync 2010


September 29, 2015 Leave a comment


In this article we will demonstrate in steps how to add additional SIP domain in the already existing Lync deployment.


The steps in brief

1. Add the new SIP domain(s) to the Topology.

2. Create DNS records for the new simple URLs, both internal and external.

3. Request new certificates with adding the new domain(s) name(s).


Steps to add the new SIP domain(s) to the Topology

Open the Lync Server Topology Builder. 

Select download the topology from the existing deployment. 


After the topology builder has opened, Right click on the topology and click edit properties.


Click on add new domain to add the new sip domain.


Then click on publish topology.



Create DNS records for the new simple URLs, both internal and external


Service Protocol






Add it to your public DNS entry



Point it to your FE server pool-(Internal+External) DNS



Point it to your FE server pool-(Internal+External) DNS




Should be created on your public DNS



Should be created on your public DNS




Should be created on your internal DNS


Request new certificates with adding the new domain(s) name(s).

· Open Lync server deployment wizard.

· Select Install or Update Lync Server System.


· Select Step 3 Request, Install or assign Certificates.


For internal certificate keep select the following option.


Then press Request and Next.


If you don’t have the option to connect directly to your internal CA, you should choose the second option as the below.


Choose the path you will save the certificate request in and the CSR name.


Choose the following option if you have a certificate template, in our scenario bypass this option.


Type the same friendly name as the below.


At the end of this wizard you will need to select the new sip domain in my example it was and your old domains to the SIP domain setting on subject Alternative Names (SANs) section, then adding all your additional subject alternative names.


PS. “after upgraded the certificate you need to run the following command { Stop-CsWindowsService} on your Lync server management shell”


Now after you generated the new certificate request through your internal CA, you just need to install it on your FE servers, to do that you have two options here.

Option #1


Option #2

From start menu type mmc, file, Add/Remove Snap in, certificate, computer account and finish.

And import the new certificate to personal as the below.


The final step in this wizard is to assign the new certificate to Lync services as the below screen.


Don’t forget to start Lync service by the following command

{ Start-CsWindowsService}.


Important P.S. “you need to export the same certificate with private key if you have more than FE servers in order to add it to all your FE servers and this done by the following steps.”




Till now you can

enable new sip domain users and access Lync with the new sip domain from you internal network.

To access from External you just need to update your public certificate with your new SIP domain and it’s (SANs).

Read more…

Lync 2010 mobile can’t connect to the server. it may be busy or temporarily unavailable

December 30, 2014 1 comment

Dears, I would like to share the following article with you,

In the last week we have renewed the Lync 2010 internal and external certificates, internal and external desktop client working normally without any issue, but the mobile client can’t connect.

General Info.

Mobile application requests for Mobility Service.

mobile application requests for Mobility Service

PS Both the internal Mobility Service URL and the external Mobility Service URL are associated with the external Web Services FQDN. Therefore, regardless of whether a mobile device is internal or external to the network, the device always connects to the Microsoft Lync Server 2010 Mobility Service externally through the reverse proxy.

Issue symptoms

Lync Mobile users get the following Error message “can’t connect to the server. It may be busy or temporarily unavailable” while trying to connect.


Investigation result

· After reviewed the mobile client logs and simulate the test by the test Lync connectivity analyzer, I have found that An error occurred while mobile client sending the request to the Lync proxy server even through port 443 or 80.

. In my scenario we don’t have a reverse proxy, instead of that we using the Lync Frontend servers as a proxy server at the same time, it has a two IPS on the same NIC,22 for internal services and,51 for the proxy server.

PS. This is not supported scenario, you must use a separate server for the Revproxy if you are going to use software like TMG or any other else, and that if you don’t have a reverse proxy device.

. We use the HW load balance for High availability for the internal and proxy services.


In my case the IIS web service component of the internal and external sites was missing the binding configuration, so that if you have the same case with the same scenario all you want to do is assign the proxy IP to the external site with port 443 and public cert, and assign the internal server IP to the internal site with port 443 and internal cert.

Categories: Lync 2010

Lync 2010- Transfer to self failed

April 22, 2014 Leave a comment


        Anyone has been got the following diagnostic ID: “29113” with diagnostic header reason: “Transfer to self failed” as the information below shots while trying to make a Lync call from mobile device.





you just need to uncheck “Enable refer support” in Trunk Configuration section.

Voice Routing

Trunk Configuration


Categories: Lync 2010

WARNING: Get-CsCertificate encountered errors.

November 10, 2013 Leave a comment

Are you facing this noise warning while you check your Lync certificate by “ Get-CsCertificate | fl –property * ”

WARNING: Get-CsCertificate encountered errors. Consult the log file for detailed analysis, and ensure all errors (1) and warnings (0) are addressed before continuing.

Capture2 (2)

you feel like Angry smile

Don’t worry my friend you can simply resolve it as the following:

1- Open your Lync server 2010 – Deployment wizard.

2- Choose Install or update Lync server system.

3- Choose Step3: Request, Install or Assign Certificates.

Capture3 (2)

4- Then Run Again or Run.

5- Choose the Certificate that have the issue it must be in none status.

Capture5 (3)

6- Then Click Assign and the choose the related certificate after next.

Capture4 (2)

7- Then Next and Done.Winking smile

Now try again to check the certificate by using the following command (Get-CsCertificate | fl –property *) from Lync powershell.

Capture6 (2)

Time zone of SQL server Reporting services (SSRS) is inconsistent with the Time Zone of the Quality of Experience (QoE).

May 22, 2013 Leave a comment

Hi Dears simply when you face the mentioned Issue as the following figure screen while trying to open your Lync Monitoring console, just follow the following steps to resolve this issue.



1- Go to your SQL server that own Lync DB to open the QoE DB stored procedures as the following.


2- Then select the dbo.RtcClearTimeZoneInfo


3- Now make a new query to run it as the following.


Now the issue should be resolved clip_image005


Note: this issue may happen also with lcsCDR DB and the resolution the same just select dbo.RtcClearTimeZoneInfo  from lcsCDR DB.

How to Configure Lync On-Premise for Federation to Lync Online

May 19, 2013 1 comment

In this article I suppose that we finished the the Lync online external communication configuration, now we will go to touch on the Lync On-premise side.

As we know by default, Lync On-premise has three providers that Lync already provides federation with.


To add your Office 365 Lync Online, click the new hosting provider and add your Lync Online domain name as show in the screen below.


For those of lover use PowerShell, you can bypass the console and run the following command in the Lync Management shell:

New-CSHostingProvider -identity LyncOnline -ProxyFqdn -Enabled $True

If you have used the PowerShell method, refresh the Lync On-Premise Control Panel. Which ever method you use to add the provider, you should now see your new hosting provider.


Configure the Lync On-Premises Domain
Your Lync Server 2010 On-Premises environment must contain at least one Enterprise Pool or Standard Edition server and at least one Edge server.

1. Purchase a UC Certificate from a publicly trusted Certification Authority, such as DigiCert or VeriSign, configured as the example follows:

  • Subject Name: sip.Your
  • Subject Alternative Name(s): meet.Your,dialin.Your,webaccess.Your,sip.Your

2. Assign the new certificate to your Edge external interfaces, then restart services.

3. Create the required external DNS SRV and A records to support Lync On-Premises services with your DNS provider.
Type: SRV
Service: _sip
Protocol: _tls
Port: 443
Weight: 1
Priority: 100
TTL: 1 Hour
Name: Your
Target: sip.Your
Type: SRV
Service: _sipfederationtls
Protocol: _tcp
Port: 5061
Weight: 1
Priority: 100
TTL: 1 Hour
Name: Your
Target: sip.Your
Type: A (Host)
Target: < Access Edge External IP >
Type: A (Host)
Name: webaccess.Your
Target: <Reverse Proxy External IP>