SharePoint Stuff

Author Archive

Luke Smith

I’ve been working with Microsoft Technologies for over 20 years, my main focus now being Microsoft Online Services. I manage the Cloud Services at ElysianIT Limited and as a P-SELLER at Microsoft. I have worked with many organisations from SMC to Enterprise. I’ve been working with Microsoft Technologies since DOS 5.0, to date I have been working on Microsoft’s latest cloud technology Windows Azure, Windows 10 Office 365 and Microsoft SharePoint

UDP and TCP port tester / Skype for Business Testing

Written by Luke Smith. Posted in Microsoft

Recently I have been working with a customer who has Skype for Business Online (SfB) part of Office 365. The customer is successfully using the Skype for Business client (Windows\mac) and is extending the use of SfB to their meeting rooms using the Polycom RealPresence Trio 8800 (UC Software version:

The Polycom fails to connect to SfB on the corporate network, however works from a home network or guest WiFi.

Different to the SfB client (works over TCP port 443) the Polycom requires UDP outbound to Office 365 this is used for accessing a time server (NTP – UDP port 123) and Lync Edge services (SIP\A&V range of ports 5060\61, 3478\81, 50,000\40)

Using the PowerShell script porttest.ps1 you can test the outbound UDP ports to SfB:

Test-Port -comp -port 123 -UDPtimeout 10000
Test-Port -comp -port 3478 -UDPtimeout 10000
Test-Port -comp -port 50019 -UDPtimeout 10000
Test-Port -comp -port 5060 -UDPtimeout 10000
Test-Port -comp -port 5061 -UDPtimeout 10000

Failed Output:

Server :
Port : 123
TypePort : UDP
Open : False
Notes : Unable to verify if port is open or if host is unavailable.

Server :
Port : 3478
TypePort : TCP
Open : False
Notes : Connection to Port Timed Out

Server :
Port : 50019
TypePort : TCP
Open : False
Notes : Connection to Port Timed Out

Server :
Port : 5060
TypePort : TCP
Open : False
Notes : Connection to Port Timed Out

Server :
Port : 5061
TypePort : TCP
Open : False
Notes : Connection to Port Timed Out


Allow UDP outbound from the firewall to Office 365. more information here:
Polycom Ports
Office 365 Ports and URLs
Skype Port Changes

Azure AD DS Hybrid with Azure AD and Intune MDM Q&A

Written by Luke Smith. Posted in Microsoft

Q1: Why can’t I “factory reset” my Windows 10 device even though it’s listed in Intune under “Azure AD Devices”, however the device is not listed in All Devices
A1: Azure AD Join devices don’t allow you to factory reset. Your device needs to be enrolled with Intune MDM before the device can be “factor reset”. To enable Intune MDM run though the following
1. Enable Intune MDM integration with Azure AD:
2. License user for EMS (AD Premium and Intune required):
3. Device Enrolment:
4. To force intune MDM enrolment you can install the company portal app from the Microsoft Store:
NB: if joining windows AD DS and Azure AD see Q3:

Q2: Can I factory reset a Windows 10 device which is Windows AD DS Joined, Azure AD Joined and Intune MDM Managed
A2: Yes, to configure please see Q3

Q3: can I automatically enrol a windows 10 windows AD DS joined device into MDM and Azure AD
A3; Yes, however you need to be using build 1709 or above, for more information please see : and

Q4: Is it possible to add the BitLocker Protector key to AzureAD? even if you enabled BitLocker before the device was Azure AD Join?
A4: Yes, the following PowerShell will need to be executed:

Add-BitLockerKeyProtector -MountPoint “C:” -RecoveryPasswordProtector
$BLV = Get-BitLockerVolume -MountPoint “C:”
BackupToAAD-BitLockerKeyProtector -MountPoint “C:” -KeyProtectorId $BLV.KeyProtector[1].KeyProtectorId

Further information:

Intune make sure the DNS CNAMEs are created:
Intune Factory reset\Remove company data descriptions:
Intune Non-windows updates:
Intune device compliance policies:
BitLocker Management: