Remotely control a Mac
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
What does Apple have that any business would want in the other direction, though?
Please answer your own question - as a person who's never used a mac (ok well not since the Macintosh) I have no clue.
-
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Just use the open source ones. Why use a commercial VNC variant?
-
@Dashrender said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
What does Apple have that any business would want in the other direction, though?
Please answer your own question - as a person who's never used a mac (ok well not since the Macintosh) I have no clue.
So Apple has nothing we'd want. what's he looking for, then?
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
What does Apple have that any business would want in the other direction, though?
That's a good question, to which I really don't have an answer. I guess the only one I can think of is OSX Server? I mean licenses for VNC are cheap, I just don't want to cough up any money for something I might be able to find for free.
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Just use the open source ones. Why use a commercial VNC variant?
Which open source ones have you used that are any good? Not doing much so very limited functionality is ok.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
What does Apple have that any business would want in the other direction, though?
That's a good question, to which I really don't have an answer. I guess the only one I can think of is OSX Server? I mean licenses for VNC are cheap, I just don't want to cough up any money for something I might be able to find for free.
VNC is free and has been since the 1990s.
-
-
-
@scottalanmiller said in Remotely control a Mac:
I made the mistake of associating VNC with RealVNC.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
I made the mistake of associating VNC with RealVNC.
Oh, yeah that's just one of many VNC vendors. They came along long after VNC was already everywhere. Mac OSX and Linux have VNC baked in and totally free. RealVNC is a commercial, supported VNC derivative primarily for Windows which is the only platform without a native VNC included with it.
Why are you not using the built in VNC of the Mac? What's making that not a good option?
-
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
I made the mistake of associating VNC with RealVNC.
Oh, yeah that's just one of many VNC vendors. They came along long after VNC was already everywhere. Mac OSX and Linux have VNC baked in and totally free. RealVNC is a commercial, supported VNC derivative primarily for Windows which is the only platform without a native VNC included with it.
Why are you not using the built in VNC of the Mac? What's making that not a good option?
I saw you can enable screen sharing and use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
-
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
I made the mistake of associating VNC with RealVNC.
Oh, yeah that's just one of many VNC vendors. They came along long after VNC was already everywhere. Mac OSX and Linux have VNC baked in and totally free. RealVNC is a commercial, supported VNC derivative primarily for Windows which is the only platform without a native VNC included with it.
Why are you not using the built in VNC of the Mac? What's making that not a good option?
I saw you can enable screen sharing and use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
VNC is VNC. The VNC server built into the Mac will work with any VNC client anywhere.
-
@BBigford said in Remotely control a Mac:
use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
Why do you need a client? Same question as with the server. Mac has everything that you need included. What's the purpose of replacing the built in and supported VNC client with a third party one?
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
Why do you need a client? Same question as with the server. Mac has everything that you need included. What's the purpose of replacing the built in and supported VNC client with a third party one?
I'm trying to remotely control a Mac with Windows. Microsoft's RDP client from the App Store didn't seem to work. Even after enabling screen sharing on the Mac, I couldn't use Microsoft RDC from my Windows workstation. But after downloading TightVNC, I could use that to control the Mac after enabling screen sharing.
-
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
Oh, so the issue is that you want Windows to have the VNC protocol handled natively. That's a Windows failing, not a Mac one. It's Windows lacking the client to connect to EVERYTHING that isn't Windows.
Macs come with the server, client AND the client for attaching to Windows, too. Apple actually does everything right here, it is Windows alone that is lacking.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
Why do you need a client? Same question as with the server. Mac has everything that you need included. What's the purpose of replacing the built in and supported VNC client with a third party one?
I'm trying to remotely control a Mac with Windows. Microsoft's RDP client from the App Store didn't seem to work. Even after enabling screen sharing on the Mac, I couldn't use Microsoft RDC from my Windows workstation. But after downloading TightVNC, I could use that to control the Mac after enabling screen sharing.
Right, because an RDP client talks to RDP servers, not to VNC servers. Enabling VNC on the Mac would not be expected to make an RDP client see it.
-
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Which ones are you referring too? Most VNC is free not just free for personal use..
I'm saying why does it have to me the native Mac one? Tight VNC etc are open source (not sure if they have a Mac version) but I'm sure there are ones for mac
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
Oh, so the issue is that you want Windows to have the VNC protocol handled natively. That's a Windows failing, not a Mac one. It's Windows lacking the client to connect to EVERYTHING that isn't Windows.
Macs come with the server, client AND the client for attaching to Windows, too. Apple actually does everything right here, it is Windows alone that is lacking.
Now I see where you're talking about the failing... You can connect from a Mac with RDC because it knows how to handle a Windows PC. But you can't connect with RDC to a Mac because Microsoft's RDP program doesn't know how to handle an Apple PC.
Now I see.
