Friday, January 16, 2009

How to configure Citrix XenApp Plugin site

Citirx XenApp Plugin is formerly known as Program Neighborhood Agent, which enables the Citrix clients to automatically log onto a farm and access published applications like a normal local program.

There is an excellent article to describe the procedure on how to configure it on Web Interface and clients here. But I decide to write a complete guide based on my practice.

1. Create a PNA site on the Web Interface in the Access Management Console
- Start the Create Site wizard- Select XenApp Services as the type of the site!
- Accept the default settings for IIS Location (/Citrix/PNAgent) unless you want your own URL, for example /PNA)
- After the site is created successfully, you need to configure it now
- You will need to enter the farm settings (farm name, at least one XenApp server in the farm, and port if it's not the default value of 80)
- Please select the correct Published Resource Type for your farm, either Remote, or Streaming, or both
- Finish the site creation and initial configuration

2. Perform advanced configuration
- You can perform advanced configurations by right clicking the newly created site as well as config.xml under it- At site level, you can modify the farm settings (to add a new farm, for instance) and change DMZ settings as a usual site
- You can also configure the authentication methods. By default, Prompt and Pass-through are selected and Pass-through is the default authentication method. Especially, I will set "Allow users to save password" for Prompt method
- I usually configure "Manage shortcuts" on config.xml so that the Start Menu and Desktop shortcuts can be configured cleanly and removed when user logs off. This, of course, depends on your environment

3. Now you need to restart the web site in IIS admin for the changes to effect

4. Set up the client
- Install the XenApp Plugin
- Run the client named "Citrix XenApp", formerly known as "Program Neighborhood Agent"
- You will be prompted to enter the server address (of the config.xml file) as below. Update it and you will be able to connect to the site automatically (if Pass-through is set as the default authentication method), or user ID, password and domain (if Prompt is the default)- After the login and applications are refreshed, depending on your configurations of "Manage shortcuts" on config.xml, you now should access published applications from Start Menu, Desktop, or by right clicking the XenApp Plugin icon in the system tray

Thursday, January 1, 2009

Set up vnc server on Fedora

It's been painstaking for me to set up Xvnc server on my Fedora 10 Linux server, so here I summarize the steps for future references.

1. Download and install the tightvnc-server rpm package from tightvnc web site.
2. I've got the following error now when I try to run the command "Xvnc". Unfortunately I have to download and install the font rpm package, xorg-x11-fonts-misc.
Could not open default font 'fixed'
3. Create the folder, /usr/X11R6/lib/X11/fonts.
4. Create the soft link as below,
ln -s /usr/share/X11/fonts/misc /usr/X11R6/lib/X11/fonts/misc
5. Set the vnc password with the command "vncpasswd". The maxim password length is 8!
6. Edit $HOME/.vnc/xstartup and comment all the lines. Add the desktop session that you want to start. For example,
startkde (if you want to start KDE)
gnome-session (if you want to start GNOME)
7. Start Xvnc with the command "vncserver",
- Edit /usr/bin/vncserver and add the fontPath environment variable if necessary. In our case, it's "/usr/X11R6/lib/X11/fonts". Moreover, you need to add Write permission to this file before editing it.
8. Check the firewall settings and open the 5801/5901 (5802/5902, etc.) ports, if necessary.
9. On the client, access the Xvnc server via VNC Viewer at the port 5901, or http://:5801 from the browser.

- VNC authentication is based on a common password only. If you want to access the desktop with whichever user's session, edit xstartup in that user's home directory. For example, if you run "vncserver" from root's session, edit /root/.vnc/xstartup, run "vncserver", and then remote users will log onto root's desktop. Similarly, if you start vncserver from the user ''s session, edit xstartup at /home//.vnc accordingly.
- Run the command below to kill a vnc process

vncserver -kill :
vncserver -kill :1 (example, kill the first vncserver process at display 1 and port 5901)