January 22, 2015

This meeting may have expired, or it's possible you're using a bad URL.

Issue: Unable to access meeting.

Error: We're having trouble getting you into the meeting.

This meeting may have expired, or it's possible you're using a bad URL. If the latter, try calling into the meeting using the phone number on the invite, or ask the organizer to drag you into the meeting from the Contacts list.

Problem Statement:

Today I came across one issue were user has scheduled meeting however unable to use the meeting and it says ‘This meeting may have expired’. 

Resolution / Workaround:

a.     Workaround 1:

1.    If user has scheduled this meeting then he can check under link:  https://meet.mydomain.com/scheduler/ sign-in using credential like user name ‘mydomain\baluilag’ and password ************.
See if the affected meetings.

2.    If User have not scheduled affected meeting using Scheduler then they cannot modify however they can verify and join meeting from scheduler.  

b.    Workaround 2:

3.    User can use Meet Now option and use meeting entry information for their meeting.
Lync 2013 > Meet Now > click on More Option > Meeting Info > Meeting URL. See the screenshot 

Use the meeting URL and sent to attendee for joining. 

NOTE: User meetings expire 14 days after the scheduled end time.

There is no specific solution for above issue because meeting is expired per configuration.

Thank you.

January 18, 2015

Lync status show updating and display ‘Maximum Followers Reached’ in Lync 2013.

Issue: Lync status show updating and display ‘Maximum Followers Reached’ in Lync 2013.
Problem Statement:
I came across an issue where couple of users Lync status hasn’t updating on Lync client. It says updating however Lync presence status not get updated after long time.
Affected users Lync status shows as updating and Lync contact card display message as ‘Maximum Followers Reached’.
This is basically happens because affected user are more popular and get added as contact on Lync more than 200 times. By default Lync user can be contact as 200 by other Lync users.
E.g.  When one Lync user adds another Lync user as a contact, the first Lync user is subscribing to five categories of information about the second Lync user. Updates for these categories of information are automatically sent to the first Lync user. The user model assumes a default of 1000 category subscriptions per Lync user. This means that a Lync user could be a contact of as many as 200 other Lync users.
Resolution/ Workaround:
Follow the below steps in order to resolve issue.
To verify the issue you check on Event viewer on Lync Front End server and you will see ID: 32078 and it will shows as ‘A user has reached the limit for maximum category subscriptions per publisher’.
A.    Without policy changes: If you don’t have permission on server then do below.

1.     Delete unused contact or group from Lync buddy list.
2.     Ask other user to delete affected users contact from their buddy list.
3.     Wait for some time and check the status. It will show correct status.

B.    Using Lync client presence policy:
1.     Log on to Lync server and open Lync Server management Shell.
2.     First use get command to see default policy.

Command will return the MaximumCategorySubscription number and MaxPromptedSubscriber number.
MaxPromptedSubscriber: 200
MaximumCategorySubscription: 1000 

3.     Now you need to change the default presence policy to show more contact.  I would recommend instead of changing default global policy you can create new policy and assign the new policy to affected user.
Command let:
New-CsPresencePolicy -Identity "TooPopularPolicy" -MaxPromptedSubscriber 400 -MaxCategorySubscription 2000 

If you already have policy created AND want change the value then use below command let:
Set-CsPresencePolicy -Identity "TooPopularPolicy" -MaxPromptedSubscriber 600 -MaxCategorySubscription 3000 

4.     Now you have Presence policy created, time to assign policy to affected user. Command let:
Grant-CsPresencePolicy -Identity "Balu Ilag" -PolicyName "TooPopularPolicy" 

Wait to get changes apply. You will be able see correct status and contact card message next to status Maximum Followers Reached’ will not show again.
Note Updating MaxCategorySubscription to a higher value could impact network bandwidth on the Lync server network

Apply to: Lync 2010 and Lync 2013.

Thank you.

Lync 2013 crashing when make or receive audio or video call?

Issue: Lync 2013 crashing when make or receive audio or video call?
Problem Statement:
Recently couple of user complaining about Lync 2013 client is hung and later it crashing.
They have to close and reopen Lync client in order to IM. Whenever affected user make call or receive audio or video calls Lync 2013 client gets hung and later it crash. Instant messaging, multiuser chat everything works fine however it crash when do audio or video.
Resolution / Workaround:
Here are the resolution steps:
1.    Open Lync 2013 client and see the version Lync 2013 > Option drop down menu > Help > About Lync > see the version.

Do not use older that above client.
2.   Install Lync 2013 updates,
a.   Uninstall KB2817465
b.   b. Install KB28881070   http://support.microsoft.com/kb/2881070

c.   Check if issue resolve.  If not then do below.

3.    Repair Office 2013 client and see if issue resolves. Not then do next step.

4.    Uninstall Office 2013 and reinstall and updated the same.

5.    Updated Audio and Video drives. Check AV call for issue resolve.

6.    Uninstall Citrix Receiver client application and see the Lync 2013 Audio and Video call works or not.

However my issue has not resolve. 

a.     When I closely look on Lync 2013 client found resolution.

b.    To narrow down the issue, have disconnect all USB devices and used PC Audio device.


c.     Later tested Lync Audio and Video calls.

d.    Call got through without any issue and Lync client hasn’t crash.

Means Lync 2013 client was crashing due to uncertified USB headphone and camera device drives. 

Apply to:  Lync 2013 32 and 64 bit, Windows 7 64 bit, Windows 8.1 64 bit. 

Thank you.

January 10, 2015

Lync Server Update Improves Lync Web App Experience for Google Chrome users.

Lync Server Update Improves Lync Web App Experience for Google Chrome users. 

