If you have paid any attention to any articles relating to desktop virtualization, you will quickly see claims like:

• Will Windows 7 fuel desktop virtualization adoption
• How desktop virtualization eases Windows 7 Migration
• Windows 7 Drives Desktop Virtualization
• Windows 7 and Desktop Virtualization: The New Tools
• Windows 7 - The Desktop Virtualization Catalyst 

 
I could go on, but you get the point. The major thought is that Windows 7 and desktop virtualization go hand-in-hand, but how do you get there?  You are not only migrating the OS but you are also migrating to a virtualized desktop operating environment.  Is this too much change for an organization?  
 
NO.  This is the perfect time to make the move.  Think about it this way, we have the opportunity to start with a clean slate.  We can define the new operating system that completely aligns with the organization's policies.  We can provide an environment that self heals and is optimized each and every time a user connects.  But in order to achieve these benefits, we have to design the environment correctly.  We need to focus on
•    What do we include in our base desktop image?
•    How do we deliver the operating system to our end point (which might be a physical or virtual desktop)?
•    How do we integrate applications into the mix?  
•    What are the recommendations for allowing users to personalize their environment without impacting the business?
•    What are the best practices for providing a great user experience for any user over any connection?
 
These are some of the topics being presenting in this week's Microsoft TechNet broadcast focusing on "Accelerating Windows 7 Migration with Citrix and Desktop Virtualization"
 
The show starts on Thursday, November 12th at 1PM Eastern time and you can register here

Daniel - Lead Architect - Worldwide Consulting Solutions

• Twitter: @djfeller
• Desktop virtualization information: Ask the Architect - Next-Generation Desktop site
• Questions - Then Ask The Architect

I got an interesting item in my inbox from a friend who was speaking with VMware about their VDI solution.  He asked me if the information VMware was telling him was true. He was especially curious because he knew I wrote the Citrix XenDesktop Enterprise Designreference architecture that VMware was referencing to talk about how much better View was. VMWare's approach is laughable.  They are taking a detailed consulting design document  and trying to compare it to the VMware View reference architecture, which if you read it like I have (wasted 2 hours of my life), you will quickly see it is high-level and full of marketing spin and provides no insight.  I, on the other hand, was trying to provide all of you in the community with insight into how to design a large, and complex customer environment with XenDesktop.  Anyways, I told him the angle they were using and he thought it was ridiculous.  I was going to leave it at that, but I've been seeing and hearing more about it from others so I thought I would provide all of you with the same information.  Let's break it down: 

Scalability:

• Misconception: VMWare says that XenDesktop has poor hypervisor scalability. They say that on a 16 core server XenDesktop can only support 40 users (3 users per core). 
• Truth: The XenDesktop reference architecture for the hosted virtual desktops is 8 cores, not 16.  In the design phase, we estimated 40-50 VMs per server, which averages to 5-7 virtual desktops per core.  We were a little conservative as we were not sure how the unique applications would impact the system.  But you can look at Project Virtual Reality Check scalability white paper to get a good comparison of XenServer and ESX.  Although the design VMWare references was for XenServer, the same estimates would have been used if the hypervisor was running ESX.

Storage:

• Misconception: VMware likes to say that XenDesktop is a storage pig in that we need a lot of storage associated with each virtual desktop. 
• Truth: This particular design had a requirement to keep a few system items persistent across workstation reboots so we recommended the creation of a local, persistent disk of between 3-5GB to store items like event logs, performance metrics, antivirus definitions, etc.  This is not NAS/SAN storage; it is the storage on the physical XenServer.  Think about it. You buy an 8 core server, install XenServer, which is small, and the rest of the local storage is wasted.  We utilize that for the persistent store of the virtual desktops.  This means we cannot do XenMotion on the virtual desktops, but most customers I've spoken to do not have this requirement.  After looking at VMware's reference architecture I don't see any level of detail as to the amount of storage they require.  I wonder why not. 

Workloads:

• Misconception: VMware states that they can get more users on a hypervisor than we can.
• Truth: This is all around scalability tests, which I'm not a fan of.  I can easily find you 5 tests that show XenServer is better and another 5 that shows ESX is.  The VMware reference architecture had users connected for 14 straight hours, seems like a long workday to me. I have a question for VMWare: What company did you create this architecture for where users would work for 14 hours? Please tell me as I do not want to work there.  As we all know, the most typical system hit is during startup and logon. So by expanding the session time from a few hours to 14, the overall average utilization rates can be significantly lowered, thus providing an inaccurate estimate to the hardware
• Truth: The Citrix Reference Architecture made estimates based on the applications and expected real user workload, not simple apps and 14 hour workdays.  VMware's reference architecture was based on standard scalability samples shown below. If this was an actual user workload, I totally want to work for that company because that job looks so easy:
  • Microsoft Word - Open/minimize/close, write random words/numbers, save modifications.
  • Microsoft Excel - Open/minimize/close, write random numbers, insert/delete columns/rows, copy/paste formulas
  • Etc

RAM:

• Misconception: The amount of RAM that VMware recommends in their reference architecture is nuts.  They say they can get 96 users on a server with 96GB RAM.
• Truth: If you subtract the hypervisor overhead you are looking at "USABLE" RAM of about 800MB per virtual desktop.  I say usable because ESX has probably enabled memory ballooning.  It is true that XenServer does not have memory ballooning, but I would recommend customers disable this feature for virtual desktops.  On XenDesktop projects that use the ESX hypervisor, I also recommend disabling this feature.  Users and desktops are more dynamic than server workloads, meaning the RAM consumption is going to fluctuate greatly.  If RAM starts to decrease to the critical threshold, what happens to the hypervisor?  It must free up memory by paging this to disk.  Isn't this an intensive system process that consumes more resources at a time when resources are scarce?

End Points:

• Misconception: Vmware talks about the end points and only focus on thin clients and end points that we can repurpose with a Linux OS or locked down Windows OS. What about the newer end points that organizations have already spent money on? 

• Truth: With VMware View you still will connect to the VDI desktop and idle your local hardware. Seems like a lot of wasted desktop resources to me.  XenDesktop, on the other hand, allows you to re-use those desktops as a local streamed virtual desktop. Don't be fooled, there is more to desktop virtualization than VDI.

Provision:

• Truth: Closer to the end, the reference architecture talks about the time to provision X number of linked clone desktops.  I'm not sure if this is automated or if an admin has to do each desktop one-by-one. I'll give VMware the benefit of doubt here and say it is automated, but taking 161 minutes (2 1/2 hours) to provision 500 virtual desktops seems long to me.  I personally don't think this metric is important, even though XenDesktop is measured in seconds.  If it is automated, you do all of this in the build out phase and not in production. So the time it takes is irrelevant to me. Why did they choose to include it? No idea

So my advice to anyone who is still reading this blog... Take everything you get with a level of skepticism.  Do your own due diligence and look at the details to see if things were glossed over or if an in-depth analysis and design was completed.  That recommendation even includes the materials I post.  I try to be open and honest in my blogs, white papers, TechTalks and videos, but I am a little biased to Citrix because they pay my bills. 
If you want to discuss more, or have further questions, then Ask the Architect

Daniel - Lead Architect - Worldwide Consulting Solutions

• Twitter: @djfeller
• For the latest desktop virtualization information visit the Ask the Architect - Next-Generation Desktop site
• Questions - Then Ask The Architect

My role allows me to speak with many different people (customers, technologists, coworkers, administrators, etc). I've been able to see presentations comparing the different desktop virtualization solutions out there.  One of the problems I see is that many of the solutions only focus on one aspect of desktop virtualization, and that is the VDI model. 

VDI is only one aspect of the entire desktop virtualization solution.  This is a concept that many fail to comprehend. For example, I attended Gartner ITExpo last week and was amazed at how many people I talked to only thought about the VDI scenario (you know VDI, allowing you to have a remote virtual desktop running on a hypervisor in the data center).  When I talked to people about the other options, I could see their eyes light up.  

If you are reading this and only know about the VDI version, the I suggest you take a look at FlexCast to get a better understanding at all of the different options out there (FYI, even the CIO magazine identifies there is more to desktop virtualization than VDI). But in a nutshell, here's the deal... desktop virtualization includes:

