July 30, 2015

How to identify the source of the poor call quality issue?


How to identify the source of the poor call quality issue?
As a client when you try to connect to a Lync or Skype for Business conference or make a peer to peer call, the audio or video quality may be choppy, tinny, or delayed. This causes the meeting or call to be unusable.

How to identify the source of the issue?
In Lync 2010, Lync 2013 and Skype for Business client you can use voice and video quality indicators to identify how well you're being heard or viewed. New indicators that are displayed in the conversation window tell you when conditions are present that may affect the quality of the voice or video call. These conditions may include poor network connectivity, low-bandwidth network connections, or poor audio quality from a particular device. In scenarios in which you experience poor audio quality, click the indicator to display possible reasons for the audio issue and to link to relevant resources.
 

The conversation window displays the network quality or signal strength of the call using one, two, or three bars (similar to many mobile phones).
On Lync 2010

On Lync 2013


On Skype for Business 2015
 


As a general guideline, to troubleshoot scenarios in which you experience poor audio or video quality in a Skype for Business conference, follow these steps: 

1.    Determine whether the computer is using a wired or wireless Internet connection. A wired connection can provide more bandwidth and stability in most cases and should be the preferred method of connecting if that kind of connection is available. Additionally, consider turning off any wireless antennas to avoid connecting through a wireless connection.

2.    Make sure that the audio/video device that is being used is approved and certified to work with Lync and Skype for Business client. For more information, see the following Microsoft TechNet topic: USB Peripherals

3.    Select the correct device, and make sure that the recording volume is at the appropriate level. In the upper-right area of the window, click the gear icon, click Tools, click Options, and then click Audio Device. Verify that the appropriate device is selected.



Adjust the Microphone slider to the volume level that you want. Speak at your usual voice level. The indicator should go no higher than the midway point.

4.    Do not make calls over a wireless Internet connection, virtual private network (VPN), or remote access service (RAS) connections.

5.    If the problem persists, transfer the call to a mobile phone or landline. To transfer a call, in the Lync conversation window, click the Transfer button, and then do one of the following:
1.    Click one of your other numbers (such as your mobile phone number).

2.    Click another Person or Number. In the dialog box, type the phone number you want to transfer the call to, and then click OK.

6.    If poor network quality is affecting audio, you may see the following messages in Lync:
  • Network connectivity is causing audio quality issues
  • Network connectivity much be causing audio delays

Thank you

Windows 10 countdown is over


Windows 10 countdown is over
 
Yesterday Microsoft released Windows 10. They rolling out the public release of Windows 10 to the world. This is a hugely significant milestone for Windows. This is Microsoft’s best Windows release ever! Check out Terry's blog for details on this public release.

Below machines are qualify for FREE Windows 10

·       For PCs running Genuine Windows 7/8 – these machines qualify for a free upgrade to Windows 10 through Windows Update. (You can also do a media-based upgrade though the Microsoft Software Download site.)

·       For PCs not running Genuine Windows 7/8/10 – you can purchase Windows 10 at your local retailer or at online retailers like Microsoft Store.com.

·

Windows 10 free 90 evaluation edition available:

The Windows 10 Enterprise Preview has been updated and replaced with the Windows 10 Enterprise Evaluation edition. This free, 90-day evaluation will help you test your apps, hardware, and deployment strategies.

Watch What's New in Windows 10 Deployment for new recommendations for upgrading existing devices using a simple in-place upgrade process, provisioning tools for transforming new devices into ones ready for enterprise use, as well as updates to traditional deployment tools and techniques (ADK and beyond).

 
Thank you.   

July 27, 2015

How to add or remove OWA machine to existing WAC Server Farm?


How to add or remove OWA machine to existing WAC Server Farm?
Recently I was working on customer issue where PowerPoint presentation rendering was not working. The issue was one of Office Web App server was down and due to that OWA servers were not communicating with each other’s over 809 port, as soon as we remove faulty server from WAC farm and restarted Office Web Apps service, PowerPoint presentation rendering started working.
Now question comes how to remove existing OWA machine from WAC server farm and add new Office Web Server to existing farm.
How to add new Machine to existing farm?
1.    First get the current WAC Farm detail by using below cmdlet:

