Forum Discussion
LPE Device Support
Trevor, for your LPE update issue, take a look at the SAN on your FE's certificate to make sure it has the entry of ucupdates-r2.your-domain-name.
Also, thanks for looking into the LPE's on S4B 2019. I've decided to migrate to S4B 2015 to play it safe until all of the cx600 devices have been replaced (going with Audiocodes HD445) then proceed with 2019. Im sure it'll be a bit more stable by then :)
ucupdates-r2 is only required under certain circumstances, namely when an LPE device is deployed but never signed-in with a user account. Under that scenario, the device takes the DNS Domain Name from DHCP and appends the ucupdates-r2 hostname in an attempt to access device update services so that it could be updated without a user account being logged in.
If you actually sign-in with a user account, the device strictly uses the Internal/External Web Services URL of the pool the user account is homed on. ucupdates-r2 is not deployed on either my 2019 or 2015 pools (or certs). Device update works just fine on the 2015 pool under current configuration.
Either way...I think you're in a good place to go to 2015 first and worry about 2019 later.