VDI in Windows Server 2012

2,797 views

Published on

More info on http://techdays.be.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,797
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
155
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • When looking at a Desktop Virtualization strategy, you want a solution that gives you the options to provide the best capability and user experience for the user at the time she needs access to the service.The challenges of managing a desktop are that you want to minimize IT cost and complexity while creating an inclusive enterprise wide management strategy that addresses the virtualization of data and user settings, applications, and operating systems.Some questions for you to think about while investigating a Virtualization Solution are: What is your application management strategy?What is your data management strategy?What is your mobile worker management strategy?What is your management strategy across multiple physical and virtual form factors? Microsoft can help with your broader management strategy as you plan your Windows 8 deploymentsWith Desktop Virtualization, we have broken the bonds between the OS, Application, and Data and User Settings. With Virtualization solutions in each of these areas, we provide our customers the ability to provide the best solution for the customer depending on the individual need.
  • Embracing BYODKey Messages:With Windows 7 Flexible Workstyle solutions, IT can embrace the BYOD trend, letting employees bring their personal PC or tablet for work.The benefits include a rich user experience, centralized management of apps and data, enhanced security and compliance, and great choice of Windows devices in a responsible way.Windows 8 along with investments in VDI improves the user’s experience even further by supporting touch and high latency connections.Microsoft Office 365 enables secure, anywhere access to email and calendars, Office Web Apps, web conferencing software, and file sharing capability.Microsoft VDI also supports non-Windows-based devices.As BYOD becomes common today, IT has a challenge in how to enable BYOD, while ensuring end-user productivity and securing the corporate environment. With Windows 7-based devices, IT can embrace the BYOD trend by providing:A rich user experienceWith centralized management of apps and dataAnd enhanced security and complianceAll of that on a great choice of Windows-based devicesBut Windows 8 streamlines the experience even further. By lightly touching the remote access icon on an employee’s Windows 8 tablet, she can login and open a VDI session running in the corporate data center with all her data, applications and settings, as if she were working in the office. For example, she can access her corporate SharePoint sites to submit her timesheet, which she forgot to do before leaving for vacation—from her own Tablet.[speaker notes continued on next hidden slide]
  • Benefits of VDIKey Messages:VDI in Windows 8 delivers the following benefits:Rich Experience EverywhereBest value for VDIEfficient ManagementBack to VDI in Windows Server 2012, we have focused on providing the following benefits:[CLICK]Rich Experience Everywhere.RemoteFX provides rich multimedia experiences through inbuilt software GPU or via hardware GPU in the server. Users can use tablets and any USB peripheral, thanks to true USB and multi-touch-remoting capability. Users receive consistently rich performance over high latency, low bandwidth networks such as wide area networks (WANs).[CLICK]Best value for VDI.FairShare ensures high system performance by dynamically distributing system resources. User disks provide the flexibility to deploy lower cost pooled- and session-based desktops, without sacrificing personalization. Support for lower cost memory such as SMB for file sharing and Direct Attached Storage (DAS).[CLICK]Efficient Management. Simplified wizard makes VDI easier to set up with automatic configuration of VMs. The in-box management console provides powerful administration for users, VMs, and sessions, without requiring additional tools. VMs and sessions can be intelligently patched through randomization and throttling of tasks, ensuring high system performance.
  • RD Virtualization Host – integrates with Hyper-V to provide VMs that can be used as personal virtual desktops or virtual desktop pools. User accounts can be assigned a unique personal virtual desktop or be redirected to a virtual desktop pool that provides VM-based, centralized desktops based on a pool of virtual machines that are shared by multiple users.RD Session Host - Hosts Windows-based applications or Windows desktops for RDS clients. An RDSH server can host App-V applications and session-based desktops. Users can connect to an RDSH server (via RD Connection Broker, RD Web Access or Remote App and Desktop Connection) to run programs to save files and to used network resources on that server. Administrators can use a load-balanced RDSH server farm to scale the performance by distributing RDS sessions across multiple servers.RD Connection Broker – provides a single, aggregated view of RemoteApp applications, session-based desktops, and virtual desktops to users. It connects or reconnects a client computer to either a session-based desktop, virtual desktop or RemoteApp program. It also stores session state information (Session IDs, User names, RD Session Host server name).RD Web Access – provides a customizable web portal for accessing session-based desktops, virtual desktops, and RemoteApp programs. Client queries an RD Web Access server over HTTPS. Resources are displayed from more than one farm, or a combination of farm and individual servers. You can filter the view on a per-user basis so that each user sees only the authorized programs.(continued on hidden slide)
  • So, let’s also look at what we’ve done with High Availability.What you’re looking at is the high-level deployment architecture for all the components that go together in VDI deployment. We looked at these just a couple minutes ago. In order for a VDI deployment to scale and be highly available, each of these components needs to be highly available. In WS08 R2, this is how things worked.RDWeb: Can be scaled out. It’s a web app, so it can scale out as a farm of web servers. Since WS08RDG: Also a web app, so it can scale out as a farm of web servers. Since WS08RDVH: A Hyper-V server, so it works as a HyperV Cluster. Different nodes in the cluster. If one fails, the workloads in the cluster, such as the VMs can migrate to another node in the cluster. Since WS08R2RDLS: Supported a cluster mode since WS08. RDVH and RDSH can access multiple servers in a farm.RDSH: TS Fram. Since WS03, very early version, has supported a farm configuration.The key new thing in WS2012 in this area is the high availability and scalability of connection broker. In WS08R2, we only supported Active/Passive Clustering for connection broker. In WS2012 we changed to support Active/Active mode. Connection broker has an internal database to store the configuration and runtime data for the entire deployment, things like where the user is logged on. What VM is on which host, which apps are published, etc.
  • (continued from previous hidden slide)When Broker is configured in HA mode, you have multiple instances of the Broker, all of which run against a SQL DB cluster. All Broker instances are active: They are responding to load at the same time. Hence this configuration provides both availability and scale.All the key tasks that Connection broker manages, such as VM creation, or user logon creating/mountiung user VHDs, as well incoming connections that get redirected through Broker, all of these tasks work seamlessly with a multi-instance, highly available Broker deployment.This config requires that you have a SQL server in your configuration to host all the data for your VDI deployment. We support a wide variety of SQL clustering modes and SQL versions, including for example SQL Denali & “Always ON” High Availability mode. The most recent innovation that SQL is bringing to the space.Add’l notes:Wizard in Admin UI walks you through the steps needed to set up a new broker instance. Automatically migrates configuration data from the source broker’s data store to the shared SQL database. PowerShell cmdlet to do the same.As in many other farm-type ha configurations, the broker instances need to be configured so they are at the same DNS name and authenticate under the same name. This is typically accomplished by using DNS Round Robin and a shared SSL certificate.  
  • Let’s look at how to configure Active\\Active Remote Desktop connection brokers. The key new thing in WS2012 in this area is the high availability and scalability of connection broker. In WS08R2, we only supported Active/Passive Clustering for connection broker. In WS2012 we changed to support Active/Active mode. Connection broker has an internal database to store the configuration and runtime data for the entire deployment, things like where the user is logged on. What VM is on which host, which apps are published, etc.When Broker is configured in HA mode, you have multiple instances of the Broker, all of which run against a SQL DB cluster. All Broker instances are active: They are responding to load at the same time. Hence this configuration provides both availability and scale.As in many other farm-type ha configurations, the broker instances need to be configured so they are at the same DNS name and authenticate under the same name. This is typically accomplished by using DNS Round Robin and a shared SSL certificate. We can further simplify management by leveraging another new feature of Windows Server 2012, Central Certificate Store (shown in diagram). The central certificate store provides a single location (ie a file share) where shared certificates, such as those used by Web farms, can be managed. When the request for the certificate is received by the Web server, instead of picking the certificate from the local computer MY store, the Web server picks it from the configured CSS binding location. This means that administrators need to manage only a single certificate instance for a particular Web site in a farm-based configuration.All the key tasks that Connection broker manages, such as VM creation, or user logon creating/mountiung user VHDs, as well incoming connections that get redirected through Broker, all of these tasks work seamlessly with a multi-instance, highly available Broker deployment.This config requires that you have a SQL server in your configuration to host all the data for your VDI deployment. We support a wide variety of SQL clustering modes and SQL versions, including for example SQL Denali & “Always ON” High Availability mode. The most recent innovation that SQL is bringing to the space.Wizard in Admin UI walks you through the steps needed to set up a new broker instance. Automatically migrates configuration data from the source broker’s data store to the shared SQL database. Powershellcmdlet to do the same.As in many other farm-type ha configurations, the broker instances need to be configured so they are at the same DNS name and authenticate under the same name. This is typically accomplished by using DNS Round Robin and a shared SSL certificate.  
  • [Review slide contents]
  • [Review slide contents]
  • [Review slide contents]
  • [Review slide contents]
  • [review the VDI Infrastructure requirements as shown on the slide]The virtual machine mode in Sysprep is a new feature introduced in Windows Server 2012 that makes creating and cloning virtual machines faster.
  • [Review slide contents]
  • From Server Manager, run Add Roles and Features Wizard and select Remote Desktop Services Scenario-based InstallationSelect Deployment Type of StandardSelect the desired deployment scenario, either Desktop Virtualization or Session Virtualization. Note that the wizard will adjust for configuration of the appropriate role services in support of the selected scenario. On the slide, 3a shows VDI and 3b shows Session.
  • Review the role services to be installed. Note that the wizard will install the Remote Desktop Broker and Remote Desktop Web Access for both the VDI and Session deployment scenarios; however, 4a shows the Remote Desktop Virtualization Host in support of VDI while 4b shows the Remote Desktop Session Host being installed.Steps 5 & 6 are identical for both VDI and Session, allowing you to specify the appropriate server to be used for each role (RD Connection Broker and RD Web Access)
  • Depending on the scenario you are configuring, you next specify the server to be used for either the RD Virtualization Host server or the RD Session Host servers.The final step of the wizard runs a compatibility check and if all the selected servers pass the check, the deployment will be finalized.
  • From Server Manager, run the Add Roles and Features Wizard, and then select Remote Desktop Services Scenario-based InstallationSelect Deployment Type of Quick StartSelect Deployment ScenarioDesktop Virtualization Session Virtualization
  • Select the server on which to install the roles and services. Note that the only difference between the VDI and Session Deployment process is the configuration of the virtual desktop template for VDI. The wizard will run a prerequisite check and if it passes, the deployment will be completed.
  • [Review slide contents]
  • [Review this summary of VDI architecture choices]
  • Remember:Pooled VMs. Pooled VMs give users access to high-performance desktops from any connected device. VDI assigns users VMs on-demand from an existing pool. When they log off a VM, VDI returns the VM to the pool for another user.Personal VMs. Personal VMs give users access to a personal, high-performance desktop over which they have full administrative control.This slide presents details of the differences between the two.[review slide contents]
  • There are two types of virtual desktop collections available in Remote Desktop Services in Windows Server 2012: personal and pooled. You have the option to let Remote Desktop Services automatically manage virtual desktops in a virtual desktop collection.Perhaps the most interesting improvement is the ability of IT Pros to create a pooled virtual desktop collection, which is a template of the desktop that's to be used by all VDI users in an organization. A whole batch of virtual desktops can be created using the template. An IT pro just has to maintain the patch cycle for the single template, and not for the multiple users. To confirm deployment, connect to a collection with Internet Explorer by typing:https://<FQDN of server>/RDWeb
  • [Review slide contents]
  • [Review slide contents]
  • With the improved RDS, Microsoft has dropped the requirement of having a physical graphics processing unit in place on the client device to use its RemoteFX technology. RemoteFX can support graphics-intensive apps, such as CAD/CAM design programs, on thin-client devices. Now, the thin client no longer needs a physical GPU to run such applications.[review the other bullets on the slide]Microsoft improved the WAN performance of RemoteFX, adding about 10 improvements. Highlights include optimized media streaming, adaptive network autodetect, single sign-on, multitouchand Remote Desktop with the new Windows 8 experience.With regard to multitouch support, RemoteFX on Windows Server 2012 now supports full remoting of gestures (e.g., pinch and zoom) between the client and host with up to 256 touch points. Microsoft added a Remote Desktop app to the Windows Store to provide an immersive touch-first remoting experience.The optimized media streaming feature in RemoteFX is designed to reduce bandwidth consumption. Adaptive network autodetect frees end users from having to specify the network connection type. Microsoft also streamlined the single sign-on process by reducing the number of certificates involved.RemoteFX can be configured through Group Policy.
  • Unifying of the remoting experience. All features of RDP are available to both sessions and VMs, providing a consistent user experience.WAN Improvements. RDP performs well even over high-latency connections, such as satellite links. Through the use of progressive download, H.264 encoding for video compression, and UDP as needed to reduce networking overhead, RDP can display bandwidth-intensive content such as video over high-latency networks.Simplified connection. Users can connect to their personal collection of VMs and RemoteApp programs assigned to them by logging in with their email address and password.Improved user personalization. User profile disks allow users to preserve user personalization settings across session collections and pooled virtual desktop collections—even for settings not stored in a user profile. This feature is available for both sessions and VMs.More integrated local and remote experience —In Windows Server 8, Remote Desktop Services supports remoting of a broad range of USB devices (such as an all-in-one printer, a scanner, a biometric reader, a webcam, or a VoIP headset) from both sessions and VMs. RDP now also supports Aero Glass UI remoting in sessions, even when more than one monitor is connected to the client device.
  • Support for multi-touch and gesture remoting. Use multipoint touchscreens and tablets even when connecting to a session or VM.Simpler logins. Windows Server 2008 R2 supported Web-based singlesign-on for RemoteApp programs so that a user could provide their credentials just once to authenticate to any RemoteApp provided in any farm. This support has been extended to include VMs assigned to a user.Evenly distributed allocation of resources to everyone on a RD Session Host server. VMs are isolated from each other, but sessions all compete for the same server resources. In Windows Server 2012, processor time, disk I/O cycles, and network are all shared evenly among all sessions on a RD Session Host server so no single user can consume all resources.Concurrent reconnection. One advantage of RDS is that you can disconnect from your workspace and then reconnect from another location. In Windows Server 2012, you can disconnect, go home, and then reconnect to the RemoteApp programs and VMs that you were using all at once, saving time as you restore your work environment.
  • Basically, this slide is showing a web page and how we dynamically look at the content of the page and compress them all appropriately. So this page, for example, there is a lot of text, a set of images and a Flash video playing. With RDP8, we look at each of those components separately and encode them using a different encoder that is appropriate for the type of content. So text being coded in one way, we make sure that we always maintain the text to stay clear. With images, we can do what we call a progressive rendering to make sure that we can get the page up for the user and deliver the clearest version appropriately. Same as with video and animations - we have a few ways that we can handle video to make sure that what we deliver to the user is a great way. One other thing that we can do is take any video whether it is Flash, Silverlight or Movie encoded in H264 and send it down at the end-point, take care of decoding and then play it back if the end-point is capable of doing that. We also do things like switch to UDP traffic for video, where you drop a few package, few packets are delivered, lots of because of the speed and there is a way to retransmit it.
  • So, a little bit more on RemoteFX progressive rendering. Basically, if we look at the network speed and determine it’s a slow network, we send the text down. The text is always clear but we actually send multiple iterations of the graphics on the page. It’s little bit like how surfing the web was back in the 90’s, if you remember doing that, images were first coming very blocky and then werejust progressively re-rendered or your browser re-rendered the images, so you didn’t have to wait for the entire image to download to be able to see the page. The graphic here shows how they would potentially look. One of the other things that we are doing in Server 2012 is dynamically detect the network speed and adjust appropriately. If we determine we are on a very fast connection the server will use progressive rendering. If we determine it’s a slow network then progressive rendering will kick in to deliver best experience to user.
  • With Windows Server 2012, technologies such as RDS and Hyper-V provide the scalability and flexibility that enterprises demand from their virtual desktop platform.FairShareFairshare is a collection of technologies that ensure that no single VM or session hogs machine resources (memory, disk I/O and bandwidth), thereby reducing the impact to other users on the system. If a VM / Session starts to utilize more resources than deemed safe by the system, Fairshare will automatically throttle the resource in question, thereby dynamically distributing that resource across other VMs/ Sessions.RDS has Fairshare built in to manage resources for Sessions. Hyper-V has a collection of technologies to manage bandwidth, I/O and memory, collectively ensuring performance of VMs.
  • [review slide contents]
  • [review slide contents]
  • [review slide contents]
  • [review slide contents]
  • [review slide contents]
  • [Initial Build]V-Alliance was created to provide Microsoft and Citrix partners with the tools and resources to help customers design and implement virtualization solutions that meet business needs for flexibility, security, scalability, device independence. MS and Citrix have been close partners for over 20 years, dating back to the days of Windows NT.[See http://www.citrixandmicrosoft.com]Microsoft and Citrix are better together in delivering the best complete Desktop Virtualization solution in market:Microsoft…is the Market Leader for DesktopsBest in class Application VirtualizationOver 45m MDOP licenses sold and more than 100 cases studies of global companies using App-V and many together in partnership with Citrix technologiesCitrix XenApp and XenDesktop provide full support for App-V integrated the delivery of virtual applications to the Citrix Receiver or surfaced within Cloud Gateway for self service. Customers can get the best of both virtual application and virtual desktops by combining Microsoft and Citrix.With UE-V, customers can be confident their personalized settings for the OS and applications will be with them no matter how they access Windows 7 or Windows 8. If they are using XenDesktop for their virtual desktops or Xenapp for application access, UE-V will keep their experience consistent in both cases.Modern Server PlatformMicrosoft Cloud OS vision delivers a modern platform of products and services that helps enterprises transform their current infrastructure. The Cloud OS delivers Integrated Virtualization via Hyper-V and VDIto help enterprises achieve the modern datacenter, which includes an infrastructure that provides a generational leap in agility, leveraging virtualization to deliver a highly scalable and elastic infrastructure with always-on, always-up services across shared resources and supporting cloud service delivery models with more automated management and self- service provisioning. With Windows Server 2012, the Microsoft Cloud OS is engineered for the cloud from the metal up with virtualization built as an integrated element of the operating system, not layered onto the operating system. Citrix technologies are built to run on Microsoft. XenDesktop and XenApp can be run on top of Windows Server 2012 and Hyper-V and if desirable HDX and RemoteFX can be used together.Microsoft Hyper-V is the Hypervisor optimized for VDI (with a 40% higher VM density)
  • [continued from previous slide]Microsoft System Center offers People-centric management of Devices, Desktops and virtual assets, from hardware to apps, data and OS, in the cloud or on premises Is integrated with Citrix via the XenApp Connector allowing XenApp apps to be managed and delivered through SCCM.Together, Microsoft System Center Configuration Manager and Citrix XenDesktop ensures IT organization  have a more accurate inventory of virtual desktops, improved enforcement of configuration policies, greatly enhanced reporting to meet business and technical demands, and complete automation of virtual disk patching.Citrix XenApp and System Center Configuration Manager in combination facilitate a broad range of application and desktop delivery mechanisms demanded by today’s business needs.  This also enables a single pane of glass to deliver any Windows application to any user on any device through the broad footprint of Citrix Receiver.Citrix XenDesktop and System Center Virtual Machine Manager pairing enables delivery of high-availability and load balancing services for XenDesktop virtual machines while leveraging Citrix Provisioning Services to extend scalability to thousands of concurrent virtual desktops in a single infrastructure.By integrating the XenApp’s robust provisioning features with the hypervisor management features in Virtual Machine Manager, administrators can  add (or remove) computing horsepower to meet growing and/or flexible demands.Microsoft’s Virtual Machine Manager in combination with Citrix XenServer facilitates unified virtual machine management across both XenServer and Hyper-V hypervisors with the same levels of parity for deployment, migration and a variety of host management functions. Citrix in cooperation with ComTrade has developed a Management Pack that extends Operations Manager’s vision deeply into a XenDesktop infrastructure.  This added visibility greatly enhances the efficacy of Operations Manager’s behavioral, logging, and performance monitoring, and aids IT administrators in quickly tracking down problems and implementing resolutions.
  • Citrix is…the market Leader for Virtual Desktops with XenDesktop which provides a solution thatsupports all FlexCast models to deliver virtualization scenarios on any device type. Here are some examples on where Citrix brings additional value on top of the Microsoft platform. Receiver, XenDesktop and XenApp help customers when they have needs in the following areas:   Many devices types accessing Windows applications or desktops in the datacenter A consistent rich experience across ALL - Windows XP, Windows Vista, Windows 7 & 8 over LAN/WANNon-Windows devices accessing Windows applications or desktops in the datacenter over LAN or WAN Hosted Application compatibility for Windows Server 2012, Windows 8 and down level operating systems -i.e. Windows Server 2008, Windows 7 or belowCustomers need to mix & manage multiple Windows Server versionsWAN support for sessions running on Servers other than Windows 2012Need enterprise scale VDI administration tools that integrate with system centerExtend VDI solutions beyond sessions and VMs to include Desktop Streaming using PVSNeed to embrace both private and public cloudsXA solutions on common IaaS clouds powered by Citrix CloudPortal Service ManagerCitrix provides the only certified workload on MS Private CloudSupport customers with heterogeneous hypervisors in the datacenterXenClient provides an enterprise client hypervisor solutions for all users that enables:Efficient image management and update via the XenClient Synchronizer that can deliver images to clients both on the LAN and WAN.Provide the ability for everyday users to leverage their Windows Enterprise license by simply being able to use multiple local VMs with all their USB devices and rich graphics capabilitiesEnable high security scenarios by leveraging a ‘kill pill’ feature to automatically suspend the use of VMs that have not contacted home frequently enoughTogether, Microsoft and Citrix offer best of breed solutions for all Desktop Virtualization Scenarios. We’ll talk about each of these in turn over the next few slides
  • Customers will find that in a world of mixed Windows Server platform, mixed virtual desktop environments, mixed end-user devices, mixed clouds and mixed desktop use cases, they will need a Citrix solution to help bring it all together and make coherent sense out of it all.With the introduction of Windows Server 2012 and Windows 8 Microsoft has made a number of investments in VDI and customers often ask why Citrix?  The market is evolving, technology is moving fast. Microsoft and Citrix continue to work together to ensure a great experience for are shared customers. Microsoft has a longstanding partnership in helping customers in virtualization and access, and both technologies build on and expand the Microsoft platform to deliver significant value to our joint customers. They continue to work closely with Citrix to ensure a high level of integration with our products and look forward to this partnership continuing as Windows 8 and Windows Server 2012 bring new opportunities for innovation.
  • SummaryIn this session you’ve learned about:The Power of VDI and how it’s deployment has been simplified.The partnership between Microsoft and CitrixThe improvements made to high availability of remote desktopsThe improvements to RDS that Windows Server 2012 brings to the tableThe enhancements to RemoteFX
  • VDI in Windows Server 2012

    1. 1. Separating the desktop computinglayersMicrosoft delivers a broad range of desktop virtualization offerings to • Folder Redirectionaddress your unique business and IT challengesProfiles • Roaming Data & User Settings • User Experience Virtualization (UE-V) • Profile disks • Application Virtualization (App-V) Applications • RemoteApp Operating • Virtual Desktop Infrastructure System • Remote Desktop Services session- based desktops
    2. 2. Embracing BYOD/COIT Virtual Desktop Hosted Infrastructure Applications (VDI) (RemoteApp) Office 365 BENEFITS Powered by Remote Desktop Services (RDS) • Secure, fast browsing • Rich user experience; FIREWALL • Touch enabled with Windows 8 devices WINDOWS 8 ADVANCEMENTS • Centralized management • High fidelity RemoteFX experience on of app & data (IT) LAN / WAN • Multi-touch support for modern • Enhanced security applications and devices and compliance (IT) • Support for local USB, Lync, etc. • Great choice of Windows- based devices
    3. 3. Your computer IS your tool for work Your computer CONTAINS your tool for work
    4. 4. …. To this From this….Well its really asquare…..
    5. 5. Benefits of Microsoft VDIRich experience Best value for virtual Efficient managementeverywhere desktops Rich multimedia Fairshare Simplified wizard experiences True USB and multi-touch In-box management User disks remoting console Consistently rich Lower-cost storage Intelligently patching performance
    6. 6. Windows Server 2012 RDS Architectural Components SMB, SANs, or direct attached local storage
    7. 7. High availability for all RDS rolesNew in Windows Server Web farm Remote Remote Desktop Remote Desktop2012 Remote Desktop Connection Desktop Remote Desktop Virtualization Host Remote Desktop Virtualization Host Connection Broker Virtualization Host Connection • Active/active high availability Broker Broker Remote Desktop mode for brokers Remote Desktop Web Access Remote Desktop Web Access Remote Hyper-V Web Access Desktop cluster • Scale-out File Server and Connection Broker resiliency SQL Server Clustering Databas Remote Desktop e Remote Desktop Session Host • Requires Microsoft SQL Remote Desktop Session Host Session Host Server Remote Remote Desktop • Automatic data migration Remote Desktop Gateway Desktop Gateway from single instance to high Gateway Remote Remote Desktop Remote Desktop Session Host farm Web farm availability Remote Desktop Licensing Desktop Licensing Licensing Cluster
    8. 8. Configuring RD Connection Broker forhigh availability RD Virtualization Host Remote Desktop Connection Broker 01 Hyper-V clusterRD Client DNS Remote SQL Server Cluster Desktop Connection RD Broker 02 Gateway RD Gateway Farm Remote Remote Desktop Desktop Connection Session Host Broker 03 RD Session Host Farm HA Central Certificate Store
    9. 9. High Availability - RD ConnectionBroker configuration prerequisites• SQL Server (at least SQL Server 2008 R2) for connection broker servers to use• SQL server configured with full permissions granted to connection broker servers• Windows firewall on SQL server configured to “Allow SQL Server Access” from connection brokers• Network folder to store SQL database files (can be created on SQL server computer)• SQL client installed on connection brokers• Static IP addresses configured on the connection broker servers.• DNS “A” resource records for each of the static IP addresses that point to the same, shared name (enables DNS round robin)
    10. 10. HA Configuration BrokerConfiguration• Starting point for enabling HA is to configure a single RD connection broker for either virtual machine or session-based deployment• In Server Manager, configure RD connection broker for high availability• Enter SQL connection string, database folder, and DNS round- robin name
    11. 11. HA RD connection broker results• Local connection broker data migrated to SQL and the connection broker will start using SQL for data immediately• In Server Manager, the option to add additional connection broker servers to is enabled • If the connection broker role service is not already added to server, it will be added automatically• RD connection brokers use SQL to store data• The RD virtual host, session host and Web access (end nodes) are configured with all the RD connection broker server names • Will choose a connection broker name at random to connect to• RDP clients use the DNS round-robin name• If any RD connection broker loses connection to SQL, all connected end nodes immediately disconnected and will try to establish connection with other connection brokers
    12. 12. Virtual desktop deployment choices Desktop Pooled Personal Sessions VMs VMs Corporate Office Branch Office 1 platform • 1 experience • 3 deployment choices FIREWALL Home Library / Coffee house
    13. 13. Session Virtualization Requirements• The computer must be a member of a domain• The RD Connection Broker role service cannot be installed on the same computer as Active Directory Domain Services• Administrator must belong to the local administrators security group• A network share configured for storing user profile disks is required • All RD Virtualization Host computer accounts must have the ability to read and write to this location
    14. 14. VDI Infrastructure Requirements• The server must have hardware-assisted virtualization• The computer must be domain-joined• The RD Connection Broker role service cannot be installed on the same computer as Active Directory Domain Services• Administrator must belong to the local administrators security group• A network share configured for storing user profile disks is required • All RD Virtualization Host computer accounts must have the ability to read and write to this location• VDI Quick Start • The virtual desktop template (a virtual hard disk) • Must be generalized by using Sysprep (Virtual Machine Mode), and then shut down • A virtual switch must NOT be created on the server running Hyper-V (the Quick Start deployment type creates one)• VDI standard deployment • The virtual desktop template must • Have the correct virtual switch selected • Be generalized using Sysprep (Virtual Machine Mode), and then shut down
    15. 15. Desktop virtualization (VDI)deployment modes• Desktop Virtualization (VDI) • Standard • Installs appropriate roles on separate computers • Quick Start • Installs the RD Connection Broker and RD Web Access role services on a single computer • Creates a pooled virtual desktop collection with two pooled virtual desktops based on a virtual hard disk that’s the virtual desktop template • Creates a Hyper-V network switch named RDS Virtual
    16. 16. Standard Deployment a - VDI b - Session
    17. 17. Standard Deployment (cont.)
    18. 18. Standard Deployment (cont.) a - VDI b - Session If compatibility check succeeds, deployment proceeds
    19. 19. Quick Start Deployment a - VDI b- Session
    20. 20. Quick Start Deployment (cont.) a - VDI b - Session [Need screen shot of virtual desktop template from a machine with hardware virtualization enabled]
    21. 21. Preparing the Master or Gold VM (Virtual DesktopTemplate)a desktop virtual machine on the Hyper-V server• Configure • Snapshots ARE supported for the template VM • The VDI creation process will use the currently active (“Now”) snapshot • If static memory is configured, the minimum amount is 1024 MBs; if dynamic memory is configured, the maximum memory must be at least 1024 MBs • If using the standard deployment model, the master VM must be connected to a virtual switch that can communicate with a domain controller • Note: Quick Start creates a virtual switch• Install the operating system and any applications that need to be included in the template VM • OS must be at least Windows 7 with SP1 or Windows 8 • Installed in a workgroup • VMs are automatically joined to the domain specified in the VDI wizard• Apply any patches or updates to the VM as required• Make any other configuration changes as required • For example, you can create a customized default profile. Note that this would require you to use Sysprep and an unattend.xml file with the CopyProfile setting set to TRUE in the specialize phase of Windows setup • In this case, you must generalize the image and then run through Out-of-the-box experience (OOBE) set up again before the final preparation of the image• In the virtual machine run the following command from WindowsSystem32Sysprep directory: • Sysprep /oobe /generalize /mode: vm
    22. 22. Choosing the Right VDI Architecture
    23. 23. Detail: Personal vs. Pooled VMs
    24. 24. Virtual Desktop Collections with UserProfile Disks • Created in Remote Desktop Services tool of Server Manager* • 2 types of collections • Personal desktop • Update with WSUS • Shared (“pooled”) desktop • Update automatically using a VDI template • Connect to a collection with Internet Explorer https://<FQDN of server>/RDWeb*Session collections can also be created
    25. 25. Personalization with User Profile Disk• Benefits What should I deploy?• Available with pooled virtual • User profile disk with every machine collections and RDSH virtual machine pool and collections RDSH collection• Stores all user settings and data • UEV to roam settings across• Container for: collections • Roaming User Profile • FR to roam user data across • Folder Redirection cache collections • User Environment Virtualization • FR to centralize user data• Roams with user within backup collection• Appears as local disk, improves app compatibility
    26. 26. RemoteFX over LAN or WAN RemoteFX delivers a consistently rich user experience to users over LAN or WAN (regardless of deployment model) Hardware and software GPUs Rich multimedia Corporate LAN USB redirection Internet or WAN Multitouch WAN acceleration Single sign-on
    27. 27. RemoteFX – Improved UserExperience• Enables the delivery of a full Windows user experience to a range of client devices • Improved WAN performance • Multitouch support • Includes rich clients, thin clients, and • Configured through Group Policy ultrathin clients• Delivers a rich user experience for: • Virtual Desktop Infrastructure (VDI) • Provides a 3D virtual adapter, intelligent codecs, and the ability to redirect USB devices in virtual machines • Session-based desktops and RemoteApp programs to a broad range of client devices• Integrates with the RDP protocol • Enables shared encryption, authentication, management, and device support
    28. 28. Windows 8 RemoteFX Improved User ExperienceUnifying of the remoting experience • All features of RDP are available to both sessions and VMsWAN Improvements • Progressive download, H.264 encoding for video compression, and UDP as needed to reduce networking overheadSimplified connection • Users can connect to their personal collection of VMs and RemoteApp programs assigned to them by logging in with their email address and passwordImproved user personalization • User profile disks allow users to preserve user personalization settings across session collections and pooled virtual desktop collectionsMore integrated local and remote experience • Remoting of a broad range of USB devices (such as an all-in-one printer, a scanner, a biometric reader, a webcam, or a VoIP headset)
    29. 29. Windows 8 RemoteFX Improved User Experience, cont.Support for multi-touch and gesture remotingSimpler logins • Single sign-on for Remote App programs extended to include VMs assigned to a userEvenly distributed allocation of resources to everyone on a RD SessionHost server • No single user can consume all resourcesConcurrent reconnection • You can disconnect, go home, and then reconnect to the RemoteApp programs and VMs that you were using all at once, saving time as you restore your work environment
    30. 30. RemoteFX adaptive graphics Text Content Image Content Video/Animations
    31. 31. RemoteFX progressive rendering
    32. 32. Fair Share Dynamically distribute resources (bandwidth, CPU, and I/O)Help ensure high performanceacross user virtual machines Apply to both sessions andand sessions virtual machines
    33. 33. VDI Licensing componentsTwo main components: • License for connecting to the VDI Infrastructure: RDS CAL • For any solution using any of the Remote Desktop or RemoteFX services, including Citrix XenDesktop, Citrix XenApp, etc. • RDS CAL licensed per user or per device • Includes rights to use App-V with Remote Desktop sessions • License to access a virtual instance of a Windows Client OS: • Software Assurance (SA) • Virtual Desktop Access (VDA) • Windows Intune • Companion Subscription License (CSL)A license to access a virtualized instance of a client OS is always required • The circumstances and context determine what kind of license (SA, VDA, CSL, etc) is required
    34. 34. Software Assurance VDI Benefits• Access to Windows 8 Enterprise edition• Access rights for up to 4 VMs concurrently (local or remote)• Roaming Rights for access from non-corporate device• Access to Windows Thin PC for free• Option to purchase MDOP• 24*7 support, training vouchers and other benefits
    35. 35. VDA (Virtual Desktop Access)• Rights to access virtual copies of Windows via devices that don’t qualify for SA: • Thin Clients • Consumer Devices (e.g. iPads) • Third party devices (contractor PCs) • PCs not covered by SA• Licensed Per Device• Annual Subscription
    36. 36. Companion Subscription License• Optional add-on for primary user of SA or VDA licensed devices• Is for companion (non-primary) devices• Single license covers up to 4 additional devices• Eligible for any personally owned and/or non-x86 corp-owned devices anywhere (on/off-prem)• Includes Windows To Go and VDA rights• No local install rights• Offered in EA, EA subscription, Select Plus, and EES/CASA programs• No companywide commitment required and can be purchased in any quantity• Included with any Windows RT device
    37. 37. Licensing Windows SA, VDA, and CSL Primary work device? Primary User of (regardless of ownership No Yes Corp owned? No On Premises? and location) SA/VDA licensed device? No Yes No Yes Yes Windows RT Any Device Other x86/x64 PC Other x86/x64 PC (No License Required (Roaming Rights: No (Thin Client, iOS, (w/ Qualifying OS) (iOS, Android, etc)(w/ Qualifying OS) for VDI) License Required) Windows RT) VDA CSL SA
    38. 38. V-Alliance: Microsoft and Citrix Jointly Integrated, Unified Management User State Virtualization Application Virtualization OS Virtualization
    39. 39. Why Citrix for desktop virtualization?Work anywhere, made anywhereIf you need…• a mix of Windows Server 2003, 2008, 2008 R2 & 2012• a mix of Windows XP, Windows 7 & Windows 8 virtual desktops• a mix of Windows & non-Windows user devices• a mix of private, service provider and hybrid desktop infrastructures• a mix of use cases (e.g. VDI, streamed OS, remote, offline, 3D, apps…)• to scale hosted desktop, sessions, apps from hundreds to many thousands of end-points• to support heterogeneous hypervisors in the datacenter …then you need enterprise class desktop virtualization from Citrix
    40. 40. Summary VDI Simplified Citrix Improved High Partnership Availability RDS RemoteFX Improved Enhanced

    ×