Get-OfficeWebAppsFarm

Result will show Machine name, InternalURL, externalURL

To add new OWA machine to existing farm:
Log on to Office Web App server which you want to add to the existing WAC farm.
Then run Get-OfficeWebAppsFarm command:
You will get below result as this machine is not part of an Office Web Apps Server farm.

Also you will see error message from: event ID: 8123
 

Now you need to add this server as a part of Office Web Apps server farm:
Cmdlet:
New-OfficeWebAppsMachine -MachineToJoin OWA2.mydomain.com
 
Now if you run Get-OfficeWebAppsFarm command you will see below result as new server added to existing farm.
You can restart Office web apps service to take immediate effects


How to remove Office Web App server from existing WAC farm server?

Run below mentioned cmdlet on machine which you want to remove from WAC Farm server.

Remove-OfficeWebAppsMachine –Verbose

 
Now run the Get-OfficeWebAppsFarm. Result will show that there are two office Web Apps server.


Thank you.

July 26, 2015

Users are unable to see PowerPoint Presentation.


Issue: Users are unable to see PowerPoint Presentation.

Error Message:

1.    Some presenting features are unavailable due to server connectivity issues.

2.    Sorry, PowerPoint Web App ran into a problem opening this presentation. To view this presentation please open it in Microsoft PowerPoint.


Resolution:

First thumb rule is check if this is client side issue or server side.  You can easily identify if all users are facing same issue that means issue from server side.

Also make sure that all Lync 2013 and Skype for Business client showing same issue. If respective to client version.

[For Lync 2010 client PowerPoint (PPt) sharing works legacy way, where there is no involvement of Office Web App Server so don’t consider Lync 2010 for side issue.]

Assume that all Lync 2013 and Skype for Business users are seeing same issue.

Now time to check if any known changes has been done recently, Like Windows updates installed on Lync and WAC server, any firewall changes etc.

Wherever I use WAC consider as Office Web Apps server

Assuming that there is no known changes..

First will do Lync server side troubleshooting:

1.    If users are able to upload PowerPoint presentation in meeting and participant able to see uploaded content that is indicating that Lync Server correctly functioning. E.g. attached image has shown presentable content.

 

2.    Now time to open Event Viewer on Lync Server and find Event 41032.

This event Logged on Front End Server upon Successful Discovery of WAC Server/URLs (this happens first time when we add WAC Server to topology and publish or publishing the topology or upon restart of Lync Server Web Conferencing Services).

3.    If Event 41032 is not logged on FE server then check Event 41033 logged on Office Web App servers. If Event ID 41033 is indicating that Lync server unable to contact WAS server for WAC URLs. Means Office Web Apps server URLs discovery failed.  

4.    Time to check discovery URLs. Browse your WAC farm URL:


Expected result is XML page. If you are not getting xml page result then you need to verify your WAC IP listing on 443 or not. You can telnet and check.

In my case I am getting correct result. Means no firewall issue and getting correct WAC URLs, Lync FE contact WAC URLs correctly. So problem somewhere else.
 

5.    Log on to internal computer and browse discovery URL with Office Web App server FQDN. Like below.


You must get same xml page. If you are getting xml page result means Office Web Apps server also listening on 443 and responding correctly.  

6.    Start logging on Lync 2013 / Skype for Business client, Lync Front End with WAC scenarios and reproduce issue.

Open client log with snooper and look for <diagHeader>, you may see below information.

