Windows Virtual Enterprise Centralized Desktop

5,141 views

Published on

Virtualization brings about new use cases that did not previously exist in traditional desktop environments. These use cases include the ability to create multiple desktops dynamically, enable user access to multiple virtual machines (VMs) simultaneously, and move desktop VMs across multiple platforms, especially in load-balancing and disaster recovery situations. Microsoft designed Windows Virtual Enterprise Centralized Desktop (VECD) to enable organizations to license virtual copies of Windows client operating systems in virtual environments.

http://www.microsoft.com/windows/enterprise/solutions/virtualization/licensing.aspx

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,141
On SlideShare
0
From Embeds
0
Number of Embeds
34
Actions
Shares
0
Downloads
109
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Windows Virtual Enterprise Centralized Desktop

  1. 1. Windows Virtual Enterprise Centralized Desktop<br />1<br />
  2. 2. Agenda<br />New Desktop Virtualization Scenarios…<br />…and why traditional Windows Licensing does not work<br />Introduction to VECD<br />Customer Scenarios for VECD<br />2<br />2<br />
  3. 3. Desktop Virtualization<br />The need for a new type of Windows License<br />
  4. 4. What is Desktop Virtualization<br />Roaming Profiles<br />Folder Redirection<br />Microsoft Application Virtualization<br />Data, User settings<br />Local Desktop Virtualization<br />Applications<br />Microsoft Remote Desktop Services<br />Microsoft Virtual Desktop Infrastructure<br />Microsoft Enterprise Desktop Virtualization<br />Remote Desktop Virtualization<br />OS<br />Traditional Client Computing<br />Desktop Virtualization Enables new scenarios<br />Hardware<br />
  5. 5. Use Cases for Virtual Desktops<br />Users can access to virtual Windows running on a server from authorized devices, including thin clients<br />VM on portable media<br />IT can provide managed desktops to non-managed third party owned Windows PCs<br />VM on Contractor / Offshore PCs<br />Employees can access their personalized corporate desktop from their home Windows PC<br />Virtual copies of Windows provided on media such as USB / DVD<br />Remote boot VM from network storage device<br />VM on Employee owned PCs<br />Blade PCs<br />Create and store a Windows image on a storage device, such as a network server, which may be run over an internal network locally in physical or virtual operating system environments <br />Virtual Desktop Infrastructure (VDI)<br />Multiple users are accessing blade PC with a single copy of Windows physically installed per blade.<br />
  6. 6. Why not traditional Windows?<br />
  7. 7. Virtual environments and licensing<br />What Virtualization Demands: Licensing Flexibility<br />Ability to run Windows Client OS on servers<br />Unrestricted movement of VMs across hardware platforms<br />Added Value: Software Assurance<br />Flexibility<br />Value<br />Upgrade / Downgrade rights for OS<br />Access to Enterprise editions of OS<br />Reassignment rights after 90 days.<br />Access to technology such as MDOP and WinFLP<br />Support and training from Microsoft<br />Basic Value: OEM License<br />Pre-installed OS<br />Bound to hardware<br />No reassignment rights<br />
  8. 8. Limitations of traditional Windows licensing for virtual environments<br />Additional<br />Value<br />What you expect from your virtual desktop environment…<br />Improved Business Continuity<br />Increased Desktop Flexibility<br />Move VMs across servers in case of server downtime<br />Load balance VMs across multiple servers<br />Create desktops dynamically from golden images<br />Dynamically adjust the number of VMs in your environment<br />Product support for the different components of the complex VDI infrastructure<br />OEM licenses bound to hardware<br />Retail licenses can be reassigned only after 90 days<br />OEM and retail licenses cannot be dynamically assigned<br />OEM and retail licenses do not include any product support from Microsoft.<br />…and the limitations of traditional Windows licensing<br />
  9. 9. Introducing Windows Virtual Enterprise Centralized Desktop (VECD)<br />
  10. 10. What are the different flavors of Windows VECD?<br />What is Windows VECD<br />Windows VECD is a device based annual subscription program to help you license virtual copies of Windows (XP, Vista, Windows 7)<br />Windows VECD for SA<br />Windows VECD<br />What devices can <br />be covered?<br />Rich clients, Thin clients<br />Rich clients<br />Is Software Assurance a pre-requisite?<br />No<br />Yes<br />$110/year/device<br />$23/year/device<br />What is the retail price?<br />Does it have Software Assurance benefits?<br />Yes<br />Yes<br /># of rich clients without SA<br /># of rich clients with SA<br />Total # of Windows VECD licenses required<br /># of thin clients <br />(Irrespective of virtualization infrastructure)<br />
  11. 11. Windows VECD is designed for virtual environments<br />Improved Business Continuity<br />Increased Desktop Flexibility<br />Additional<br />Value<br />What you expect from your virtual desktop environment…<br />Access corporate desktop images from non-corporate Windows PCs<br />Single VECD license allows concurrent access for up to 4 VMs<br />Work at home rights included<br /> Dynamic desktop licensing enabled through KMS/MAK activation<br />Install windows on any combination of hardware and storage<br />Unlimited movement between servers and storage<br />Reassignment rights to another device after 90 days, or in case of end-point failure.<br />Unlimited backups of both running and stored VMs<br />Includes SA benefits such as 24*7 call support, training vouchers, access to Enterprise versions of Windows, etc<br />Option to purchase MDOP and WinFLP<br />…and how Windows VECD delivers<br />
  12. 12. Windows VECD recommendations for your users<br />Windows VECD for SA<br />Windows VECD<br />VM on portable media<br />VM on Contractor / Offshore PCs<br />VM on Employee owned PCs<br />Blade PCs<br />Remote boot VM from network storage device<br />Virtual Desktop Infrastructure (VDI)<br />Valid<br />Recommended<br />
  13. 13. How to buy VECD<br />Windows VECD for SA<br />Windows VECD<br />Available under EA, Select, Open Value, Campus<br />Order on existing SA agreements<br />For new agreements, create a new SA agreement, and then add Windows VECD for SA<br />SKU number starts with DSA000xx<br />Execute ammendment B31<br />Expand qualified desktop definition to include thin clients<br />For existing EAs, new multi-profile needs to be created<br />SKU number starts with DTA000xx<br />
  14. 14. VECD Scenarios<br />
  15. 15. Scenario 1<br />Standard User<br />License requirement<br />100 VECD for SA Licenses<br />50 VM<br />80 Users<br />100 PCs with SA<br />VECD is a device based license.<br />My company has 100 corporate PCs covered under SA that need to access our VDI environment. However, we only have 80 users and only 50 VMs are used at any one time. <br />100 devices accessing VDI100 VECD Licenses<br />If PCs already covered with SA 100Windows VECD for SA<br />If PCs not covered with SAupgrade to SA, 100 Windows VECD for SA <br />Scenario<br />License<br />
  16. 16. Scenario 2<br />Shift Workers<br />Shift 1<br />License requirement<br />Shift 2<br />Shift 3<br />100 Windows VECD for SA Licenses<br />150 VM<br />300 Users<br />100 PCs with SA<br />VECD is a device based license.<br />100 devices accessing VDI 100 VECD Licenses<br />If PCs already covered with SA 100 Windows VECD for SA<br />If PCs not covered with SAupgrade to SA, 100 Windows VECD for SA<br />My company has 100 PCs, with 300 workers accessing our VDI environment in shifts. At any time, 150 VMs are being accessed using VDI.<br />Scenario<br />License<br />
  17. 17. Scenario 3<br />Mixed Desktop Hardware<br />License requirement<br />License requirement<br />100 Windows VECD for SA<br />100 Windows VECD<br />100 PCs<br />100 VM<br />100 Users<br />100 Thin-clients<br />VECD is a device based license.<br />200 devices accessing VDI 200 VECD Licenses<br />100 thin clients 100 Windows VECD <br />If 100 PCs already covered with SA 100 Windows VECD for SA<br />If 100 PCs not covered with SAupgrade to SA, 100 Windows VECD for SA<br />My company has 100 PCs and 100 thin clients using VDI. Only 100 devices are used at a time, and access 100 VMs of Windows Vista or Windows XP. <br />Scenario<br />License<br />
  18. 18. Scenario 4<br />Occasional Home User<br />License requirement<br />Occasional Home access<br />100 Employees <br />No additional Windows VECD Licenses<br />(each a named user of VDI device at work)<br />VECD licenses includes home use rights for the primary (“named”) user of a company owned PC covered under VECD. <br />My company has 100 employees who are the primary users of 100 PCs covered under Windows VECD at work. These employees occasionally work from home and access the corporate VMs via VDI from their home machine (owned by employees) <br />Employee is a primary user of VECD device at work No additional VECD Licenses<br />Employee is not a primary user of VECD device at work 100 Windows VECD <br />Scenario<br />License<br />For Microsoft Office application use at home, you must have Microsoft office license with SA coverage and register for Home Use Rights at no additional cost. <br />Note<br />
  19. 19. Scenario 5<br />100% Home User <br />License requirement<br />100 Windows VECD Licenses<br />100 Employees use work machines from home<br />These authorized devices will have to be licensed <br />My company has 100 employees who work from home and will access corporate VM via VDI from their authorized device at home. <br />If the device is a thin client100 Windows VECD<br />If it is a PC and is covered with SA 100 Windows VECD for SA<br />If it is a PC and is not covered with SA 100 Windows VECD <br />Scenario<br />License<br />
  20. 20. Scenario 6<br />Roaming Users<br />License requirement<br />300 Windows VECD for SA Licenses<br />100 Users<br />300 Company Devices<br />VECD is a device based license. <br />300 devices accessing VDI 300 VECD Licenses<br />If PCs already covered with SA 300 Windows VECD for SA<br />If PCs not covered with SA upgrade to SA, 300 Windows VECD for SA<br />My company has 300 corporate PCs need to access our VDI environment. However, we only have 100 users and only 50 VMs are used at any one time. <br />Scenario<br />License<br />
  21. 21. Scenario 7<br />Non Corporate-owned PC<br />License requirement<br />Jan - June<br />June - Dec<br />100 Windows VECD Licenses<br />100 Contractors <br />100 Contractors <br />My company has 100 contractors that are working for 6 months, and then 100 different contractors are employed for the other 6 months. Each contractor will have one PC (owned by the contractor) to access our corporate VM via VDI. <br />Each non-corporate owned PC will require Windows VECD license. Windows VECD license comes with 90 day permanent reassignment rights. <br />Scenario<br />License<br />100 non-corporate PC accessing VDI 100 Windows VECD Licenses<br />

×