You need to restart the PC. This is a common issue with Hosts being installed on Windows Server. Yes, the Host can run without restarting the PC, but sometimes restart is still required, especially on Windows Server.
Regarding this tooltip. We are going to remove it altogether in the upcoming update, because the tooltip is redundant. Now the Details view in the Viewer has all the necessary columns including HostName.
A question: Are you updating an existing installation with your custom Host package, or is it a new installation on that PC? That is, no Host was previously installed.
But my ID-Server doesn't see any new devices. Ok, i stopped the service and ran the exe by hand to check its settings. All settings are reverted to default - this means, standard ID-Server is used, no saved passwords etc...
You can simply run Settings for Host from the Windows Start menu.
1. I can not use your Example 1 above, though our example used two users and two computers, in fact it would we two users (or more) and ten computers or more. To change each host and remove/change one user from each host is a major pain in the butt as you know... :-)
Yes, that is why we came up with option 2 (auth server) in version 6.5 :) Albeit it requires that you use a self-hosted server, i.e. this option is not available if you stick with our public server infrastructure.
-When on Comp 1 and User 1 has full rights on only Comp 2, User 1 can not see any address book entries nor Comp 2. So this prevents (for me anyway) any access including View to the address book. Yet, if I add the User 1 to the "Parent" Address book with No Rights, and No rights to any child Comp's (Shows User 1 Inherited yet no check marks for any rights), User 1 can now see the address book and even control Comp1-4. Again, User 1 has No Rights yet now has full control. This seems broken to me?
I'm not sure I can understand the example without actually looking at your settings, so yes - perhaps we could use a remote session. Let me know if you can - just end an email to firstname.lastname@example.org or PM through the forum.
When you set user 2 to no access to computer B you effectively only tell the program not to show the computer B record in user 2 address book. However, they can still access the remote Host (computer B) if they know access credentials for that Host.
In other words, address book access rights and Host access rights are two different independent things. But you can combine them (see option 2 below).
There are two options to resolve that:
1) Change security settings on the Host. For example, create user accounts on each Host and then if you need to prevent a certain user from accessing a Host just disable their account on that specific Host.
2) Use the "authorization server" role of the RU Server. This is described here (see "Authorization role" section) and we'll also soon update our documentation with detailed instructions on how to set up custom server security as we call it.
With option two properly configured your users will only have to sign in their Viewer to be able to access the Hosts. The advantage of using auth server option is that you can centrally manage Host permissions and change them in one place instead of having to change security permissions on each Host (as is with option 1).
Sorry for the lack of documentation on setting up auth server, it will be available very soon and appear in this chapter. Feel free to ask any questions you might have.
If you can't connect to the 2nd Host regardless of the sleep or login status, then the issue has nothing to do with sleep or being logged in. This looks like a general connection issue. Here are two solution guides that may help you troubleshoot the issue depending on whether it's direct or Internet-ID connection: