'''NOTE: This is a draft.'''<br />'''NOTE2: This is specific to setup VNC for Mac machines.'''<br />'''NOTE3: From these notes we should create steps to setup VNC for developers'''<br /> = For How to connect === From a Mac clients client ==
* Use Apple's Remote Desktop - VNC that comes with the Mac machines
* Use the FQDN, e.g: vnc://talos-r4-snow-001.build.mozilla.org
= For = From a Linux clients client ==NOTE: This section Remmina Desktop Client has only been verified on tested as a Linux client that managed to connect to Mountain Lion. We might Other versions have not have these issues with the other OSesbeen tested.
You For Linux clients, you will have to allow for enable "legacy VNC " instead of Mac's version before you can connect as well as setting the password.See the section "Enable legacy access VNC and set the password.Based on [http://technosense.blogspot.ca/2009/03/start-vnc-from-command-line-and-connect.html this] article".
Once you run those commands you will be able to VNC and you will have to use your cltbld credentials. You might have to connect a second time for the connection to stick. == From a Windows client ==TightVNC has been tested by Honza to work to connect from Windows to a Mountain Lion releng machine.Honza has determined that real VNC free is faulty = Setup for loaning ==== Mac OS X 10.6 - Snow Leopard ===TBD === Mac OS X 10.7 - Lion ===TBD === Mac OS X 10.8 - Mountain Lion ===TBD === Mac OS X 10.9 - Mavericks ===TBD = Releng connection notes (post VNC connection) === Mac OS X ==Each of our Mac versions have slight differences with regards as to which user to login with once you have VNC'ed into the machine. === Mac OS X 10.6 - Snow Leopard ===Login as the root user with the root password. It will take you to the Builders's session. === Mac OS X 10.7 - Lion ===No need to figure out.As far as I know we don't have the need to VNC into build machines. === Mac OS X 10.8 - Mountain Lion ===Mac relengers can login with the root user, however, you will be starting root's VNCsession without being able to see what is happening under Builder/cltbld.You can try the Builder user, however, it will only be a request that will require an authorization and there's no one on the other side to grant you the access.https://bugzilla.mozilla.org/show_bug.cgi?id=733534 === Mac OS X 10.9 - Mavericks ===TBD = Enable legacy VNC and set the password ==We have to enabled enable legacy VNC and set a new password (as I can't seem to guess figure out what the right onecurrent password is):
<pre>
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart \
-restart -agent -console
</pre>
This is all based on [http://technosense.blogspot.ca/2009/03/start-vnc-from-command-line-and-connect.html this article].
More info about the command (for the curious):
defaults write /Library/Preferences/com.apple.RemoteManagement ARD_AllLocalUsers -boolean TRUE
</pre>
= Mac OS X 10.6 - Snow Leopard =
VNC as the root user with the root password. It will take you to the
Builders's session.
= Mac OS X 10.8 - Mountain Lion =
For Mac VNC clients, you can connect to the root user, however, you will be starting root's VNC
session without being able to see what is happening under Builder/cltbld (You can start a request to see but you would need someone already on the Builder's account to grant you access).
https://bugzilla.mozilla.org/show_bug.cgi?id=733534
For Linux clients, you have to enable "legacy VNC" instead of Mac's version:
<pre>
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart \
-configure -clientopts -setvnclegacy -vnclegacy yes
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart \
-configure -clientopts -setvncpw -vncpw supersecret
</pre>
Once you run those commands you will be able to VNC and you will have to use your cltbld credentials. You might have to connect a second time for the connection to stick.
= Mac OS X 10.9 - Mavericks =
= Deleted =
<strike>
== Mac OS X 10.7 - Lion ==
VNC as cltbld.
</strike>
== Install RealVNC ==
NOTE: I don't know if these instructions worked or I simply fixed Apple's VNC to allow legacy clients.
<strike>
NOTE: These instructions have worked for a 10.8 Mountain Lion machine and connecting from Ubuntu 13.10.
* Download RealVNC
wget -OVNC-5.1.0-MacOSX.pkg http://www.realvnc.com/download/binary/1364
* Install it (the installation takes a bit of time)
installer -pkg VNC-5.1.0-MacOSX.pkg -target /
* Request a personal free 30-day license key
Visit [http://realvnc.com/purchase/activate http://realvnc.com/purchase/activate]
* Apply the license
/Library/VNC/vnclicense -add <license key>
* Start things up (based on [http://technosense.blogspot.ca/2009/03/start-vnc-from-command-line-and-connect.html this] article):
<pre>
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -configure -allowAccessFor -allUsers -privs -all
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -configure -clientopts -setvnclegacy -vnclegacy yes
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -configure -clientopts -setvncpw -vncpw supersecret
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -restart -agent -console
</pre>
* Use Remmina Remote Desktop Client
</strike>
