Stephan Schwarz

A quick and dirty work around I can see would be if the executable would have 1 more location to lookup it's configuration files.

Instead of looking only in Appdata or programdata, it should first look in it's current directory.

Both for a config file, and a branding file.

This would allow users to simply create an archived file for someone else to download and extract and have a completely portable version of WaykNow with the desired settings and branding.

I have a small suggestion for enhancing the product even further.

If user A connects to user B's system in order to provide remote assistance, and would record the session I think it would be good for user B to be made aware of the session being recorded.

Could be as simple as a small dot with a description "rec" that would be gray (or not shown) until user A starts to record. Then it should either be a red dot, or pulsate. If the "notification" screen for screen sharing was already closed, it should pop up again in the corner to raise awareness as well.

While I would say verbal notification and agreement should be enough, I do think that user B should be explicitly be made aware that the session is being recorded.

Hello,

I've installed WaykDen without much of an issue (only suggestion I have is to also add the default login credentials to the regular guide and not only in he argo tunnel guide, since I couldn't find this at first).

Now I'm trying to understand how the product should be "used" from a management perspective.

I configured LDAP with our internal AD using the example string

Set-WaykDenConfig -LdapServerType ActiveDirectory -LdapUsername ldap-user@contoso.local -LdapPassword ldap-password -LdapServerUrl ldap://ipaddress -LdapUserGroup 'Domain Users'

After this, I restarted the WaykDen service.

However I'm unable to log on to the website using my AD credential

Neither UPN, samaccountname, contoso\samaccountname work.

p.s.: There is no device such as a firewall of windows firewall blocking the traffic from the WaykDen to the DC.

Hopefully these questions are easy to answer:

• Is there any more documentation in regards to setting up and troubleshooting LDAP authentication?

• On the topic of authentication, any plans for identity federation with SAML 2.0? Or RADIUS. Either of these options will make it easy to support in place multi factor authentication methods.

• If I create a local user in WaykDen, I can log on to the website with it, but immediately presented with a forbidden message, is this normal?

• I get that same forbidden message, if I change the user permission from reader to machine contributor: what are these two roles supposed to be?

• What are the Machine groups for? I for example created a goup and assigned the local normal user to it, but that user account is still not able to see anything from the dashboard.

• If I assign a computer to a machine group, it is still only listed in the top level "Machines" section. I also can't see which group a computer belongs to (I think..)?

Right now, I really don't see the use of user accounts in WaykDen. Is there anymore documentation on the product itself instead of just the GitHub stuff?

Thank you Richard, this was exactly what I was looking for!

Hello,

I was wondering, whether the actual Wayk Now client has command line parameters which can be called to launch the application?

Example:

• A parameter to start a Wayk Now session to an IP or ID, with additional optional parameters for authentication

• A parameter to start Wayk Now and directly open the bookmarks page

• If the application is already running, it should simply perform the specific task.

Hi,

It's actually the latter of the two, multiple clients connected to a single session at the same time.

We don't really use terminal servers at all.

If it is easier from a programming side, I suppose it would be suffice if only 1 connected client has control of the remote host, where another connected client would only be able to view.

I figured I'd throw this request out there. We have work a around to still achieve this, but would be nice to see it as a feature.

Hi,

I have had multiple requests regarding "concurrent remote sessions".

For example we have a few EKG systems, that are in the room with a patient. These systems, store all data locally and upload the data once the recording session has been completed. This means that the live data can only be seen on the device itself.

The medical staff wants to see the live values, right now with WaykNow only 1 person can connect to the remote system.

Sometimes however, our medical staff wants to consult with one-other and ask another colleague to also look at the data.

This scenario could be easily translated into a servicedesk scenario where a servicedesk technician asks another colleague to also connect to a remote system to both look at an issue someone has.

It would be really nice, if it would be possible to lift the restriction of only having 1 inbound connection.

Previously they used Teamviewer (which allowed this), but the way licensing works now I cannot configure a local license anymore it seems. So I want to completely phase out Teamviewer in our organization.

I would actually be fine with a feature like this to be locked behind the Enterprise version, since I am actually planning on getting that due to the on-prem Den server.