Recent and upcoming Google changes to the Chrome browser affect the Lync Web App on both Mac and Windows platforms, and require us to make changes to Lync Server and Lync Online in order to deliver a great experience for Chrome users.  We have begun making these changes, and expect to complete them in the first quarter of 2015; in the meantime, when needed, we will provide users with manual work-around instructions as part of the meeting join experience. 

For Mac users:  Google discontinued support in October for the 32 bit version of Chrome on Mac.  Because the existing Lync Web App works only in the 32 bit version of Chrome, Mac users must for now use either Safari or Firefox to join a Lync meeting.  When joining a Lync meeting, users with Chrome set as their default browser will see a message instructing them to copy the Lync meeting URL, open Safari or Firefox, and paste the meeting URL into the new browser window.  The Lync meeting will then begin.  We plan to remove this manual step for Chrome users by adding support for the 64 bit version of Chrome early in 2015. 

For Windows users:  The most recent update to Lync Server 2013 (Cumulative Update 5.0.8308.857) provided manual work-around instructions to Windows users with the 32-bit version of Chrome set as their default browser, even though the 32-bit version of Chrome is still supported on Windows.  On 12/31/2014, we released a new update to Lync Server 2013 (Cumulative Update 5.0.8308.866) to remove the manual work-around instructions and to allow the Lync Web App to run in Chrome as it did previously.  We encourage administrators to apply Cumulative Update 5.0.8308.866 as soon as is practical to avoid the manual work-around.  We have already begun applying this update to Lync Online.  

What’s next?  As noted above, we plan to add support for 64 bit Chrome on Mac early this year.  We are also working on solutions to minimize the impact on Chrome users with the planned deprecation of the so-called “Netscape Plug-In API”, or NPAPI, targeted by Google for April, 2015.   

Byline: Daniel Jonathan Valik.


January 1, 2015

Microsoft Most Valuable Professional Award Third time

Microsoft Most Valuable Professional Award Third time
Today I have received Microsoft MVP Award third time consecutively (2013-2015).

My MVP recognition in Lync Technology.

Big thanks to Microsoft and MVP program management team.

Thank you


December 27, 2014

Lync needs your user name password to connect for retrieving calendar date from Outlook.

Issue: Lync keep asking Password to connect Outlook from externally.
Error Message:
Credentials are required
Lync needs your user name password to connect for retrieving calendar date from Outlook. 
Problem Statement:
My Lync works as expected from internally, work properly with Outlook. When Lync connect externally Lync keep asking credential however never accept the correct credential and keep getting password prompt.
Lync Sign properly however when it connect Outlook for Free/Busy and calendar information it give above prompt however never accept credential.
Why Lync try to connect?
Lync tries to connect Outlook to get following services.
  • Calendar and Free/Busy information from Outlook
  • Exchange Web Services (EWS)
  • Response Group Service
  • Address Book Service.
But some reason if Lync is unable to connect above services then Lync will show password prompt.
This issue occurs for multiple reasons, and in certain scenarios, it is the expected behavior. Lync generally prompts you for credentials only after you're signed in and when it must connect to an external service such as the Microsoft Exchange Free/Busy service or the Exchange Calendar service.
Basically Lync doesn't integrate automatically with Outlook, Lync prompts you for credentials before it lets you connect to Outlook to retrieve Calendar and Free/Busy information. Lync doesn't automatically connect to EWS, Lync prompts you for credentials before it lets you access the EWS URLs.
In my case Lync continues to prompt for credentials that means there's probably an issue with Outlook or with the Exchange services.
If the Exchange server or EWS is unavailable, this causes Lync to continuously prompt for credentials because it can't contact Exchange for authentication. To resolve this issue.
Already verified that Outlook has connectivity to the mailbox and I can EWS URLs (internal and external) correctly under Lync configuration (Press Ctrl key + Right click on Lync Icon and say ‘Configuration Information’). 
Able to resolve autodiscover record. autodiscover.domain.com – IP Address.
Environment Details: Exchange 2010, Lync Server 2010, TMG for Reverse Proxy. Lync 2010, Lync 2013, Outlook 2010, Outlook 2013.
When I checked authentication on exchange and TMG for Exchange Autodiscover found below:
Exchange Anywhere has -> Basic Authentication
TMG Web (Outlook Anywhere) Rule has -> Basic Authentication. 

As per Microsoft recommendation web rule must pass the request to Server for authentication.
TMG or Web publisher should not do authentication. To resolve my environment issue we did below configuration changes.
Exchange Outlook Anywhere configurations:
Log on to Exchange CAS server and Open Exchange PowerShell and Run the below command:

a.     Set-OutlookProvider EXPR -server $null Get-Outlookanywhere | set-OutlookAnywhere -clientAuthenticationMethod NTLM -iisauthenticationMethods NTLM

b.     Get-OabVirtualDirectory | Set-OabVirtualDirectory -IISAuthenticationmethods NTLM

c.      DO the IISReset on ALL CAS servers
Follow the below steps on TMG:
a.     Log on to the TMG server.

b.     Open Firewall and right click on Outlook Anywhere Rule

c.      Set on the Publishing Rule (not Listener) authentication "No Delegation, but Allow client to authenticate directly".

d.     Click on- APPLY. 

After making above changes our Outlook password prompt and Lync password prompt issue got resolved and working fine.

Thank you

December 26, 2014

Microsoft Window Server 2003 end of life.

Microsoft Window Server 2003 end of life. 

So many organization still using Windows Server 2003. The end of support (EOS) date for Windows Server 2003 is fast approaching. On July 14, 2015, Microsoft will stop releasing critical patches for Windows Server 2003. Running unsupported software presents significant risks and complications for your business that will only increase in severity as time goes on.
Think for Server Operating System Up-gradation. 

Thank you.