Welcome to YLOAN.COM
yloan.com » College-University » 1Y0-A05 XenApp Study Guide Part 4
College-University Vocational-Trade-Schools Root Category Home-Schooling scholarships books certification students

1Y0-A05 XenApp Study Guide Part 4

1Y0-A05 XenApp Study Guide Part 4

1Y0-A05 XenApp Study Guide Part 4

Managing Applications

Remote and Streaming Application Delivery Methods

Using a web browser, a XenApp Web site allows users to access:

* Remote and streamed applications

* Content

Streamed applications can be pre-deployed in one of two ways:

* UsingRADEDEPLOY.EXE.

* Configured in the published application.

When configuring an application delivery method policy the administrator can configure the policy to:

* Force server access

Forces streamed applications toalways launch from the server.

* Force streamed delivery

Forces the applications toalways stream to the desktops of the client devices.

Publish an Application

Whenpublished, users can access applications installed on the XenApp servers.

* The applicationsappear to run locally on the client devices.

* Published applicationsprovide the administrators control over what resources users can access on a server.

Unlike published server desktops.

Published server desktops allow usersunlimited access to the resources on a serverwhich can result inusers changing configurations and settings that can causeserver vulnerabilities.

If you install and publish an applicationafter installing XenApp, you mustupdate the file type association in the server's Windows registry.

* To update file type associations:

* In theAccess Management Console, select the server where the application is published.

* SelectAction >All Tasks >Update file types from registry.

Bydefault, all resources are published to theroot folder of the application set.

* An administrator canorganize published resources in an application set by placing the published resources infolders during the resource publishing process or afterwards.

For example, if many Microsoft Office applications are published, an administrator might decide to place the Microsoft Office applications into a folder calledMicrosoft Officemaking iteasier for users to locate these applications.

Users can open published content using two types of content redirection:

* Client-to-server

Allows users touse a published application on the XenApp server to access files residing on thelocal client device.

Requires XenApp Plugin on the client devices.

Client drive mapping must be enabled so that the local content can be accessed by the application on the server. If drive mapping is not enabled, thepublished application opens and displays an error

Application is unable to access the local content that initially triggered the application to start.

* Server-to-client

Server-to-client is a policy rule that can be configured for specific connections toopen web browsers on the user's computer instead of the XenApp server.

Users might frequently access web and multimedia URLs they encounter when running an email program published on a server.

* If you do not enable server-to-client content redirection, users open these URLs with web browsers or multimedia playerson the XenApp servers.

* Tofree servers from processing these types of requests, you canredirect application launching for supported URLs from the server to the local client device.

The following URL types are redirected:

HTTP

HTTPS

RTSP (Real Player and QuickTime)

RTSPU (Real Player and QuickTime)

PNM (Legacy Real Player)

