I was able to perform an upgrade of my Horizon environment from 7.5.1 to 7.5.2 . Hope this will fix the problem with Windows 10 v1809. I'll report the result by tomorrow.
The 7.5.2 release notes lists the problem as resolved:
When you say horizon admin, i'm not sure what you mean. Is that from the web browser admin interface? For this setting, i used ADSI edit.
I upgraded to 7.7 on one of my connection servers and that completely disabled the ability of tera 1 zero clients connecting. I haven't had the time to try 7.6, or 7.8 connection servers. But the work around to allowing tera1 clients to view connection servers have been working for me up to 7.5.1. So i'm stuck right now until we get money to replace the hundreds of tera1 zero clients.
Upgrading the Connection Server to 7.5.2 solve the problem with "agent unreachable" on Windows 10 v1809!
CS=7.5.1 with Horizon agent 7.5.2 = not working
CS=7.5.2 with Horizon agent 7.5.2 = working
You add the entry on ADSI, thats right.
I mean, when you edit the Pool and change something like "Max number of client", the entry on the ADSI DB for that pool is gone. The issue with the unavailable machine is back.
I made also tests.
CS=7.5.1 with Horizon agent 7.5.1 = not working
CS=7.8.0 with Horizon agent 7.5.1 = working
Wow - thank you everyone. Looks like they're up to 7.8 now. Will give it a try.
I got this response from support today.
As per the development team, upgrade of connection server to 7.5.1 and higher will fix the issue. It is not an issue from agent end and hence even after trying different version of agent, the issue still persist.
Please refer to release notes of View 7.5.2 https://docs.vmware.com/en/VMware-Horizon-7/7.5.2/rn/horizon-752-view-release-notes.html#resolvedissues
As per release notes: 2289040: Automated desktop pools created on Windows 10 1809 go into the Agent Unreachable state.
I haven't tested this. I may try. I would rather install the latest but i tried that and my tera 1 clients could not connect.