Monday, November 24, 2014

How to customize meeting invitation in Lync Server 2013?


How to customize meeting invitation in Lync Server 2013?
Recently received request from customer to customize their Lync meeting invitation and add company logo, legal disclaimer text and support link.
Available options:
You can customize your Lync meeting invitation in following ways.
A.    Lync Server control panel. That is you GUI Mode.
B.     Lync Server management shell.
What permission I need?
You must have RTCUniversalServerAdmins group (or has equivalent user rights), or assigned to the CsServerAdministrator or CsAdministrator role, log on to any computer that is in the network in which you deployed Lync Server 2013.
A.    Using Lync Server control panel:
1.     Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. Or Server Lync Server control panel in server and open the same.
2.     In the left navigation bar, click Conferencing and then click Meeting Configuration.
3.     On the Meeting Configuration page, click New, and then do one of the following:
a.     To create a site-level policy, click Site configuration. In the Select a Site search field, type all or part of the name of the site for which you want to define meeting join settings. In the resulting list of sites, click the site you want, and then click OK.
b.     To create a pool-level policy, click Pool configuration. In the Select a Service search field, type all or part of the name of the pool service for which you want to define meeting join settings. In the resulting list of services, click the pool you want, and then click OK.
 
4.     Do any of the following:
a.     In the Logo URL field, type the URL for your organization’s logo image.
b.     In the Help URL field, type the URL to your organization’s help or support site.
c.      In the Legal text field, type the URL to the legal text or disclaimer that you want to include in meeting invitations.
d.     In the Custom footer text field, type footer text, up to 2 KB. 
 
To Customize the Meeting Invitation by using Lync Server Management Shell

1.     Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.
2.     Run the New-CsMeetingConfiguration or Set-CsMeetingConfiguration cmdlet to create or configure the meeting invitation options. For example, run:
New-CsMeetingConfiguration -Identity site:Redmond -LogoURL "http://www.mydomain.com/logo/contosobanner.gif" -HelpURL "http://www. mydomain.com/support" -LegalURL "http://www. mydomain.com/disclaimer" -CustomFooterText "Communications may be monitored or recorded."



Thank you.

Sunday, November 23, 2014

Failed to register with back-end database. Microsoft Lync Server 2010, File Transfer Agent will continuously attempt to reconnect to the back-end.


Issue: Lync 2010 / 2013 client shows limited connectivity.
Error message: Lync Limited connectivity.
Problem Statement:
Recently one my customer site, all users where getting Lync limited connectivity error on Lync 2010/2013 client. Lync user status changed to presence unknown.
Buddy list shows as presence unknown and gray color.
When I checked on FE server found below error events.
Event ID: Event ID’s: 1020: Failed to register with back-end database. Microsoft Lync Server 2010, File Transfer Agent will continuously attempt to reconnect to the back-end.  While this condition persists, no replication will be done.
The Connection string: Data Source         = CHICS027VS01.chi.catholichealth.net;
                Database            = xds;
                Max Pool Size       = 5;
                Connection Timeout  = 60;
                Connection Reset    = false;
                Enlist              = false;
                Integrated Security = true;
                Pooling             = true;
Exception: [-2] System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Event ID: 32068: Failed to update Mcu health in the backend. This will be retried but if this continues to occur conferencing functionality will be affected.
Event log shows that backed connectivity was failure.  
Resolution / Workaround:
I have checked SQL server and found that server is unavailable due to that users presence information was not showing and users were getting limited connectivity error.
Actually Cluster network VLAN was down. Due to that SQL Cluster IP was not able to communicate to the cluster and it leads to SQL DB down.
Laster we have corrected cluster vLAN issue and now back-end is functioning correctly.
Later user’s presence status got corrected and everything is working as expected.  

Thank you

Lync 2013 Mobility Troubleshooting guide


Issue: User is unable to login Lync 2013 mobile client.
Error: Can't connect to the server. It may be busy or temporarily unavailable. Please try again.
PA: Once you have latest CU updated on your Lync Server 2013 then mobility gets deployed automatically so no need install additional patch or anything else.
Here are the Troubleshooting steps which use as per below steps or your logic and sequence.
1.     Use updated Lync 2013 mobility client on your mobile phone.

2.     Type Sign-in address and then Password and Click on “Advance options”

Type: Domain\username and then try Login. Still gets error look down.

If you gets error then something with your Server side which you need to look.

3.     Lync 2013 mobile client either inside or outside get login through Reverse Proxy server only.
So you have to look on Reverse Proxy first.

