The device will then automatically perform a DNS query for the hostname for each domain name which may have been passed via those DHCP options.
Typically the certificate issued to the Lync Front End server is from an internal private Certificate Authority, which unfortunately means the device cannot automatically download the update without intervention.
Normally device updates are triggered after signing in to the Lync Server as described in detail in the previous article.
Attempts to use 1.0.522.x versions would always fail with As older versions of firmware may still be in use or come pre-installed on new devices then there may exist a scenario where the devices are unable to successfully sign-in to a Lync Server 2013 environment (specifically OCS 2007 RTM versions).
And because the only way to update the Lync Phone Edition firmware is by the device requesting and downloading the package from the Lync Server then this appears to be a cyclic problem.
It is important to understand that although Lync Server 2013 brings a host of new 2013-branded clients (e.g.
Windows, Mobility), the (LPE) client was not updated in the same manner.
The question then becomes, which RDS components can work with different versions and which need to be the same?
So with that in mind, here are basic guidelines for supported configurations of Remote Desktop Services in Windows Server 2016.
Windows Server 2016 removes the restriction for the number of Connection Brokers you can have in a deployment when using Remote Desktop Session Hosts (RDSH) and Remote Desktop Virtualization Hosts (RDVH) that also run Windows Server 2016.
The following table shows which versions of RDS components work with the 20 R2 versions of the Connection Broker in a highly available deployment with more than two Connection Brokers.
When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability.
Most environments include multiple versions of Windows Server - for example, you may have an existing Windows Server 2012 R2 RDS deployment but want to upgrade to Windows Server 2016 to take advantage of the new features (like support for Open GL\Open CL, Discrete Device Assignment, or Storage Spaces Direct).
This little-known behavior is hardcoded into all firmware releases.