From: <sip:bilag@mydomain.com>;tag=def1d6afed;epid=3acd7df579
Call-ID: 26f89de3a2e74445a9166487bead93e4
CSeq: 1 SERVICE
User-Agent: UCCAPI/15.0.4709.1000 OC/15.0.4711.1002 (Skype for Business)
Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="6C6CFE79", targetname="FE.mydomain.com", crand="3724870c", cnum="211", response="2dc782bb2b9d9321ddeb2988538a81d027b79eda" Content-Type: application/msrtc-reporterror+xml Content-Length: 1108
http://schemas.microsoft.com/2006/09/sip/error-reporting
">sip:bilag@mydomain.com;gruu;opaque=app:conf:focus:id:1HR09FLH" callId="b04e2fffeed54487b1b6f292e7d6f263" fromTag="d543445ec7" toTag="854E0080" requestType="" contentType="" responseCode="0">54024;reason="A viewing URL navigation was attempted.";ClientType=Lync;Build=15.0.4711.1002;ContentMCU="sip:bilag@mydomain.com;gruu;opaque=app:conf:data-conf:id:1HR09FLH";ConferenceUri="sip:bilag@mydomain.com;gruu;opaque=app:conf:focus:id:1HR09FLH";LocalFqdn="2-LFYXVJ12.mydomain.com";Url="https://wac.mydomain.com/m/Presenter.aspx?a=0&e=true&WopiSrc=https%3A%2F%2FLyncpoolweb.mydomain.com%2FDataCollabWeb%2Fwopi%2Ffiles%2F104C-C-126422C&access_token=AAMFEGPqIHJT4SZfiyrOilkY5HUGEBt6LQTtFYN5Yo5I_aJRXUeBEGPqIHJT4SZfiyrOilkY5HWCAhylgyBRaaoncE2Ph0fN3BsbkgJrizEJieGEZVHN0ssz1mGJHIYIoAoa_xSU0ggIDURhdGFDb2xsYWJXZWI&<fs=FULLSCREEN&><rec=RECORDING&><thm=THEME_ID&><ui=UI_LLCC&><rs=DC_LLCC&> 
http://schemas.microsoft.com/2006/09/sip/error-reporting
">sip:bilag@mydomain.com;gruu;opaque=app:conf:focus:id:1HR09FLH" callId="b04e2fffeed54487b1b6f292e7d6f263" fromTag="d543445ec7" toTag="854E0080" requestType="" contentType="" responseCode="0"><diagHeader>54031;reason="The WAC presentation failed with a server error.";ClientType=Lync;Build=15.0.4711.1002;ContentMCU="sip:bilag@mydomain.com;gruu;opaque=app:conf:data-conf:id:1HR09FLH 
http://schemas.microsoft.com/2006/09/sip/error-reporting
">sip:bilag@mydomain.com;gruu;opaque=app:conf:focus:id:1HR09FLH" callId="b04e2fffeed54487b1b6f292e7d6f263" fromTag="d543445ec7" toTag="854E0080" requestType="" contentType="" responseCode="0"><diagHeader>54020;reason="The WAC presentation failed with a critical error.";ClientType=Lync;Build=15.0.4711.1002;ContentMCU="sip:bilag@mydomain.com;gruu;opaque=app:conf:data-conf:id:1HR09FLH".; ";ConferenceUri="sip:bilag@mydomain.com;gruu;opaque=app:conf:focus:id:1HR09FLH";LocalFqdn="2-LFYXVJ12.mydomain.com";
https://wac.mydomain.com/m/Presenter.aspx?a=0&e=true&WopiSrc=https%3A%2F%2Fpoolweb.mydomain.com%2FDataCollabWeb%2Fwopi%2Ffiles%2F104C-F-10EEAC9&access_token=AAMFEGPqIHJT4SZfiyrOilkY5HUGEBt6LQTtFYN5Yo5I_aJRXUeBEGPqIHJT4SZfiyrOilkY5HWCAhylgyBRaaoncE2Ph0fN3BsbkgJrizEJieGEZVHN0ssz1mGJHIYIoAoa_xSU0ggIDURhdGFDb2xsYWJXZWI&<fs=FULLSCREEN&><rec=RECORDING&><thm=THEME_ID&><ui=UI_LLCC&><rs=DC_LLCC&>";ErrorType="fatalDocument";ServerVersion="15.0.4571.1502";ErrorMessage="Sorry, PowerPoint Web App ran into a problem opening this presentation. To view this presentation please open it in Microsoft PowerPoint.";CorrelationId="2b0dbfb9-fe96-4e5d-a39f-769c6e9b7f36"
 
