In a classic case of skim reading the documentation we had trouble publishing a Skype for Business environment externally using a Microsoft Web Application Proxy (WAP). This was mainly impacting the Skype for Business mobile client which was failing to log on.
You could still access all of the standard web sites through a browser such as dialin and meet though.
This happened due to a missed step when setting up the WAP. If the internal and external URLs are different, you need to disable the translation of URLs in the request headers. Use the following powershell command on the WAP server.
$Rule = (Get-WebApplicationProxyApplication -Name "Insert Rule Name to Modify").ID
Set-WebApplicationProxyApplication –ID $Rule –DisableTranslateUrlInRequestHeaders:$True
Once completed reload the mobile client and it should connect without issues.
There are numerous tools that can be used for migrating servers between domains but what happens when you have invested…
You may experience issues resulting in mail failing to be delivered to internal users. This may be difficult to detect…
.Net Framework 3.5 is getting old now and really shouldn't be installed unless it's required but if you do need…
Microsoft have done a good job making the patching process for Skype for Business as simple as possible but over…
If you deploy a new VMM bare metal build environment you may face an issue where the deployment fails with…
Public Folders don't seem to have the usage that they used to so it's been a while since we worked…