Citrix Consulting has updated the CloudGateway Express Implementation Guide to reflect the latest StoreFront 1.2 and the receiver 3.3. The guide provides step by step instructions for setting up a proof of concept for StoreFront. Building a proof of concept environment is the best way to allow users to see the benefits of StoreFront no impact on production. While putting together the POC guide, I am very happy to see all the new Storefront 1.2 features such as additional support for XenDesktop and customer HTML5.
With the POC guide update, I will post a series of blog posts discuss additional considerations when migrating from the web interface for StoreFront. The next blog articles are deeper in the HTML5 client configuration with Access Gateway, user provisioning first time with account services, and ideas for a gradual approach allowing users to opt using StoreFront while keeping the optional web interface. So StoreFront is a great product, a sudden transition to a new interface can be a shock to users. Allow users to choose before StoreFront Web Interface is completely eliminated will help gain acceptance.
Do not let your StoreFront Start Bare (Auto & Icons featured)
StoreFront takes a different approach to the application display from the the Web interface. Instead of having all applications appear on the Home screen, users will be presented with a blank screen when they first login. Before a user can launch an application, they must choose from a list of applications that will then place the application on the approach screen.This house applications deemed "self-service" allowing users to select the applications that they use on a regular basis to be shown. The applications selected to be on the home screen are then stored in a SQL database that enables applications appear on the Home screen from any device they connect from.
To prevent users from having a blank screen when they first log in, it is recommended that administrators automatically implement appearing applications. To do this, set Keywords: Auto the description of the application within XenApp. Another keyword that can be used to organize applications is featured. Unlike the keyword auto which places certain applications on the home screen, the keyword only place in Featured Featured applications category. The application will also appear in a different category if a client application file was specified. To request a feature, set Keywords: Featured as the description of the XenApp inside. Since StoreFront does not show the value of the description field, adding additional text after the keyword will not provide any advantage and will not stop the word run. Web interface, however, shows the value of the description field in the detail view as shown below:
Categories
Although it was generally a good idea to organize applications in the Web interface in folders, it is even more important to do with StoreFront. Each published application and desktop appears in the Desktop Receiver under the "All Applications", unless otherwise stated. This makes it difficult for users to easily find the applications they need for similar applications are grouped.
To easily move applications organized in the XenApp console subfolders in a corresponding client application file, the following PowerShell command can be used:
Add-PSSnapin citrix * - ErrorAction SilentlyContinue Get-XAApplication -FolderPath Applications "admin Tools" | Set-XAApplication -ClientFolder "Administrative Tools"
 |  |
| If none of the categories are used, the menu is very strict. | This is how it should look, applications grouped into easily recognizable categories. Also note the descriptive category . |
How StoreFront Treats Desktops
StoreFront 1.2 introduces many important features for viewing workstations by via the receptor for the web page. These improvements include navigation and launch of workstations without requiring the subscription, the launch of the desktop on logon if one office is published, allowing the Web site must be configured to access only the office and access to local (transparent reverse).
As with the web interface does not differentiate between StoreFront XenDesktops hosted desktops and XenApp server desktop published. Both workstations appear within the category Desktops. StoreFront also includes automatic launch and Desktop Viewer capabilities. If this feature is not desired for a specific Terminal Server services office, the XenApp administrator can add a special keyword in the field of office published description. The keyword format is as follows: Keywords: TreatAsApp. This keyword can also be used on desktops published from XenApp and they appear with applications so that all appear in one window without tabs.The configuration XML below shows the user interface display for applications and desktops to be personalized. It allows a receiver to the website to limit the view to either applications or workstations and allows the default display to set. If XenApp is mainly used, change the default view to "apps" would be recommended.
0 Komentar