1. Hosted shared desktop
2. Hosted VM-based VDI desktop
3. Hosted blade PCs
4. Streamed local desktop
5. Virtual Apps to installed desktops
6. Local VM-based desktop

I want to focus on the Streamed local desktops scenario. This is the one that really got people's attention at Gartner.  Why?  Because most organizations do not do a big bang effect of replacing their end point devices. Instead, most have a rolling lifecycle where each year a portion of the endpoints are upgraded and over the course of 3-4 years the entire desktop environment has been upgraded. Once the process completes, it starts over, never ending.  
 
Let's now say you are embarking on a desktop virtualization project.  It seems like  a waste of resources and money to idle those desktops that are only 1 year old. They are powerful enough to run Windows 7 and the latest applications, so why would we not use the hardware we already have?  This is where the streamed local desktop comes in. It uses the same XenDesktop infrastructure, the same OS images, the same application layer and the same personalization layer.  The only thing that changed is the hardware layer.  
 
As money always seems to speak louder than words, think about it this way: If you have 3,000 desktops and they are replaced every 3 years on a rolling cycle, that means 1,000 of those desktop are less than 1 year old.  If you estimate 50-100 virtual desktops on a hypervisor (XenServer, ESX or Hyper-V) then you need 10-20 fewer physical servers, which is a substantial cost savings (and even greater if you are using a hypervisor that costs money).

So I encourage all of you to not think about the VDI-only solution but instead to look at your environment as a whole. Chances are you will see that VDI-only might work for you, but probably isn't the best way to run your business. Think about it this way... You can create documents in Notepad, but would you really base your business on a solution that only does one thing, or would you use a more complete solution like Microsoft Word that gives you options?  

Daniel - Lead Architect - Worldwide Consulting Solutions

• Twitter: @djfeller
• For the latest desktop virtualization information visit the Ask the Architect - Next-Generation site
• Questions - Then Ask The Architect

I have recently returned from Gartner ITExpo in Orlando.  It was quite interesting, especially some of the thoughts they had around the economy and impending recovery.  One thing stated during the conference should not be a surprise to anyone, during a recession you save your money by not taking on any new projects. By not implementing beneficial upgrades to your systems. By not delivering newer versions of your applications to users.  

This does have the benefit of saving money, but this can only go on for so long.  Eventually, your competitors will stop saving and start expanding. Where will you be?  

We are at a very unique inflection point that can have lasting ramifications to your IT infrastructure.  We are:

1. Coming out of a recession. We are very likely to see a slew of projects going across the tables to install this or upgrade that. So it is looking like the next 1-2 years will have IT taking on a lot of tactical projects.
2. Getting ready for a major operating system upgrade with Windows 7. Whether you are ready or not, Windows XP doesn't have much time left, and most people are skipping Windows Vista. How are you going to migrate?
3. Able to do things that were unheard of in previous years. We can virtualize a massive server into small chunks, we can do the same to an operating system, applications, and the user's personalization layer and deliver it to any type of device imaginable (phones, PCs, MACs).  

So what does this mean? It means you can continue running your environment like you have for the last 10-20-30 years, or you can ask yourself one simple questions: "Is there a better way?"

We have a very profound opportunity to correct the issues of the past.  And if we do it correctly, the resources required to update, maintain and support our environment will greatly reduce.  So when the next recession comes around, your organization will be ready with a fast and streamlined approach towards maintaining your IT environment as well as continuously providing new services.  But where to begin?  

Take a look at your infrastructure. What area requires a lot of time and resources to maintain?  Probably your desktop environment.  Let's investigate and fix it, but let's do it right.  Make sure you look at all aspects

1. The users: what do they need and how do they work
2. The devices: what type of devices, what capabilities
3. The locations: where are they located, what bandwidth pipes are available
4. The applications: how many are there, what level of dependencies do they have, who uses what

This information is critical.  This is what you need if you want to do the desktop virtualization solution correctly, from day 1.  Is it going to be something you can do in 10 minutes? No. Is it something you can implement in 1 hour? No. Why?  Because we are taking something that is seriously complex and trying to create a solution that can scale and simplify our lives. So during the next recession, we won't have to stop delivering new services, but can forge ahead and beat your competition with an entirely new delivery solution.  
Daniel - Lead Architect - Worldwide Consulting Solutions

