I found all the missing settings. Documentation was all over the map, and it took some detective work to get it all straightened out.
For future reference, yes I needed to open up the ports in my ERAS. Using the stock Windows Firewall setting tool wasn't enough. I had to manually create my own rules in the "Advanced" setup.
Going to the Client workstation I had to enter the Update Server using the full name including port number.
Then under "Setup" and "Advanced Tools" I had to find "Remote Administration" and enter the server name but without http or port number. I see no reason to have to do both as one relies on the other they should have been on the same screen. For a rather "stock" setup, burying something like this under "advanced tools" isn't the way I would have done it. Ease of use is one of my priorities, and so far this isn't even close.
Almost there... I then needed to go to Windows Firewall on each client and add the anti-virus program to that list. Not a problem, but most other programs that need firewall access have a facility for doing it automatically. Again, I shouldn't have had to do this manually.
Once ALL these steps were done, finally things started showing up in my Admin Console. My last step was to go to my server and each workstation and turn off the "sleep" mode of the NIC so it could receive updates in a timely fashion.
I'm giving up on the "push install" idea. I have to sit at each desk anyway to make all these manual changes before any push would have any hope of working. As long as I'm already there and interrupted their routine, I might as well do the job myself.
I think a single tutorial that outlined these steps would have saved me two weeks of frustration.
All in all, I think the product works great. I'm just disappointed in all the hassles in getting it set up, taking me two weeks and EIGHT messages on this forum before I got the first helpful answer and that came from a member, not ESET.