Update on the "Browse for JVM for IcedTea-Web": I found that the path /usr/lib/jvm/java-8-openjdk/jre makes it happy on all counts, including lib/rt.jar so that is probably a better path to use

If you just want your computer using Wayland to control a remote system, jnlp files still work.  Java Web Start (jnlp files) are deprecated starting with Java 11, so you have to have jdk8-openjdk and icedtea-web installed, then when joining a session choose the SystemProfiles / Default / WebStartDirect to get the jnlp file.  If you have multiple java versions installed you will have to either run "sudo archlinux-java set java-8-openjdk" to set 8 as your default, or setup icedtea-web to use the right JVM by running /usr/share/icedtea-web/bin/itweb-settings, going to JVM settings and "Browse for JVM for IcedTea-Web".  I picked /usr/lib/jvm/java-8-openjdk and when it tried to validate it found bin/java and complained that it couldn't find lib/rt.jar but worked anyway and I could open jnlp files no problem.

If you want your machine to be controlled then yes it won't work because ConnectWise doesn't support Wayland.  As I understand it the Wayland security model doesn't currently allow for that kind of remote control as a system service at all.  The ConnectWise agent still connects so you can run shell commands through the Control dashboard, but you can't see or control the remote screen.

The script won't work on Arch for a couple reasons.  First is the error you are seeing which happens because it checks for a supported package format (deb or rpm for Linux, pkg for Mac) and it doesn't properly error check if it can't find one of those.  The second is that it relies on the old init scripts instead of systemd, so even if the files got installed it wouldn't start on Arch, which is systemd only by default.

It would be great if ConnectWise added Arch and systemd support, but in the meantime if you go to my GitHub link right above your post you can find my workaround for Arch. You point it to your deb file and it will repackage it for pacman and install it with a systemd service.

No problem, I hope it helps someone out there.  It doesn't seem like it should be that hard for connectwise to default to a simple systemd unit file, and revert to init.d if someone is trying to deploy it on one of the few modern systems without systemd.

Now they just need to get full Wayland support sorted out haha

In response to https://control.product.connectwise.com/communities/1/topics/3881-arch-linux-support I created a very simple systemd unit as part of repackaging for arch.  It just copies the initrd script into the ConnectWise Control folder in opt, and the systemd unit file just calls the init script.  Definitely not a polished final product, but gets the job done as a short term workaround.  Here's a link to the repo

https://github.com/kelderek/connectwisecontrol-arch

In case it filters the URL go to github and look for me (Kelderek) and the repo is connectwisecontrol-arch. Let me know if it works for you!

I made a first pass at this here:

https://github.com/kelderek/connectwisecontrol-arch

In case it filters the URL go to github and look for me (Kelderek) and the repo is connectwisecontrol-arch.  Let me know if it works for you!

100% agree.  It is ridiculous that this hasn't been addressed. As you said, Wayland isn't even the future anymore, it is the present except for extremely conservative distros.  Ubuntu held back Wayland and defaulted to x.org for nVidia drivers for a long time, but even that now defaults to Wayland.  Support either needs to be added or connectwise should stop advertising Linux support