MedV/AppV Overview

Editor's Notes

• #3: *1, Microsoft MDOP customer study. Base: Current MDOP customer n=108, non-MDOP customer n=367*2, MDOP ROI Analysis by Wipro. Wipro Product Strategy and Architecture Practice’s Analysis of Features, Cost Benefits, and Effects on IT Best Practices that Improve IT Infrastructure Optimization, March 2007, Sponsored by Microsoft, available on our website at <http://download.microsoft.com/download/8/f/4/8f461f10-23fd-472a-8af9-72153b56fcc1/MDOP%20TCO%20Wipro%2020March%202007.xps>
• #7: The first part of this animation represents Full Infrastructure Mode which used to be called “Classic Mode”. The second part of the animation shows 3rd party flow and Standalone.
• #8: The Application Sequencer is the primary tool used to package physical applications into virtual applications. For staff who are used to packaging with tools such as WYSE or Installshield the process will feel similar but less complex and quicker. Many customers can sequence applications in 1-2 hours for complex applications like Office. <See case Studies in Appendix for examples if asked> The Sequencer outputs a virtual application package which contains a number of files that are interpreted by the client in order to virtualize and launch the application. These files provide information such as the path to the streaming server/management server, the icons for the application, and the actual .sft file which is the virtualization file for running the application. In the 4,5 version we’ve streamlined the Sequencer to make it more intuitive. There are shorter wizards to enable the packager to move through the sequencing process quickly. We've also added the ability to create an MSI installer for each sequenced application. This is useful when integrating w/3rd party solutions and using standalone mode for user who don’t’ connect to the network as often. The experience is the same. Double click the MSI and the application and Icons are loaded into cache and ready for the user to initiate immediately.
• #9: There are many options for sequencing virtual applications. Sequence them as independent applications (Animation1) where they could still communicate but do not share resources (Animation2); sequence more than one into the same virtual bubble so they can share resources (animation3). With this second approach, in the past,you needed to virtualize the middleware with every application that needed it causing you to have large virtual packages and also forcing you to open and update each package when an update to the middle ware was required. This caused the creation of large packages and was time consuming. We can now create a 1:Many scenario (Animation4) where they can package a middleware application once and allow it to be used by many applications through dependency configurations. This reduces “package bloat” thus creating a small footprint when delivering the virtual application. It also simplifies package updates. In the past you would have to open every virtual application package that included the middleware, not you only have to open a single package, update it and publish it our so that all dependant packages can use the updated version. In addition, DSC can be used to include Plug-Ins with your virtual applications in the same manner. Remember that all dependencies created using DSC are defined and configured by the administrator. The end user experience is seamless, it just works and they don’t know the difference between a virtual or physical app.
• #10: Flexible Deployment OptionsWe provide flexible options to meet just about every business need. Based on the business requirements the customer has the ability to choose the solution that meets addresses their business requirements. With App-V you are licensed for standalone, Streaming with App-V infrastructure. Configuration Manager and App-V for TS and App-V for SPLA requires additional licenses for those products. We stream securely and it’s not just file streaming. When using App-V infrastructure we can stream over http/s and provide support for over the internet streaming. Internet Facing behaves just like Outlook over HTTP when using the rich client. It feels like you are on the network and the application is streamed using http when initiated by the user. When using ConfigMgr in an internet facing scenario only download and execute is supported, no streaming in the current release.Readily Accessible Applications for Users, Manageable for ITApp-V 4.5 supports internet-facing-server scenarios, in which users that are not on the corporate network or who leave the corporate network can still use App-V. The use of non-secure protocols on the internet is not supported (RTSP and HTTP). We support both domain joined and non-domain joined clients on XP, Vista, Win7 Beta (non production). For specific configuration details see our whitepapers “App-V Security Best Practices” and “App-V Security Operations Guide” located on the App-V TechCenter. Metering is available when using App-V Full infrastructure. It is configurable by the administrator to limit the number of licesnses available for launching applications and report on the usage of those apps. App-V policy polling allows the client to automatically check for new applications, updates, refresh shortcuts… We are localized in 11 languages and adding. No other vendor has this level of coverage to meet global business needs. We provide an OpsMgr management pack, and ADM template for client configuration setting at the enterprise and all errors are logged into the Event log and can be picked up by OpsMgr.http://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx
• #11: * Source: http://mediaproducts.gartner.com/reprints/microsoft/vol10/article9and10/article9and10.htmlVirtual Application Management in the Box When you purchase App-V you get access to the client, the sequencer and the management infrastructure all at a single cost. The infrastructure allows you to manage the updates once you deliver them to your end users. The application update is seamless. Place your updated version on your streaming server, assign it to your end users and the next time they launch the application the client will recognize a new version is available it load the new version. Since reboots are captured during the sequencing process no reboot is required when a new application is received. Updating App-V infrastructure components is accomplished using Windows update or by downloading the updates and delivering them via your software distribution system. We work hard to make sure the applications themselves are minimally, if at all, impacted. Application licensing and metering is available via the App-V management infrastructure and tracks who is using, when they used it and how many licenses are being used so that you have a better feel for who and when they are used. You can also set policies to not allow application launch if number of licenses are exceededVirtual and Physical Application ManagementBy automating Application Distribution using System Center, organizations can shift from a Basic IO Model to Rationalized IO Maturity stage very quickly. This translates into a savings from 4.6 weeks to test and deploy a package, to 4.6 days. This shift also supports the cost reduction of managing a machine from 1320.00/PC at the Basic stage, through to 580/PC at Standardized, and then down again to 230/PC at the Rationalized stage. 1 Study focused on the Financial Services sector showed that through the adoption of centralized management, and application virtualization, War on Cost studies have shown that this maturity migration can reduce desktop-facing FTEs by 35% (desk side support reduced 50%), and an overall TCO reduction of $281 per user. App deployment time reduced also shrinks from 8-10 weeks to < 5 days through automation and virtualization.Another study focused on the Health Care sector, showed that through the adoption of centralized management, and application virtualization, there was a 41% reduction in deskside support visits, with higher svc-levels achieved. IT labor costs were reduced by at least $107/desktop, resulting in a significant improvement in agility.System Center and Application Virtualization help organizations minimize the number of applications that exist in the OS image of their target systems. By reducing the need to pre-install applications in an OS image, Application Virtualization reduces image size and allows for quicker deployment and recovery times. An image only needs to contain the standard set of corporate utilities and applications. By removing applications from the OS image, System Center and App-V allow organizations to standardize and consolidate images. App-V when used with System Center allows administrators to “layer” applications on top of a standard image based on a user’s Active Directory group membership or other role, location etc definition. This is different than the layered approach offered by traditionalESD systems which actually modify the OS when user- or group-specific applications are deployed and thus “brand” the machines, tying them to specific users or group of users. Because System Center and Application Virtualization can deliver applications virtually, it keeps the OS free from the wear and tear that installations, tweaks, preference modifications and removals inflict on the OS over time. It is these types of changes that tie a system to particular users and again cause administrators to worry about the state on each machine and the ramifications of backing up (or not backing up) each and every device in their enterprise.Configuration Manager scales to the largest of organizations today. Introducing SQL cluster support and SQL Reporting Services, through to the managed limits of 200,000 per Central site, 100,000 per Primary Site, 200,000 for System Health Validation, and 25,000 per Management Point. Configuration Manager is able to meet the demands of any sized organization. Together, Microsoft Application Virtualization 4.5 and System Center Configuration Manager 2007 R2 provide a full PC life cycle management solution for deploying and managing both physical and virtual applications for enterprise customers. The combination of these two products enables customers to leverage their existing infrastructure investment and seamlessly integrate into existing workflows to package, test, deliver, and manage virtual applications for their end-users alongside physical software packages using 1 tool. When combined with other capabilities such as operating system deployment, software update management, inventory and license management, as well as model based configuration management, this combination provides a strong foundation of client focused services.  Building on a platform of SQL, SQL Reporting services, hierarchal site management distribution and scale support for large enterprise workloads, Microsoft Application Virtualization 4.5 and System Center Configuration Manager R2 can handle the distributed, mobile network landscape of today's modern organizations.Scale to 250k+ managed nodes for true enterprise landscape supportSupport your remote branch offices with diverse network and administrative needs as easily as you do corporate locationsRunning SQL 2005/2008 means advanced site database scale support, cluster and reporting services designed to meet the needs of distributed organizationsControl when change happens, and reduce change management costs with delivery control such as Maintenance WindowsDrive SLA and Scorecard success with explicit targeting, scheduling, runtime checks and seamless rollback Chain virtual and physical application packages right into OS Deployment scenarios.Asset Intelligence provides the ability to translate technical inventory into meaningful business terminology.  For example, ‘winword.exe ver10.90210’ can be translated into Microsoft Word XP Full Package Product (FPP).  This translation into Software Product Versions, Families and Categories, allows the organization to not only understand their software inventory landscape the way the business requires - but through this translation other elements of an inventory such as installation source are understood.System Center delivers a management solution to the mobile workforce that in addition to Application Virtualization support includes security management, Network access protection, traditional software delivery and more. Through seamless integration of virtual application technology into the core product, System Center ConfigMgr provides a platform for the mobile workforce that is consistently connected outside of the corporate boundaries. Application Virtualization – either provided as a streaming service, or as a locally available application, integrates with ConfigMgr to deliver a centralized, managed desktop experience for the traditional Task Worker environment. Supporting locked down environments through client elevation, System Center and App-V allow the administrator to efficiently deploy, update, manage and control the task worker landscape. Kiosk systems introduce an environment to the network landscape that requires increased management control. In addition to the random access of users accessing the system and without a consistent user relationship to target configuration management against, System Center can still maintain a consistent configuration for this class of system by utilizing both system (and user) based targeting, WoL technology, maintenance windows, and desired configuration management baselines. In addition, the ability to remotely schedule, and target software updates, application refreshes and even OS rebuilds is all possible through System Center integration.The kiosk system does not have the benefit of a traditional user profile target, but through the use of System based targeting to a locked down machine, System Center and App-V can deliver a consistently managed desktop environment that includes all the elements of a traditional rich client scenario.System Center provides the ability to deliver a managed desktop within the Terminal Server environment, whether that be a traditional application publish concept, or a mixture of physical and virtual. System Center can combine with other elements of the suite to provide Guest OS hosting management, performance management as well as data protection and backup services.When combined with System Center, Application virtualization extends beyond the corporate network into offshore, mobile workers and home working scenarios. Using Internet Based Client Management, System Center can deliver virtual applications alongside physical applications, in addition to software updates, and other configuration management services. Where light infrastructure is present for example in a branch, ConfigMgr can take advantage of workstation class systems to deliver Distribution point capabilities to local clients.
• #13: I’d like to quickly walk thru the infrastructure options that are available for MANAGING App-V. And in the next slides we’ll see how these compare to ThinApp’s capabilities.Extending Scalability and Deployment OptionsIn the past, SoftGrid 4.2 was pretty good at scaling up (servicing more users with more servers behind a load balancer) in a centralized location, however it needed to have better options for scaling out to the diverse enterprise requirements which include low bandwidth branches, rarely connected users and customers with existing ESD systems.  Microsoft App-V 4.5 offers a multiple options for easily scaling out the environment and provides seamless integration with SCCM 2007 R2 by allowing customers to easily deploy virtual applications through the SCCM 2007 R2 infrastructure and scale their deployments following known workflows. There are three main infrastructure options for extending scalability:App-V Full InfrastructureThis option includes the Microsoft System Center Application Virtualization Management Server (MSCAV) which includes full streaming capabilities, Desktop Configuration service, Package/Active Upgrade, basic licensing and metering. This infrastructure requires Active Directory and SQL Server and is an update to the existing Softgrid Virtual Application Server that Microsoft Softgrid 4.2 customers are familiar with using.App-V Lightweight InfrastructureThe lightweight infrastructure consists of the Microsoft System Center Application Virtualization Streaming Server. This server has streaming capabilities including active/package upgrade without the Active Directory or SQL Server requirements; however it does not have a Desktop Configuration Service, licensing or metering capabilities. This service relies on the manual or scripted addition of a manifest file for virtual application configuration. The Desktop Configuration Service of the MSCAV Management Server may also be used in conjunction with the MSCAV Streaming Server so the Management Server configures the application, but the Streaming Server delivers it. This lightweight infrastructure provides two additional options:The RTSP Streaming Server is typically used to deploy a branch model enabling you to scale too many locations and maintain the out-of-the-box Active Upgrade capabilities.  This is useful when the customer does not want to deploy SQL servers at each location but still requires streaming capabilities. An App-V Management Server is deployed centrally and streaming servers are deployed in each branch.  This is recommended for customer who does not have an existing ESD solution and will leverage App-V management infrastructure.  Use in branch office scenarios where the server will reside on the local area network and the data will not traverse the WAN or Internet.  The HTTP Streaming Server allows you to use an existing ESD infrastructure and add a new http server to stream applications.  HTTP streaming is optimized for internet/intranet delivery over wide area networks and is recommended for Internet-facing scenarios and businesses that require streaming capabilities across large, disperse networks.  Active Upgrade is not available when using HTTP streaming.App-V Standalone ModeThe Sequencer now has an option to create an MSI file which automates the addition of the virtual application. The MSI contains metadata so a distribution system can recognize it and control the virtualized applications. Standalone mode requires the client to go into standalone mode which only allows MSI based updates of the virtual applications and streaming is not allowed while in standalone mode. This mode is meant for those rarely connected users that need the power of virtualized applications, but do not have access to a server. Increased supportability includes improvements such as:Client cache improvements. The maximum size of the client cache has been increased to 1 TB.Improved Manageability. Integration and support for VSS writer, MOM Pack, ADM template Accessibility. The product is now Section 508 compliant, bringing App-V in line with other Microsoft products. Re-designed Sequencer.  Simplifies the process and reduces the complexity of creating virtual application packages. There is now a single wizard for creating a new package and advanced settings have been put into an optional screen
• #14: With more than 14 million licensed seats and more than 30 publicly available customer case studies, it is clearApp-V is the desktop TCO hero.Swedish medical center saved money: more than one million dollars in deployment and support related costsHeidelberg, a global manufacturer, increased business agility, by reducing application packaging time in more than 50 percent.Tuv Nord, a technical services provider, improved business continuity using App-V by reducing downtime to minutes.App-V allows you to immediately save costs on virtually all Windows desktops and lays the foundation for future desktop virtualization deployments.
• #16: I’d like to start with the business need for MED-VWhen you are facing an OS upgrade you are required to go through a process of mapping your applications and testing that all of them work on windows 7.Although we offer a range of methods and tools to fix compatibility issues, in most cases, there is going to be a subset of applications that are not yet officially supported by their vendor, or might not work at all. Getting the application to work, upgrade to a new version that supports Windows 7, or find another workaround for all those application takes time. You will find yourself with a set of applications that are not ready when you are ready to move to Windows 7. That is what MED-V is trying to help you with. We suggest that you first upgrade to Windows 7 and then work a solution for those applications at a later phase, accelerating the time for OS upgrade.How do we do it?
• #17: We do it by using Virtual PC to run a previous version of the OS, such as Windows XP, and on top of it run the applications that are not supported or tested on Windows 7. From the end-user perspective those applications are available from the start menu, just as any Windows 7 application, and they run on their desktop seamlessly, so there is almost no user training required.
• #18: Before I continue to talk about MED-V, one of the common questions we get is how the solution I just described with MED-V is different from what was recently introduced in Windows 7 Pro – the Windows XP Mode.First I want to quickly describe the history of Windows XP Mode.Up until Windows 7, Microsoft had a virtualization software called Virtual PC 2007, that focused on enabling multiple OS for developers and IT.With Windows 7, we provide virtualization software, that is focused on assisting small businesses to run incompatible applications on Windows 7.Windows XP Mode, is a preconfigured Windows XP environment that is available for customers who have Windows 7 Pro and up.It allows those customers to manually install their incompatible applications on this Windows XP image, and run them seamlessly on their Windows 7 desktop.From the user experience it is similar to what MED-V offered on Windows Vista.
• #19: However, while Windows XP Mode is a great solution for a single user or a small business. When it comes to larger organizations, where IT needs to deploy incompatible applications in scale, they need a way to deploythose virtual machines, provision and customize them accordingly, control their settings centrally and finally support and troubleshoot..That's what MED‑V is providing – the deployment of those Virutal PCs in the enterprise.Another thing to remember about MED-V when comparing to Windows XP Mode, is that it will not require PCs to have hardware assisted virt (such as Intel VT or AMD-V technology)
• #20: Another common question I’d like to addressis what’s the difference and another MDOP virtualization technology – App-V.It’s important to understand that these are not competing technologies. Nor is one replacing another. These are two different technologies that address two different use cases. Application Virtualization can simplify the way you deliver applications to the desktops. With App-V youcreate a package for every application that is self-contained and is isolated from all other applications on the desktop. This application can then be delivered and become instantlyavailable to users on their desktops without any wait time for installation. We recommend every IT organization to consider App-V as part of their Windows 7 application deployment strategy.
• #21: MED-V is different from Application Virtualization because we do not create a package for one application. We actually create an additional instance of Windows on the same desktop. So that you create a copy of Windows XP on the same desktop that is running Windows 7.
• #23: It all starts from a Virtual PC image that encapsulates a desktop environment: an operating system (OS), applications, and any management or security tools commonly used desktops. One of the common questions is how do I manage this virtual machine once it’s deployed, how can I deliver applications to it, patch it, apply corporate policies to it, run anti-virus in it, and more. The recommended solution is to join each deployed virtual machine to the organizational Active Directory domain, and manage it as any other desktop.MED-V facilitates this process and makes it easy to configure and transparent for the end user. Then the virtual PC image is loaded into a centralized repository (which is an IIS-based web-server) that holds all the images ready to be deployed.The next component is the management server that enables administrators to take the images from the repository, associate them with a policy, and provision them to Active Directory users or groups.The server components, are controlled from a single management console. Finally, on the end-client, a client component needs to be installed using any standard software distribution that the organization has.The client has two roles:It authorizes against the server, obtains the usage policy, retrieves the image from the repository, and apply the policy to the local Virtual PC settingsThe second role is to manage control the Virtual PC session end-to-end providing a seamless user experience
• #24: Thank you for watching this session, I hope that you find MED-V and MDOP valueable for your Windows 7 deployments.
• #26: MED-V v1 System Requirements Client Windows Vista SP1/2 – 32-bit (2GB RAM Recommended)Support for Windows 7 will be added in Q1 CY2010 via MED-V 1.0 SP1Virtual machineMicrosoft Virtual PC 2007 SP1 (+QFE) Guest OS: Windows XP Pro SP2/3, Win2000 SP4Guest browsers: Internet Explorer 7 or 6 SP2ServerWindows Server 2008 (Standard/Enterprise)IIS web server for image delivery (Optional)SQL Server 2005(SP2 Enterprise ), any 2008 (Optional reporting)Languages: English UI (with support for Western-EU OS)
• #27: To learn more about MED-V I’d like to refer you to various resourcesHigh-level overview, case studies, and of course a demo video in the MED-V website.Technical documentation at Technet – From architecture document, through evaluation guides, planning guides and videos that walk you through most of the product flows and administrationSoftware itself is available with the rest of MDOP on the volume licensing site.Evaluation is available for MSDN and Technet subscribers, depending on their subscription levelFinally all the announcements are in the MDOP blog, and technical articles and FAQs are at the MED-V technical blog