I am thrilled to introduce you to the storefront 3.1 Tech Preview, , the here available for download (Citrix Login required) .
The main features of this Tech Preview included a new administrative console and a new management PowerShell SDK. These are storefront management much easier.
In the past, we would get a lot of feedback that the existing Storefront management console is not sufficient for many scenarios, so it is essential for administrators must resolve to run PowerShell commands or edit web.config. Also, it might not be configured with different authentication settings for various businesses such is a major obstacle for many organizations.
We have in the last year working hard all address these concerns. The new administration console and manage PowerShell SDK are the result of the hard work of the team. We believe that with the new administration console, most administrators do not PowerShell commands or editing configuration files must be run.
Please raise any questions and / or provide us with your feedback by using our discussion forum.
Store Centric Conceptual Model
When you open the new administration console, you will find that all configuration settings now organized around businesses. found
settings in the Authentication node and Receiver for Web node in earlier versions of Storefront are even available now as manage authentication methods action and manage receiver for Web sites action within the memory node in the lower right pane. These tasks are now save specific. That is, configured in this task settings are related to the selected memory.
is the settings in NetScaler gateways node and in Beacons node in earlier versions of storefront you manage now are configurable via the NetScaler gateways action and beacons manage action in the upper right pane that are against valid cross shops.
Why do we have these changes?
First Storefront 3.1 different authentication settings for various businesses supported that performs multiple authentication services to a storefront deployment. There is a 1-to-many mapping between the authentication service and stores. There is also a 1-to-many mapping between the memory and Receiver for Web sites.
Without the UI architecture change, several authentication services in the UI implementation would make it more difficult to understand the associations between different services. In addition, our usability studies have suggested that the organization of the user interface to business fit better with the administrator conceptual model as administrators often think about different stores for different purposes or for different organizations and treat up authentication, Web access as properties of a memory.
memory Dedicated authentication settings
As mentioned above, the Administration Console before this release only supports a single authentication service for a Storefront deployment. This means that all the shops in the provision have to share the same authentication settings.
In the new administration console you are given a choice to use a shared or dedicated authentication service when you create a business. By default, a new authentication service for a new cache is created. If you will be the memory you want to create authentication settings to share with another business, you can check the box Use a Shared Authentication Service , and then select the disk (s) you want to configure authentication with from the drop-sharing menu , This setting is not available when you create the first shop.
is created after a storage, you can specify whether the authentication settings to share with other stores or not. Select the memory you want to change, and select the Managing Authentication Methods action. Then select the Extended menu in the pop-up dialog, followed by the selection of Common Authentication Service Settings from the drop-down menu. Another dialog popped for you to make the change.
delegating authentication to XenApp / XenDesktop Farms / sites
delegating authentication XenApp / XenDesktop farms / sites was in storefront 3.0 introduced. However, it was only configurable via Power. Now you can configure this feature using the administrative console. To do this, select the store you want to change, and select the Managing Authentication Methods action. In the pop-up dialog box, select the is associated with a user name and password settings drop-down menu, and then select password verification configure .
Select Delivery Controller drop-down menu and a dialog will indicate for you pop up on XenApp / XenDesktop broker used, to authenticate users.
policy for password expiration warning
You can now configure policies for password expiration warning that the administration console. Select the memory you want to change, and select the Managing Authentication Methods action. In the pop-up dialog box, select the Settings drop-down menu associated with username and password and then select manage password options .
A dialog is popped for whether to configure to allow users to change their password. If you allow users to change their password at any time, you can also configure the policy for password expiration warning.
highly available multi-site Configuration Store
[1945001mehrereXenApp/XenDesktopzuaggregierenFarmen/StellenfürLoad-BalancingFailoverundDisaster-Recovery-Benutzerzuordnung] highly available multi-site storage configuration is set up a very powerful feature storefront. This used to be about editing the web.config only configurable. We have now introduced UI support to configure most of the common applications. Users farm mapping and single aggregation groupTo multi-site aggregation in the administration console, select the store you want to configure, and select the device Delivery Management Controller action. If you configure more than one farms / sites, the button in the user mapping and multi-site aggregation configuration section is enabled Configure, as shown below.
select Configure button, a new dialog popped for you to choose if you want to set the user mapping or resource aggregations.
If you select card users controller They are provided with dialogues available to specify user groups and Delivery Controller. When the user from the same domain hosting server the storefront, you can select user groups from the Active Directory. Otherwise, you must specify SIDs manually.
If you Aggregate Resources , you will be provided with a dialog available to decide, so what / sites holdings you want to aggregate group resource with the same name and path a symbol of the user.
Optimal Gateway Routing
Optimal Gateway Routing allows you to route HDX connections to different XenApp / XenDesktop farms / sites on different NetScaler gateway. UI support this feature for the configuration is added to the new Administration Console. To configure an optimal routing gateway, select the store you want to configure, and then select the Configure Store Settings Action in the right pane. In the pop-up dialog, select Optimal Routing HDX as shown below.
to the Gateway Select want to use and click Delivery Controller manage . Another dialog is for you Pop-up to select the farms / sites you would like traffic on the selected gateway to route HDX.
Store Advanced Settings
Advanced settings related to a business together and available grouped in the Advanced Settings of Configure Store Settings screen.
You can configure have found that there is a Advanced Settings shown section on the Edit Delivery Controller dialog below.
The Settings button a new dialogue brings for you Farm / configure site-specific advanced settings.
for Web Site Standard Receiver
Storefront 3.1 supports a receiver for setting website as Default Web Site for Your Storefront deployment, so users must enter only the base URL, eg https://sf.acme.com to the browser to access the specified recipient for website. This can be done in the store creation time on the following screen.
You can also set or save the default Web site to change creation. Simply select the Default site set IIS Action in the upper right pane. They will be displayed with a dialog to configure this feature.
Additional Receiver for Web configuration
Many additional settings related to web receiver now configurable to the administration console. Select the memory you want to configure, and then select the manage Receiver for Web Sites action. Select the website that you want to change, and click the Configure key. A pop-up dialog box is presented for you to change configuration for the site, as shown below.
Select Session Settings to configure different timeout values.
Select to change Workspace control session reconnection, separation and shutdown behavior.
Other settings are available from Advanced Settings section.
In addition expands the Deploy Citrix Receiver section, so upload Receiver installation packages to Storefront server, if you want your user receivers from the Receiver for Web Site to download.
Administration PowerShell SDK
Storefront 3.1, a new management PowerShell SDK provides. The documentation for this SDK can be found here for download. You can together with objects, you not only do the same tasks as the administrative console with the console. Cmdlets concentrated in the new SDK on administrative tasks and to storefront providing wide configration, Stores, authentication and Receiver for Web.
grouped New cmdlets with STF ahead. Example:
# Install the required components Storefront
Add-STFDeployment https://storefront.mycompany.com -Confirm: $ false
# an authentication service with a store Add IIS virtual path in the context of
$ authentication = Add-STFAuthenticationService "/ Citrix / AuthenticationStore"
# Add a business that uses the new authentication service configured the supplied XenDesktop server
$ store = Add-STFStoreService -VirtualPath "/ Citrix / Store" -AuthenticationService $ authentication -FarmName "XenDesktopFarm ''
-FarmType XenDesktop - server publishing "XDEUA", "XDEUB"
# Add a receiver for Web site so that users can access published in the store, the applications and desktops
$ recipient = Add -STFWebReceiverService -VirtualPath "/ Citrix / StoreWeb" -StoreService $ store
The SDK also high-level scripts that enable to script and automate storefront installations. You can adjust the high-level examples to your specific requirements.
Existing PowerShell cmdlets, supported with the prefix DS even for business continuity. However, they are outdated and will eventually be removed in the future.
0 Komentar