Entries tagged with app-v - TechNet Edge

Microsoft Application Virtualization (App-V) 4.6 User Experience

yung — Mon, 01 Feb 2010 17:40:00 GMT

The main delivery in App-V 4.6 is 64-bit supportability. The rest of the product features and functions are much the same, if not identical, with those in App-V 5.1 SP1. The following shows App-V 4.6 Windows Desktop Client and App-V 4.6 Client for Remote Desktop Services (or Terminal Services) installed in a 64-bit operating system.

This screencast is not a tutorial of App-V 4.6. Viewers are expected to be experienced with App-V and familiar with the App-V infrastructure. The App-V user experience presented here is based on a server-based deployment scenario with a full, App-V infrastructure, with packages streamed in RTSPS over port 332. Using RTSPS provides high security since the communication between App-V Servers and Clients is signed and encrypted. The following table depicts the methods for deploying virtual application packages to terminal servers and Windows desktops. In the screencast, I employed an App-V Management Server with local SQL Server 2008. The demo environment consists of virtual machines running within my laptop which has Windows Server 2008 R2 with Hyper-V role added.

Source: Application Virtualization 4.5 for Terminal Services

The topology diagram shown below highlights the configuration of the demo environment. Here contoso.corp is an Active Directory domain with an App-V infrastructure having the following components:

An App-V Management Server is responsible for publishing the shortcuts and file-type associations and streaming application packages to App-V clients. The App-V Data Store is in a SQL database and retains information related to the App-V infrastructure.
An App-V Management Console is a MMC 3.0 snap-in management utility for App-V Management Server administration. An App-V Management Console can be installed with an App-V Server as configured in the demos here, or on a separate workstation that has MMC 3.0 and .NET 2.0 installed.
An App-V Client provides the virtual environment for running virtualized applications by managing and streaming App-V packages into cache, publishing refresh, and interacting with designated App-V Servers. Both App-V Desktop Client and App-V/TS Client are available and demonstrated in the screencast.

To minimize the number of virtual machines needed, I installed App-V Management Server, App-V Admin Console, and SQL Server 2008 in the domain controller, dc.contoso.corp. While App-V 4.6 Terminal Services (App-V/TS) Client was installed in the Remote Desktop Session Host (RDSH), app.contoso.corp. And App-V 4.6 Windows Desktop Client was installed in a managed Windows 7 desktop, w7ent.contoso.corp. The domain, contoso.corp was configured with DirectAccess with w7ent as a DirectAccess client.

In the demos, I first talk about how the demo environment is configured. With the App-V default application (which is the test application installed with App-V Management Console), I added domain admins as the authorized users to verify the readiness and correctness of the App-V infrastruture. Later, I used a test account, alice, to test the streamed, App-V applications. Notice the demo environment was constructed to mainly present the user experience of App-V 4.6 with minimal complexity. No attempt was made to optimize the performance, server placement, or user profile management.

Additional resources:

