Conrad Sallian's community posts


User access control

Conrad, Support (Posts: 3074)
Feb 26, 2017 10:35:18 pm EST
Thank you Ross! We'll do our best to publish the relevant tutorials and concept explanations as soon as possible to ease the adoption/migration process for new users.

User access control

Conrad, Support (Posts: 3074)
Feb 26, 2017 7:59:40 pm EST
Hello Ross,

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 support@remote-utilities.com or PM through the forum.

Thanks.

User access control

Conrad, Support (Posts: 3074)
Feb 26, 2017 2:40:43 pm EST
Hello Ross,

Thank you for your message.

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.

Thanks.

Connection problem when a computer entering into sleep mode and reopen it

Conrad, Support (Posts: 3074)
Feb 24, 2017 12:06:08 am EST
Hello Vasilis,

Thank you for your message.

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:

Direct connection not working
Internet ID connection not working

Hope that helps.

Dropdown boxes not opening

Conrad, Support (Posts: 3074)
Feb 22, 2017 7:56:11 pm EST
Hello Michael,

Yes, you need to enable "Capture alpha blending windows". Please, refer to this article.

Thank you, Benny, for your answer.

New to Remote Utilities coming from LogMeIn

Conrad, Support (Posts: 3074)
Feb 22, 2017 3:16:44 pm EST
Hello Michael,

Thank you for your message.

Does Remote Utilities allow me to log in anywhere & get to the PC that are installed with Remote Utilities?

You mean anywhere on the Internet? Yes, of course. You can use the "Internet ID" connection type with either a persistent remote module or an ad hoc agent.

Can I give other users logins so that they can log into their PCs?

Unlike  [censored] Remote Utilities is stand-alone software. There is no web account or a hosted web panel. Instead you install the software on both ends of a connection (on the remote side you can optionally use a run-only Agent) . You can enable a simple single-password access to a remote PC, or create separate users with their own permissions.

Hope that helps. Let me know if you have other questions.

Computer changes to Logged Off

Conrad, Support (Posts: 3074)
Feb 17, 2017 10:25:07 am EST
Hi Scott,

You are welcome. Sorry about the message being a bit misleading. Actually, we are planning to improve the update process a bit in the upcoming release and make it more comprehensible.

Computer changes to Logged Off

Conrad, Support (Posts: 3074)
Feb 16, 2017 5:58:59 pm EST
Hello Scott,

Thank you for your message.

Probably, this is about Windows update issue described here.

I highly recommend that you update to version 6.5.0.8. Both your Viewer and Hosts. Refer to this tutorial to update.

If you still have issues after the update, let me know.

Remote Utilites Seems to connect to wrong port

Conrad, Support (Posts: 3074)
Feb 16, 2017 5:37:44 pm EST
Hello Ryan,

Are you trying to connect from the same network or from different networks? If the former, try to connect to a different network (if you are on Wi Fi, switch to 3G/LTE, or vice versa) and try the same.

Also, could you send a screenshot of your mobile app's server settings window? You can send a screenshot via a private message or to support@remote-utilities.com

Looking forward to your reply.

Remote Utilites Seems to connect to wrong port

Conrad, Support (Posts: 3074)
Feb 15, 2017 7:20:21 pm EST
Hello Ryan,

You need to remove http:// part.