• Twitter: @djfeller
• Ask the Architect - Next-Generation site
• Questions - Then Ask The Architect

We have had a great discussion going about user-installed applications and the need/risks associated with this type of solution. One of the comments I received in favor of allowing users to install applications was around Firefox. For those of you who don't use Firefox, there are thousands of add-ons a user can install to customize their browser experience. I personally have about five different add-ons configured with my Firefox implementation.

Now I've been advocating the need for IT to have a process in place that can handle the expansion of the application pool for the users as needed by:

1. Taking user requests for new applications/tools
2. Validating the need
3. Delivering in a timely manner

This is all well and good until we get to the topic of these add-ons. I don't expect any IT organization to have a requirement to support the add-ons. There are thousands of them. Think about it, do you really expect your IT to be spending time messing with these add-ons? And what would it look like for the user? A Firefox application with thousands of add-ons? CRAZY (I do wonder at what point that app would crash. Maybe need a MythBuster episode on it)

All of the sudden, I had a very enlightening experience. I just got my new XenDesktop 4 environment built. I went in an started to personalize my environment, including my 5 Firefox add-ons (remember I'm using pooled desktops from a single base image with roaming profiles). The next day, when I logged onto my virtual desktop, my Firefox starts up and BAM all of my add-ons are still there?!?!

I did some investigation into this. Well, this is an example of an intelligent application design. The add-ons are located within the user's profile (the roaming portion). User's are able to customize the Firefox application without any special tools/utilities. The discussion about Firefox and the add-ons is now a non-issue as the application manages this for us.

So, 1 application down, only 999,999 to go   The point is you need to test before deciding if something will or will not work.

Daniel - Lead Architect - Worldwide Consulting Solutions

• Twitter: @djfeller
• Ask the Architect - Next-Generation site
• Questions - Then Ask The Architect

Now that XenDesktop 4 includes numerous ways to deliver virtual desktops, (Greater description of the FlexCast technology), we need to take a look at how those applications are integrated into:

1. Hosted/Shared desktops
2. Hosted VM-based desktops (VDI)
3. Hosted Blade PC desktops
4. Local Streamed desktops
5. Virtual Apps to Installed desktops
6. Local VM-based desktops

(BTW, this also aligns with a CIO magazine article on Desktop Virtualization's 5 most important flavors) 

And this is a question that Cole M sent into Ask the Architect.  As always, the short answer is "It Depends", but I try to do a little better than that in the latest Ask the Architect Video. 

Daniel - Lead Architect

Follow me on Twitter: @djfeller

Follow the latest in desktop virtualization

Send Desktop Virtualization questions to: AskTheArchitect@Citrix.com

Did Brian Maddenmake a valid point about VDI and desktop virtualization that most people missed?  

Brian discussed a VDI€‰challenge, user-installed applications, which was in response to a desktop virtualization postI recently wrote about the same topic. Brian's premise was that each user needs to be able to install their own applications and should be allocated 2 virtual desktops:

1. First one locked down by IT
2. Second one is open where users would have full control

When I first read this I thought, well yes that would work but talk about a nightmare situation.  Many of the comments posted were extremely funny and I encourage you to read them (especially the one that said "Steve Ballmer must be smiling"). But seriously, if you think about what Brian is saying, it does have validity, if done correctly.

Sure there are tools/solutions that can allow users to install their own applications but we should not open the flood-gates and allow users to install whatever they desire. Not only are you looking at a management nightmare, but you are also looking at security risks, legal risks, and productivity risks.  What I can see happening is an environment that is suited to what the user needs. Something like the following...

1. Each user gets their IT-delivered desktop that includes all known corporate applications.  These applications are delivered into the desktop either through installation, streaming or hosting.  Users will inevitably try to install apps/plugins/tools into the corporate-delivered desktop.  The app will work until the user reboots (assuming shared image mode).  Once rebooted, the app is gone and the cycle starts again.  If the application is a new business requirement, there must be an IT process in place where users can request a new application. IT must have SLA's in place that allows them to assess the validity of the request, profile the application and deliver it to the virtual desktop in a timely manner (a few days to a week). Until the application is ready for delivery by IT, the user can continue to install or request a second virtual desktop (step 2 below).
2. Each user has the "ability" to self-service a second virtual desktop that can be used as a "playground".  Many power users have a need to install, test, evaluate different tools to make their jobs easier. Most users only need these applications for a few days or weeks, at least until a project is complete. Other users only need the application until IT is able to properly deliver the application into their corporate-delivered desktop.   This is where a second virtual desktop, i.e. a self-service desktop, could be requested. This is something like Brian recommended, 2 desktops. But the second desktop is only used if it is needed and requested through a self-service process. Of course because IT does not know what users will do to this desktop, proper security precautions must be taken into account.  With this option, users would have the ability to:
   1. Select the OS
   2. Select the life of the desktop (days, weeks or months)
   3. In the background, workflows are initiated that creates a new desktop, assign it to the user, and allow changes to be stored within the writable, user image.  When the timeframe expires, the desktop is deleted from existence.  

This option solves many of the challenges users experience in a virtual desktop world.  How to install temporary applications. How to use a new business application until IT is able to assess and deliver it properly.  

The point is that we must understand the users and their needs.  Most users can get along perfectly well with the applications delivered from IT.  But a sizeable portion of the user group needs autonomy, freedom, experimentation... A Playground. The one size desktop does not fit all.  Some user's might have two different desktops, others only 1.  We need to change the way we think about delivering desktops to users.  And in order to meet user expectations, we need systems (technical and process oriented) in place that can accommodate the users in a timely manner.

• Twitter: @djfeller
• Ask the Architect - Next-Generation site
• Questions - Then Ask The Architect
• See me talk about designing your XenDesktop solution on Citrix Live

Daniel - Lead Architect - Worldwide Consulting Solutions

With so many articles flying around about desktop virtualization and VDI, have you ever seen or heard of anyone actually implementing this solution? And even if you have, I bet you, like me, have many questions to ask.

Well, I've had the opportunity to sit down with Sandy Kingdon, a Dynamic Desktop architect for CSC. Sandy is working on a large XenDesktop implementation and I was able to speak with her about it. It is an interesting discussion and architecture in that it uses Citrix XenDesktop, VMware ESX and AppSense User Environment Management

• Current Capacity: 1,000 users
• End of Year Capacity plan: 10,000 users
• End of Project Capacity plan: 40,000 users
• Virtual desktop specifications: Based on customer analysis and experience
• Antivirus requirements and updates design
• Application integration with the user desktop images
• User-installed applications requirements and design
• End-point device configurations

This discussion was focused on the architecture, design considerations and experiences.  I can imagine as this project continues to grow to their 40,000 user goal we can have additional discussions on lessons learned, tips/tricks, etc. 

If you want to hear more and see what else we have going on around desktop virtualization architectures, I recommend you visit the Ask the Architect site. Also, if you or someone you know who is currently or already completed a desktop virtualization implementation, I'd be eager to hear from you.

• Sandy Kingdon (CSC) Podcast
• Ask the Architect - Next-Generation site
• Questions - Then Ask The Architect
• Twitter: @djfeller

Daniel - Lead Architect - Worldwide Consulting Solutions

Some of the questions I've received lately is how to design a large-scale, enterprise XenDesktop architecture.  We all can attest that most systems put into place become much more difficult to architect as the number of users increases.  I'm not talking about Citrix products, I'm talking about any product.  Which one do you think would be more difficult to design:

• A 100 user (insert your own product here) environment
• A 10,000 user (insert your own product here) environment
• A 50,000 user (insert your own product here) environment
  

Most of you will probably agree that it gets quite a bit more difficult as the number of users increases.  And if we do a typical type of design, I would tend to agree, but I'm thinking we can simplify this so even the 10,000 and 50,000 user XenDesktop environment can be as easy as a 100 user deployment. 

Many of you are probably thinking, this guy is full of it, he is too pie-in-the-sky for me.  And when I first started thinking about this simplified architecture, I tended to agree. But as I've continued looking into this and discussing with other architects, I've come to the realization that I might be on to something here.  See for yourself in the following video.  I plan on posting additional videos around this concept in the future to show/demonstrate how it would work.  But for now, I bring to you the Pod concept (and don't forget to leave your comments) 

Daniel - Lead Architect

Follow my Blogs: http://community.citrix.com/blogs/citrite/danielf

Follow me on Twitter: @djfeller

Send Desktop Virtualization questions to: AskTheArchitect@Citrix.com

Watch previous Ask The Architect Videos at: http://www.citrix.com/tv/#video/1063 

On August 11, 12, and 13 we delivered a Ask the Architect TechTalk series focused on desktop virtualization and VDI.  The three part series focused on:

1. Deciding between VDI and Terminal Services
2. Designing a desktop virtualization solution with XenDesktop
3. Migrating users from physical devices to virtual desktops
   

During the TechTalk webinar, we received many great questions but were unable to answer them in the time allotted. This blog post will attempt to provide those answers. But first, I wanted to let you know where you can get access to the recorded webinars and the PowerPoints.

Part I: Deciding between virtual desktops (VDI) and virtual applications (Terminal Services)

• Recorded Webinar
• PowerPoint

Part II: Designing a desktop virtualization solution with XenDesktop

• Recorded Webinar
• PowerPoint

Part III: Migrating users from physical devices to virtual desktops

• Recorded Webinar
• PowerPoint

And as always, you can follow me on Twitter @djfeller.  And now to the Q/A session...
Part I: Deciding Between VDI and Terminal Services:

Q: What would be your recommended platform if streaming video or audio is needed to be delivered to a structured user environment?

A:  For structured users, we typically recommend the shared, server-based desktop but you bring up an interesting design requirement.  Typically when you hear people talk about some of the value-adds with XenDesktop, the focus is on the multimedia experience.  Well, many of those multimedia optimizations are also present within XenApp.  Now, if you have used XenApp in the past, multimedia was  a little sketchy, but I encourage you to take a look again.  There have been some impressive enhancements made, which you can see as part of the XenApp MythBusters series (http://community.citrix.com/display/xa/XenApp+Myth+Busters)\\

Q: We want to get away from running around the entire building updating all of our different applications constantly. So we don't want anything local. How do I do this?

A: For those users who require desktops, you would want to stream the entire desktop to the end point device or use a desktop appliance and connect to a hosted virtual desktop. This would eliminate the need to install items locally and allow you to manage everything centrally. 

Q: How do we prevent users from updating their streamed desktops?

A: This is a challenge for any desktop operations environment.  When users install applications onto their desktop (this could be new apps, windows updates, IE updates/plugins, etc), the support costs climb quickly because these apps have not been validated by the IT team.  With XenDesktop, we have users receive their desktop from a single streamed image.  If a users makes changes to the desktop, those changes will NOT remain with the desktop after a reboot. Rebooting the XenDesktop desktop results in a brand new, clean desktop environment. 

Part II: Designing a Virtual Desktop Solution with XenDesktop

Q: I've been considering VDI for a while but our branch environment only has 512kb circuits.  How could this possibly work in this environment?

A: The branch office situation will have an impact on the type of virtual desktop you can deliver.  For example, I would not recommend using a streamed desktop for those devices unless you install a local Provisioning Services server within the branch.  If that is not an option, you also have the ability to allow the branch users to utilize a hosted virtual desktop that runs within the data center. The branch office users would connect to the hosted virtual desktop over Citrix's transport protocol, which is extremely lightweight.  The latest scalability numbers I saw were around 15kbps (average per user). This is only an average. If you are doing a lot of multimedia operations, then I would expect that number to increase, but if you are only doing textual operations that number would likely decrease. 

Q: What is best faster processors or more memory

A:  Depends on the component.  # The XenServer that delivers the hosted virtual desktops needs both in equal amounts.  If your virtual desktops are 2GB RAM, then on a 128GB XenServer you would only get about 50-60 virtual desktops (all because you will run out of RAM).  You need to select your processors so that they are fully utilized at the same time RAM is fully utilized. 

1. XenDesktop Controller: CPU intensive during logons and hosted virtual desktop startup (RAM and Network underutilized)
2. Provisioning Services: Network intensive. RAM is also used for file caching the vDisk images so more read requests are services by RAM instead of by disk. CPU is underutilized
   

Q: What's the best way to handle printing services for mobile and remote users.

A: As we are unsure what type of printers a remote/mobile user will have mapped on their local device, it is typically best to utilize the auto-creation of the user's printer and to use the universal print driver This allows the user to see their local printer within their hosted virtual desktop and to not be required to install the actual print driver.

Q: We package software with Wise Package Studio....what kind of support/compatibility will we get if we go to VDI

A: If you want to install the applications within the virtual desktops, the Wise packages are still viable options. However, if you are wanted to stream the applications into the desktop, then you need to create an application profile with the XenApp tools, as application streaming is different than application installing (which Wise does).

Q: Isn't it more efficient to allow the networking devices to compress the data stream rather than utilize CPU resources?

A: In general it is.  Depending on your environment and design, there is defiantly an option to integrate a network compression solution to compress the traffic, thereby offloading these processes from the server's CPU.  The Citrix Branch Repeater is able to do this for many different protocols, thereby helping to improve the overall user experience. 

Q: What is the best way to handle print traffic, I am thinking of things like should this be included in base build, should you use a specialist application to throttle bandwidth usage etc.

A:  XenDesktop actually contains a policy that allows you to throttle bandwidth for different types of communication, including printing.  So for slower connections, you can tighten the screws on the printing traffic so this doesn't disrupt the user experience.

Part III: Migrating Users from Physical Desktops to Virtual Desktops

Q: What type of profiles do you recommend.

A: You will need some type of profile that is capable of storing the user personalization settings across many different devices. This means you will need a roaming profile solution as the basis of the environment.  In XenDesktop (if using pooled desktops), a user will use a different virtual desktop everyday. Also, any changes made to the actual desktop are lost upon reboot.  During logoff, we need to upload all user settings to a centralized location that all virtual desktops can access.  When the user logs back into another virtual desktop, their settings are copied from the central site to the virtual desktop, thus personalizing it.  Unfortunately, roaming profiles have their own issues/challenges that can be mitigated by using a profile management solution like the Citrix Profile Management. 

Daniel - Lead Architect - Worldwide Consulting Solutions
Follow me on Twitter: http://www.twitter.com/djfeller
Follow me in the Blogs: http://community.citrix.com/blogs/citrite/danielf

Do you have a desktop virtualization design or architecture question? Then Ask the Architect

What is it?

Many times when people are looking at a solution or trying to create a design, they have a question as it relates to their environment.  Although there are numerous documents and best practices on the Citrix knowledge base, many of these are based on a "recommended architecture" which typically does not look like many of your environments.  This is where Ask the Architect comes in.  If you have a question regarding your desktop virtualization project, send an email to AskTheArchitect@Citrix.com.  (HINT: Make your questions short and to the point.)  Based on your email question, we will strive to find you an answer and post a video on CitrixTV (because many other people will have similar questions).  The answers will be brief and to the point, less than 5 minutes (we don't want to bore you and we still have lots of other things to do too).

What it is not?

The desktop virtualization Ask the Architect is not a way to get a complete desktop virtualization design. For a full-scale design, I would recommend you get in touch with Citrix Consulting, who have already been instrumental in designing some of the largest desktop virtualization solutions. It is also not a troubleshooting forum, as there are already many forums for those items (plus I've never heard of any Citrix products having issues )

Who is Ask the Architect? 

This is a big question. You don't want to send in an email and have it answered by a marketing or sales person who tells you to buy another product. You want someone who has designed complex solutions.  This is why Ask the Architect is not 1 person, but many.  Based on the question submitted, the most experienced Citrix Architects from our Consulting organization will create an Ask the Architect video post and submit it to CitrixTV for all to see. 

How to Get Stared?

Start watching the Ask the Architect series on CitrixTV.

• Episode I: VDI and PVS for Multiple Remote Sites: http://www.citrix.com/tv/#video/882  

Email: AskTheArchitect@Citrix.com
Note: This blog was brought to you from a hosted XenDesktop virtual desktop with a XenApp-streamed Firefox browser.  

Daniel - Lead Architect - Worldwide Consulting Solutions
Follow me on Twitter: http://www.twitter.com/djfeller
Follow me in the Blogs: http://community.citrix.com/blogs/citrite/danielf