Happy new year! I wonder what 2019 has in store for us?
It’s been 6 or so weeks since our last update to the client, and this update brings just the one fix. Kb 4461557 takes the Office 2013-based client from 15.0.5085.1000 to 15.0.5101.1000 (although it’s reported in the kb as 15.0.5101.1002).
This update fixes the following issue:
Nothing documented.
Nothing documented.
Continue reading ‘Lync 2013 / SfB 2015 Client Update – January 2019’ »
The phone in my ‘mugshot’ this year is an old red buttinski, or ‘butt’ for short. In other countries you might call it a lineman’s handset. (If you refer to these by any other name in your country, please post it to the comments).
I’m not too proud to admit that I’m frequently plagued by identity crises. As a consultant I spend my days signing into and out of many different deployments of SfB and Microsoft Teams, and I *regularly* lose track of which system I’m in.
With Windows it’s easy: you just ask a CMD or PowerShell prompt “whoami” and it tells you.
With Skype for Business it’s pretty simple too: just click on your picture (a shortcut to the setup/Options menu) and then on the General tab all is revealed.
It’s there in Teams, but not where you think:
The trick is to hover or click on your own icon/photo in any post you’ve made to a channel. Your contact card will show, revealing (at the very least) the address you used to sign in:
It even works when you’re a guest:
This works in the stand-alone Windows client, the browser and even the mobile client.
Thanks to fellow MVP @Loryan for pointing this one out.
– G.
The larger and more complex your on-prem SfB installation is, the greater the likelihood of encountering firewall problems.
If you run this script on your Front-End server(s) it will:
(Yes I’m figuring if 50001 is open, so will 50002 and 50003.)
Download the script from the Technet Gallery site.
v1.1 7th April 2019.
v1.0 10th December 2018. This is the initial release.
– G.
It’s been a month since our last update to the client and quite some time since we’ve seen a security update. This update brings one fix. Kb 4461487 takes the Office 2013-based client from 15.0.5071.1000 to 15.0.5085.1000.
Nothing documented.
Nothing documented.
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – November 2018’ »
It’s been a month since our last update to the client and our October update brings one fix. Kb 4461446 takes the Office 2013-based client from 15.0.5065|5067.1000 to 15.0.5071.1000.
Nothing documented.
Nothing documented.
Continue reading ‘Lync 2013 / SfB 2015 Client Update – October 2018’ »
Having worked out in my previous post how to get a VVX working with a Wi-Fi network connection, the next obvious challenge was to go fully cordless, and that meant ditching the PoE.
Whilst browsing the UCS 5.8 release notes I couldn’t help but notice the addition of support for Wi-Fi connectivity, added to all phones in the range that possess a USB port (except the VVX1500 apparently). This is delivered via an Obihai USB dongle, the “OBiWiFi5G” – which I was able to pick up for $AUD45 at the Bays Du e. So now we have the makings of a wireless VVX…
Well, it’s only kinda wireless – it’s still tethered to power, and that hardly makes it wireless. I wondered what we could do about that… but I’ll address that in my next post.
It’s been a month since our last update to the client and our fresh Spring update [here in the southern hemisphere] brings one fix. Kb4092457 takes the Office 2013-based client from 15.0.5059.1000 to “15.0.5067.1000” (according to the KB).
The client – and get-csconnections – report it as 15.0.5065.1000.
Nothing documented.
Nothing documented.
Continue reading ‘Lync 2013 / SfB 2015 Client Update – September 2018’ »
It’s not an uncommon requirement to provide a “courtesy” phone in a public area. In a hotel it might be a “house phone”. In many deployments all the visitor does is lift the handset from its cradle and the phone autodials or “hotlines” to the required destination.