Sizing XenDesktop 7 App Edition VMs

In the Mobilizing Windows applications for 500 users design guide, we made the recommendation to allocate 8vCPUs for each virtual XenDesktop 7 App Edition host (formerly known as XenApp). Spreading this out across a server with two Intel Xeon E5-2690 @2.9GHz processors and 192 GB of RAM, we were yielding about 200 users per physical server and roughly 50 users per virtual server. Of course, the design guide is the end result of a lot of testing by the Citrix Solutions Lab. During the tests, we had the Solutions Lab compare many (and I mean many) different configurations where they … Continue reading Sizing XenDesktop 7 App Edition VMs

Just the Apps

We get so excited with the thought of VDI, we often forget to take a step back and focus on what we are trying to do. Here is a recent example… We need to find a way to get an application to our users. Our first problem is that many of our users are not local, which makes installation a challenge. The second problem is that many users want to use the application on non-traditional devices (tablets) because it is more convenient. We’ve heard that VDI can help us with this. What will it take? First, this is a good … Continue reading Just the Apps

Control layer in the XenDesktop 7 Blueprint

Control, control, you must learn control! – Yoda The control layer is about creating a single, cohesive foundation for the solution that supports the user-layers (users, access and resources). You can NOT do the control layer if you haven’t defined your user layer, access layer and resource layer. The control layer of the XenDesktop 7 blueprint is subdivided into Access Controllers – responsible for providing the connectivity to the resources as defined by the Access Layer Desktop Controllers – manage and maintain the virtualized resources for the environment Infrastructure Controllers – standard infrastructure components The point of the control layer … Continue reading Control layer in the XenDesktop 7 Blueprint

Extending the blueprint to focus on your resource layer

Users Access Resources The Resources layer is the next stage of the blueprint. Resources are the desktops and applications that we want to deliver to each user. This is also where many people get stuck because the perception is that there are a lot of options. There can be a lot of option until you start looking at it from a user group per user group perspective. Plus, when we look at the resources we want to deliver, we focus on a few core areas. If we look at our blueprint, we can break this down into 3 different user … Continue reading Extending the blueprint to focus on your resource layer

Blueprint for Accessing your desktops and apps

Based on the XenDesktop 7 Blueprint, we have already created a definition of our user layer. The next step is to define how users will access their environment. Just like a house, you have doors and locks. In order to gain entry, you have to have the right keys for the right door. Defining the access layer is basically focusing on the required access policies for internal vs. external users. What’s an access policy? It is simply defining the following 4 items: Authentication point: Where do users first enter their credentials. Typically, this is either StoreFront or NetScaler Gateway. Authentication … Continue reading Blueprint for Accessing your desktops and apps

Begin your XenDesktop blueprint with your users

The users matter first. This is why we have a blueprint for XenDesktop 7 because we want to avoid starting wrong. We want to make sure that the first thing we focus on are the users. Think about it this way, when building a house, one of the first things you have to figure out is what type of a house do you want/need (bungalow, cottage, mansion, split level, etc). Sometimes, you might determine that you don’t need a house and end up with a condo or apartment. To make this decision, you have to look at yourself and understand … Continue reading Begin your XenDesktop blueprint with your users