They were resolved, partly by opening ports 2196-99 on each server.
That would be why the host wasn't initially registered with the web interface.
As stated in the above post, after fixing the errors, the secondary showed up in hosts; but still had no control.
Exactly what does that mean -- "still had no control"? Could you describe what happened when you tried to create accounts on that server?
they are just now independent, with no single-sign-on; I think I read somewhere that that's no longer supported?
The new host management system is much more efficient than single sign-on, so yes, we did deprecate the SSO functionality. It still existed in the code though, and by request from one of our clients we have put it back in the UI in the latest build. (The page to add remote hosts to the master server is under Utilities, and the option to enable it on the slave servers is on the "Legacy SSO" tab of the admin settings page.) Only the basic single sign-on login page functionality is supported though; the centralized administration and centralized provisioning features were removed long ago.
When I have the time, I plan on installing Linux Control Daemon on a new server to see if I can get it working.
While the v3 launch has been a bit bumpy, this area really isn't one of the problematic ones; if everything is done correctly (meaning all ports are open, correct hostnames/IP addresses are used, all directions are followed, etc.) it should "just work". We have done a substantial number of paid installations since launch, and this part is virtually flawless every time.
I'm sure I can get it to show up in 'hosts' with the other servers; but besides the possibility of the host being available in the Host drop down when adding a new account, I have no idea what to look for to verify that it's working
1. Make sure it shows up in the Host dropdown when adding an account.
2. Select that Host and create an account on it. If the account is created, then congrats, it's working fine.
in other words, how is the control server supposed to look when it has control of another server?
With V2 it was obvious with single-sign-on having each controlled server with it's accounts listed below the master server accounts.
In v3, all of your accounts from all servers are shown in the same accounts list. You can, of course, filter by host using the controls at the top.