Entries tagged with vdi - TechNet Edge

Concept of Desktop Virtualization [Concept of Desktop Virtualization]

yung — Wed, 21 Oct 2009 21:21:00 GMT

The traditional desktop computing model, as shown in Fig. 1, has been one where the operating system, applications, and user data and settings are bonded to a single computer. We will buy a computer either with OS and some applications pre-installed, or apply a hard disk image with targeted OS and selected applications to the computer hardware. Once a computer is deployed, a user can then log in the system, customize the environment, run applications, change settings, create data and files. This model is straightforward and easy to understand. With respect to desktop deployment, this means that the OS, application execution/presentation and user data are all self-contained within a single device. This model has the advantage of simplicity because it leverages well understood technologies that ship with Windows. In addition, because a PC with this model is configured to be completely self-sufficient, this solution is well-suited to mobile use. However, the tight binding between the various layers may not be a preference for all scenarios. This model has its limitations.

The tight couplings between each layer provide efficiency; they also introduce dependencies, hence complexities. And these complexities make it difficult for users to move the applications, settings, and files from one PC to another in case of upgrades or a lost or stolen laptop. When exemplified by thousands of desktops and laptops, as many enterprises do, the management of these laptops and desktops becomes a major concern. As mobile work force and the number of branch offices continue to grow with the proliferation of Internet and the advancement of networking technology, the work environment and data access patterns of information workers have become dynamic and been rapidly evolving. The long term maintenance associated with computing resources based on the traditional computing model is becoming cost-prohibitive for many companies, while impairing the IT’s ability to quickly prepare for or respond to a business opportunity.

Desktop Virtualization is the process of separating, or more precisely isolating, out these individual components, and managing each one separately. Fig. 2 shows by isolating these components, we can now abstract and virtualize the computing resources. Each layer can then reference a resource in other layers based in the abstraction or virtualization boundary and without specifying the specifics of how a referenced resource is configured within its host layer. Over all this reduces complexity and improves PC and application management.

When it comes to virtualization, not all solutions are equal. Microsoft has developed a number of virtualization solutions to address specific issues as depicted in Fig. 3. There are times a virtualization solution may not be cost-effective while offering deployment flexibility. It is crucial to recognize that and architect a virtualization solution accordingly to produce maximal business benefits.

in reply to Concept of Desktop Virtualization

Microsoft VDI Part II - Virtual Desktop Configuration [Microsoft VDI Part II - Virtual Desktop Configuration]

Matt McSpirit — Mon, 28 Sep 2009 15:11:00 GMT

Microsoft VDI Part II: Virtual Desktop Configuration

Welcome to part 2 in a 3-part series focused on the Virtual Desktop Infrastructure (VDI) capabilities in Windows Server 2008 R2 Remote Desktop Services!

In these videos, Partner Technology Specialist, Matt McSpirit, from Microsoft UK, walks through configuring Microsoft VDI, and in part 2, we walk through the Virtual Desktop Configuration!

You can view the rest of the series, and more, here!

in reply to Microsoft VDI Part II - Virtual Desktop Configuration

Microsoft VDI Part III: Client Side Experiences [Microsoft VDI Part III: Client Side Experiences]

Matt McSpirit — Mon, 21 Sep 2009 15:12:00 GMT

Microsoft VDI Part III: Client Side Experiences

Welcome to part 3 in a 3-part series focused on the Virtual Desktop Infrastructure (VDI) capabilities in Windows Server 2008 R2 Remote Desktop Services!

In these videos, Partner Technology Specialist, Matt McSpirit, from Microsoft UK, walks through configuring Microsoft VDI, and in part 3, we wrap up by taking a look at the Client Side Experiences!

You can view the rest of the series, and more, here!

in reply to Microsoft VDI Part III: Client Side Experiences

Microsoft VDI Part I - Server Side Configuration [Microsoft VDI Part I - Server Side Configuration]

Matt McSpirit — Mon, 21 Sep 2009 07:01:00 GMT

Microsoft VDI Part I: Server Side Configuration

Welcome to part 1 in a 3-part series focused on the Virtual Desktop Infrastructure (VDI) capabilities in Windows Server 2008 R2 Remote Desktop Services!

In these videos, Partner Technology Specialist, Matt McSpirit, from Microsoft UK, walks through configuring Microsoft VDI, starting, in part 1, with the Server Side Configuration!

You can view the rest of the series, and more, here!

in reply to Microsoft VDI Part I - Server Side Configuration