4.     First you need to look on external DNS record, i.e. lyncdiscover.sipdomain.com

e.g. lyncdiscover.mydomain.com it should point to reverse proxy IP. (TMG or F5) per environment.

5.     If you are using TMG or F5 for reverse proxy then you must look the configuration that how it forwarding request FE pool (FE server address).

6.     TMG/ F5 must listen on 443 and 80 port and forward the requests to FE server on 4443 and 8080.

7.     This is important steps which you need verify that valid certificate is assigned to your reverse proxy or not. (Create client and server profile in F5 (reverse proxy) and assign the public SSL certificate on it. If you have TMG then assign the public certificate to TMG rule).

Test is simple to verify the certificate: browse the external web service (externally) and the see certificate.
E.g. my web service Eweb-ws-ext.mydomain.com


If you are getting above page then open certificate and see the SAN names. Below name you might see on valid certificate (this is all depend on environment to environment).

a.     Lyncdiscover.domain.com

b.     External web service address

c.      Dialin.domain.com

d.     Meet.domain.com

e.     Accessedge fqdn

f.       Webconf fqdn

If certificate does not have valid name then you need to get new certificate with required name.

8.     If DNS record is available and pointed correctly to reverse proxy IP address then, browse the this URL from externally
https:\\lyncdiscover.sipdomain.com, you should get file save prompt like below screen.


9.     If you open that file, then you will see below data. E.g. my external web service address, Eweb-ws-ext.mydomain.com

{"AccessLocation":"External","Root":{"Links":[{"href":"https:\/\/Eweb-ws-ext.mydomain.com\/Autodiscover\/AutodiscoverService.svc\/root\/domain","token":"Domain"},{"href":"https:\/\/Eweb-ws-ext.mydomain.com\/Autodiscover\/AutodiscoverService.svc\/root\/user","token":"User"}]}}

If still user is not able to login on Lync then do the below troubleshooting. Look like reverse proxy getting resolve however traffic is not reaching to FE server.

10.                        You can do the test which will let you know that your external request is coming to you Front End Server and show the traffic.

a.     First you have to allow external traffic on your external firewall on 443 and 80 Port. Once it allows then you can test.

b.     You can capture the traffic in firewall level where you see the traffic is going from your Reverse proxy to FE server on 4443 port.

If capture not showing traffic then you need to look at Reverse proxy configuration.

11.                        If you are using TMG or F5 for reverse proxy mechanism then you must look the configuration that how it forwarding request to your FE pool (FE server address).

12.                        TMG/ F5 must listens traffic on 443 and 80 port and forward that traffic to FE server on 4443 and 8080.

If Reverse proxy shows correct configuration then do below test on your FE server.

13.                        You can try to login on Lync on mobile and then open the IIS log and find the users SIP URI who is logging from mobile device to Lync server. if you are not seeing any Autodiscover request or your test users SIP URI then do the below troubleshooting.

14.                        See that internal and external site directory. Like below screen.



15.                        Check UCMA web directory and see the port number, Internal- 443 and 80 and External must have 4443 and 8080.

16.                        Also you can test the Autodiscover is getting resolve or not internally on FE server.

17.                        On FE server- https:\\localhost:4443\autodiscover\autodiscover.svc\root 


18.                        You can capture the traffic on your Front End server using “Network Monitor” or Wire Shark etc. where you can see and narrow down the issue.

You use: below filter in network monitor

a.     Tcp.dstport==4443

b.     Tcp.port==4443

Using above filter you see the handshake. 

If these Front Server test works as expected the then you have to look on your Reverse proxy and firewall rules and capture the TCP traffic on 4443 port.
NOTE: this is generic troubleshooting steps which may vary case to case.

Thank you.

Wednesday, November 12, 2014

Unable to delete duplicate contacts from Outlook 2013.


