7
1. User signs into the Connection Broker: End users can log into the Connection Broker from a Web
browser, thin client, mobile device, or Leostream Connect. Different clients support different
authentication methods, such as user name/password, smart cards, or fingerprints, and different
display protocols. Users that connect to their desktops using the SPICE protocol must install the
Leostream Connect software client on a Windows client device.
2. Connection Broker authenticates user: Once the Connection Broker has the user’s credentials, it
searches for the user in the domains defined in the > Users > Authentication Servers page. If the
user previously logged in, the Connection Broker begins by looking in the authentication server
used for the previous login before searching the remaining authentication servers in the order
defined by the authentication server’s Position property. If this is the first time the user logged in,
the Connection Broker searches all authentication servers in order of their position.
3. Connection Broker offers resources based on user’s policy: The Connection Broker then assigns a
policy using the assignment table associated with the authentication server chosen in step 2. The
policy determines the desktops and applications offered to the user, the USB passthrough
permissions, and the display protocol used to connect the user to their resources. At this point, in
addition to assigning a policy, the Connection Broker assigns a role to the user.
4. User requests connection to desired desktop: The user selects one or more of their offered
desktops.
5. Connection Broker assigns desktop: After the user selects one or more resources, the Connection
Broker assigns those resources to the user. Once a resource is assigned to a user, the Connection
Broker will not offer that resource to another user.
After the assignment is made, the Connection Broker initiates the remote session. This process
varies based on display protocol used. In most cases, the Connection Broker sends the connection’s
definition to the user’s client and the viewing application on the client launches the remote
connection to the desktop.
If the user is using an Active-X RDP client or another external viewer, the Web browser on the client
retrieves the viewing component stored in the Connection Broker. The viewer then runs in the
user’s browser.
In any case, the remote viewer in the client’s environment connects directly to the desktop. The
connection does not flow through the Connection Broker.
6. User ends remote viewer session: If the Leostream Agent is installed on the remote desktop, you
can manage the user’s session differently based on if the user disconnects or logs out of their
remote session.
7. Connection Broker unassigns desktop: If the user’s policy releases the desktop back to its pool, the
Connection Broker unassigns the desktop. Otherwise, the Connection Broker retains the desktop
assignment.
8. Connect Broker applies power policy: Lastly, the Connection Broker takes any power control plan
actions set in the user’s policy.
(25 páginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais