WMS Pro (paid version) can be used on-premises or public cloud.   It is a much better solution, includes support, BIOS management, reporting, Advanced software delivery policies, etc.. Free trial here [URL]  
Hello -  We have a WMS server that used to only be accessible internally, but we're testing from user's home offices.  So, before we were connecting to it with its .local DNS name, but now we've created a public DNS entry and are connecting to it that way.  We changed the address in the CCMProtocolConfig.xml file for WMS server and MQTT server.  This does work but somewhere, either in the WMS server or the thin client it's holding on to the old .local address.   For example - periodically an event will appear for devices saying: Generic Audit event received from "Hostname" - Failed to connect to WMS server [URL] Current WMS server [URL] This is ok and doesn't really break anything, but the problem is that when we try to push any applications out, they don't work, and we find this in the logs: Download url [URL] , Downloading C:\Wyse\WDA\TaskMgmt\\AdvAppPolicy\\Downloads\\Installer\Installer.msi failed : Result : ERROR_SERVER_NOT_REACHABLE We can Band-Aid this with a host file entry but would rather fix it correctly.  Does anyone know where the WMS server/TC/Both are holding on to the old hostname?  
WMS Server Name Change