Swizznet citrix receiver.Bevor Sie zu Google weitergehen
Looking for:
Swizznet citrix receiver |
Bevor Sie zu Google Maps weitergehen.Citrix Receiver for Windows 4.x - Issues Fixed in This Release
This article is intended for Citrix administrators and technical teams only. It communicates with the aggregation tier StoreFront or Web Interface services to obtain details about what resources are available for the user, and it can facilitate launching those resources.
By default, SSP activities are driven by user interaction. However, SSP exposes sufficient information for its activities to be scripted.
The advantage of this approach is that it allows SSP to do most of the difficult operations and in particular handle authentication. This provides support for all the authentication methods without having to interact programmatically with the aggregation tier.
SSP also coordinates the session launch process. This article outlines the scripting process and provides a list of parameters for reference. Assuming the system is set up to communicate with the same provider or store for all users, the SSP model is to:. Create shortcuts for the resources the user has subscribed to or that the administrator has auto-subscribed them to. The store may be set as mandatory , in which case all resources are subscribed.
If Receiver is communicating with a Web Interface Services site then all resources are automatically subscribed. By default, there is a delay of about two minutes before the store is contacted. You can override this by setting the following registry keys and adjusting for WowNode as appropriate:.
For any subscribed application, SSP builds a Start menu shortcut that launches an HDX session for that application when the user selects it. These shortcuts persist after the user logs off from the aggregation tier.
If the user selects the shortcut without being logged on, they are prompted for credentials before the application launches. There is an exception to this: if the published application is tagged with a prefer keyword that has a value matching an existing local shortcut, no hosted shortcut is created.
This is to save the overhead of a hosted launch where a local one might suffice. SSP mimics a local install by building an.
Running these. This may be the simplest launch option for scripting: look for the relevant. If you want to drive SSP directly for launch instead of through an. There will be keys in there named farm-name server-farm-name. In these keys you'll find a LaunchString value that shows the relevant parameters. These parameters are user-independent and can therefore be cloned from a reference user to a general case.
These launchstrings will be of the form. You can copy and reuse these parameters without interpretation. This may be off-putting if the aim is to try and build a control for these independently. It is not necessary though to understand resources at this abstract level if more control is required.
Additional command-line arguments can follow the above format or be passed to the. For both the stub and the direct launch methods, SSP will take care of authentication and interaction with the Web Interface or StoreFront.
Alternatively to -launch, -qlaunch , which has a simpler syntax, can be used. Please see below for details. A cache file is created per provider when SSP exits. This file records the last enumeration details and allows SSP to start up quickly. The name of the cache file is decorated with the internal store name. Running the command selfservice. The cache file contains information about each resource, including all the information needed for a launch.
The launch command line contains:. The cache file will contain some LaunchCommandLine entries, but only for subscribed or prelaunch resources. There is also a dump. This file is intended for external consumption unlike the cache file. It contains some but not all LaunchCommandLines. Reconnect to any existing sessions the user has. By default happens at launch time and app refresh time. Create a provider. For example: SelfService. Launch applications. Failed to load featured products content, Please try again.
Customers who viewed this article also viewed. Log in to Verify Download Permissions. Information This article is intended for Citrix administrators and technical teams only. Method Assuming the system is set up to communicate with the same provider or store for all users, the SSP model is to: Start up.
Authenticate to the store. Enumerate the resources the user is entitled to access. Store interaction By default, there is a delay of about two minutes before the store is contacted. Setting is in milliseconds. Cache file for resource details A cache file is created per provider when SSP exits. The launch command line contains: SelfService. Reconnect any existing apps for current user. Log off the current user and leaves their applications connected.
Disconnect applications for all users on endpoint. Disconnect applications for a specific user. Note 1 : These parameters are available only in Receiver 4. Was this page helpful? Thank you! Sorry to hear that. Name Name is required. Email Email address is required.
Close Submit. Featured Products. Need more help? Product issues. Open or view cases Chat live. Other support options. Share this page. Set to 1. Contact the server to refresh application details as in —poll, but if no authentication context is available, prompt the user for credentials.
Log off all the active sessions for the current user Note : This flag is available only in Receiver for Windows 4.
Comments
Post a Comment