Q: How can I get this version back on my computers?

yup, same issue, just upgraded one of my machines today and can't connect to it any longer...  really ***** for me as that machine is remote at a server farm with no easy access for me

uodate your remote desktop app or update your remote desktop clients through software-update in the "apple menu"

of course this was the very first thing I tried... all machines are running 3.6 470.93

Is only Remote Desktop.app upgraded to 3.6 or are the clients upgraded to 3.6 as well? 

Assuming you upgraded the clients to 3.6 then do the following to see if the screen sharing server process is enabled to run:

1. ssh to an affected client

2. Execute:  sudo launchctl list | grep screen

If the service is enabled then you will see the following output:

If the service is running then the next thing to check is to make sure the expected processes are running and under the correct user ids.

Execute:

1. Start a screen sharing connection to an affected client (expected of course that it won't actually connect)

2. ssh to the affected client

3. Execute: ps alxww | grep -i screen

You should see something like this:

    0 64671     1   0  33  0  2572076  85544 -      Ss     ??    0:05.26 /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/Ma cOS/screensharingd

  501 64673   238   0  33  0  2567544  23064 -      S      ??    0:02.94 /System/Library/CoreServices/RemoteManagement/ScreensharingAgent.bundle/Content s/MacOS/ScreensharingAgent

This first column is the uid under which the process is running.  screensharingd should be running as uid 0. ScreensharingAgent should be running as the uid of currently logged in user (501 in the example above) or 0 if no one is logged in.

If the uid for screensharingd is not 0 and/or ScreensharingAgent is not running then something may have gone wrong when the service was restarted during the client upgrade process.  If possible, try rebooting the machine and see if you can control the screen after the reboot.

Hello,

Well, rebooting the machine doesn't do anything.

Here are my results of the commands you talked about.

sudo launchctl list | grep screen

ps alxww | grep -i screen

0   390     1   0  49  0 19285132  18480 -      Ss     ??   26:07.54 /System/Library/Frameworks/ScreenSaver.framework/Versions/A/Resources/ScreenSav erEngine.app/Contents/MacOS/ScreenSaverEngine -loginWindow

  501  8039  8029   0  31  0  2434892    532 -      S+   s000    0:00.00 grep -i screen

still nothing... this is really starting to SUCK!  that computer is at it's log in screen and I need to get it logged in and controlled so I can start working again!

Thanks for your help btw,  I assume I'm the only one with this issue?

Same issue for me as well after the update, and I know it was the update because I remoted in to do the update, then once the update was complete it booted my connection. Nothing seems to work to let me in.

The same behavior here. Looking for a solution...