Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
no edit summary
image =Warning.png|
heading =WARNING|
message = Proceed with extreme caution. This should only guidance has not been tested nor will be attempted supported by advanced usersAmahi. Continuing could break your HDA and a reinstall from scratch may be necessary.}}<brdiv style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">It '''NOTE:''' The one-click [https://www.amahi.org/apps/vnc VNC App] has been discontinued for Amahi 7 or greater. The reason is still under developmentthat it pulls a lot of packages, including desktop and that breaks DNS in Fedora.}}</div><br />
__TOC__
For TigerVNC to work an a Desktop Environment must be installed even if the HDA does not boot to the selected Desktop Environment. So far KDE and Mate Desktop Environments have been tested.
This guidance is based on a clean installation of Amahi 8 or 9, using the [[Amahi_8_Install|Fedora 21 Server DVD]] or [[Amahi_9_Install|Fedora 23 Server DVD]] install method.
== Cinnamon (Amahi 8/Fedora 21) ==
* As root, install Cinnamon Desktop Environment:
= TigerVNC Server Installation =
* It is recommended to only use TigerVNC on a secure network or via a VPN.
yum install tigervnc-server
*Once install we need to create new configuration file, vncserver@.service is only a template file, from this we need t to create a the following config file.
cp /lib/systemd/system/vncserver@.service /lib/systemd/system/vncserver@:1.service
WantedBy=multi-user.target
*Under [Service] replace with the following<USER> with the user name setup in Amahi/Fedora. For this example we will use tom. Please note The modified file will look like this is for root access ONLY, see below on how to setup for other users.
[Service]
Type=forking
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i> /dev/null 2>&1 || :' ExecStart=/sbin/runuser -l tom -c "/usr/bin/vncserver %i" PIDFile=/home/tom/.vnc/%H%i.pid ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i> /dev/null 2>&1 || :'
* Once the root config file vncserver@:1.service has been modified we next run the commandas root.
systemctl daemon-reload
* We now have to modify the firewall and open port 5901 in the iptables, run the command as root.
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 5901 -j ACCEPT
= Password Setup =
*These are universal for both Amahi 8 and 9
* Set the VNC password for the user as defined in the vncserver@:1.service, this will create the .VNC folder for each user and place a file called passwd inside the folder.
* From the example log into terminal as root the user, in this example it will be tom and run the following command
vncpasswd
= Setup Desktop Environment Access =
* Modification of the ~/.vnc/xstartup will be required to match run the chosen Desktop-Environment. At this point the xstartup file doesn't exist so we have two optionsdo the following.
For this example we need to login as rootthe user.
* Create the xstartup file using the command below then copy/paste the required xstartup for the chosen desktop enviroment.
nano ~/.vnc/xstartup
== Amahi 8 (Fedora 21) ==* Or we can use For the commands below to start/stop the vncserviceCinnamon Desktop on Amahi 8 (Fedora 21), this will create modify the default xstartup file which can then be modified. The service has to be stopped to allow the modification to work when restarted. systemctl start vncserver@:1.service systemctl stop vncserver@:1below.service * Below are xstartup scripts for the various desktop environments, if the xstartup was made via your favourite editor then simply cut/paste the script required else if using the default xstartup remove its context and again cut/paste required script. === MATE-Desktop Environment ===
#!/bin/sh
#
== Amahi 9 (Fedora 23) ==
For the LXDE Desktop on Amahi 9 (Fedora 23), modify the xstartup to the below.
#!/bin/sh
#
= Starting Tiger VNC =
systemctl enable vncserver@:1.service
systemctl start vncserver@:1.service
= TigerVNC Server Commands=
* The following commands will allow you to autostart start on boot and start the vncserver service.
systemctl enable vncserver@:1.service
systemctl start vncserver@:1.service
* The following commands will allow you to disable autostart start on boot and stop the vncserver service.
systemctl disable vncserver@:1.service
* The following command will restart the vncserver service.
systemctl stop restart vncserver@:1.service
* The following command will display the status of the vncserver service.
= Multiple User Setup =
* It is possible to setup multiple user login's other than root. For this example with will create 2 other users, Tom Dick & DickHarry.
* For the example the commands will be
adduser dick
adduser harry
* Then create a password for that user using the following command
* For this example the command will be
passwd dick
passwd harry
* When requested enter a password and renter the password to verify it for each user created.
* Once the user are created we will need to assign configuration files for each user. For this will assign the following config files as followed. Carry out the below as root.
* Tom Dick will be assigned the following config file using the following.
cp /lib/systemd/system/vncserver@.service /lib/systemd/system/vncserver@:2.service
* Dick Harry will be assigned the following config file.
cp /lib/systemd/system/vncserver@.service /lib/systemd/system/vncserver@:3.service
* Once the config files are created we will need to modify them for the correct user access. Accessing the files using your favourite editor the config files need to be modified under [Service] to reflect the assigned user. For this example the files should look like the following.
* For Tom Dick (under root control)
nano /lib/systemd/system/vncserver@:2.service
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l tom dick -c "/usr/bin/vncserver %i" PIDFile=/home/tomdick/.vnc/%H%i.pid
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
* For Dick Harry (under root control)
nano /lib/systemd/system/vncserver@:3.service
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l dick harry -c "/usr/bin/vncserver %i" PIDFile=/home/dickharry/.vnc/%H%i.pid
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
systemctl daemon-reload
* We need to assign password to access vnc-server for each user, for this each user needs to login in via terminal and run the the command as below, this will be the same procedure as described under the password section
* As above we can Log in as each user and run the following command to create the xstartup file either by.
nano ~/.vnc/xstartup
* For this example we will use the MATE-Desktop Environment, each user will copy Again modify the following into their xstartup file. #!/bin/sh # # Uncomment as above to use the following two lines for normal cinnamon desktop: # unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS # exec /etc/X11/xinit/xinitrc # [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/environment.Xresources xsetroot -solid grey vncconfig -iconic & x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & mate-session &
* Once each xstartup file is modified we need to start each service. Login as root and run the following commands.
systemctl start vncserver@:3.service
* Once the services are running then each user can access their remote desktop using a client software as listed below. The ip address will depend on how you have setup your HDA.
* From the example tom's Dicks access ip address will be
192.168.1.10:2
* For dick's Harrys the access ip address will be
192.168.1.10:3
= Windows Client Software =
[[File:UltraVNC_Screen1.png]]
If connection is successful it will as ask for a password, which is the password entered from the setup above. = Screenshots = Screenshot of KDE Remote Desktop