Reducing Desktop Costs Part 2 Virtualizing the Desktop – Tech Focus September 2009

Alan Le Marquand — Wed, 16 Sep 2009 11:11:00 GMT

The question posed in part 1 was Is the cost of ownership of your Microsoft client systems rising? Are you looking for ways to reduce the costs associated with deploying Windows and managing it thereafter?

There are two solutions available to help combat these costs. The first post covered deploying an actual client and the issues that need to be addressed there, this post and the next will cover the potential cost savings using the virtualization options.

So if deploying a Windows 7 client is not an option, then an alternative solution is to virtualize. There are two core options to this. Each has different cost saving benefits. The two options are:-

A complete desktop virtualization
Virtualization of just the applications.

These are in no particular order. The potential cost saving depends on your current environment and what you obviously need to add or change to implement them.

This post looks at the desktop virtualization option and within this concept the first virtualization option is what is often called “Presentation Virtualization”. Microsoft’s technologies for this option is Remote Desktop Services.

Remote Desktop Services, formerly known as Terminal Services, provides technologies that enable users to access Windows-based programs that are installed locally on a Remote Desktop Session Host server, or to access the full Windows desktop.

So what are the advantages and therefore cost saving of this? Basically Remote Desktop Services lets you deploy and maintain software from a central location. Because you install the programs on the RD Session Host server and not on the client computer, programs are easier to upgrade and to maintain, which in turn helps to reduce maintenance costs. Before going into the potential cost saving of this solution, it’s worth looking at these 3 webcasts to expand on the technologies more.

If you’ve watched these webcasts you now know that clients connect to a central resource to gain access to applications or a desktop. Clients do not have to be all local to these servers, the service can be made available beyond the corporate network with services such as TS Gateway and TS Broker service. There is an IPD guide for Terminal Services and a detailed web page that leads you step-by-step through the process of planning a Remote Desktop Service infrastructure. If webcasts above are a bit long there is also a video series on TechNet Edge, this also takes you through 5 steps to install and configure RDS.

So where do the saving come in?

The centralization of software, the applications are installed in one place, makes maintenance and updating easier. It also helps radically simplify the burden of regulatory compliance.
The specification of clients needed to run the software via RDS is lower than clients that have the software installed locally.
You can ensure all clients have access to a consistent suite software regardless of location, thus reducing calls to help desks to install software and the potential lengthy install process of low bandwidth links.
Your data has an extra level of security. RDS can help eliminate data theft if a laptop is stolen or lost.

Before we go further, one last point on RDS. If you’ve read the additional information above and the idea of making applications available via RDS sounds like something that you want to investigate further, then I’d suggest reading the next post in this series on Application Virtualization. For pure application deliver App-V is a better choice – also see the diagram at the bottom of this post.

Next on the Desktop Virtualization front is Microsoft Enterprise Desktop Virtualization (MED-V). MED-V basically enables deployment and management of Microsoft Virtual PC Windows desktops, this is designed to help organizations upgrade to the latest version of Windows even when some applications are not yet functional or supported on this version. The diagram opposite shows the difference between MED-V and APP-V – which I will cover in the next post.

The bottom line to remember about these two solutions is that MED-V resolves conflicts between operating system and Application, App-V at a minimum resolves conflict between Applications running on the same operating system, however it’s potential use is much wider and potential for cost savings much greater.

There is a lot more to MED-V, more than I can cover in this post, plus article linked to the diagram above does a great job going through it in detail.

This post was about desktop virtualization using technologies like RDS, VDI and MED-V. Each solves a different business problem and so in that respect do represent a cost saving to your organization in respect of how you operate today. How you measure the saving depends on how fast a return you are looking for. VDI will potentially save you money, but the saving is offset by the initial outlay. In all the solutions above there is the potential for initial outlay in infrastructure, the level of outlay will obviously lengthen the time before you see potential cost savings.

Next up I’ll cover App-V, and this technology will certainly make you think hard about how you deliver applications in the future and the cost savings that entails.

Windows Server 2008 R2, Remote Desktop, VDI and Virtualization

James O'Neill — Wed, 16 Sep 2009 07:01:00 GMT

With the arrival of Server 2008 R2 the range of choices an IT pro has for delivering an application to users desktops is quite bewildering. In this video we look at the new Remote-Desktop - how it it builds on the technologies we have had, but also how new possibilities to deliver a virtual desktop infrastucture are opened up by the combination of Hyper-V and the new connection broker

