Raspberry Pi 3 as a Thin client using Citrix Receiver

I've been working on using a Raspberry Pi as a Thin client - Citrix Receiver

Here are some thoughts:
1. Get Pi, Rpi, Raspberry PI: Here is a good one: http://amzn.to/290tTxI $74.99
a. Get...
i. Raspberry Pi 3 (RPi3) Model B Quad-Core 1.2 GHz 1 GB RAM
ii. 32 GB Micro SD Card (Class 10) - Raspberry Pi Recommended Micro SD Card pre-loaded with NOOBS
iii. CanaKit 2.5A USB Power Supply with Micro USB Cable and Noise Filter - Specially designed for the Raspberry Pi 3 (UL Listed)
iv. High Quality Raspberry Pi 3 Case, Premium Quality HDMI Cable, 2 x Heat Sinks,
b. What you have...
i. All of the RPI's have USB, ethernet, HDMI, and audio out.
ii. If you get a RPI 3 you have On-board WiFi and Bluetooth Connectivity
c. What you think might have but you really don't have what you need.
i. Micro USB power needs to be clean and constant, while the Arduino is meant to be powered from another machine's USB port, the RPI should be a nice clean consistent 2+ Amp source.
ii. 16+ GB Micro SD card. You probably will use up more space if you are using the local device for storage like a traditional desktop. The most important part here is to use a class 10 card for speed.
iii. Don't use an old IDE cable from an old desktop. Some of you will laugh but some of us have machines that used Pre-SATA drives. If it has a "Committee to Re-Ellect Nixon" sticker, you probably shouldn't use it. If you are going to do IoT stuff with it too, then start off with something like: http://amzn.to/29kUD8O $89.99
d. What you might want to watch out for...
i. Raspberry Pi 2, this will not have Bluetooth or WiFi, you will have to add this on via USB and buy those devices separately.
ii. RPI, and RPI2 are a little slower than the RPI3
2. Built in OS ready to run thin client:
a. http://www.thinlinx.com/index.html
i. Not an IoT OS, it is locked down.
ii. make sure you are connected to network on boot.
3. OS choices: https://www.raspberrypi.org/downloads/
a. NOOBS, has a bunch of stuff ready for use in schools etc. Just need to install the Receiver.
b. Raspbian: Based on Debian like NOOBS, also just need to install receiver.
c. Ubuntu Mate: My favorite, ready to install receiver. I have not gotten the NetScaler Gateway plugin to work yet, but I haven't tried very hard. I'm pretty optimistic though.
d. Don't try Windows 10 IoT core, or the other IoT focused or Service focused OS's like OSMC. They might work, but they are focused on other roles so there are a lot of extra stuff to install if you want the desktop apps to work like browsers etc.
4. Expect a Receiver experience, not a browser HTML5 experience.
a. My best results are from using the receiver. The Open Source browsers are not as peppy as one would expect, and the published browsers are a more user friendly experience.
b. Because Chromium ~ Chrome; and IceWeasel ~ FireFox, are not quite equivalent, the receiver is really the best way to go.
5. Single monitor experience: My goto is always Synergy. (If you can't go, then run the app.) http://symless.com/synergy/ It is pretty clunky to swap keyboards, and I don't find myself actually using the device unless I can just slide my mouse over and use the alternate OS.
6. Running a full OS instead of ThinLinX has forced me to do stuff on the OS. I run Raspbian (Like Debian) and extra traditional Linux Desktops side by side with my Windows and MACs. I have learned a lot about Fedora, Ubuntu, SuSE, and RedHat by just running extra screen real estate on the side of my primary desktop for watching videos, playing music, running web apps, manipulating and copying drives, cards etc.
7. Install and Configure Citrix Receiver: http://www.martinrowan.co.uk/2015/08/citrix-receiver-linux-raspberry-pi-...
a. Pretty much the same steps regardless of the exact OS.
b. I remember having to do a certificate step but I think that the newer versions of the OS's have taken care of that.

Desktop Delivery: 
Citrix XenApp: 
Application Delivery: 
Powered by Drupal