This guide is intended for IT professionals, and tells how to configure Remote Desktop Connection Broker in a failover cluster. The configuration provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection
A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service. This guide describes the steps for configuring Remote Desktop Connection Broker (RD Connection Broker) in a failover cluster, as part of a configuration that provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection. As you work with the configuration in this guide, you can also learn about failover clusters and familiarize yourself with the Failover Cluster Manager snap-in in Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter.
Deploying Remote Desktop Connection Broker with High Availability click here: Start download
Failover of clustered RD Connection Broker
Servers providing a virtual desktop
1. The user requests a connection to a virtual desktop, either a personal virtual desktop or one from a virtual desktop pool.
2. The RD Gateway receives the request.
3. The RD Gateway sends the request to a virtual machine redirector (that is, RD Session Host running in virtual machine redirection mode). The virtual machine redirector informs RD Connection Broker, and then waits for the IP address of a virtual machine.
4. RD Connection Broker requests information about a virtual machine from the RD Virtualization Host.
5. RD Connection Broker receives information about a virtual machine and then provides that information to the virtual machine redirector.
6. The virtual machine redirector communicates through the RD Gateway, providing the client with the IP address and connection information for a virtual desktop.
7. The client connects to a virtual desktop.
8. The virtual desktop is displayed on the client.
The following illustration shows the same sequence of events occurring despite the failure of one node of the cluster. Because a second cluster node is still running, it can respond to client requests as they occur.
Figure 3 Servers providing a virtual desktop after a failure
Cluster Screen Shots
RDP Connection Options
· Remote Desktop Services (http://go.microsoft.com/fwlink/?LinkId=154440)
· What’s New in Remote Desktop Services (http://go.microsoft.com/fwlink/?LinkId=185916)
· Install the RD Session Host Role Service (http://go.microsoft.com/fwlink/?LinkId=185917)
· About Dedicated Farm Redirection and Virtual Machine Redirection (http://go.microsoft.com/fwlink/?LinkId=185918)
· Remote Desktop Connection Broker (http://go.microsoft.com/fwlink/?LinkId=185919)
· Verify Connection broker cluster configuration (http://go.microsoft.com/fwlink/?LinkId=188508)
· Remote Desktop Services Script Repository (http://go.microsoft.com/fwlink/?LinkId=190312)
Lately there are all kind of virtual waves that customers want everything have to be virtual unless..
Well Microsoft does have several guides to do this I pointed out 3 guides that are a good basic to start.
This step-by-step guide walks you through the process of setting up a working personal virtual desktop accessible by using Remote Desktop Web Access (RD Web Access) in a test environment.
Personal virtual desktops are virtual machines that are assigned to a user within your organization and available by using either RemoteApp and Desktop Connection or Remote Desktop Web Access (RD Web Access). In this guide, we will set up a personal virtual desktop and connect to it by using RD Web Access.
This step-by-step guide walks you through the process of setting up a working Remote Desktop Services infrastructure in a test environment. During this process, you create an Active Directory® domain, install the Remote Desktop Session Host (RD Session Host) role service, and configure the Remote Desktop Connection client computer.
This guide is considered the basic Remote Desktop Services step-by-step guide. All other step-by-step guides developed for Remote Desktop Services will assume that this guide has been completed first. This step-by-step guide walks you through the process of setting up a working Remote Desktop Services infrastructure in a test environment. During this process, you create an Active Directory® domain, install the Remote Desktop Session Host (RD Session Host) role service, and configure the Remote Desktop Connection client computer. After you’ve completed this process, you can use the test lab environment to learn about Remote Desktop Services technology on Windows Server® 2008 R2 and assess how it might be deployed in your organization. The goal of a Remote Desktop Session Host (RD Session Host) server is to host Windows-based programs or the full Windows desktop for Remote Desktop Services clients. Users can connect to an RD Session Host server to run programs, to save files, and to use resources on that server.
Deploying Remote Desktop IP Virtualization Step-by-Step Guide
Remote Desktop IP Virtualization provides administrators the ability to assign a unique IP address to a program that is available by using RemoteApp and Desktop Connection.
Remote Desktop IP Virtualization provides administrators the ability to assign a unique IP address to a program that is available by using RemoteApp and Desktop Connection. In this guide, we will configure Remote Desktop IP Virtualization and access it as a standard user by using RemoteApp and Desktop Connection.
The Microsoft® Application Virtualization Dashboard helps you monitor virtualized software applications across your organization. The dashboard’s built-in charts, gauges, and tables let you track any APP-V dataset in near-real time, so you can easily stay on top of the usage, health, and compliance of all your virtualized applications.
The App-V Dashboard is designed and built on Windows SharePoint Services 3.0 as the application platform by using Microsoft Application Virtualization 4.5/4.6.
Benefits of the dashboard include:
- Actionable information out of the box. The dashboard comes with a wide range of valuable, built-in reports like top 5 applications used, top 5 users, applications never used, application usage for a specific user, system utilization, and many more.
- Near-real-time access to key information. The graphical dashboard lets customers view any App-V dataset in near-real time.
- Easy to build and configure. The dashboard’s wizard-based tools let customers easily create new dashboards in minutes.
- Easy to customize. The dashboard can easily be customized to meet the needs of different departments and other groups. Any data set in the Microsoft Application Virtualization database can be presented on the dashboard, in chart, gauge, and table formats.
- Flexible & interactive. Users can easily filter data and create ad hoc, custom views. Filters allow users to quickly drill down from high-level to more specific data.
Join the Beta Program for the Dashboard
The App-V dashboard is now in beta release. Want to get an advance look at the dashboard, and a chance to provide feedback so it best meets your needs? Join the beta program!
To join the beta program, click here. You can also send your enquires about this Solution Accelerator to firstname.lastname@example.org.
How the Dashboard Works
The Application Virtualization Dashboard is designed to work with an existing Application Virtualization 4.5 or 4.6 infrastructure. The Dashboard queries the Application Virtualization database and uses the resulting data set to present key infrastructure metrics in a graphical format.
The Application Virtualization Dashboard uses SharePoint Web parts to manage and display data sets:
- Microsoft Dashboard Configuration Web Part. Use this Web part to create and modify the SQL queries that produce the data sets and the other properties that govern how the Dashboard displays the data sets.
- Microsoft Dashboard Viewer Web Part. Use this Web part to display the data sets. A Dashboard Viewer Web Part displays one data set at a time. The Application Virtualization Dashboard can contain multiple copies of the Dashboard Viewer Web Part at once, each copy displaying a different data set.
The following figure shows how users can interact with the Web parts to retrieve and display data.
Figure 1. Application Virtualization Dashboard Process Flow
The Application Virtualization Dashboard process flow involves the following sequence of activities:
- An IT Service Manager requests a new data set.
- The IT Administrator uses the Dashboard Configuration Web Part to define the new data set.
- The IT Administrator stores the configuration information for the new data set (the information is saved in the Windows SharePoint Services Content database).
- The IT Administrator adds a new copy of the Dashboard Viewer Web Part to the default Application Virtualization Dashboard and then modifies the Web part to display the new data set.
- The IT Service Manager browses to the Application Virtualization Dashboard site.
- Windows SharePoint Services queries the Application Virtualization database as specified by the data set configuration.
- Windows SharePoint Services renders the new data set using the Dashboard Viewer Web Part.
Requirements for the Application Virtualization Dashboard
The App-V Dashboard integrates with an already functioning deployment of System Center Application Virtualization and has no additional infrastructure requirements. It is assumed that App-V and it’s database are configured in accordance with Microsoft installation guidance.
The following table lists software requirements for the Application Virtualization Dashboard.
App-V Dashboard Software Requirements
Microsoft Internet Explorer® 7.0 or Internet Explorer 8.0.