Great to hear we have a guinea pig! We tested this internally, and we've had customers implement linux unattended, but they never report back.



Do an attended session on that machine that delivers the JNLP file with the Java client. This has the encryption key as an argument. You'll see it; it's the long base64 encoded string.



Elsinore.ScreenConnect.Core.jar and Elsinore.ScreenConnect.Client.jar are in the Bin directory of your installation. You'll also see them referenced in this JNLP file.



/etc/init.d is a directory. I'd create the sc.sh in there as a symbolic link to the instance at /var/lib/screenConnectGuestClient/sc.sh



http://manpages.ubuntu.c...rdy/man8/insserv.8.html

You run insserv with the script as an argument. Like this:





You know, I'm not sure what I meant by this. I think each distro may have a different way of specifying when services are supposed to run. Quite honestly, I had hoped someone who really knew linux would chime in and tell me all the things we did wrong ;)

I think you'll need to leave JAVA_HOME to be "/usr"

In the script it shows:


So it appends /bin/$javaCommand

Ok so after a couple of days we have settled on a hybrid fix that appears to be working.

We have not been able to get the daemon running consistently.

So I thought I would post here what we have done so to help anyone else that me need it.


Ubuntu 10.10


install java6 jre

$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get install sun-java6-jre

Then via firefox we connect to our SC host.

http://xx.xx.xx.xx:8040

we set up a public session to connect to.

after the initial connection and the Elsinore.ScreenConnect.Client.jnlp download we disconnect.

now we go into the firefox downloads directory and copy the Elsinore.ScreenConnect.Client.jnlp to another directory (i.e. /bin).

We then edit the Elsinore.ScreenConnect.Client.jnlp file changing two arguments

line 15 - the session identifier ( looks like <argument>bb4a62f2-bf52-4ff7-9fe6-aeccaa9b2b5f</argument>

change it to : <argument>00000000-0000-0000-0000-00000000000</argument>

also change line 18 <argument>THIS.IS.YOUR.HOSTID</argument>

change it to the Server Name so you can keep them straight <argument>SERVER.NAME</argument>

I then chmod 755 and dos2unix the the file

$ sudo chmod 755 Elsinore.ScreenConnect.Client.jnlp
$ sudo dos2unix Elsinore.ScreenConnect.Client.jnlp

Then right click the file and "execute", make sure you choose "Java 6 web start" as the application.

You will now be connected.

So now the challenge was to get it to autostart.

So what I did was write a quick bash script to run at startup.

sc2.sh

#!/bin/bash
createSC() {
/usr/bin/javaws -Xnosplash FULLPATHTO/Elsinore.ScreenConnect.Client.jnlp
if [[ $? -eq 0 ]]; then
echo Screen Connection created successfully
else
echo An error occurred creating connection
fi
}
if ps ax | grep -v grep | grep -c "FULLPATHTO/Elsinore.ScreenConnect.Client.jnlp" > /dev/null
then
echo "SC service running, everything is fine"
exit
else
echo Creating New Remote Connection
sleep 90
createSC
exit
fi


put it in the /bin directory with the .jnlp file

I then chmod 755 and dos2unix the file

$ sudo chmod 755 sc2.sh
$ sudo dos2unix sc2.sh


PLEASE NOTE: I put an 90 sec delay before it starts the java connect so the server has time to connect to the internet, if it is not connected it will fail. So there will be a delay before you see the connection dialog on the server.


Finally I put the sc2.sh in the startup session

again using Ubuntu 10.10 with Xfce interface

Applications >> Settings >> Xfce 4 Settings manager >> Session and Startup

Choose "Application Startup Tab"

Click "Add"

>> Name: "ScreenConnect"

>> Command : Browse to your "sc2.sh" file (NOT THE .JNLP FILE)

Click OK >> Close

Now reboot. 90 seconds after the desktop shows you should see the connection dialog and also see the SERVER.NAME on your Screen Connect Console under "Unattended"

Now after every reboot the system will come back up and connect to the SC Console.

So I hope this helps anyone using Linux.

Of course if someone gets the daemon piece running please lets know.

Thanks and Good Luck

Jim


EDIT: I have been able to replicate this on 6 servers so far without issue

We have quite a few customers using a variant of this solution here:
http://forum.screenconne...9_Linux-Unattended.aspx

ScreenConnect runs fine; it's just a matter of getting the startup configured correctly.