Microsoft Vista Desktop Infrastructure (VDI) Licensing and Windows Virtual Enterprise Centralized Desktops (VECD) [Microsoft Vista Desktop Infrastructure (VDI) Licensing and Windows Virtual Enterprise Centralized Desktops (VECD) ]

yung — Tue, 08 Sep 2009 22:31:00 GMT

In TechNet Game-On Tour currently being delivered in the US east coast, I talked about Remote Desktop Services (RDS) and Virtual Desktop Infrastructure (VDI) and got very overwhelming response. It’s indeed an exciting feeling when witnessing desktop virtualization works in a predictable way and behaves as designed. In my conversations with the attendees, one of the frequently asked questions has been the licensing of VDI and I thought to point out some pertinent information here.

The basic Windows Original Equipment Manufacturer (OEM) license with traditional desktops is not designed for use in VDI, since it is bound to the OEM hardware device, with no reassignment rights.

Software Assurance (SA) provides organizations with additional values including the ability to reassign a license after 90 days, upgrading or downgrading to latest versions of the OS, and accessing to desktop virtualization technology in the Microsoft Desktop Optimization Pack (MDOP). Still it does not provide the ability to create desktops dynamically or move desktops across different hardware and storage platforms, etc., i.e. a level of flexibility that a VDI solution needs.

Windows Vista Enterprise Centralized Desktops (VECD) is a new type of license designed to help customers license virtual copies of Windows. It is a device-based subscription, which means the total number of licenses is equal to the total number of devices that access the virtual environment. VECD is an annual subscription, following the SA model. Additional information on Licensing Microsoft Windows for virtual environments is available. Or simply download the VDI Licensing brochure.

VECD:

Allows customers to make as many copies of the OS image as they like, which is helpful when creating dynamic desktops.
Allows customers to move the image onto any combination of servers and storage devices.
Comes bundled with work at home rights.
Comes bundled with Software Assurance benefits.

in reply to Microsoft Vista Desktop Infrastructure (VDI) Licensing and Windows Virtual Enterprise Centralized Desktops (VECD)

Building Sandbox for Evaluating RDS and VDI [Building Sandbox for Evaluating RDS and VDI]

yung — Wed, 05 Aug 2009 19:01:00 GMT

I have just finished developing the content of RDS and VDI to be soon delivered in the Session 3 of the upcoming TechNet events. To minimize the required hardware, both the RDS and VDI demos are to be carried out using one laptop. In this screencast I briefly described how my demo laptop was set up. In upcoming screencasts, I will walk through the steps to manage applications for remote access, integrate RDS components for VDI, and via a browser access a personal or pooled Virtual Machine running in data center without VPN.

in reply to Building Sandbox for Evaluating RDS and VDI

Windows XP to Windows 7 migration - Remediate Virtualize

David Tesar — Wed, 29 Jul 2009 07:01:00 GMT

Giovanni explains the differences between XP-Mode, MED-V, APP-V, and VDI and how these virtualization options can help with remediation of your incompatible applications and migration to Windows 7.

Watch the overview video for Windows XP to Windows 7 migration which links to all 5 videos in the series.

View the XP to Windows 7 migration process diagram which will walk you through the tools and resources available from Microsoft to help you each step along the way.

What Virtualization Means for the Desktop

Dave Morehouse — Wed, 29 Jul 2009 06:59:00 GMT

Brad Anderson and Jeff Wettlaufer are together again, this time for a chat on desktop virtualization scenarios and technologies. Using Brad's whiteboard for illustration, they cover application virtualization, desktop (or hardware) virtualization, presentation virtualization, and finally, virtual desktop infrastructure, or VDI.

For additional information relevant to their discussion, please refer to:

- dave //

Virtualization at TechEd09

Adam Bomb — Fri, 29 May 2009 07:01:00 GMT

I caught up with Edwin Yuen to get a tour of the Virtualization booths at TechEd09 and find out what's new in virtualization from Microsoft. He showed me Hyper-V, Virtual Machine Manager, Virtual PC (including Windows 7 XP Mode), VDI and more. I even managed to get Jeff Woolsey and Edwin both to talk a little about third party virtualization solutions <coughvmwarecough> and how their offerings compare to ours.
You can find out more info about the sessions on virtualization at TechEd by visiting www.msteched.com as well as the Microsoft Virtualization site at www.microsoft.com/virtualization

Mad About MED-V Part 2 of 4, User Experience [Mad About MED-V Part 2 of 4, User Experience]

yung — Fri, 17 Apr 2009 17:42:00 GMT