Client log was showing diagHeader 54020  - The WAC session has failed with a critical error.  The error message indicates the reason given to the client.  The client was unable to view the content as a result.  – This occurs normally when the server fails to handle the PPT conversion & reports failure. 

7.    Now start logging on Lync front end server with WAC scenario logs and correct.
 

155699 TL_VERBOSE(TF_COMPONENT) [pool\FE]26B4.2F24::07/24/2015-02:45:31.281.000312EA (DataMCU,MeetingS.OnConnect:meetings.cs(387)) ( AA3274F1 )Setting url base for sip:bilag@mydoamin.com to https://poolweb.mydomain.com/CollabContent/{C5810594-C849-455C-9DB7-F672B9665B9C}/1HR09FLH/

168746 TL_INFO(TF_COMPONENT) [pool\FE]26B4.2F24::07/24/2015-02:45:44.013.0003211D (DataMCU,ReservationManager.ReserveTitleInternal:reservationmanager.cs(289)) ( AA3274F1 )ReserveTitleInternal(PowerPoint file.pptx, 1) 

182846 TL_INFO(TF_COMPONENT) [pool\FE]26B4.2F24::07/24/2015-02:46:09.713.00032A74 (DataMCURunTime,UploadStreamPsom.constructor:uploadstream.cs(333)) Receiving file. Cookie=5036, maxFileLength=2415, file=C:\ProgramData\Microsoft\Lync Server\WebConferencing\Temp\{C5810594-C849-455C-9DB7-F672B9665B9C}_1HR09FLH\40825f5d-9933-4191-9226-2d92bdfea8ba.dl
183286 PowerPoint file.pptx 

From the Lync server side traces, it’s clear that PPT upload is fine & failure is occurring while rendering happens. The problem seems to be on the Office web App servers only.  

8.    Logged in to WAC server and checked Event log found that. 

Found Error events (Event ID 8118) related to port 809 communication. This port is used for intra node OWA farm servers’ communication.

We have two Office Web Apps server and port 809 was open on both Office Web Apps server. You can verify port using telnet.

Make sure the following ports aren’t blocked by firewalls on either the server that runs Office Web Apps Server or the load balancer:

·       Port 443 for HTTPS traffic

·       Port 80 for HTTP traffic

·       Port 809 for private traffic between the servers that run Office Web Apps Server (if you’re setting up a multi-server farm)

In my case there was intermittent failures on communication between both OWA servers.
To isolate the issue remove one OWA server from OWA From and tested. As soon OWA1 server who showing error event 8118 removed from WAC Farm PowerPoint presentation started working.

Corrected issue on Office Web Apps issue and added the same to OWA1 server to Farm and everything started working.

Thank you.

How Office Web App server request flow work?


How Office Web App server request flow work?

1.    Assume that user logged on Lync 2013 or Skype for Business 2015 clients and browse the Meeting URL and joined Lync / Skype for Business meeting and upload the PowerPoint presentation to Meeting.

2.    Lync / Skype client uploads the PPT file to Lync front end server.

3.    Lync 2013 Front end Server Encrypts and saves the PowerPoint presentation file on to the Lync file share (content store) and generates File ID and Access Token to access presentation file.

4.    Lync server then retrieves WAC Server name URL (stored in CMS during WAC (OWA) Discovery process) and forms an URL that includes, WAC Presentation URL, File ID and Access Token of the PPTX File.

5.    Lync Access Server sends this WAC URL formed to Presenter as well as attendees.

6.    Lync Presenter/Attendee’s Client sends requests to this URL and contacts office web app server to get the PowerPoint presentation.

