Microsoft Office (Exchange) 365 – RDSH Myth 20 Comments

For many years now, the everything in cloud is happening more and more, among all the services / software available as a services, most of the vendor are promising a cheaper way to manage their software and a much more simple way to manage it.. I know some of you will disagree with what I writing about and some will agree, this is a view from my experience on the field :) A couple of weeks ago I launched a small poll on Twitter asking this question : "Why Do you think companies are moving to Exchange 365 ?" Here are the results : "It's less complex" won the poll follow by "it's a fashion" and then "it's cheaper"... I tend to agree with everything here, because if you get rid of a complete Exchange infrastructure with all the people you need to architecture and manage it, it will be cheaper and less complex for sure ! But this is just a dream without complexity of companies and without user's usage of their Outlook. What I try to point here is : Moving to Exchange 365 is not as easy as it seems, some company do have a "basic" Outlook / Exchange usage and it won't bring issues but most of the companies I saw have had issue because Microsoft and Microsoft's Partner did not capture the way users were used to work with their Outlook mail software. The picture above is the "put everything into the Cloud, you will save money" ideal. This ideal is true and can be reached when you know your users work habits and already have an organised mail infrastructure. But this ideal can be easily broken If it looks easy on the paper or in a Powerpoint presentation, simple things can break this kind of project into pieces and make it fails.. How ? Here is a list (to be completed :D ) Outlook plugins Online Mode RDSH environment Bad Architecture decision / Consulting ... ... Outlook plugins is the work enemy of the Cloudification because it means in 90% of the case you'll be forced to keep Outlook mail client, it's a road block for OWA adoption... Once you're stuck with the Outlook mail client, you need to deal with the Online or Cache mode with Exchange 365... Piece of cake right ? Workstation / Laptop --> Cache mode enable, no problem ! But what about…

Netscaler Gateway X1 theme 46 Comments

What I like when I access my virtual desktops and applications is consistency thought different systems, front web and UI... Citrix have try with the green bubble theme to bring this but that wasn't really a success due to this "not very good looking" theme :)

Citrix Receiver 11.9.0 for Mac color issue 12 Comments
">

I had this weird issue on my iMac 27" running OS X Yosemite 10.10.2 with the Citrix Receiver 11.9.0 while installing it. The color of my Windows 8.1 published desktop went really weird : On the left this is my desktop with Citrix Receiver 11.8 and on the right Citrix Receiver 11.9, this is really weird and resizing, full screen or not, the color remain degraded. So I posted on Citrix's forums and I got very quickly an answer from Dustin Norman [link] To make it quick a change in the Citrix Receiver config file needs to be done. You need to edit and change the line in the [WFClient] section And then, here you go, everything is back to normal. vd3d is the component for Aero redirection, I don't fully catch what is the impact to disable it, I need to check it a bit further to fully understand.

Load Balancing TFTP with Netscaler 10.5 30 Comments

Implementing Citrix Provisioning Services (PVS) is very common nowaday when it's about deploying Shared Desktops (XenApp) or Pooled, Private or Personal Desktops (XenDesktop). If there are still some debate around about using TFTP+PXE vs using BDM (Boot Device Manager) I still observe a large number of deployment made using TFTP+PXE rather than BDM. Both of these two solution have Pro and Cons (Check Wilco's website here) and this is an architectural choice you need to plan ahead the project. Using TFTP and PXE bring several spof along the line and need to be consider and design as the most resilient as the high availability require. TFTP is not redundant by design, using the DHCP 66 options (Boot Server Host Name) allow the use of only one IP address. and there is no redundance behind that. With Citrix Netscaler, Citrix gave us the ability to bring high availability to this spof and address this issue. With Netscaler previous version (prior 10.x) that wasn't that easy to setup and the understanding of Netscaler feature like Layer 2 Mode, DSR etc... And if you didn't understand exactly everything what you were doing, all the PVS traffic was going through the Netscaler and believe me, that was really pain in the ass... I saw that kind of mistake a number of time... With Netscaler 10.1 then 10.5 things are a lot more easy... So I just jump on the occasion I had at one customer's place to load balance 4 Citrix PVS servers (TFTP + PVS) to deliver this simple and fast how to. Information you need to gather : IP Adresses and name of all PVS servers (with TFTP) One IP Adress for the Virtual Server (VIP) One or more Netscaler 10.5 (I made this configuration with 10.5.51.10.nc) Here is a basic architecture overview of component we are impacting : Netscaler #1 and #2 : This is were the configuration will take place PVS Servers #1, #2, #3 and #4 : All the PVS / PXE / TFTP servers we will use in this example DHCP Servers #1 and #2 : This is where we will configure the 66 option by using the Load Balanced IP Address (VIP) VMs : All these Virtual Machines will use PXE to boot get the Load Balanced TFTP address to launch the ARDBP32.bin file.   Let's got for the Netscaler configuration, first you need to login, if you're using a multi Netscaler architecture you…

