Shulou(Shulou.com)06/02 Report--

StoreFront 3.7 introduces support for Windows Server 2016 and some cool features. Let's take a look at what functions there are!

Windows Server 2016 Support

With the release of Windows Server 2016, Citrix SotreFront also announced support for the latest Windows Server 2016, which provides zero-day support in Citrix's solutions. This is one of the things Citrix works with Microsoft on.

Windows Server 2016 Day 1 Support!

Citrix StoreFront supports two versions: datacenter and standard.

II. Regional preference function

In geographically distributed large-scale deployments, the location of the user will be a useful parameter or an important parameter in selecting the VDA to launch the application. The zone preference function allows a VDA in a specified preferred zone to be used to satisfy an initiation request for a shared resource. That is, in sites with multiple zones, the zone preferences feature gives administrators more flexibility to control which VDAs are available to launch an application or desktop.

When using Global Server Load Balancing (GSLB), NetScaler can provide StoreFront with the location of user devices. StoreFront already has the ability to use this information to prioritize XenDesktop sites for launching load balancing applications.

The zone for the client's current location can then be passed to the agent if provided in StoreFront's launch request.

In regional preferences, there are three important elements:

Region: The location of the user's home region data, such as a profile or home region share. This is called the user's home area.

Application: The location where the application data is stored. This is called the main area of the application.

User: The current location of the user (where Citrix Receiver is running). This is called user location.

In this example, the VDA is distributed across three satellite regions, but all in the same Delivery Group. Thus, the proxy can choose which VDA to use for user initiation requests. This example indicates a number of places where users can run their Citrix Receiver endpoints:

User A is using a device with Citrix Receiver in satellite zone 1;

User B is using a device in satellite zone 2.

A user's documents can be stored in several locations:

Users A and B use part of satellite region 1;

User C uses a portion of satellite region C.

In addition, one of the published applications uses a database located in satellite region 1. You can associate a user or application with a zone by configuring it as a primary zone:

Configure a home zone for users by adding users to a zone.

Configure the home zone for an application by editing the application properties.

A user or an application can have only one home zone at a time. (Exceptions for users may occur when multiple zone memberships occur due to user group membership.) However, even in this case, the agent can only use one master zone.)

Although regional preferences for users and applications can be configured, the agent can select only one preferred region at a time. The default priority for selecting preferred regions is App Home> User Home> User Location. (You can limit the order, as described in the following section) When a user launches an application:

If the application has a configured zone association (an application home zone), the preferred zone is the application home zone.

If the application does not have a configured zone association, but the user has a configured zone association (user home zone), the preferred zone is the user's home zone.

If neither the application nor the user has a configured zone association, the preferred zone is where the user is running an instance of Citrix Receiver (user location). If the zone is undefined, random VDA and zone selection are used. Load balancing applies to all VDAs in the first zone. If there is no preferred zone, load balancing applies to all VDAs in the Delivery Group.

Administrators can customize the settings for regional preferences as needed:

When configuring (or deleting) a user's or application's home zone, you can also further restrict how zone preferences are used (or not used).

Enforce user primary zone use: Within a Delivery Group, you can specify that a session should start in the user's primary zone (if the user has a primary zone) and that there will be no failover to another zone if resources are unavailable in the primary zone. This restriction is useful when users need to avoid the risk of copying large configuration files or data files across multiple regions. In other words, users would rather reject a session launch than launch it in a different zone.

Enforce application home zone use: Similarly, when configuring an application's home zone, you can indicate that the application should only be launched in that zone and that it will not fail over to another zone if resources are unavailable in the application's home zone.

No application home zone and ignore configured user home zones: If you do not specify a home zone for an application, you can also indicate that no configured user zones should be considered when launching the application. For example, an administrator might want users to run a particular application on a VDA close to the computer they use (where Citrix Receiver is running), using user location zone preferences, even though some users might have different home zones.

Once these associations are set, the agent can select them to help select a better and more appropriate region to start the session.

Zone preferences based on the client's current location need to be provided by StoreFront as part of the launch request to the broker. StoreFront receives this information as determined by NetScaler zone preference policies bound to vServer. An HTTP header called "X-Citrix-ZonePreference" can contain a list of up to three zone names that are inserted into all requests sent to StoreFront.

Changes in XenApp/XenDesktop 7.11 to accept zone information from StoreFront. This information is contained by a so-called RequestAddress element, which contains an optional ordered list of regions near the user client location, determined by NetScaler. The data NetScaler provides for each zone is determined by a string that matches the zone name defined in XenDesktop. For a successful launch, the ResponseAddress element contains the zone ID and name of the zone in which the selected resource is located. It is the proxy component that will determine the zone information for the application to launch. StoreFront's responsibility is to pass this value from NetScaler vServer to the broker. No configuration is required in StoreFront to perform this function.

Finally, if you want to use the enforcement zone preferences, there are some limitations:

There is only one preferred region for startup, and if no resources are available for that region, note that the sub-region preferences are not considered.

StoreFront performs only basic validation before passing zone information to agents. It does not attempt to filter out areas unknown to the agent.

Third, support small device login UI

When users access StoreFront Receiver on a small device, for example as a smartphone. The login page cannot be fully accessed and used. In previous versions, users saw only one corner of the entire screen. The end user needs to scroll a lot to see all the interfaces.

Example from previous version:

Examples in STOREFRONT 3.7

For version 3.7 of StoreFront, the login UI can be resized between 3 sizes

desktop

mobile phone

mixed

The UI size is determined by the smaller of the two size of the screen. This is to avoid UI switching from one size to another when the device and screen rotate.

Of course, there are some limitations. Users can only use this option with the X1 UI, not with the classic UI.

Finally, if you want to see how your StoreFront page looks, you don't have to grab a mobile device to test it. Simply append "? -" to the StoreFront URL ph"。For example: Desktop.Citrix.com/Citrix/StoreWeb/?- ph

IV. Support self-service password reset

Self-service password reset gives end users greater control over their user accounts. After configuring a self-service password reset, end users experiencing account issues can unlock their account or reset their password to a new password by answering several security questions correctly.

In previous versions of StoreFront, only password resets using Single-Sign On were supported. With the new Self-Service Password Reset 1.0, you can use the StoreFront Management Console to allow users to register answers to security questions they configure in the Self-Service Password Reset Configuration Console.

After configuration, the next time a user logs in to Citrix Receiver or Citrix Receiver for Web. Security password reset function can be used.

After configuring this option in StoreFront, users will see the Account Self-Service option during login.

If you click on this link, you have two options:

After that, the user needs to answer some security questions if all the answers match. an unlocking or resetting operation is performed.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.