no they cannot..and will not. their track record is when they do this type of thing their supprt of said devices is going to stop...it may take years..but it will die. it took them two years of this behaviour for them to drop linux servers. i bet mac m-series devices are next to die.
it looks like screenconnect has no intention of doing this. the last time they took us on this kind of ride they killed the linux server. I honestly do not believe at this pint they even intend to support he m series macs at all.
we got all kinds of assurances about linux servers too..until you folks said nopers not doing it anymore..along with similar "issues" delaying progress for two plus years until you folks said nope. Given the track record...i will stay with you are preparing to move on from m-1,2,3 clients as they aren't a huge segment of the market anyway...the internal issues int his care..probably the venture capital owners now wanting to spend the money....
they could be considering dropping apple client support.
the last time you folks did this you waited two years and killed Linux server support...i am not confident in your track record here.
hell teams runs natively on linux. This is the type of answer we got a couple of years before they abandoned linux..with it stagnating for a year before they finally killed linux support. Considering that macos is bsd based and now it's not an int3l x86 platform i would not be shocked if they abandoned mac now..given it is no longer an x86 platform.
you are falling behind more..now the m2 is out and another variant will be out soon. you have had more than ample time to prepare for this. The last we saw an answer like this you abandoned linux support. Be honest with us..do you intend to actually do m1 support or is this the final nail int he coffin for apple support on SC?
It's not going to get updated to the windows version folks. Matt already pretty much stated as much on an earlier thread....
sc has said the writing is on the wlal fro Linux in another thread:
Thoughts for moving forward--
I actually think most of
it has been fixed already in a 20.2 build. It's just in a parallel
universe to our existing release pipeline, which is why it has lagged.
personally think it's a shame the Linux/Mono usage has declined to such
a degree. I thought it was neat technically we could really master
(*ducks*) both platforms in a very unique way-- what other commercial
product runs on Mono?
Our code base is in good shape and
could be moved to .NET Core without a lot of obvious work. The one
thing stopping it is our Extensions; most extensions have ASP.NET
components, and we can't easily change and break compatibility without a
lot of impact.
Y'all should probably see the writing on
the wall if you haven't already. I know that when I'm a consumer of
something, I like to feel like my business is valuable to the vendor.
And although y'all are very valuable to me personally because I like
Linux, I like arguing, I like critique of my creations, etc, I think
y'all probably have an opinion about how much you think my superiors
care about this particular enjoyment of mine. And we're sitting with
just maybe 40-50 of y'all who are looking at a $65/year renewal? To the
credit of my superiors, they have very much supported us doing the
right thing and getting y'all in a good state, but we've spent a good
$50k+ on this Linux/Mono refork, and we won't see nearly the return to
cover that, so eventually they'll probably come a-calling for resources
to be spent elsewhere. So I'd say the work on the Mono framework to get
it compatible with 20.3+ seems unlikely.
Like I said before, ConnectWise wants to do the right thing. So what's the right thing?--
There will be a 20.2 release which addresses what we perceive as the stability/compatibility issues.
You know you can move to host SC no Windows with your existing SC license, right? (including this option for completeness ;))
you're interested in moving to Cloud, let us know. I think there are
existing deals that a bunch of customers have taken advantage of here.
I'm sure if you are constructive about it, that could likely be
Thread is at the following URL:
Considering that edge is switching to the chrome codebase within the next few months...once that occurs there's no way for Linux standalone to be accessed as all the browsers will block Linux SC because it only supports tls 1.0.
Customer support service by UserEcho