So running my first Citrix XenDesktop 5.5 Deployment, Did the pilot and the design on 5.0 SP1 but when 5.5 came out the first day i saw no reason not to jump straight to 5.5. As i work for a software development company the requirements for developer are quite high so we took some careful consideration when designing the environment as one must when every user us utalising their own Oracle or MS SQL Database plus some JBoss and Eclipse thrown in for good measure.
Long story short we split up the system to a C: and a D: drive for OS and installs respectively, All well and good, nothing in any of the citrix design guides i read saying this wasent possable? XenDesktop just links into VMware and esentially clones the VM right? Wrong! think its best summed up by the one line i got from Citrix support
The Machine Creation Service will always recognise only the first drive, if you require desktops with multiple drives you would work around the MCS by using PVS to stream disks, use partitioning, or manually add disks after MCS has deployed the VM’s.
This little hack allows you to run commands directly at the server itself and is very handy for doing things like enabling SSH in inetd.conf. First thing first. This only works on the fee based version not the free one and you must be sitting at the server and not RCLI.
- Step One: At the server console type ALT-F1
- Step Two: Now you’ll just see basically a console log with no prompt. Don’t sweat it! Just type: unsupported and hit enter. This does not echo back so you will not see your input.
- Step Three: Now a big scary tech support warning will pop up. Just laugh it off and enter your server password at the prompt.
And you’re in! I really just do this to enable SSH but I have also used this to edit etc/hosts to rule out DNS issues.
Quick tip for anyone running Debian Lenny under VMware. As the tools were open sourced you can now find an implementation in your apt tree. Although personally i haven’t seen a quick and easy guide floating around.
Run the fowling as root
apt-get install open-vm-source
module-assistant prepare open-vm
module-assistant auto-install open-vm
Update!: If you are getting out of date tools in your vmware see this comment for an explination