(This is a cross-posting from http://blogs.technet.com/yungchou/.)

Microsoft Virtual Desktop Infrastructure (VDI) Explained

yung — Thu, 14 Jan 2010 18:00:00 GMT

This is a follow-up posting and a continual discussion of desktop virtualization and Remote Desktop Services (RDS) relevant to Windows 7 and Windows Server 2008 R2 (WS2008R2).

I highly recommend that those who are not familiar with RDS, take a moment to review the architecture and know what role RDWA, RDG, RDSH, RDVH, and RDCB each is playing when serving a remote access request. This will facilitate one’s understanding of the integration between RDS and VDI. It will set the stage for the next level of discussion in my upcoming post, going over the nuts and bolts of building a VDI solution. I wrote this article with the following flow in mind:

What It Is
- User Experience
- RemoteApp and Desktop Connection
How It Works
- Considerations
- VDI Licensing
- RDS vs. VDI
Why VDI
Best Practices for VDI
Closing Thoughts

What It Is

Microsoft Virtual Desktop Infrastructure (VDI) is a centralized desktop delivery solution. The concept of VDI is to store and run desktop workloads including a Windows client operating system, applications, and data in a server-based virtual machine (VM) in a data center; and allow a user to interact with the desktop presented onto a user device via Remote Desktop Protocol (RDP). Notice VDI is part of an enterprise’s cohesive, holistic virtualization strategy across IT infrastructure to support Microsoft’s vision of Dynamic IT. VDI is not an isolated architecture, but one of the many technologies available to optimize enterprise desktops.

User Experience

A notable component in the Remote Desktop Services (RDS) of WS2008R2 is the availability of Remote Desktop Connection Broker (RDCB). RDCB is a native VDI connection broker, providing a unified experience for access to VDI as well as traditional, session-based remote desktops. With RDCB, virtual desktops are now delivered similarly to RemoteApp. For example, a user will access http://rds-all.contoso.corp/rdweb and be presented with a webpage with authorized applications and desktops, once authenticated, as shown below.

Here, three Office 2007 applications are published as RemoteApp which works very much the same with that in Windows Server 2008. In Windows Server 2008 R2 however, RemoteApp programs shown on this consistent URL can be composed from multiple sources. The RemoteApp programs shown here are not necessarily installed on the same Remote Desktop Session Host (RDSH) or Terminal Server. They can be from multiple RDSHs and Terminal Servers, yet composed and presented with the same URL. Further, the presence of a RemoteApp program is based on the access control list of a published application in RDSH. By default, all authenticated users will have access to published RemoteApp programs.

The icon, My Desktop, appears for only those who are assigned with a personal virtual desktop. The assignment can be done in RDCB, or the User object in Active Directory. When a user click My Desktop icon, a virtual desktop will be delivered to the user’s device, once the user is authenticated. The follow screen capture shows Word 2007 accessed as a RemoteApp program and a virtual desktop delivered via VDI to a user on a non-managed Windows 7 client.

The icon, Contoso Desktop, is for accessing a virtual desktop running on a VM dynamically picked from a VM pool defied in RDCB. Notice once a VM pool is defined, the icon to access a VM in the pool will show up on the RDS webpage for all authenticated users, regardless if a user has access to the pool. Both the display name of the page and the display name of the icon to access a VM pool can be easily customized in RDCB, here “Contoso Wonder LAN” and “Contoso Desktop” are both customized display names. Further information of the RDS architecture and how RDCB plays a central role in a VDI solution is available in “Remote Desktop Services (RDS) Architecture Explained.”

RemoteApp and Desktop Connection

A new feature in WS2008R2 worth mentioning here is RemoteApp and Desktop Connection which provides the ability to access to RemoteApp programs, remote desktops, and virtual desktops from the Start menu of a Windows 7 PC. In Windows 7, a user can go to Control Panel to configure it with a few mouse clicks in a friendly wizard-driven process. The URL of an intended RDS webpage and user credentials of an intended user are needed to complete the process. When RemoteApp and Desktop Connection accessing a target RDS webpage on a user’s behalf, the user will be prompted for credentials. The screen capture on the right shows the Widows 7 Start menu integrated with RDS resources published on the Contoso Wonder LAN page shown earlier. If the user deletes the settings configured in RemoteAll and Desktop Connection, the Contoso Wonder LAN and its content will be removed accordingly.

To facilitate RDS/VDI deployment, an enterprise administrator can create and distribute a client configuration (.wcx) file to a user to facilitate configuring RemoteApp and Desktop Connection. Another way is to distribute a script to run the client configuration file silently, so that RemoteApp and Desktop Connection is set up automatically when a user logs on to their account on a Windows 7 computer. The automation can be easily done, minimize operator intervention, and provide a great user experience.

With RemoteApp and Desktop Connection, a Windows 7 user can access RemoteApp programs and virtual desktops directly from the Start menu without the need to specify the RDS URL. This minimizes the user training and offers a consistent user experience on using Windows applications.

How It Works

With VDI, a virtual desktop is isolated from the client’s device and runs in a VM maintained in a data center. Here the device can be a desktop, laptop or thin client. A VDI user interacts with one’s virtual desktop through RDP which provides a rich desktop experience. Similar to session-based remote desktops (formerly known as Terminal Services), VDI provides a server session with a full-fidelity desktop environment that is virtualized within a server-based hypervisor. The premise on VDI is that all VDI users are running virtual desktops on VMs. Key technical components making VDI a reality include:

Windows Server 2008 R2 with Hyper-V
- A virtualization host which runs VMs and is essentially a grid in the virtualization solution infrastructure
- A library/repository with virtualization resources like VMs, VHDs, hardware/software profiles, etc.
Microsoft Application Virtualization (App-V)
- A dynamic application deployment vehicle based on user profiles and transparent to local operating system
- A tool available in Microsoft Desktop Optimization Pack (MDOP) via Software Assurance
Microsoft Remote Desktop Services
- A single and consistent URL for accessing resources published in multiple RDSHs and terminal servers
System Center Management Suite with Virtual Machine Manager (SCVMM, optional and highly recommended)
- A comprehensive management solution for managing enterprise IT lifecycle
- Simplifying the deployment, provisioning, and management of virtualization hosts and VMs

In a VDI deployment, there are two models: (1) a static or persistent virtual desktop and (2) a dynamic or non-persistent one. In static mode, there is a one-to-one mapping of VMs to users. Each user is assigned with a designated VM. Since VMs are commonly stored on a Storage Area Network (SAN) and execute on a server, a larger number of users will likely lead to significant SAN requirements.

In a dynamic architecture, on the other hand, there is only one master image of the desktop stored. All user personalization, profile, applications, etc. are stored separately from the desktop. When a user requests a desktop, a VM cloned from the master image is combined with the user’s personal data and applications dynamically delivered to the user device based on roaming profiles and App-V. This delivers a personalized desktop experience by dynamically provisioning a base image. it simplifies the overall VM management by reducing the number of desktop images maintained.

Considerations

Both RDS and VDI are core components of desktop virtualization, and they satisfy specific computing requirements and scenarios with deployment readiness and flexibility. For a remote task worker who needs to access a specific application for carrying out a well-defined task like entering data or reporting a status for time reporting, inventory update, or incident reports, etc. RemoteApp may be sufficient. A knowledge worker, on the other hand, who performs complex or unstructured routines like analyzing data, architecting a solution, design a product, writing code, troubleshooting system, etc. will likely require full access to a desktop to assure productivity, and deploying a virtual desktop is one solution.

Notice that VDI, while flexible, does require more server hardware resources than the traditional session-based remote desktop approach. In general, VDI requires an upfront investment in server and storage hardware to store and execute all needed VMs. To ensure users able to access virtual desktops, the network supporting VDI needs highly available since for a user, no network connectivity, no virtual desktop accessible. Generally speaking, the network bandwidth requirement is also expected relatively higher to support VDI than that supports Terminal Services. Virtual machine management software is also essential to manage enterprise virtual desktops, i.e. VMs, running in hypervisor hosts. On user experience, one should not expect a remote desktop or a virtual desktop to perform exactly as well as a locally installed desktop. Audio, video, and USB performance on a remote desktop may not be as rich as those directly running on or attaching to a user’s device. The fact is a rich client will always provide a superior user experience to that delivered with VDI. Overall, considerations of a Microsoft VDI solution should include, but not be limited to:

Infrastructure with Hypervisor hosts
Virtual machine management
Application provisioning
Connection management
Data center capacity
Image management
Licensing

VDI Licensing

VDI essentially delivers a desktop on demand to a user device via a network connection. This is different from running a conventional desktop machine with which an OEM license is bound to hardware and cannot be dynamically assigned as VDI does. The traditional licensing has become insufficient to correctly reflect the number of licenses consumed in a desktop deployment delivered with VDI.

To accommodate new deployment scenarios, Microsoft has introduced two new offerings for VDI: Microsoft Virtual Desktop Infrastructure Standard Suite (VDI Standard Suite) and Microsoft Virtual Desktop Infrastructure Premium Suite (VDI Premium Suite). Both the VDI Standard Suite and the VDI Premium Suite are licensed per client device that accesses VDI environment, and thereby allow for flexibility of server infrastructure design and growth. Additional information on Remote Desktop Services Licensing is available.

RDS vs. VDI

Like many solutions, there are pros and cons in employing RDS or VDI, as shown below. And in my view, just like the debates on ”thick client vs. thin client” and “in the cloud vs. on premises,” I have no doubt there will also be a mix of the two, RDS and VDI, in enterprise IT in a foreseeable future. I believe what we must recognize is that business requirements should dictate a solution chosen.

Why VDI

Since virtual desktops delivered by VDI are VMs running in a data center, enterprise IT can realize all the benefits of centralized desktop management. Strategically, VDI enables enterprise IT to

Deploy desktops in virtual machines on secure and centralized server hardware, which improves business continuity, data security, and desktop lifecycle management
Enable a user to access and run one’s desktop and applications wherever the user may be, which offers desktop location independence and improves business productivity
Transform enterprise IT deployment from infrastructure-focused model into a user-centric approach, which improves user productivity

VDI is not for every user but provides deployment readiness and flexibility for specific scenarios including:

Contract/offshore workers
Anywhere access and work-from-home scenarios
Centralized desktop computing

Best Practices for VDI

Segment desktop users and categorize user requirements to better understand user scenarios. Assess who can benefit from centralized desktops, and with what kind of business benefits.
Centralizing desktops can be implemented using RDS, VDI, or a combination of the two. And user requirements should determine which is best fit.
Separate applications from desktop image, dynamically provision desktop applications based on user, and minimize the number of desktop image. One solution is to employ Microsoft App-V/TS or App-V for Terminal Services with a VDI solution. Further discussion of App-V/TS will be in my upcoming blog and beyond the scope of this article.

Closing Thoughts

We must be aware that running virtual desktops does not eliminate licenses or IT management costs. And it may be a challenge to prove the TCO reduction with an emerging technology like VDI which uplifts IT’s capabilities to a new dimension by fundamentally changes how desktops and applications can be deployed and managed like a service using virtualization.

“Service” sometimes can be a very scary term. For decades, enterprise IT has been delivering services to its customers. Today, we are still learning and debating how to quantify and put a business value to IT services. VDI, in my view, is a service and I am almost hearing “everything as a service” now. To ensure a success and realize business benefits of a VDI solution, a baseline is integral and should be first established. As discussed earlier, VDI works well for some scenarios, and there are times VDI may not be the most cost-effective way, nevertheless it is a solution with most predictability to succeed. The key is to be clear on what a VDI solution is trying to achieve and, as critical, identify: what to measure, where to draw a line, and on which direction an organization is heading. Although it sounds a common sense and like project management 101, in a VDI project basics are critical. And I here predict:

Without setting an objective, a VDI project will for sure fail.
Without defining completion criteria, a VDI project will creep in scope, run over budget, and never be completed.

I have already seen VDI and other virtualization technologies like App-V and RDS bringing new opportunities and challenges to many of us. Going forward I believe VDI will continue having an impact on how you, I, and organizations perceive IT and carry out an IT business. As cliché as it sounds, this is an IT transformation from an infrastructure-focused deployment to physical devices into a dynamic and user-centric approach with virtual desktops. Perhaps, this is what I am really saying:

Without being specific on what to achieve in the long run, an IT transformation is hardly justified.
Without setting incremental goals, an IT transformation can certainly start, yet with much uncertainty to ultimately realize the business benefits that the transformation brings.

(This is a cross-posting from http://blogs.technet.com/yungchou.)

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.

Reducing Desktop Costs Part 3 Application Virtualization – Tech Focus September 2009

Alan Le Marquand — Tue, 22 Sep 2009 13:11:00 GMT

The question posed in the first part of this series 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, the second post cover Desktop virtualization options:-

Remote Desktop Services.
MED-V

This final post looks at the application virtualization and the how this technology will change your view on how to install software onto your clients.

Microsoft Application Virtualization (App-V), which is a core component of the Microsoft Desktop Optimization Pack for Software Assurance, transforms applications into centrally managed virtual services that are never installed and don’t conflict with other applications

In the webcast Optimize Windows 7 with Microsoft Desktop Optimization Pack, you will see how the technologies to assist in the virtualization of legacy applications work.

App-V basically works by “pulling” applications instead of the tradition paradigm of "software push" to install the entire applications. The first time end users request an application, the App-V client rapidly responds and "pulls" only the code necessary to start the program from a central Virtual Application Server—typically 20 to 40 percent of the total application. When the session terminates, the application and its user preferences are saved in a file-based cache location. Subsequent application launches are loaded from this local cache, resulting in faster launches with little impact on network bandwidth while ensuring that the user’s applications are also preserved, even in the case of unexpected computer shutdown.

The following two additional webcasts combined go into more details about the above description on how App-V works and how System Center can also assist with built in management of App-V.

How does App-V changes the game when it comes to software distribution? First there is the deployment model. Packages are created using a wizard, the packages are loaded onto a central server and the application is ready for use. Using this you also have much more granular control on who can install an application. Using the security model you simply add the application to the user profile or security group in Active Directory and that user is now authorized to install and run the application. Using this packaging process to get an application ready could reduce IT Department labor by 81%, plus the reduction in support calls for application deployment could be 89%.

The case for using App-V as the method of choice for deploying applications in an organization is compelling, the latest Cost Reduction Study covers the potential savings of this solution in greater depth, with some very interesting case studies.

So what have we covered in this series?

The first thing is that the range of options and tools available to provide users with the latest tools to do their job, whether that is Windows 7 on their PC or Office 2007 as their productivity suite, is wide and varied.
Centralized Management options offer the best form of cost saving, whether that be by providing a desktop through Remote Desktop Services or Applications via App-V.
Application Virtualization (App-V) is going to change the way you think about and deploy applications to users.

Deploying the latest desktops to users and cost savings are not mutually exclusive. However, cost savings are not achieved with the click of button. The best solutions are a combination of technologies well planned. For example, Windows 7 on the desktop with applications delivered by App-V, these are the two most effective technologies, but you do have to plan your implementation. When you do the research and planning up front you can easily prove the cost effectiveness of IT Solutions.

For more about this topic please visit my blog

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 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 //

TechNet Video: Virtualisierung 360°

Ralf M. Schnell — Mon, 04 May 2009 13:07:00 GMT

Über Virtualisierung wird intensiv diskutiert, und kaum jemand bezweifelt, daß durch Virtualisierung Einsparungen erzielt oder Mehrwerte realisiert werden könne. Aber wie? Es gibt viele Arten der Virtualisierung und damit auch viele Möglichkeiten, diese sinnvoll einzusetzen. Wir geben in diesem Video einen Überblick über das Virtualisierungs-Portfolio von Microsoft und zeigen an einigen Szenarien, wo die unterschiedlichen Technologien vorteilhaft eingesetzt werden können.

Referent:
Ralf M. Schnell
Technical Evangelist, Microsoft Deutschland GmbH
http://blogs.technet.com/ralfschnell

Präsentation und Video herunterladen