This is the part 2 of a 4-part Mad About MED-V series. This screencast presents the user experience of running MED-V applications by going through essential user operations. The Mad About MED-V series includes the following screencasts and each link will be updated once the associated screencast is published.

Part 1, Concept and Architecture
Part 2, User Experience (this posting)
Part 3, Configuring Workspace Policy
Part 4, Creating Deployment Package

and each link is to be updated once the associated screencast is published. The remainder of this posting highlights some of the content presented in Part 2.

Seamless UI Integration with Host Computer

As discussed in Part 1 of this series, a MED-V workspace policy optionally allows a MED-V application integrated into the All Programs menu of the host computer as shown below, despites the fact that the MED-V application is configured and running in a Virtual PC behind the scene.

Running MED-V Application

To run a MED-V application, the workspace must first be started. A MED-V client can be loaded at Widows startup time if specified in the MED-V Client Settings, in such case a workspace can be also set to start automatically. This ensures the workspace is always in place, should a user require running a MED-V application once the computer has been started. And if the workspace has not been initialized, it will start on demand followed by bringing up the application upon completing the workspace initialization. Once a workspace is started, additional options like locking/restarting/stopping workspace become available when right-clicking the MED-V client icon in the system tray. A user also at this time has the access to utilities like the File Transfer tool as shown below. The Fire Transfer tool enables a user to transfer files between the host computer and the MED-V application running in the Virtual PC in the background.

In MED-V workspace policy, a MED-V administrator can optionally configure a color border to surround a running MED-V application as shown above. The setting of showing a color border can be easily changed or disabled within workspace policy by a MED-V administrator.

Redirecting URL

A MED-V workspace policy can be configured to automatically redirect a request for a target website from the host computer to the browser in the Virtual PC. This allows every request to a target URL with a web application incompatible with the browser installed on the host computer gets redirected to a compatible browser running in the Virtual PC behind the scene. The following screen capture shows a request redirected from the host computer which runs IE7 to the IE6 (with a red border) running in the hidden Virtual PC.

in reply to Mad About MED-V Part 2 of 4, User Experience

Mad About MED-V Part 1 of 4, Concept and Architecture

yung — Tue, 14 Apr 2009 17:37:00 GMT

Microsoft Enterprise Desktop Virtualization, or MED-V, is a desktop virtualization solution providing a self-contained computing environment including the OS, intended applications, and customized settings, if any. Desktop virtualization allows an application to run in a specific OS environment different from the OS running the hosting computer. MED-V uses Microsoft Virtual PC to provide a virtualized and customizable computing environment required by an intended application, yet incompatible or conflicting with that in the hosting computer. In other words, MED-V allows computing environments which are incompatible, conflicting, or with different requirements to run currently in the same physical device. For instance, running a legacy or line-of-business application requiring Windows XP SP2 in a Vista SP1 desktop or deploying a managed computing environment (like a corporate-managed desktop) to a non-managed (like a personal or home) desktop are some of the business challenges MED-V addresses.

MDOP now includes 6 tools and solutions as below and is available to Software Assurance customers.

Diagnostics and Recovery Toolset
Asset Inventory Service (AIS)
Advanced Group Policy Management
System Center Desktop Error Monitoring
Application Virtualization (App-V)
Enterprise Desktop Virtualization (MED-V)

Customers interested in MDOP should review the faq and contact their software vendor or Microsoft for additional information. For a comprehensive guide on Microsoft Virtualization from data center to desktop, download it here. I have produced the 4-part Mad About MED-V screencast series to offer a quick review of MED-V solutions including the following. I will update each link, once the associated screencast is published.

Part 1, Concept and Architecture (this posting)
Part 2, User Experience
Part 3, Configuring Workspace Policy
Part 4, Creating Deployment Package

In the part 1 screencast, I talked about the MED-V fundamentals to establish a baseline for subsequent discussions in the series. The remaining of this post highlights the key concept, architecture, and pertinent information of a MED-V solution.

Desktop and Application Virtualization Concepts

MED-V is probably the least understood piece in Microsoft Virtualization Solutions. A desktop virtualization solution MED-V is as opposed to App-V, an application virtualization. This distinction is an important one since they solve two different areas of business problems. Desktop virtualization addresses the incompatibility between a target application and the host operating system by virtualizing an entire desktop, i.e. a self-contained runtime environment including the operating system and the application. Such that a target application requiring, for instance, Windows XP SP2 and incompatible with Windows Vista can still be deployed to a Vista desktop by running the application in a hidden Virtual PC running Windows XP SP2 while using MED-V to seamlessly make the application accessible from the Start-All Programs menu on the host computer. App-V, on the other hand solves the incompatibility between two applications by offering a virtualized application runtime environment, the so-called bubble, while allowing these applications running on the same operating system instance. The following illustrates the concept.