MMS (Microsoft's Media Format)

Published resources can be configured to control the following options for the client device:

* CPU Priority

Changes the CPU priority of the published resource.

* Client audio

Allows support for applications to which SpeedScreen Multimedia Acceleration does not apply.

* SSL and TLS protocols

Requests the use of the SSL and TLS protocols for plugins connecting to the published resource.

* Encryption

Controls which plugins are allowed to connect based on their encryption level.

* Client printers

Allows the published resource to open without waiting for the client printers to be created.

Session Sharing

Session Sharing:

* When a user starts a published application, an ICA connection is made to a XenApp server.

* If the user starts a published application on a different server, another ICA connection is made.

* If a user starts a published application on a server that the user already has an ICA connection to, the same ICA connection will be used

If the user is already at the ICA connection limit, a new ICA connection will not be started.

Configure ICA connections limits in a singlepublished application:

* When publishing the application.

* In the properties of the published application.

Configurefarm-wide ICA connection limits:

* By configuring the farm properties in the Access Management Console.

For applications to launch and use session sharing, certain criteria must be met:

* All applications need to be installed on the same server.

* All applications need to be published seamlessly

As opposed to a fixed sized or full screen window size.

* Connection limits at the farm level and application level should be set to 1.

* Session sharing requires thatcolor depths, screen resolutions, audio quality and encryption levels (if used) are equal on all published applications that will share the session.

Profiling an Application

Before publishing a streamed application, an administrator must use theStreaming Profiler toprofile the application.

* Publishing a streamed application makes profiled applications available to users.

* An administrator publishes a streamed application using the Access Management Console.

* The application profile is stored on a file share.

To maximize streamed application compatibility:

* It is a best practice to install a profiler on each operating system in use within the environment.

If one operating system is used to create all of the profiles there is a good possibility that a profile created on one operating system will not work properly on a different operating system.

* When installing the Citrix streaming profiler on a profiling computer, the computershould have standard software, such as anti-virus programs, Service Packs and updates that are part of the company image installed.

When creating a streaming profile, an administrator can configure how restrictive theclient isolation environment should be.

* Enhanced security, which is the recommended best practice, prevents the running of the executable content that the user downloads into the isolation space.

This setting protects against users running malicious code or spyware.

* Relaxed security permits the running of executable content that the user downloads into the isolation space.

Publish a Streaming Application to a Client

To publish a streaming application to be streamed to the client:

* In theAccess Management Console, right-click theApplications node and selectNew >Publish Application.

* ClickNext on theWelcome screen.

* Type the application name and clickNext.

* SelectApplication, configureStreamed to client and clickNext.

* Specify the location of the profile being published.

* Select the application from theApplication to launch from the Citrix streaming application profile drop-down list and clickNext.

* Select the users that will be allowed to access the published application.

* Configure the appearance and location of the application shortcuts and clickNext and clickFinish.

Publish a Streaming Application to a Server

To publish a streaming application to stream to the server and be accessed by the client devices using ICA:

* In theAccess Management Console, right-click theApplications node and selectNew >Publish Application.

* ClickNext on theWelcome screen.

* Type the application name and clickNext.

* SelectApplication, configureAccessed from server and clickNext.

* ChooseRemote to grant users access to the published application installed on the server via ICA or RDP and clickNext.

* Specify the location of the profile being published.

* Select the application from theApplication to launch from the Citrix streaming application profile drop-down list and clickNext.

* Select the servers on which the application will run to be accessed through an ICA connection and clickNext.

* Select the users that will be allowed to access the published application.

* Configure the appearance and location of the application shortcuts and clickNext.

* ClickFinish.

Configure Encryption for a Published Application

ICAencryption:

* Guards against the threat of eavesdropping.

* Secures the information sent between client devices and XenApp servers

* Is configured in:

XenApp policies

Published applications

* Is available in several encryption strengths:

Basic

RC5 (128-bit) logon only

RC5 (40-bit)

RC5 (56-bit)

RC5 (128-bit)

SSL Relay:

* Secures end-to-end ICA communication between:

Client devices and XenApp servers.

* Secures XML communications between:

Web Interface servers and XenApp servers.

* Is a great security solution for a very small implementation of five or less XenApp servers.

* Is a good choice when:

Secure communication for the Citrix XML Service is required.

A DMZ is not required.

IP addresses do not need to be hidden.

Or NAT is configured.

End-to-end encryption of data between the clients and servers is required.

To configure SSL Relay:

* Obtain and install a unique server certificate on each XenApp server.

* Install a root certificate on each client device and Web Interface server.

* Using theSSL Relay Configuration tool, configure:

Relay credentials

Connections

Ciphersuites

* Restart the XenApp servers.

Ciphersuites:

* Are an encryption/decryption algorithm.

* Are used when SSL Relay is being used.

* ProvideCOM andGO* by default in XenApp.

Managing XenApp Policies

Impact to Users with Multiple Policies

XenApp policies:

* Are applied when an ICA session begins.

If a policy is changed while users are connected to a session, the change does not take effect until a new session is initiated.

The rules remain in affect for the duration of the session.

* Receive a number upon creation.

By default, anew policy has thelowest priority of all policies.

The number assigned is based on the number of policies that exist in a server farm.

Toprioritize a policy:

* In theXenApp Advanced Configuration tool, click thePolicy node.

* Right-click the policy in the right pane and clickPriority.

If you want to assign the policy the highest priority, clickMake Highest Priority.

If you want to assign the policy the lowest priority, clickMake Lowest Priority.

If you want to increase the priority of the policy one level, clickIncrease Priority.

If you want to decrease the priority one level, clickDecrease Priority.

Apply Policies to Whom or What

After a policy has been created and configured, and administrator canfilter the policyusing:

* Client names

* Access control (connections made through Access Gateway)

* Users and user groups

* Servers

* Client IP addresses

To filter a policy toaffect only a certain range of IP addresses:

* Click thePolicy node in theXenApp Advanced Configuration tool.

* Right-click the appropriate policy in the right pane and selectApply this policy to.

* ClickClient IP Address.

* ClickFilter based on client IP address.

* ClickAdd.

* ClickIP Range and clickOK.

* ClickAllow and clickOK.

Issue: Remote users are complaining that an audio-enabled application that they use is performing badly. There are no complaints from the local users.

Probable cause: Not enough bandwidth available over remote connection.

Solution:1) Cut down on the bandwidth used for audio in an audio-enabled application by creating a XenApp policy and enable theSound Quality rule in theClient Devices >Resources >Audio folder. 2) Limit the audio bandwidth per session to desired level. 3)Apply the policy to the users that are experiencing the application degradation.

