It is so great when you have a nice HP Server, which is in every HCL of every Software Vendor - from Linux to Windows. But if that is not the case and you want to build a small lab at home or in the garage you might want to decide to build a " Server" on your  knees. And while an installation in a data centers on those fine HP DL 380 or BL blades never have got me any troubles this time I faced many of them! So the setup:

Motherboard: MB ASUS M3N78-VM NF8200 AM2 FSB 5200MHz PCIe mATX
Memory: DDR2 2x2048MB Kit Kingston HyperX 1066MHz CL5
CPU: CPU AMD Phenom X4 9650 2,30GHz AM2+ 4MB 95W
Hard Drive: SATA 320GB WD
CD-ROM: some old IDE CD-ROM

So, with brand name components like this you would think of some HW incompatibility as the last option. Not the case with XenServer 5.5 Installation. Besides the HCL list of XenServer can be found here:

http://hcl.xensource.com/

After burning the CD which I downloaded from Citrix:

http://www.citrix.com/lang/English/lp/lp_1688615.asp

with a good Plextor DVD Writer I put the DVD into the IDE Drive and started my knee build Server. The first error I got couple of times was KERNEL PANIC - the ...

So you decided to learn something about Terminal Services or as it is called now - Remote Desktop Services. Where do you start. First you have to decide what version are you planning to work with. If you are new to the TS world I would suggest to Start with Windows 2003 and only after engage the 2008 version. Keep in mind that while the difference between Windows 2003 and 2003 R2 in terms of Terminal services is marginal, there is a big difference between 2008 and 2008 R2. I personally would recommend to go for those two books on the topic:

Terminal Services for Microsoft Windows Server 2003: Advanced Technical Design Guide (Advanced Technical Design Guide series) from Brian Madden

and for Windows 2008

------------- MSDN --------------------------

If you are one of the lucky owners of Microsoft MSDN subscribtion and you are working on something which imply testing Terminal Services application mode you might wonder whether or not you can get TS CAL's as part of your MSDN subscribtion. Indeed you can, just follow this simple guidline:

1) Install Windows 2008 or R2 or 2003 or even 2000  (with MSDN key to avoid death after 180 Days)
2) Activate W2008 (you will have to do that once in awhile since MSDN keys need to be reactivated once in a while)
3) Install Roles, TS inclusive
4) Call Microsoft Clearance house (a.k.a when you are in License Server - add TS CAL - activate by Phone - call Clearance house)
5) State your MSDN subscribtion number and what ever information they will ask
6) Request the type of TS CAL you need (W2000, 2003 or 2008)
7) enter the code stated by MS employee

Thats it. So as a valid MSDN subscriber you can call MS Clearance house and request TS CAL for developer purposes and only for them. According to the License agreement you are not allowed to use it in production.

It is not a good practice to store Profiles locally on a Terminal Server - just because if the server dies all the data of your users is gone (unless you made a backup :-) ). However, if you have to have it you might sometimes notice that the disc space on your TS Box looses space faster than expected. When you do some research you find out that mysterious WER folder, which might contain hundreds of MB's in your users (each of them) folders. This WER folder is the place:

C:\Users\%username%\AppData\Local\Microsoft\Windows\WER

where the Windows Error Resporting information is stored. Unless you can start something with that you don't need that folder or the information in it. It's the folder where all the application crash information is stored for a particular user.

http://technet.microsoft.com/en-us/library/cc709644(WS.10).aspx

http://msdn.microsoft.com/en-us/library/bb513638(VS.85).aspx

To Disable Windows Error Rep ...