Storefront 3.0. Meanwhile, hopefully you have learned that the headline feature for this version to provide a uniform user experience across all receivers available and improving adaptability.
If you want to learn more about it, please call to Richards blog article here.
But back to publication! Today I want to call all the other new features in storefront available 3.0.
Please note that you must import the storefront PowerShell modules before you can run a PowerShell commands in this article. The following code snippet does this for you:
$ dsInstallProp = Get-ItemProperty -Path HKLM: SOFTWARE Citrix DeliveryServicesManagement -Name InstallDir $ dsInstallDir = $ dsInstallProp.InstallDir & $ dsInstallDir .. to support scripts ImportModules.ps1
Classic receiver experience
to help you transition to the new Unified receiver experience smooth, storefront 3.0 constitutes existing green bubble UI (as the classic receiver experience called). In this way you can take full advantage of the new features immediately, and update the user experience when users are ready.
If you perform an in-place upgrade from 2.x to 3.0 Storefront, the user interface for the existing Receiver for Web sites is considered the classic green bubble UI remain. When you create new recipient for sites after the upgrade or reinstall will see in the new unified user interface users.
to the new unified user interface for an updated website allow the Storefront management console, by selecting the Disable Classic Recipient Experience Action in the right pane for the selected recipients for the site.
The above action alone is only the uniform user interface for your Web allow users. To the unified experience for the user with the latest native receiver (eg Receiver for Windows 4.3 and Receiver for Mac 12.0), you can also configure the Store.
- Select the Stores node in the left panel
- Store Select want to configure in the central region
- Select the Ask Uniformly as Standard action in the right pane [1945015Wählen] Set the Unified receiver experience as a standard for this store in the pop-up dialog
- Select the receiver for Web -Site for native receivers from the drop-down list to use
- Select OK
Google Chrome support without NPAPI
Google Chrome on Windows and Mac is fully supported out of the box without NPAPI in storefront 3.0. To use this service, you need to update both storefront and receiver. Receiver for Windows 4.3 and Receiver for Mac 12.0 support this new technology. You can learn more about the technology and user experience from my previous blog article here.
No More Editing Hosts file
Previously as mentioned herein, Citrix recommends that you change the hosts file on your storefront server, the Receiver for Web to ensure always speaks to the local storefront server instead of the load balancer. In Storefront 3.0 we use a new feature in the .NET Framework 4.5 loopback communication between Receiver for Web and the rest of the storefront services implement. This is configurable using PowerShell cmdlets Set-DSLoopback , the syntax is
Set-DSLoopback [-SiteId]
[-Loopback]
the valid values for loopback are:
- on - This is the Web-sites receiver for new default is , Receiver for Web uses the schema (HTTPS or HTTP) and port number of the base URL, but replace the host part to the loopback IP address to communicate with storefront services. This works for a single server deployment and implementations with a non-SSL conclusion Load Balancer
- OnUsingHttp -. Receiver for Web uses HTTP and the loopback IP address with storefront to communicate services. If you are using an SSL conclusion Load Balancer, you should choose this value. You must also specify the HTTP port if the default port is not 80
- Off - This turns used for loopback and Receiver for Web storefront base URL to interact with storefront services. If you perform an in-place upgrade, this is the default value to avoid disrupting your existing deployment.
For example, if you use an SSL conclusion Load Balancer, the IIS configuration uses 81 port for HTTP and the path of the Receiver for Web Site / Citrix / StoreWeb, you can run the following command to configure the receiver for Web Site:
Set-DSLoopback -SiteId 1 -VirtualPath / Citrix / StoreWeb `
-Loopback OnUsingHttp -LoopbackPortUsingHttp 81
Please note that you disable loopback, if you want to use any web proxy tool like Fiddler, the network traffic to detect between receiver for Web and storefront services.
delegating authentication to the back-Provider
Storefront 2.x always communicates with Active Directory to authenticate users. This requires that the domain hosting server storefront has at least one way external trust to the domain that the backend hosting XenApp / XenDesktop farms / sites. This may not be possible in some implementations.
Storefront 3.0 provides the ability to authenticate to XenApp / XenDesktop farms / sites to delegate. This can be enabled by running the following PowerShell commands. Please replace the storage and authentication virtual paths appropriately.
## some variables relevant for your deployment SITEID $ = 1 $ StoreVirtualPath = "/ Citrix / Store" $ AuthenticationVirtualPath = "/ Citrix / authentication" # change auth service using XML Service auth domain-auth set DSXmlServiceAuthentication -SiteId $ SITEID -VirtualPath $ AuthenticationVirtualPath $ fs = @ (Get-DSFarmSets -IISSiteId $ SITEID -VirtualPath $ StoreVirtualPath) | where {$ _. Name -eq "default"} - Update DSFarmSet -IISSiteId $ SITEID -VirtualPath $ AuthenticationVirtualPath -Farmset $ fs are treated as all desktops applications treatment
desktops unlike applications in the storefront / receiver. They are placed in a separate tab desktop and in the case of Receiver for Web, they are not associated with workspace control. In some applications it is desirable to treat desktops applications so that they are put together with applications and get connected within the workspace control. With Storefront 2.x, you must Add TreatAsApp keyword to all published desktops to achieve this effect. This can be error prone if you just want all desktops deemed to be applications. It also lacks flexibility, if you want a memory to deal with desktops applications, and to preserve the other to the desktop behavior. Storefront 3.0 enables you to configure without the need to add the TreatAsApp keyword to all published desktops at store level treatment of all desktops and applications. This is configurable to the PowerShell cmdlets. The syntax is:
Set-EnhancedEnumerationOptions [[-siteId]
for example, if all desktops is as applications for a deal at / Citrix / shop for treating want, type the following command, which would configure for you:
Set-EnhancedEnumerationOptions 1 -siteId `
-storeVirtualPath / Citrix / shop -treatDesktopsAsApps true $
service Integrated monitoring for NetScaler
NetScaler load balancer you can see a monitor, the health of the storefront services (see the Setup screen shot of the NetScaler Admin UI below).
For Storefront 2.6 or earlier, you have to install a separate add-on package on the storefront server to support NetScaler monitoring. This will now be integrated into Storefront 3.0. It is installed by default and activated. You can use PowerShell commands to change or disable this service, the settings of that service.
to check the URL for this service, you will use the Get-DSServiceMonitorFeature . By default, this service uses HTTP and listens on port 8000. You can change this scheme to different and / or port of cmdlets with Set-DSServiceMonitorFeature . For example, if you use the service HTTPS and heard to change to port 444, you can run the following command to configure it
Set-DSServiceMonitorFeature -ServiceUrl `
https: /. / Localhost :. 444 / storefront Monitor
to remove if the deployment by the Remove-DSServiceMonitorFeature cmdlets
Advanced Store Customization SDK
storefront offers a Store customization SDK for advanced business logic adaptation. If you are not familiar with it, you are referred to here for more details. There are a number of enhancements to this SDK in Storefront 3.0.
- A new adjustment point is during the introduction process added shortly after the broker the VDA address assigns, but is activated before NetScaler Gateway. In this way you can gateway change which are used for the HDX connection to the context data, such as the client IP address or VDA IP address, etc.
- Several new features, such as to add gateway information and HDX introduction properties data to the adaptation context further information available, the customization to support decisions.
- The service request matching point pre-XML extended extended multi-site aggregation, such as changing the equivalent farm sets to support the aggregation group and the order of operations may be used for the launch.
offer more flexibility for adaptation is the Storefront web API extended to allow specified custom HTTP headers that are passed on the memory-matching points. For example, you can Receiver user interface to provide user session enhance preference and they happen in the store matching points to change sent to the XML Service or the ICA file requirements. This custom HTTP headers to be passed to the store matching points, you must add the header to the white list in the web.config file under the Receiver for Web site.
- Open web.config with your favorite text editor
- localize
... - Add a new section named forwardedHeaders the specified custom header, for example,
[1945019[
...
Replace the values of the header name with your actual custom header name.
0 Komentar