After the Security Update 2016-002, I am unable to VNC into any Mac Machine that was updated.
Error: The user account you selected isn't available
We have same problem here.
After this last updates, we can't connect to mac through VNC anymore.
We suspect the problem started after the "Remote Desktop Client Update" and before the "Update 2016-002".
😊 I do not have the Security Update 2016-002 installed. 😊
Thanks for the heads up. I better backup my machine before doing the update.
I'm remoted to my mac running 10.10.5. I found the apple solution too slow for my needs. I use both the client and server software from realvnc. The client is free. The server is free for a month. Could get you going while you sort out the problem.
I have 2 machines:
One at 10.10.5 (Yosemite) started having the issue this morning (or earlier since I haven't vnc'd to it for days)
The other one at 10.11.4 (El Capitan) works fine.
Yes it is with Yosemite, not El Capitan. Also I can use any 3rd Party VNC Server/Client (RealVNC, TightVNC, etc.) and they work. These updates broke the native Mac VNC function. The update included Security Update 2016-002, and Remote Desktop update. Since they were updated together, and I did not want to jack up another one of my Macs, I did not go back and try to update them separately to see if the Remote Desktop update broke it, or the Security Update broke it. I am leaning more towards the Remote Desktop update.
Thanks everyone for your reply, I was really just checking to see if anyone else was having to issue, and to warn anybody that have not applied the updates, that you may want to hold off.
Happened to me today, after installing Safari 9.1, iTunes 12.3.3 and Remote Desktop Client Update 3.8.5.
I see the Security Update 2016-002 waiting, so I would assume it was the RDC update that broke things.
I've updated & realvnc is still working.
I have a MacMini with Yosemite hooked up to my TV. It has the "Remote Desktop Update" installed but NOT "the 2016-002 Security Update". Both Chicken of the Sea and RealVNC fail with "The user account you selected isn't available".
I am still able to connect to it via "Share Screen..." once I have a remote volume mounted. It seems to be a pain and a half trying to get "write control" using this method without having a mouse hooked up to the Mini which kind of defeats the purpose.
I also am deeply screwed. Thank god I got taxes out of the way, first. But my worklife is crushed.
I have iMac 27 inch, circa 2012, didn't update to El Capitan, as other software was not compatible.
Tried to download and install updates starting 3/20, and multiple times on 3/21, after reboot. It hangs every time,
and now still compromised. Spinning ball of death mid install. Now spinning ball on every cursor click
Have used Macs since 1989. Am working on MacBook Pro, to try to salvage issues. But afraid to do more Yosemite updates
to avoid total disaster
rccharles wrote:
I've updated & realvnc is still working.
I am having the same issue. I am actually on the phone with APPLE ENTERPRISE support and am getting the run around with them saying that the update should not have affected VNC connection.
rccharles,
If you go into Sharing -> "Remote Management" -> "Computer Settings...", did you have "VNC viewers may control screen with password" ticked and filled in?
yes
I'm able to SSH into my mini and by running this command
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -privs -all -allowAccessFor -allUsers -clientopts -vnclegacy no -restart -agent -console -menu
(understand all the options of this command before you run it, as it gives wide permissions!) I was able to remote terminal with RealVNC.
Chicken of the Sea was using the legacy VNC to connect and that seems to be what is now borked by the update.
You need to turn off apple's vnc to use realvnc server.
Here are my setting.
Please note:
-- I am running realvnc server and realvnc client to improve vnc performance.
-- I'm running on a home network behind two routers. I do not do any port forwarding on my routers.
-- in security and privacy, I turned off the firewall. There is a way of opening the ports. I did this at one time.
-- I've turned off encryption on the server.
-- I've turned off authentication on the server. There is an option to save your password on the client. I was doing this.
If you are using a 3rd party RealVNC server and not the built in "Remote Management" feature, then your "works for me" isn't really relevant! 😁
But using the kickstart command I posted above does allow me to use the RealVNC viewer with the OSX built-in "Remote Management" process, even after the borked update.
I've tried to make it clear that I'm using realvnc. I'm offering it as a work-around.
It's great that you figured out how to run Apple's vnc from the command line.
R
Mac VNC not working after Security Update 2016-002