Issue: Unable to delete duplicate contacts from Outlook 2013.
Error Message: You cannot make changes to contents of this read-only folder. 
Problem Statement:
You can found that in Outlook 2013 People tab, there's a "Lync Contacts" folder under "My Contacts", which is created by Lync 2010/ 2013 client enabled by option "Save my Lync contacts in my personal contacts folder on Exchange" / selected “Microsoft Exchange or Microsoft Outlook” under ‘Personal Information manager’. However sometime you are seeing duplicate contacts there and when you want to delete any contact under "Lync Contacts", a pop-up windows displayed and said: you cannot make changes to contents of this read-only folder.
Lync Contact folder shows duplicate contacts and that will not allowing to delete or move those contacts in any other folder. 
Resolution:
Not allowing delete or move Lync contacts from Outlook is the expected behavioral. Sometime it will allow you to delete Lync contacts from Outlook however most of the time it won’t allow to delete.
You have couple of option to delete these unwanted contacts:
1.     Delete “Lync Contact” folder from Outlook 2013.
2.     Delete “Lync Contact” folder from OWA.
3.     Visit MS site:  http://support.microsoft.com/kb/2916650
Before deleting any contact, first disable the Lync – Outlook sync.
Lync 2013 à Options à Personal à Personal Information manager and select “None”.
Then use above method to remove Lync contacts.
In My case issue was bit different, user were seeing more than 10K contacts under Outlook 2013, one phone number was showing so many time under Lync contact. Later we have deleted the contacts from Outlook 2013 through OWA and then allowed to sync Lync contacts to Outlook again.
However after some time Lync buddy list appeared under Outlook Lync Contacts however one phone shows more than 100 times.
When I checked users buddy list found that duplicate Phone number was added there as contact in Lync and that phone number was not in use.
Later deleted that phone number from Lync buddy list and issue got resolved.
I don’t know why that number was syncing and showing more than one time on Lync Contact in Outlook However after deleting that number from Lync buddy list issue got resolved.

Article applicable to:
Outlook 2013
Outlook 2010
Lync 2010 and 2013. 

Thank you.

Tuesday, November 11, 2014

Lync to Skype for Business


Today Microsoft announced big news:

Lync à Skype for Business.
 

New version will be available in the first half of 2015, the next version of Lync will become Skype for Business with a new client experience, new server release and updates to the service in Office 365.

·        No big hardware investment Microsoft said.

·        Better experience

More information available on below URL.

Sunday, November 2, 2014

Windows could not start the Lync Server Front-End on Local Computer. For more information, review the System event log.

Issue: unable to start Front End service on Lync Server 2013.

Error Message: Windows could not start the Lync Server Front-End on Local Computer. For more information, review the System event log. If this is a non-Microsoft service, contact service vender, and refer to service-specific error code -2147024891.
Problem Statement:
Today I have notice that one of our Lync Server 2013 front end services was stopped mode.
When I checked and tried to start the services however service was unable to start. Checked event viewer for error messages.
Resolution:
Follow the below steps to start services:
1.     Open Services.msc and try to start Front End service and then go to ‘Event Viewer’ and see the actual error message.

2.     Event Viewer will show you the error. Error will be look like certificate mismatch, fatal error occurred when attempting to access the SSL client credential… etc. 
 

3.     Go to MMC console and see the certificates which are installed the server.

4.     If you found missing certificate then import and install the correct certificate.

5.     In my case correct certificate was available.

6.     Now I have to assign the correct certificate to Lync web services using Lync deployment wizard and assign the certificate. When you finish the certificate assign, if you don’t get any warning or error message then assume that your certificate got assigned properly.

Note: If you have multiple Front end server then export the correct certificate from working Front End server and install to the affected Front End server. 

7.     In my case after installing correct certificate but still unable to start front end service on sever.

8.     Later I have restarted Lync Front End server.  Front End service got started after server reboot.

9.     In my case wrong certificate was assigned o Front End server due to that FE service was not starting on server. 

Thank you.

Friday, October 17, 2014

Enable-CsUser : Cannot open database "xds" requested by the login. The login failed.


Issue: Unable to enroll Lync user.
Error: Enable-CsUser : Cannot open database "xds" requested by the login. The login failed. Login failed for user '...'.
 
Problem Statement:
While enabling user for Lync, getting above error message. Even user has Lync admin permission however getting above error.
Resolution:
I have CsAdministrator group permission however still getting above error while enabling user for Lync.
When I checked it properly then I found resolution.
Basically you must have of a group permission from CsUserAdministrator, CsServerAdministrator or CsAdministrator. Apart from that you must have RTCUniversalServerAdministrator group permission in order to enroll the Lync user or update data to “xds” database. 

I have added my user to RTCUniversalServerAdministrator group and run the following command again.
C:\> Enable-CsUser –Identity “mydomain\Baluilag” –Registararpool “Lyncpool01.mydomain.com” –SipAddressType “EmailAddress” –SipDomain “mydomain.com”
Now user got successfully enrolled for Lync.

Thank you.

ShareThis