logo

The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Sean  
#1 Posted : Thursday, August 7, 2014 7:57:39 PM(UTC)
Sean


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 4/16/2010(UTC)
Posts: 441
Location: Raleigh

Thanks: 5 times
Was thanked: 38 time(s) in 33 post(s)
Quote:
How can I manually stop and start the Unattended Client on a Mac?


The command to do this is as follows, where [*******] is the number following the service name. Unload will stop and load will start.

Code:
 launchctl unload /Library/LaunchAgents/screenconnect-[*******]-onlogin.plist

 launchctl load /Library/LaunchAgents/screenconnect-[*******]-onlogin.plist
ScreenConnect Team
thanks 1 user thanked Sean for this useful post.
LightAngel on 8/7/2014(UTC)

LightAngel  
#2 Posted : Tuesday, August 12, 2014 11:04:47 PM(UTC)
LightAngel


Rank: Newbie

Joined: 3/28/2014(UTC)
Posts: 4
United States

Thanks: 2 times
Thanks Sean!

This enables users to stop and start the unattended clients on Mac computers, which also forces them to reconnect to the ScreenConnect server.

This is useful when clients don't appear to be 'active' or 'connectable' in the Host area of the ScreenConnect software.

You can even create shortcuts or icons that you can double-click on to 'start' and 'stop' the unattended clients.


To create these icons / shortcuts:

Open TextEdit, open the Format menu and choose Make 'Plain Text'.

Put one of the lines of codes into the file and Save it as: filename.command

( For example: ON.command -or- OFF.command )

Opening these files will run the line(s) of code contained inside them.

You may encounter a message that says:

The file "filename.command" could not be executed because you do not have appropriate access privileges.

Go to Applications > Utilities > Terminal and run the following command:

chmod u+x /path/to/filename.command

( For example: chmod u+x /Users/lightangel/Desktop/ON.command )

This will give you 'ownership' and 'execute' abilities on these shortcuts, making them work again!


coriron1  
#3 Posted : Tuesday, April 14, 2015 10:09:46 AM(UTC)
coriron1


Rank: Member

Joined: 12/2/2014(UTC)
Posts: 16
United Kingdom

Originally Posted by: Sean Go to Quoted Post
Quote:
How can I manually stop and start the Unattended Client on a Mac?


The command to do this is as follows, where [*******] is the number following the service name. Unload will stop and load will start.

Code:
 launchctl unload /Library/LaunchAgents/screenconnect-[*******]-onlogin.plist

 launchctl load /Library/LaunchAgents/screenconnect-[*******]-onlogin.plist


Hi, i've just tried this on my OSX client, and i get the reply "nothing found to load". Do you have any suggestions?
Scott  
#4 Posted : Tuesday, April 14, 2015 12:45:07 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
if you run the following command, what is the output?

ls -alh /Library/LaunchAgents/screen*
ScreenConnect Team
expphoto  
#5 Posted : Friday, May 8, 2015 5:03:20 PM(UTC)
expphoto


Rank: Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 1/16/2015(UTC)
Posts: 28
United States
Location: Arizona

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
Originally Posted by: Scott Go to Quoted Post
if you run the following command, what is the output?

ls -alh /Library/LaunchAgents/screen*


I tried this and I get :

-rw-r--r-- 1 root wheel 457B Dec 31 1969 /Library/LaunchAgents/screenconnect-9b05f53f7c397980-onlogin.plist
-rw-r--r-- 1 root wheel 465B Dec 31 1969 /Library/LaunchAgents/screenconnect-9b05f53f7c397980-prelogin.plist

I also tried unloading both, and got nothing to load.
Scott  
#6 Posted : Monday, May 11, 2015 2:37:08 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
What is the exact command you used to unload/load it? Can you post your command and the exact output?
ScreenConnect Team
rgreen83  
#7 Posted : Friday, October 23, 2015 4:59:49 PM(UTC)
rgreen83


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 2/16/2015(UTC)
Posts: 69
United States
Location: Missouri

Thanks: 6 times
Was thanked: 3 time(s) in 3 post(s)
Should this still work? On 5.5 SC on 10.11 or 10.10 osx these unload/load commands dont give errors but also don't seem to restart the agent either.
Scott  
#8 Posted : Monday, October 26, 2015 2:57:52 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
So if you issue the unload the icon is still in the system bar?

What happens if you grep for the screenconnect client process? It would be something similar to:

Code:

ps aux | grep "screenconnect*"
ScreenConnect Team
rgreen83  
#9 Posted : Monday, October 26, 2015 11:04:23 PM(UTC)
rgreen83


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 2/16/2015(UTC)
Posts: 69
United States
Location: Missouri

Thanks: 6 times
Was thanked: 3 time(s) in 3 post(s)
My apologies it seems I didn't give all the info. I tested and this does still work if I just want to cycle the program when it is running already. I am trying to get the process running again after performing an "un-end" procedure for accidentally ended sessions on osx. Rebooting does bring the agent back to life but the load operation alone does not, and the grep results appear the same after the session is ended or if it is unloaded using the above command. On a windows box I can simply restart the service to bring it back to life.

If this is the wrong thread I can move over to the un-end session extension thread, I just thought this unload/load operation would be the equivalent to restarting the service on a windows machine.

Thanks
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.