Citrix XenApp "Iron Cove" 6.5 Tech. Preview (Part.1) Citrix XenApp "Iron Cove" 6.5 Tech. Preview (Part.2) Citrix XenApp "Iron Cove" 6.5 Tech. Preview (Part.3) With Windows 2008 and after, Remote Desktop Services included a new way to disable logon on the machine (check this article to read more about it and thanks to Laurent Falguière) the classic way when disabling logon is always bringing problems when a user tried to launch his disconnected application hosted on a disable server... Now you can manage this behavior : Allow logons and reconnections. Enable all logons, reconnections, and session sharing (default setting). Prohibit logons and reconnections. Reroute all logons, reconnections, and session sharing to other servers. Prohibit logons only. Reroute new connections and session sharing, but allowing users to reconnect to disconnected sessions. This state persists until you change it manually. Prohibit logons until server restart. Reroute new connections and session sharing, as above, but after restarting the server, the setting automatically changes back to Allow logons and reconnections. Coming with this XenApp preview, you can find in the ISO file a new Citrix EdgeSight version, 5.4 S540 Tech Preview. Since my XenServer @ home just came back to life, I didn't had time to go very deep with this new EdgeSight release, here are so far what I noticed : EdgeSight 5.4 support Microsoft SQL 2008 R2 The new EdgeSight for XenApp client version is 5.4.0.5094 Tech Preview, only for XenApp 6 and XenApp 6.5 Older client version doesn't seem to work (my XenDesktop VMsare not showing up in EdgeSight console) EdgeSight 5.4 seems to integrate IPv6 parameters Some new options, like exporting licenses usage to a file (It doesn't work yet...) A great tool very under rated I think, this is XenApp Power and Capacity Management. This tool is going from version 1 to version 2.1. This tool helps you to switch on and off your XenApp servers regarding a load you configured within PCM console. You can read XenApp Power and Capacity Management with provisioned machines blog post I made last year. The console doesn't change at all, except in the Machine Manager (Connection to the hypervizor) where you can now use and connect XenApp PCM with Hyper-V, SCVMM and ESX with vCenter ! Now XenApp PCM is open to all big hypervizor on the market, I will implement it every time I'll have a new XenApp architecture to deliver…

In a new mission, I had to learn a new environment based on Citrix XenDesktop 4, Provisioning Services 5.6 and vmware vSphere 4.1. This week, I had a weird issue, I didn't change anything, I just didn't understood why suddenly VMs stopped to be available, in fact VMs were available but for some reason, it was impossible for everyone to access it through the Web Interface. VMs were working well XenDesktop brokers were fine Web Interface was ok Citrix License Server was up and running with correct license vmware vSphere was ok as well, VMs were running without any problem on it On the Web Interface, the following message was display while trying to launch a XenDesktop virtual desktop : "xxxxx is currently unavailable. try reconnecting and, if the problem persists, contact your administrator." On the DDC, XenDesktop Desktop Delivery Controller, I found event logs with ID 1301, source : Citrix Desktop Delivery Controller, with the following description : "The delivery controller failed to broker a connection for user xxxxx to desktop group yyyyy. The delivery controller cannot find any available virtual desktops. Please add more virtual desktops to the desktops group. If the problem is due to existing virtual desktops not becoming available, refer to Citrix Knowledge Base article CTX117248 for further information." It look like a communication problem between XenDesktop DDCs and vmware Virtual Center, so I checked every component, DDCs, Virtual Center.... I found nothing really relevant. So the next step was to enable extended logs on the DDC side, after a short search on Citrix website I found how to do do with CTX117452. I got a lot of logs, but after one day scratching my head to try to understand why without changing anything I had such behavior, I just had bunch of logs but I was missing something... Here is a short part of the pool_log.log file : I also took a log in the virtual desktops pool properties to check if everything was alright... It wasn't :   All the VMs within the Citrix Delivery Service Console were disassociated with Active Directory and a message confirm I had communication problem between vmware Virtual Center and Citrix XenDesktop : "Virtual machines could not be retrieved from the hosting infrastructure" and then a pop-up saying : "Error occurred whilst validating the list of virtual desktops. For more information about each error, hover the mouse over…

22nd Dec 2009 : I needed  a XenServer at home to work on some project for my company (Activlan), I didn't want a real server because it would be too noisy in my apartment :) So I was looking for a silent computer and I made my choice with the elements bellow : Case : Lian Li PC-V351B Power Supply : Silverstone Nightjar ST45NF - 450W MotherBoard : Asus Maximus II Gene Cpu : Intel® Core™ 2 Quad Q9550 Ram : G.Skill Extreme Series MQ 4x4096Mo PC6400 Dual Channel CAS6 Video : PNY Quadro NVS 295 PCI-E 16x (for another workstation #XD4) Hard Drive : Seagate Barracuda ES.2 S-ATA - 1000 Go - 32 Mo (x2) I though it would work fine, just some question were remaining : The network adapter on the Asus motherboard might not be compatible with XenServer and I did choose two hard drive to build a RAID 1 but I though XenServer wouldn't be able to recognize the sata RAID controller. I was right on the Sata Raid controller, it was too mainstream chip raid controller so I never got it working. The network card was fine I just got some issue with XenServer 5.6 and the checksum calculation, I had to disable the TCP Offload on the hypervisor (eq : not the vms). Hard drives, the Seagate are not a good product at all, I got 5 break down in less than 2 years, I will never buy enterprise class Seagate again. Then in june 2011, the motherboard died... 10th Jun 2011 : The motherboard is dead... Maybe it has been the source of all the recent system crashes I had... So I got to move on and chose a new motherboard. I chose Intel DQ67OW, with a new CPU an Intel Core i7 2600 which contain the virtualization instructions I missed with the previous CPU (VT-d). Case : Lian Li PC-V351B Power Supply : Silverstone Nightjar ST45NF - 450W MotherBoard : Intel DQ67OW Cpu : Intel® Core™ i7 2600 Memory : Kingstone 16GB 1333MHz DDR3 ECC Reg CL9 DIMM (Kit of 2) DR x4 w/TS Intel Video : PNY Quadro NVS 295 PCI-E 16x (for another workstation #XD4) Hard Drive : Seagate Barracuda ES.2 S-ATA - 1000 Go - 32 Mo (x2) for vms Hard Drive : Seagate Barracuda® XT SATA Revision 3.0 - 2 To - 64 Mo for vms Hard Drive…