Many customers ask me, What's the suitable solution between Microsoft VDI & App-V.As per our discussion with support team, We summarized below
Microsoft App-V Solution
Application Virtualization from Microsoft enables software to be as instantly available and easy to use as electricity. Application virtualization transforms applications into centrally managed services that don’t conflict with other applications. App-V software is provided with Software Assurance license as a part of MDOP.
v Integrated Platform
o Virtual applications work like installed applications
o Virtual applications use Windows standards
o No dedicated drive letter required
v Flexible Virtualization
o Multiple App-V applications can share the same virtual environment
o Designed to support highly integrated applications
o Preserve existing investments in App-V
v Powerful Management
o New web-based management interface
o Optimize for VDI with one management workflow
o Rich PowerShell scripting allows automation and customization
Microsoft VDI Solution
Microsoft RDS provides three deployment choices so customers can have the flexibility to deploy the right type of VDI desktop for their users, all from a single platform. Customers can host either:
Licensing for Virtual Desktops
=====================
· Windows for virtual desktops is licensed by access device. In the case of a primary work device, Software Assurance (SA) is recommended if the device uses Windows Pro, or else Virtual Desktop Access (VDA) is recommended if it is a thin-client or a non-Windows device. If the device is a secondary work device then a Companion Subscription License (CSL) is recommended.
· When purchasing a VDA license you get product key that can only activate client operating systems and must be hosted on a client operating system (Product key group: Volume license for Windows 8). The reason it must be hosted on a client OS is that the KMS key must be able to active the KMS host and we would not want a customer to be able to buy a client license and get a key that can activate a server OS.
· Thin Clients can be used to access Virtual Desktops in the servers. For enabling this, customer needs VDA license & VDI + RDS in case he is using Microsoft technology as connection broker for desktop delivery to Thin Clients or he can use Citrix/VMware and buy only RDS instead of VDI+RDS.
Option 1: Choosing Licensing components for Windows Server 2012 R2 Session Based Desktops
===================================================================
Licenses required:
· Software’s
ü Windows Server 2012 R2
ü Windows 7 or Windows 8 OS – Licensed per device to access the RD Web Access
NOTE: Licenses from original equipment manufacturer (OEM) and full packaged product (FPP) licenses does not permit the flexibility that VDI requires.
· Licenses
ü Windows Server/Client CAL – Licensed per device/user
ü RDS CAL – Licensed per device
Option 2: Choosing separate Licensing components for RDS CALs, SCCM CML, etc for VDI environment
=======================================================================
Licenses required:
· Software’s
ü Windows Server 2012 R2
ü Windows 7 or Windows 8 OS – Licensed per device
NOTE: Licenses from original equipment manufacturer (OEM) and full packaged product (FPP) licenses does not permit the flexibility that VDI requires.
· Licenses
ü Windows Server/Client CAL – Licensed per device/user
ü Virtual Desktop Access (VDA) – Licensed per device
NOTE: VDA License is only required if your Windows 7 does not have Software Assurance or you have Thin Client OS
ü RDS CAL – Licensed per device
ü RDS External Connector – Optional
NOTE: Licensed per server for Volume Licensing customer who needs to provide access for customer’s partners/external vendors who are not a part of the customer’s employees
ü SCCM CML for SCVMM Management – Optional
NOTE: You may use VMM under your VDI suite license to manage, at any one time, up to four virtual Client OSEs in which software you are using remotely from your VDI licensed device is running. Those virtual OSEs may be on up to four different VDI hosts. You may not manage OSEs that are not on VDI hosts
Option 3: Choosing license “VDI Suite” for VDI environment
==========================================
Licenses required:
· Software’s
ü Windows Server 2012 R2
ü Windows 7 or Windows 8 OS – Licensed per device
NOTE: Licenses from original equipment manufacturer (OEM) and full packaged product (FPP) licenses does not permit the flexibility that VDI requires.
· Licenses
ü Windows Server/Client CAL – Licensed per device/user
ü Virtual Desktop Access (VDA) – Licensed per device
NOTE: VDA License is only required if your Windows 7 or Windows 8 does not have Software Assurance or your have Thin Client OS
ü VDI Suite which includes (RDS CAL, Configuration Manager CML for SCVMM) – Licensed per device
NOTE: An RDS CAL that’s restricted to deploying VMs only (no session virtualization) & a CML (Client Management License) for System Center Configuration Manager (SCCM) restricted to VMM use only.
ü RDS External Connector – Optional
NOTE: Licensed per server for Volume Licensing customer who needs to provide access for customer’s partners/external vendors who are not a part of the customer’s employees
ü MDOP Suite - Optional
Good Luck :)
No comments:
Post a Comment