New WDM Installation and P25 Setup

I believe I've exhausted my searches, so hopefully this isn't a duplicate.  I've got a brand new Wyse Device Manager 5.7.2 installation for a POC and testing environment we're putting together.  We've tested the Wyse 3010 and 5030 devices and have settled on the 5030 / P25 units, based on our testing.  

In order to support our dreams of Windows 10 VDI, I installed a new VMware Horizon View 6.2.4 environment, and when I pointed the zeroes to it I got an error.  A little troubleshooting and research led me to the Teradici page, where it listed a 5.5.1 firmware update that was necessary for it to work.  I downloaded the updated firmware, created the image packages based on the Admin guides, deployed the certificate based on the Admin guides, and found that the certificate package worked fine - it deploys the certificate, and reports success.  However, the image package downloads, the P25 reboots, the firmware is still 4.8, and WDM never reports success or failure.  The event logs on the P25 show it downloads, I can verify the reboot physically (watching the one on my desk) happens, but for some reason the device doesn't update.

As a test, I updated one of the P25 devices via the web interface, rebooted, and verified the firmware updated.  When I try to push anything out after that, in WDM->Devices-Device Details->Logs, I get "REQUEST_FAILED" and nothing else.  There is nothing in the device event logs, making me believe that there's some screwy with my configuration, but I haven't been able to figure out what.  I suspect everything is related, but in all honesty, I just don't know.

As a note, the repository is working, it checks out okay.  The WDM information is provided by DNS SRV/TXT records, and that's been validated.  If I plug in a brand new device, it shows up in WDM very quickly.  As another note, if I run the DNS/DHCP lookup tool, methods 1 and 2 both fail from the server, which I don't think is normal, but since the devices appear to function, I'm not sure what that would indicate.

So, my questions are:

1) Am I missing some critical piece?  I've gone through the Admin guides, used Google, and talked briefly with Teradici support, to no avail.  Especially on the REQUEST_FAILED piece, I believe it to be on the WDM side.

2) Are there logs somewhere that I'm not seeing that would give more insight into what the WDM console is doing?  I can see errors, but I haven't been able to identify any detailed logs that would show me where some of these things are coming from.

I'm pleased with the majority of how everything is going, but unless I can figure out how to successfully manage the ThreadX 5 pieces, and why the deployed firmware isn't actually updating the device as expected, I can't really move forward.  Since it's all in an evaluation phase, I'm trying to identify issues and resolve them to keep testing going while we evaluate the software management components we're going to be using.  

Any advice on this would be greatly appreciated.  Sorry for the long, drawn-out e-mail, but hopefully the details provided can lead someone to point me in the right direction.

Thanks.