@jaredbusch said in How to run JNLP files on Fedora Cinnamon with Firefox:

@black3dynamite said in How to run JNLP files on Fedora Cinnamon with Firefox:

In Chrome, selecting "Always Open Files of This Type" doesn't work?

You are not allowed to select that for JNLP files in Chrome.

Google and Oracle bickering takes a toll on end users 😞

I would like to add few tips that I found useful (few of them I learned during support session with screenconnect team).

I have these session groups created:

Computers categorized based on their hostname start. We have different standards for server and endpoints.

GuestMachineName LIKE 'SRV*'

Filters all servers starting with SRV as a single group

HostConnectedCount > 0

This helps me to manage who is connected, used in situations when I hit a license limit or want to know who specifically connected to which session

GuestClientVersion < '6.5' AND GuestConnectedCount > 0

This shows the machines that are online and have an outdated client version. I just need to issue a reinstall command for those outdated agents.

@gjacobse said in Korora Complaint: Screen Connect:

Guess this is my first complaint about running Korora as a Daily PC.

Screenconnect

Seems that every session started for control it has to redownload the application to start IceWeasel. Also, the SC session windows is totally different than under Windows.

0_1499694609540_Screenshot from 2017-07-10 09-43-27.png

That's not a complaint of Korora, but of ScreenConnect. Why did they make it different on Java? No idea.

Updated the web.config for my ScreenConnect and now all is right in the world.

@JaredBusch said in Looking for how-to on setting up a proxy:

server {
client_max_body_size 40M;
listen 80;
server_name support.bundystl.com;
rewrite ^ https://$server_name$request_uri? permanent;
}

Yep, got all that done and it's working well. What I was referring to was redirecting traffic to HTTPS. Essentially this is the part of the file I was missing...

server { client_max_body_size 40M; listen 80; server_name support.bundystl.com; rewrite ^ https://$server_name$request_uri? permanent; }

I just started getting this the other day after updating to 6.1/updating the access app on my machine. Very annoying. Who on earth thought this was something that was needed?

Little follow up to this as SC on CentOS was discussed in abother thread.. DB size is still small.

[root@bnasc ~]# ls -l /opt/screenconnect/App_Data/Session.db -rw-r--r--. 1 root root 46764032 Jan 26 12:30 /opt/screenconnect/App_Data/Session.db

@scottalanmiller said in ScreenConnect 6.1 released:

@dafyre said in ScreenConnect 6.1 released:

@scottalanmiller said in ScreenConnect 6.1 released:

@gjacobse said in ScreenConnect 6.1 released:

@gjacobse said in ScreenConnect 6.1 released:

Updating systems - NTG done, and within 5min of update, CPU is at or less then 10%

Tagging @scottalanmiller for his experience on the system

I'm in Italy on a connection that goes down every 30 minutes because of a dead router. No way for me to have useful input to the latency of the US hosted system.

Can't contact the home owner?

And tell them that their Linksys is crap? What'll they do. Fly in from Rome with one?

You should start a revolution on the island with Ubiquiti equipment.

Yeah me for posting shit always.. Just needed this again.

Saw the error and I was like.. hmm I posted about this.

e73ed3df-73d6-4e5b-a0b5-9f55aabbde79-image.png

And it is my ERL in the colo. Not sure why yet, but it is rerouting the connection to the default port forward rule. I tried logging in with my normal admin credentials and it worked.

0_1485734891415_upload-a620752c-2416-4b4c-afc7-e19afd71aaeb

actually - I just found this page, so I think I'll sit here a spell and do some reading.

https://help.screenconnect.com/Category:Extensions

It's part of the Screen Connect system itself

Any lockups since the fix?

@jaredbusch said in ScreenConnect High CPU Usage:

@scottalanmiller said in ScreenConnect High CPU Usage:

Have another system doing this this week. Been about eight hours so far. We are thinking that it is just doing the database rebuild and compression work. But it is insane how much CPU gets used for this.

Do you not have it doing this on a regular schedule?

Not my system, it was moved to a different server and had to be rebuilt.

@scottalanmiller said in Google Chrome and ScreenConnect:

@gjacobse said in Google Chrome and ScreenConnect:

@JaredBusch said in Google Chrome and ScreenConnect:

I use chrome all day everyday. Problem is yours.

I wonder if it's the Win10 build and subsequent Win 10AU.

Possible but I suspect that Jared is on Win 10.

Windows 10 with AU even.
0_1473169810893_upload-6c80d9da-7390-48dc-b1a1-45bf2cf1986f

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

Now that's really weird.

is that 1703? What is the last cumulative update you have installed?

That one is current. Image was put on last week and then updates ran.

@Breffni-Potter said:

@JaredBusch said:

I don't care if a company gets bought by another because it is a good product and successful.

Connectwise, Their main product seems to be getting more and more unhappy users as time goes on. Even on the marketing "MSP" sites. People do not like the product.

http://www.mspcomparison.com/home/917-psa/34-connectwise-msp.html

Now when something with such a bad image, buys a product you love, would you not be worried?

I do not call a few bad reviews a bad image. happy users do not post as many reviews as pissed off users. Also note the timestamps there.

Now, I will not argue and say they are good, because I do not know that. But i have not seen bad press regarding their services, is all I am saying.

@wrx7m said:

So Chrome allows you to join and save the default application to open the session. Firefox still asks for the exe every time, save run, etc. I guess I will be using Chrome for screenconnect. Thanks for the help, Jared.

As, I showed above, I did it in FireFox also.

Nice. We need to upgrade shortly.