Adyn

Ok I just read what you are wanting do use for a client and it makes more sense that you are wanting to use what I would call proper thin client. I would ask however as Citrix sits on top of Microsoft remote desktop for ten users I would not see that much of a benifit adding Citrix into the mix unless you require a specific feature.
 
With regards to licensing with just Microsoft Remote Desktop Services (RDS) you need a license server (which could sit on a server tasked for other things) but when you add Citrix on top that requires its own license server as well.
 
Also reading that you were wanting to use Xenserver as the hypervisor you are in effect talking about putting a virtualisation product on top of a virtualised infrastructure and while with ten users you are unlikely to have issues when you start adding more you would have to be careful with your storage IO as I have seen more than a few of these go horribly wrong if the correct workload planning is not done.
 

Have a look at http://www.expta.com/2016/05/expta-gen7-home-lab-server-builds-and.html it looks exactly what you are after. I actually built one of the older ones and it would happily run six virtual machines.
 
The only thing I would suggest is that you use a bigger case as it makes it much easier. But have a read through the link as its written by a Microsoft MVP and it explains the rational about the components but the most important factor is the motherboard to ensure you can fit enough memory.
 
Then look at the workload you are wanting to deploy and let that dictate your CPU choice. If you then put a decent graphics card in it would happily play games.
 
One final point to ponder you are saying that you would be using Microsoft server products unless you can afford to buy them I would run a Windows 10, 8 with hyper v (or another virtualisation desktop product) and install your server virtual machines from Microsoft 180 day evaluation versions, anything you want to use as a permanent setup use an open source OS.
 
Its just if you setup a cool home development environment and want to use it to demonstrate self development for an interview one of the trick questions will be how is it licensed ;).
 
Oh and you can run a hyper visor (Xen, ESX etc) on a hyper visor think virtualising a virtualisation product and then you will find your home lab can do some pretty cool things.

That is what the shelf would do.. you'd put the box on the shelf inside the rack. Granted this picture shows a small one but they come in all sizes. Just an idea if you want cheap and hotswap together. I actually was forced to do this, because the Rosewell rack case I bought did not support slider rails (only fixed) so I had to buy a shelf. 
Better question is, what is your budget? "Cheap" can mean different things to different people.

 

Think waves on a beach while you have peaks and troughs they are different heights and depths, that’s analogue. Anything with waves is analogue so think sound, electricity etc.


 
The problem with waves is they are not static so if you were using electricity for a control and you wanted to sample for a certain voltage to use for controls you would get multiple readings at random when you wanted a single value.


 
Hence the requirement for digital so you can have control this is achieved by using a transistor to measure a voltage over a period (think as small as you can) to determine if that signal is a 1 or 0.


 
So now that you have a defined digital signal you can use that to carry out calculations store data whatever you can think of.


 
Now this is the bit audiophiles do not like you can reverse this process to get an analogue output but it is always a representation of the original source. Now you can do things to decrease the sampling time to get a more authentic signal but if a digital process is used anywhere then that becomes a representation of the orginal.

It has been mentioned above in relation to the different layers that devices operate at these layers are part of the network OSI model (table from wikipedia below).
 
OSI Model Layer Protocol data unit (PDU) Function[3] Host
layers 7. Application Data High-level APIs, including resource sharing, remote file access 6. Presentation Translation of data between a networking service and an application; including character encoding, data compression and encryption/decryption 5. Session Managing communication sessions, i.e. continuous exchange of information in the form of multiple back-and-forth transmissions between two nodes 4. Transport Segment (TCP) / Datagram (UDP) Reliable transmission of data segments between points on a network, including segmentation, acknowledgement and multiplexing Media
layers 3. Network Packet Structuring and managing a multi-node network, including addressing, routingand traffic control 2. Data link Frame Reliable transmission of data frames between two nodes connected by a physical layer 1. Physical Bit Transmission and reception of raw bit streams over a physical medium  
So when you for example email the other person even though it is on the same wifi network it does not communicate directly with the other user. With wifi the physical and data link layer are handled by the wireless aspect of the connection but it behaves exactly the same as the above table. Wireless is great for flexibility and mobility but not so good for bandwidth and performance hence using hard wiring. 
 
Source:http://microchip.wikidot.com/wifi:80211-osi
802.11 is a set of data link and physical layer protocols.
Data Link Layer (MAC):
Responsible for reliable link-to-link data transfer
Channel access (CSMA/CA) Addressing Frame Validation (management, data, control frames) Error detection Security Mechanisms Physical (PHY) Layer:
Responsible for putting bits “on the air”