7.    Once Office Web App Server receives this request it retrieves the Access Token, File ID and File location (file share) and access the PPTX file by contacting the Lync Content File store via Lync Front end Servers (Lync Web Services FQDN will also be present in the initial Request).

8.    Office Web App server makes a temporary copy of PPTX file and creates html (dochtml) file and sends it to the Presenter/Attendee’s Client for presentation rendering.
 

How rendering work?

1.    Lync client send WOPI App request for file (PPTX file) to Office Web Apps server (WOPI Application system).

2.    Office Web Apps server check Cache for file. If file is available in cache then Office Web Apps server respond back to client.

3.    If file is not in Cache then Office Web Apps server request file from Lync Server.

4.    Lync Server verify that request comes from Bound WOPI server and request a file from file Store (Lync file store where file stores).

5.    File store returned file to Lync Server.

6.    Lync Server returned file to WOPI App server (Office Web App server).

7.    Office Web App server create Cache document locally in dochtml format.

8.    Then return of rendered file to Lync client in Meeting.
 
Changed diagram from SharePoint WOPI to Lync. So please excuse for any error.
 
 
Ref: http://blogs.technet.com/b/praj/archive/2015/04/14/troubleshooting-office-web-app-server-integration-with-lync-server-2013.aspx
 

Thank you.

How file rendering work in SharePoint using Office Web Apps server.


How file rendering work in SharePoint using Office Web Apps server.
 

1.    Client / User send request for File to HOST server that is our SharePoint server.

2.    SharePoint server (HOST) Authentication of user using Claims authentication methods and creates auth_token for user and rights applied for file.

3.    Then SharePoint Server (HOST) responds to client / User with WOPI Host page and iFrame for file from WOPI App.

4.    Client / User Request for file from WOPI App to be displayed in the browser.

5.    Then WOPI App       Cache is checked for file existence. If file available in Cache then it Office Web Apps server respond with file.

6.    In case file is not in Cache the WOPI (Office App server) existence is discovered perform checksum on file at WOPI Host or request File is not in cache

7.    SharePoint Server (HOST) verify that request comes from Bound App server and then request file from Storage (file database).

8.    Then Database server returns file from storage and sent it to host.

9.    Later SharePoint server (HOST) Send file to WOPI App Server.

10. WOPI App server checks Cache file, generate rendering in Hot Blob Storage

11. WOPI App Send rendering of pages to Client.

 

Thank you.

July 21, 2015

Unable to see location information over new wireless subnet


Issue: Unable to see location information over new wireless subnet?
Problem Statement:
Lync / Skype for Business client doesn’t show location information over wireless subnet for all users on specific site. Wired connection shows correct location information.

Resolution:
In my case location information was showing earlier however recently wireless subnet got changed and since then location information was not displaying on Lync / Skype client.
Follow the below steps in order to resolve issue..
1.    Get new wireless subnet information and add the same subnet under Network Configuration.

a.     Browse Lync control panel URL with CsServerAdministrator or CsAdministrator permission and then open Network Configuration.

b.    Then add new wireless subnet (e.g. 10.10.10.1 /20) under site.

2.    Now you need to add your new wireless subnet to Location Information Server (LIS) subnet.
LIS subnets need to be defined.  Subnets (including location information) will be configured using the Set-CsLisSubnet cmdlet.
Command let:
Set-CsLisSubnet -Subnet "10.10.10.0" -Description "San Jose Wireless Campus" -Location "Office Wireless" -CompanyName "ABC" -HouseNumber "123" -StreetName "ABC" -StreetSuffix "Way" -City "San Jose" -PostalCode "13456" -Country "US"

3.  Add another LIS subnet if you have.

4.  Now time to publish the details information to database. Use below cmdlet:

Publish-CsLisConfiguration
Now wait for 5 min and check Lync / Skype for Business client.
 
Note: Step no. 1 is optional if you are looking for only showing location information.
 
 

Thank you.

ShareThis