Netscaler 10.5 and Storefront 2.5.2 Configuration 13 Comments

Citrix Netscaler 10.5 is out since a couple of weeks now, and if you want to read what's new about this new release just click on the [link] because there are so many things I won't list everything here. I will use this blog to refresh the "how to" I already did about Netscaler and I will go through the basic setup, certificate request, import and Access Gateway configuration to plug my XenDesktop 7.5 lab. First, you need to download your Netscaler (download if you're using a VPX appliance). You can find the appliance corresponding to your hypervizor : vmware ESX Microsoft Hyper-V Citrix XenServer KVM You can download it here : [link] - myCitrix account is required One you boot up the appliance, after give the basic information like IP address, subnet and getway, you can fireup the GUI through your favorite browser. You need to logon and follow the step by step screenshots : The basic configuration is done. now time to add a certificate for the Access Gateway, creating a private key, a CSR and finally importing the pem certificate.   Don't forget to change the nsroot password. Now the certificate part is done (thanks to Digicert for my lab) you can go ahead to the next step and configure your Strorefront server to create a new store ready to connect with the Netscaler Access Gateway. Storefront part is easy and quick to do, you can now continue by creating the Access Gateway using the new wizard and following these steps : Here you go, just a reboot to have the Access Gateway up and running. I had few issue in the end with Application Firewall with Google Chrome and Safari from a Mac OSx computer, you need to enable the learning mode to check what need to be change in Application Firewall rules and allow connexion to you Access Gateway. You can customize the Netscaler Access Gateway logon page and your Storefront very easily, Eric one of my CTP friends did a very short and nice blog about that [link] and a very detailed blog written by Feng Huang Citrite here [link] This blog will give you a good overview on what needs to be done to set up an Access Gateway with Storefront, for those who don't have time to make test, now you know !

XenApp 6.5 to XenApp 7.5 Migration (Machine) 24 Comments

Citrix will very soon offer a lot of scripts and tools to give the ability to migrate policies from a XenApp 6.5 farm to a XenApp 7.5, I'm currently testing all these Powershell script to check it out and maybe use it by including it in our migration process. What Citrix haven't give us yet is a tool to move an existing XenApp 6.5 server to a XenApp 7.5 Site, steps are fairly simple and can be automatize : Leave XenApp 6.5 Farm **Reboot** Uninstall XenApp 6.5 **Reboot** Install XenApp 7.5 VDA This is not what I recommend to do because removing a piece of software to replace by another always leave some dirty little things everywhere... This is the reason I prefer to start from scratch and migrate application; sometime it's not possible and we need to go fast, so these few steps are easy to customize and integrate in every deployment system in place. The first step is to leave the XenApp 6.5 farm : To complete this farm leave script, you need to reboot the XenApp server. The second step is to uninstall XenApp 6.5 using this command line : To complete this step the XenApp server needs to reboot again. The last step is to deploy the new VDA (XenApp / XenDesktop 7.5) using this command line : Update 25 April 2014 If you plan to move your XenApp 6.5 servers to XenApp 7.5 you need to clean a bit more than simply XenApp, I had a lot of comments about Edgesight agent, Citrix Profile Management etc... and my answer if yes you need to uninstall each of these component to avoid any conflict with the VDA. For example Esgesight can be uninstall using the following command line : This is it ! I think Citrix will offer a "graphic" tool in some point, but I needed to have that ready now, so I share it ! Resources : XenApp and XenDesktop 7.5 edocs XenApp Uninstallation Best Practices

Are we missing something ? 2 Comments

As you might know I'm the CTO of a super cool company here in France (Activlan) base around Paris and one side of my job is to watch in my crystal ball to know what our customers will need and how they could use us to remain on top of their productivity with their IT. Reducing cost and accelerate process; giving flexibility and liberty to their users and keeping the information safe when needed. What's very cool in my job is I always exchange so many things with you all during events, when we meet here and there, online and in real life that is give me a flavor of what's happening in IT in a lot of country very different than here in France. Of course I try to give back what I learned of all this shared experience and knowledge but these last months I've been busy working hard on some other project. So, this title brings me back to an old blog : VDI ok, What's next ?  published in May 2012 where my conclusion was : What really matters in the vWorld ? In the end, the data. I think that was about right in 2012 and you know, with all the VDI, RDSH, offline and online, Hypervizor of all type, application installed, streamed or isolated, using a phone a tablet, a thin client or a computer, in the end the only thing that matter remains data. Software vendor in our segment are pushing harder and harder their mobile (ie MAM and MDM) solution thinking everyone should buy these software and work with tablets and phones. I think we aren't still there just yet... When someone is hired in a company this is almost all the time a giant waste of time (and money) the first days... No desktop ready, no application access etc... In the big company, MDM and MAM need to be addressed but that will never be wildly use for the next 2/3 years, what user expect from their company is to have access to their data (core need) through a applications accessed via a desktop, or not but with a consistent environment. They want to work in an optimal way during their working hours and sometime be able to access their data from home or a remote location, but taking over the personal people's phone is over-rated for now. The MAM MDM hype remind me the…

Citrix PVS vs MCS – Despectus 21 Comments

I know this subject has been cover thousand times here and there but this is an eternal discussion we have whatever the forum or the meeting going on when we speak about Citrix. To remind people not familiar with MCS or PVS here are the main differences : MCS : Machine Creation Service PVS : Provisioning Services All the blogs, articles, white papers are very good and very technical with a lot of details but lake too often of "real life" example. Of course this is important to know  detailed performance measuring iOPs in read and write, cache mode, disk and storage type etc. but what most of the time everyone is missing is a crucial component : complexity and ability of the technical team to handle PVS and/or MCS. At many of my customers place we've implemented PVS architecture on multi-site with DFS-R and SAN / NAS etc to provision XenApp 6.5 farm lightning fast and this is every time a success when everything is setup correctly and when everything works as expected. BUT the complexity we leave behind at the customer's place leave me a though that in 70% of the case, they will call us back to fix an issue they created while trying to handle PVS and surrounding component. 20% won't call us but nothing will change, event the XenApp servers will remain in the same state as when we left. Of course writing documentation and how to for everything won't solve this issue because managing XenApp servers provisioned with PVS is complex and needs good organisation and an understanding of the product. PVS is in version 7.1 (April 2014) and haven't evolve that much during last couple of years, some say PVS will disappear with time to let MCS take over, but I honestly don't know what are the plan for Citrix about PVS. But as PVS is an awesome technology, I think Citrix will bring more and more feature to MCS and keeping the simplicity while adding feature will be an interesting chalenge. To keep this topic short (that never happen when we speak about this during CTP meetings or forums :) ) I would say for large enterprise I would continue to use PVS on the current and new deployment but put in my customer's mind the overhead of complexity could cost more than intelligent storage solution (software, hardware) and introduce few desktops (XenDesktop…