Red Hat ENTERPRISE VIRTUALIZATION FOR DESKTOPS Guia de Instalação Página 5

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 30
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 4
Quick Start
5
End user experience, to provide the optimal working environment for your end users
And much more!
To set up your Leostream Connection Broker, you define the following concepts:
Authentication Servers: A server that provides authentication services to users logging into the
Connection Broker. The Connection Broker supports Microsoft Active Directory®, Novell®
eDirectory™, or OpenLDAP™ directory services. You can specify any number of (trusted or not-
trusted) domains, using any combination of authentication server types. In addition, the Connection
Broker allows you to manually define users without configuring an authentication server.
Centers: The external systems from which the Connection Broker pulls resources, including desktops,
applications, and printers. Centers can be created from the following systems: Red Hat Enterprise
Virtualization Manager; HP® Moonshot Systems; VMware vSphere, ESXi, and vCenter Server; Citrix
XenServer®, XenApp, and XenDesktop; open source Xen; OpenStack® clouds, including HP Helion
OpenStack; and Microsoft Hyper-V via System Center Virtual Machine Manager (SCVMM), Remote
Desktop Services (RDS), and Active Directory.
Resources: Desktops, applications, and printers available for assignment to an end user.
Desktops: Virtual machines, physical machines, blades, and Microsoft Terminal Services to assign to
end users. The Connection Broker supports desktops that run Windows and Linux® operating
systems.
Applications: Applications and desktops hosted in a Citrix XenApp farm.
Pools: Collections of desktops or applications, gathered from a single or multiple centers.
Clients: An application or device used to log into the Connection Broker. The Connection Broker
supports Linux and Windows fat clients, a variety of thin clients, and Web browsers and mobile
devices.
Locations: A group of clients defined by client attributes such as manufacturer, device type, OS
version, or IP address. The end users experience can be modified based on the location of their
client, including assigning printers and modifying registry keys on the remote desktop.
Plans: Common sets of rules used as building blocks for defining the end-user experience. There are
two types of plans: pool-based plans such as protocol, power control, and release plans are applied
to pools in a policy and define how the Connection Broker manages the desktops in that pool;
location-based plans such as display, printer, and registry plans are applied to desktops based on the
users client device.
Policies: Rules that assign desktops and applications to users and define how the users entire
session is managed, including options that define assignment, login, disconnect, and logout actions.
Policies assign plans to desktops based on the desktop’s pool membership, and manage USB
passthrough permissions.
Vista de página 4
1 2 3 4 5 6 7 8 9 10 ... 29 30

Comentários a estes Manuais

Sem comentários