Conceptually desktop virtualization using Virtual PC is easy to understand. Nevertheless to deploy desktop virtualization to enterprise, system administration and scalability are rather challenging. In essence, a Virtual PC lifecycle management solution is the key to make enterprise desktop virtualization a reality, and this is where MED-V comes in. MED-V makes Virtual PC deployable and saleable with a centralized lifecycle management solution including: image creation, delivery, monitoring, and maintenance.

MED-V Conceptual Model

To run a MED-V application the associated workspace must be first started. And if a user tries to start a MED-V application while the workspace is not in place, the workspace will start on demand and once the workspace is loaded, the application will start. A workspace is a Virtual PC image with a usage policy defined by a MED-V administrator. An administrator will use MED-V management console to configure usage policy which is a set of settings defining how MED-V applications will behave for a target Active Directory users or groups. Notice that the Virtual PC is where a MED-V application is configured, and the Virtual PC is also running in the background. MED-V workspace policy allows a MED-V application to seamlessly integrate into the All Programs menu on the host computer and runs transparently with the locally installed applications. A conceptual model of the integration is shown below.

MED-V Architecture

The high level MED-V architecture as shown below starts with: (1) and (2) to create, test and upload Virtual PC images encapsulating a target computing environment of an OS, applications and optional management and security tools to the image repository by administrator; (3) MED-V Management Server, the brain of the whole system, enabling an administrator to control image repository which is an IIS virtual directory and (4) provision images for targeted Active Directory Users and Groups along with usage policies; and finally (5) delivering the images and usage policies to clients. And a client starts a MED-V application, the client will authenticate against the management server, retrieve the workspace policy, and acquire the workspace image.

Notice a MED-V Management Server also aggregates clients' events, and stores them in an external database (MS SQL) for monitoring and reporting purposes. Also a MED-V client has two functional components – the first connecting to the server and retrieving the usage policy and an associated image form the repository, while the second offering the end-user experience and managing the Virtual PC from user experience and troubleshooting aspects.

System Requirements

The information provided here is as of March of 2009.

Antivirus/Backup Software

In order to prevent antivirus activity from affecting the performance of the virtual desktop, it is recommended where possible to exclude the following Virtual Machine file types from any antivirus or backup processing running on the host:

*.VHD
*.VUD
*.VSV
*.CKM
*.VMC
*.INDEX

MED-V Trim Transfer™ Technology

One very interesting piece of MED-V solution is the Trim Transfer technology as illustrated below. Trim Transfer accelerates the download of initial and updated Virtual Machine images over the LAN or WAN, thereby reducing the network bandwidth needed to transport a Workspace Virtual Machine to multiple end-users. It uses existing local data to build the Virtual Machine image, leveraging the fact that in many cases, much of the Virtual Machine (e.g., system and application files) already exists on the end-user's disk. For example, if a Virtual Machine containing Microsoft Windows XP is delivered to a client running a local copy of Windows XP, MED-V will automatically remove the redundant Windows XP elements from the transfer. To ensure a valid and functional Workspace, the MED-V Client cryptographically verifies the integrity of local data before it is utilized, guaranteeing that the local blocks of data are absolutely bit-by-bit identical to those in the desired Virtual Machine image. Blocks that do not match are not used.

The process is bandwidth efficient and transparent, and transfers run in the background, utilizing unused network and CPU resources. When updating to a new image version (e.g., when administrators want to distribute a new application or patch), only the elements that have changed ("deltas") are downloaded, and not the entire Virtual Machine, significantly reducing the required network bandwidth and delivery time.

You can configure which folders are indexed on the host as part of the Trim Transfer protocol according to the host OS. These setting are configured in the ClientSettings.xml file which can be found in the Servers\Configuration Server\ folder.

Virtualized Desktops with Citrix and Microsoft

Joey Snow — Wed, 17 Sep 2008 07:01:00 GMT

Last week Adam and I had a chance to attend the Microsoft getVirtualnow event in Bellevue. While there we had a chance to talk with Robin Brandl who is the Global Microsoft Evangelist at Citrix. In this interview Robin details desktop virtualization using Citrix XenDesktop and Microsoft Hyper-V. Take a look at the cool stuff Robin has to show.