Cant add machines to server groups

Hi,

The proper way to register machines for unattended access is with the enrollment token, as documented here:
https://github.com/Devolutions/WaykDen-ps/blob/master/docs/deployment-automation.adoc#enrollment

The enrollment token can be used to automatically enroll (or register) a large number of machines automatically. As for the server groups once they are registered, you can either move them once they are registered (there is a default group) or you can select a group in which to enroll machines with a specific enrollment token. If you need to enroll in different groups, simply create multiple enrollment tokens, one for each machine group.

Otherwise, you can still register machines "the manual way" but it is more tedious and not suitable for automation. This requires logging in with a user that has the "Machine Contributor" role in Wayk Den from the Wayk Now application, and then clicking "register" to register for unattended access. This process can be see in the argo tunnel getting started guide (ignore the argo tunnel part, just go over the part with machine registration): https://github.com/Devolutions/WaykDen-ps/blob/master/docs/getting-started-argo.adoc

Best regards,

Thanks, that did it!!!

Quick question on the enrollment process....

I originally downloaded the .msi to my windows desktop and installed from that and then configured the client manually.
The instructions said I could use the "way-now enroll" command with the token id to register the client, but it kept failing.
I even logged of the client and deleted the machine from waykden.... but it kept failing.

Since that wasn't working... I uninstalled the client and re-installed it via Powershell per the instructions in order to get it to work.

Is that normal?

Hi,

Do you still have the logs from that machine? You can export them this way:



You can send the logs to wayk@devolutions.net, hopefully we can find a clue as to what went wrong. I don't think this is normal.

Best regards,

Hi There...

I figured out what the problem was...
It was operator error... probably shouldn't be working on this stuff so late at night... lol.
I was running the command in the command prompt instead of Powershell...

Once I ran it in Powershell, the systems register without having to reinstall the client.
SWEET!!!!

Thanks Again!!!

Hi,

I am glad that you got it working!

Best regards,