Just when I thought February was busy enough, I am now speaking at the Nordic Infrastructure Conference – NICconf in Oslo on Friday 3rd February too. Looking forward to representing Pexip here at this establish industry conference. Full agenda for the day is here and my session details are here. Happy new year all, I just […]
Updated: Speaking Engagements February 2017 with Pexip Read More »
Just in case you thought would it work or would it not, of course it does. In the below image, I am using Windows Server 2016 Hyper-V Standard Edition with GUI. Pexip Infinity will also run happily on Hyper-V Server (bare metal) too. I am using the Hyper-V role on the standard edition server.
Pexip Infinity with Skype for Business Video Based Screen Sharing (VbSS) With the forthcoming release of version 14, VbSS will be available in point to point calls from the Skype for Business 2016 client to a VTC. This is something difficult to explain so I’ve put together a short video below. In essence, today with
Pexip Infinity with Skype for Business Video Based Screen Sharing (VbSS) Read More »
So there is lots going on in this blog post. Pexip Infinity, Logitech SmartDock Skype Room System, Microsoft Exchange, Polycom VTC The Background Let’s talk around what I am doing before diving into the blog post. Traditionally, enterprises could have the following components in their video network and these were typically based on dedicated hardware
Pexip Infinity, Logitech SmartDock Skype Room System, Microsoft Exchange, Polycom VTC Read More »
I was setting up a new Surface Hub & SRS accounts on our Office 365 tenant and it was failing at creating the Exchange account. No reason why. Turns out password policy was the issue, so make sure you use a complex pa$$w0rd123 or something, depending on your tenant settings. Also to get the
Using PowerShell Scripts for setting up Microsoft Surface Hub/SRS Read More »
Whilst setting up a new server for Skype for Business (I know it’s not supported but want to test it out), the usual Add-WindowsFeature in PowerShell does not work with Server 2016. You have to use the Install-WindowsFeature instead to add in all the pre-reqs that you need. The other thing I noticed is that
