Category Archives: XenApp
XenApp Best Practice #1: For the best user experience, application and back-end data must reside together on a fast, low latency network.
What if you decided to store your cooking pots and pans in the bedroom? Every time you wanted to cook some Mac & Cheese, you would have to walk through your house, maybe up the stairs and into the bedroom to grab a pot. Then you walk back through your house into the kitchen to start cooking. And if you are like me, in the middle of cooking your delicious Mac & Cheese you realize you need another pot, so again, you walk back through your house, up the stairs, to the bedroom to grab the next pot, and then you walk back downstairs into the kitchen.
This is a horrible experience (although it might solve obesity problems with all of that extra exercise).
So tell me why you would want to have your data far away from your applications? You wouldn’t, right? But I’ve seen so many do it. Let me give you some examples:
- Exchange Online: If I have a local install of Outlook, my application data is somewhere in the cloud.
- Hybrid Cloud: We host an application in the cloud while leaving our data residing in our data center.
For the best user experience, your applications and back-end data must reside together on a fast, low latency network.
This is one of the fundamental XenApp best practices.
- Look at Citrix ShareFile. In the XenApp/XenDesktop world, we locally sync what you are currently trying to access.
- For Exchange Online, only sync the most recent email, as it is the data you will most likely access. (Take a look at the Office 365 Deployment Guide for additional design recommendations.)
- For XenApp, host applications in the right data center or cloud provider where your application data resides. If this means you have XenApp hosts in multiple locations, so be it because you can use the Applications and Desktop Service of Citrix Workspace Cloud to integrate all of these sites together into a single management plane.
- And for your home, keep your pots and pans in the place you will use them… in the kitchen.
Stay tuned for more best practices…
Daniel (Follow @djfeller)
As you saw from my previous post, Citrix now has Linux virtual desktops. You know what this means?
NEW VISIO STENCILS!!!
The new set for XenApp and XenDesktop 7.6 includes
- Linux virtual desktop
And remember, pre-built diagrams that you can modify are also included as a stencil (one of my better ideas). Just drag the stencil into your drawing and perform an “Ungroup” operation. You can now modify to fit your needs.
- Visio 2013: XenApp 7.6 and XenDesktop 7.6 Visio Stencil (2013)
- Visio 2010: XenApp 7.6 and XenDesktop 7.6 Visio Stencil (2010)
From the virtual mind of Virtual Feller
If you were at Citrix Synergy, you heard about XenApp/XenDesktop adding support for Linux virtual desktops. As my hero Homer Simpson says “I’m not impressed easily… WOW a blue car!” And that is what we have, a new car color.
We had red cars (Windows applications), green cars (Windows desktops), and now blue cars (Linux desktops). From my perspective, these are simply different applications we can deliver to users (Yes, I also believe a desktop is just another application, which I said back in 2011)
So what’s the big deal then?
It isn’t that XenApp/XenDesktop is able to deliver a Linux desktop as the Linux desktop is just another viable resource. The big deal is that
- The user simply sees a new resource they can access. The experience is the same. We continue to use whatever Receiver the user has installed, including HTML5. We still provide pass-through authentication for the user so they only have to sign on once.
- The admin uses the same tools to deliver the new resource… Studio. The admin creates a new machine catalog and a new delivery group.
- The support team uses the same tool to monitor the new resource… Director. The can see in-depth details about the user’s session, including running processes
See for yourself
The big deal is that we deliver applications (Windows apps, Windows desktops, Linux desktops) to users with a single platform.
And once you get your Linux virtual desktop running, feel free to relax with a little entertainment with the following to be executed from the terminal:
From the virtual mind of Virtual Feller
I spent the last few blogs, dissecting Microsoft Outlook and how we can integrate an Exchange Online server, as part of Office 365, with XenApp and XenDesktop.
- Can I use a Cached Exchange Mode with XenApp and XenDesktop
- When to use Cached Exchange Mode with XenApp and XenDesktop
- How to use Cached Exchange Mode with XenApp and XenDesktop
(I really need to be a little more creative with these titles)
As we saw in these blogs, when you start deploying Office 365 to your users, Cached Exchange Mode becomes more important if you want a good user experience. But what about other items within Office 365? What about Microsoft Lync? What about Microsoft Lync in an RDS/VDI environment?
I didn’t know. I, of course, have heard and seen the marketing materials about how the Citrix Optimization Pack for Lync should help the experience, but I wanted to see for myself. And I wanted you to also see.
A few things I find interesting with the optimization pack
First, it works for Lync 2010, 2013 and Online servers. As you start looking at deploying Office 365, it is very easy to see the value of a Lync Online implementation. With the Citrix optimization pack, you can still achieve the same benefits you would get with an on-premise deployment like Lync 2010 and 2013.
Second, it supports any type of XenApp/XenDesktop deployment including published applications, shared desktops, non-persistent desktops and persistent desktops.
And finally, it demonstrates another way that Citrix continues to extend the Microsoft platform.
The following provides more details on Deploying Office 365 on XenApp and XenDesktop
From the virtual mind of Virtual Feller
A little bit of knowledge can save you a lot of time (or even an arm).
As I mentioned previously, I’ve been building a new desk for my wife. For this particular project, I drew the entire desk to scale in a CAD program. The drawings were detailed to the point that they included the depth and width of the dados and rabbets (not the animal hopping in my yard). I wasn’t always this detailed. Years ago when I started woodworking, I would oftentimes just wing it. I would have no plans, no dimensions; only an idea in my head for what I wanted to build. I would eventually succeed, but it cost me in wasted lumbar and time because I would cut a board to short as I forgot to include an extra ½ inch length for the dado. With this particular project, because I took the time to draw it out to scale, the entire build went smoothly and with no wasted lumbar.
The same thing happens in IT when we try to implement something new. We oftentimes don’t think through the solution enough to come up with a solution that will align with our circumstances. Let’s think about the discussion with Outlook and whether or not to implement Cached Exchange Mode. If we use Office 365 as our Exchange Server but still implement the native Outlook client on a XenApp server, we would most likely recommend enabling cached Exchange mode.
I have some concerns with ending it there. With Office 365, every user is granted 50GB of mailbox storage. If I use Cached Exchange Mode, then I will have to accommodate 50GB of storage space for every user. This will break my storage bank. Plus, I personally find it crazy to keep a complete copy of that mailbox in two places.
- Download the Microsoft Office Administrative Template files for Office Customization (Group policy)
- Set the Sync Settings policy to limit synchronization to 3 months.
This will limit the size of the cache file by only caching the last 3 months. Most users only access emails that were sent/received within the last 3 months. Anything older are still accessible, but via online mode only. In online mode, the access might be slower, but the frequency of users accessing those files is extremely small so why waste valuable resources keeping them local.
My other concern is where do I store my cached file? In the blog “When to use Outlook Cached Exchange Mode on XenApp and XenDesktop?” we already said that a network share is the best option due to the non-persistent nature of XenApp and XenDesktop pooled desktops, but where?
Personally, I prefer the user’s profile directory and not their home drive. If a user sees a file in their home directory they don’t recognize, they will end up deleting it (I know I do that). I don’t want the users to physically manipulate that file. If the file is in their profile location, it becomes more difficult for the user to delete the file as they typically don’t have Explorer access to this location.
- Decide where in the profile path to store the Cached Exchange Mode file (.OST) file.
- Use the Microsoft Office group policy template to set the Default Location for OST Files
This now brings us one more question; should we leave the OST file on the network share and access it via the network or do we sync the file to the virtual desktop and access it locally? I believe that by keeping the file on the network share, we simplify the environment and put less strain on the physical servers hosting our virtual XenApp and XenDesktop machines. Plus, test data I’ve seen shows this to be a perfectly acceptable solution, especially when the file server is configured correctly with at least SMB 2 and the file server resources are monitored appropriately, which we should already be doing.
- Utilize Citrix Profile Management
- Set a policy for Profile Management that excludes the folder containing the OST from being copied to the XenApp and XenDesktop hosts.
- Utilize at least SMB 2 on the file server and monitor appropriately
White Paper Reference: Deployment Guide: Office 365 for XenApp and XenDesktop
Blog Series Summary:
- Part 1: Is Outlook Cached Exchange Mode on XenApp and XenDesktop supported?
- Part 2: When to use Outlook Cached Exchange Mode on XenApp and XenDesktop?
- Part 3: How to use Outlook Cached Exchange Mode on XenApp and XenDesktop?