Microsoft Hyper-V

Microsoft Hyper-V

• 1.
  Microsoft Hyper-V VDI DeploymentScenarios Ready to see how? Just click the arrow to get started.
• 2.
  Introducing Hyper-V, codenamed “Viridian”and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems. Hyper-V was introduced by Microsoft in Windows 2008 and 5.0 is last version of Hyper-V that it’s a component of Windows 2012 R2. Back
• 3.
  Architecture Hyper-V is ahypervisor- based virtualization technology for x64 versions of Windows Server 2008. The hypervisor is the processor- specific virtualization platform that allows multiple isolated operating systems to share a single hardware platform. Back Next
• 4.
  Components Microsoft Hyper-V hassome components to covers different virtualization scenarios. Some of important components are as the below: 1. Hyper-V and Failover Clustering 2. Live Migration 3. Hyper-V Storage 4. Session Modes Back Next Hyper-V and Failover Clustering Live Migration Hyper-V Storage Session Modes
• 5.
  Scalability This topic liststhe supported maximum configuration for the various components. As you plan your deployment of Hyper- V, consider the maximums that apply to each virtual machine as well as those that apply to the physical computer that runs the Hyper-V role. Back Next Virtual Machines Virtual processors: 64 Memory: 1 TB Virtual Hard Disk Capacity: 64 TB – VHDX Virtual network adapters: 12 Hyper-V Server Logical processors: 320 Running virtual machines per server: 1024 Virtual processors per server: 2048 Memory: 4 TB Physical network adapters: No Limit Virtual switches: No Limit Virtual network switch ports per server: No Limit Nodes per cluster: 64 Running virtual machines per cluster and per node: 8000
• 6.
  Supported Guests Hyper-V Supportswide range of client and servers operating systems. All Windows clients prior to Windows XP SP2 and all Windows servers prior to Windows 2003 SP2. Also Hyper-V supports most Linux distributions by LIS (Linux Integration Service) drivers and BSD distributions by BIS (BSD Integration Service) drivers. Back Next
• 7.
  Remote Protocol Hyper-V isusing RemoteFX and RDP for establishing remote connection to virtual machines. RemoteFX supports, 3D and vGPU, USB redirection, multimedia redirection and some others good features to delivering desktop experiences to the users. It’s supporting DirectX as built- in feature. Back Next
• 8.
  Licensing There is fourtypes of Hyper-V licensing: 1. Licensing for server virtualization 2. Licensing for desktop virtualization 3. Licensing for application virtualization 4. Managing virtual environments Back Next
• 9.
  VDI Scenarios Virtual DesktopInfrastructure is an important concept in IT today. Hyper-V can help IT managers to deploy their VDI scenarios. Back
• 10.
  Virtual machine (VM)–based Inthis scenario, Windows 8.1 VMs run in a Hyper-V infrastructure. You use Remote Desktop Services to provide users remote connectivity to the VMs. We can use the VM- based deployment scenario with pooled or personal VM collections. Supported client devices: The client provides access to the remote desktop. it can be a traditional device running the Remote Desktop Client in Windows, an app that supports RDP and RemoteFX, a thin or zero client that supports RDP (such as Windows Thin PC), or a RemoteFX- enabled device. Back Next Hyper-V Components For This Deployment Remote Desktop Connection Broker Remote Desktop Virtualization Host Remote Desktop Web Access Client
• 11.
  Session-based In this scenario,remote users connect to Remote Desktop Services in Windows Server 2012 R2 and run their application in Windows Server 2012 R2 sessions. Only Remote Desktop Services is required for this scenario. Supported client devices: Any device that supports RDP or RemoteFX (including Windows Thin PC) Back Next
• 12.
  Windows MultiPoint Server2012 Windows MultiPoint Server 2012 enables multiple users to share one computer and provides a low-cost alternative to traditional computing scenarios in which each user has their own computer. Supports the following: • Direct video–connected stations • USB zero client–connected stations • USB-over-Ethernet zero clients • Any device that supports RDP or RemoteFX Back Next Standard Premium Number of simultaneously connected stations 10 20 Can be joined to a domain? No Yes Virtualization support as a host or guest operating system? No Yes
• 13.
  RemoteFX Certified Devices Manyvendors introduce Zero Clients and Thin Clients to supporting RemoteFX, RDP and Hyper-V VDI scenarios. You can see some of the certified clients. The clients have three types: 1. Clients with Windows Embedded Standard 2. Linux Based 3. Dell Wyse ThinOS Back Next Dell 3012 Dell Wyse D90Q7p HP T610 – HP T510
• 14.
  That’s it Thanks forreading! Back