To apply a XenApp policyto a user or group:

* In theXenApp Advanced Configuration tool, click thePolicy node.

* Right-click the appropriate policy and clickApply this policy to.

* ClickUsers.

* ClickFilter based on users.

* Configure the users and groups filter option in one of four ways:

Apply the policy to all explicit users (non-anonymous).

Apply the policy to all anonymous users.

Apply the policy to a specific user account or user group.

Avoid applying the policy to a specific user account or user group.

* ClickOK.

Shadowing Policy

To create a newshadowing policy that willgive notification to the users being shadowed andwill not allow the users shadowing to control the desktop:

* Create anew policy in theXenApp Advanced Configuration tool.

* In the policy's properties open theShadowing folder under theUser Workspacefolder in the left pane.

* Select theConfiguration rule and enable it.

* SelectAllow shadowing.

* SelectProhibit being shadowed without notification.

* SelectProhibit remote input when being shadowed.

* Select the rule namedPermissions in the left pane and enable it.

* ClickConfigure to select the users or group who will do the shadowing and clickOKwhen done adding the users.

* ClickOK at the bottom of the policy's properties.

* Apply the policy to the users or group who will be shadowed.

After creating a policy to allow Group01 to shadow Group02, the policy needs to befiltered by users to specify that the policyshould be applied to Group02. Take the following steps:

* Select the policy and chooseActions >Policy >Apply this policy to.

* SelectUsers in the left pane.

* SelectFilter based on users.

* Select Group02 from the correct domain, clickAdd and clickOK.

Resultant Policy

Thepolicy search engine:

* Is a feature of the XenApp Advanced Configuration tool.

* Allows an administrator to find all policies that can potentially apply to a specific connection and confirm how final policy rules are merged for that connection.

Verifies that a policy will be applied correctly.

To use the policy search engine:

* Right-click on thePolicies node in theXenApp Advanced Configuration tool and clickSearch.

* Configure the search criteria

IP Address

Client Name

User

Server

Access Control

* ClickSearch.

* ClickYes to search the entire Active Directory if desired.

* Optionally, double-click a policy in the search results to view the policy priorities.


* ClickView Resultant Policy and theResultant Policy Properties screen launches.

* Expand each node to view individual resultant policy rules.

* ClickOK to close theResultant Policy Properties screen.

* ClickOK to close theSearch screen.
1Y0-A05 XenApp Study Guide Part 5 1Y0-A05 XenApp Study Guide Part 6 1Y0-A05 XenApp Study Guide Part 7 The Art Of Success - Learn From Ants Royalties University Review - How You Can Earn Ongoing Royalties Indian Pgdm Colleges Are Preferred Due To an Assortment of Raison D'ĂȘtres English Learning Problems Surviving College Hunt Suitable Guide In Finding You Appropriate Colleges What punters can learn from The Beatles, Hendrix, Gates and Obama IBM LOT-753 Braindumps LOT-738 Exam Resources Testinside LOT-836 braindumps
print
www.yloan.com guest:  register | login | search IP(216.73.216.35) California / Anaheim Processed in 0.023562 second(s), 7 queries , Gzip enabled , discuz 5.5 through PHP 8.3.9 , debug code: 455 , 16356, 249,
1Y0-A05 XenApp Study Guide Part 4 Anaheim