When you experience problems sharing PPT content in a Skype for Business meeting, the reason could be a variety of different factors not beeing implemented in the correct way.
There are many ways to publish the Office Web App server necessary to enable this feature. One of those are the IIS ARR web proxy.
In this case the proxy is set up and everything is working fine with all web services, and the officewebapp URL test(https://officewebapp.yourdomain.com/hosting/discovery) is also returning the correct XML page. However, when an internal user uploads a PPT to the meeting, the federated participant experiences just a spinning “Loading” and the presentastion does not load correctly in the client. Other internal users are able to see the presentation in the meeting.
Remove response header added from IIS on Revers Proxy server, Open Internet Information Services (IIS) Manager on IIS ARR server.
- In the Connections pane on the left side, expand the Sites folder and select the site(Default Web Site).
- Double-click the HTTP Response Headers icon in the feature list in the middle.
- Highlight “X-Frame-Options” In the Actions pane on the right side, click Remove.
- Click OK to save your changes.
- Run iisreset from an elevated commandprompt.
After Removing the X-Frame-Options the presentations renders perfectly from the OfficeWebApp server for external participants as well.
I recently came across a small chalenge which maybe is nothing to write about, but I choose to anyway as I came across a few solutions to this error message while I was investigating it.
The problem is the following message in the client log when trying to federate in a fresh Skype for Business on-prem environment.
SIP/2.0 504 Server time-out
ms-diagnostics: 1034;reason=”Previous hop federated peer did not report diagnostic information”;Domain=”partnerDomain.com”;PeerServer=”accessedgeFQDN.partnerDomain.com”;source=”accessedgeFQDN.yourdomain.com”
After some back and forth and checks of firewall rules and port openings, in addition to going over the topology a few times, I stumbled across the solution(which should have been pretty obvious to start with). It turned out that the SRV records for the domain had been registered with typo’s.
Make sure you have the correct DNS entries registered in public DNS for your domain zone.
SRV records should be in the format of _sipfederationTLS._tcp.yourdomain.com weight 0 priority 0 port 5061 host accessedge.yourdomain.com.
Make sure you enter just the _sipfederationTLS._tcp part if you do this manually, as the domain name will be appended automatically in the DNS zone.
When you do a Nslookup -q=srv _sipfederationTLS._tcp.yourdomain.com, it should resolve to your access Edge FQDN in public DNS.
Another headset review coming up. This time it’s the new Plantronics Voyager 8200 UC, a boom less headset for the business market aimed at the productive worker needing a headset to block out unwanted noise in an open office environment.
Plantronics Voyager v8200 UC and pouch.
Power and mute button located on the right ear cup.
ANC button on the left ear cup.
The Plantronics Voyager 8200 UC is such a headset. It’s delivered in a soft pouch together with a USB Bluetooth dongle(always use it when connecting to your PC/Mac), a USB charging cable and a mini jack cable for those times when Bluetooth cannot be used(in flight mode for example). The headset is available in two colors, black(the one showed in this post) and white. It has a quite nice finish with leather and aluminum, and no microphone boom.
The boom less construction is surprisingly effective, and both audio quality during conversations and the reduction of background noise is quite good. The callee is not able to hear any noise in the background when making a call, even in a quite noisy environment. The ANC has two settings when turned on, that is Medium and High. With my limited hearing I’m not able to separate the two 🙂
There are also functions for open mic, mute etc. all controlled from the buttons on the headset. When playing music, you can control play/pause, skip forward and backward etc. Incoming calls are prioritized, and answering calls are done with the buttons on the headset or by the auto answer function if the headset is lying on your desk. This is one of my favourite features with Plantronics headsets designed for UC and certified for Skype for Business. The proximity sensors allows for automatic features as ANC on/off and automatic pause of movies/music and answer/mute calls when the headset is put on or taken off. The automatic disabling of ANC when the headset is not used also acts as a power saving feature.
There are however something to bear in mind when it comes to proximity sensors and machine connectivity. As mentioned earlier in this post, the USB dongle has to be used when connecting to a PC or Mac. That being said, I’ve experienced differences between Mac OSx and Windows operating systems when it comes to operating the headset. Specially the Mac OSx seems somewhat limited in regards to controlling playback of music from the headset. I’m sure this is a problem related to the operating system API and not the headset as it works fine in a Windows Client.
When it comes to playing music or watching movies using this headset, it delivers very good sound(at least in my opinion). When using the BT dongle that comes with the headset, I’ve not experienced any problems with audio playback. Some people has experienced audio delay when streaming audio over Bluetooth, but this is not my impression. I’ve tested audio streaming both with USB dongle on my MacBook and with my iPhone and experienced no audio delay.
The Plantronics Voyager v8200 UC is in my opinion a very good all round headset which delivers excellent performance both when used as a productivity headset and as an entertainment headset streaming music and watching movies. It’s a very good alternative to the Plantronics Voyager Focus UC, which in my opinion has been the best UC headset on the market up until now 🙂
After migrating to Skype for Business and removing Lync 2010/2013 pools, you may encounter an event ID 1034 stating that the LS File Transfer Agent encountered an error while accessing a file share.
The file share referenced will be the share on the removed Lync 2010/2013 pool. If you run the command Get-CsCentralManagementStoreReplicationStatus -CentralManagementStoreStatus, you will se an entry of DeletedReplicas that states the server FQDN of your deleted Lync pool/server. If the server is deleted from the topology not to be used again, you can proceed with deleting the server from the XDS database.
The easiest way to accomplish this, is to make sure that all Lync server components are removed from the Lync server in question. Simply go ahead and remove the Lync components from the server using Add/Remove programs. Make sure to reboot the server after the removal of the Lync components. The error message in the event log should disappear after this operation.
If this is not successfull, you will have to remove the replica ID’s from the SQL database(XDS).
This procedure from the UC Lobby blog by David Paulino should do the trick.
In this post I will try to keep you updated with the current releases and build numbers for Skype for Business 2015 Server.
As of now, there has been released five updates for Skype for Business Server 2015. The Microsoft download page is updated with the latest SkypeServerUpdateInstaller, so the link will always point to the most recent CU.
Server updates and Build Numbers:
August 2019 Update – Build number 6.0.9319.562(CU10HF1)
July 2019 Update – Build number 6.0.9319.559(CU10)
May 2019 Update – Build number 6.0.9319.548(CU9)
Januar 2019 Update – Build number 6.0.9319.537(CU8)
March 2018 Update – Build number 6.0.9319.519(CU7)
January 2018 Update – Build number 6.0.9319.514(CU6 HF1)
December 2017 Update – Build number 6.0.9319.510(CU6)
May 2017 Update – Build number 6.0.9319.281(CU5)
Be adviced: CU6 has been reported to break Web Conferencing Edge service due to updates to the .Net Framework.
Check out this TechNet article if you experience problems.
February 2017 Update – Build number 6.0.9319.277(CU4 HF1)
November 2016 Update – Build number 6.0.9319.272(CU4)
June 2016 Update – Build number 6.0.9319.239(CU3)
March 2016 Update – Build number 6.0.9319.235(CU2)
November 2015 Update – Build number 6.0.9319.102 (CU1)
This post will update as new CU’s are released.