In the newly released StoreFront Planning Guide (which you can find here) comes this great overview of differences between Web Interface and StoreFront.
Where StoreFront will go beyond Web Interface in the future
|XenDesktop Deployment Scenarios
|Cross farm aggregation and de-duplication
||XA farm migration Only
|Configuration through Citrix AppStudio
|Windows Server 2012 support
|HTML 5 access on more devices
|Smartcard support from most Receivers (LAN and AG)
||Windows PNA on LAN Only
|Unified EPA/Smart Access across Receivers
|SDK for partner extensions (most Receivers)
||Ad-hoc integrations, Web Only
Where StoreFront matches Web Interface Continue reading “Differences between WI and StoreFront”
This article defines troubleshooting steps for a failure in pass-through authentication. Symptoms include getting prompted for credentials at the Web Interface logon and also getting a logon screen when you attempt to launch a published application.
Complete the following steps to troubleshoot pass-through authentication to Web Interface:
- Verify that SSONSVR.EXE is running on the client machine. If Receiver was installed with the ENABLE_SSON=Yes command line switch, then the computer must be rebooted after the installation if not this process does not load. If this process is not running for any reason, pass-through authentication will not work.
- Verify that the Citrix Receiver group policy allowing pass-through authentication has been applied to the workstation. This can be done either through Group Policy Management Console or through a Local Policy. The template for this group policy setting can be found in the following location on any workstation with Receiver installed: Continue reading “How to: Troubleshoot pass-through authentication to Web Interface”
If you have configured your Web Interface server to display your published applications in a window of percentage of your screen and you want to publish a single published application (XenApp) through your Web Interface all you need to do is the following:
1. Go to your Web Interface server and browse to the following location:
2. Open the default.ica file with notepad and add your application under the lines
Application= Continue reading “Publish single seamless application through WI”
When Web Interfaces sites or Program Neighborhood Agent sites are part of a large deployment and are the primary method of accessing applications for an organization, you might consider isolating each Web Interface site or Program Neighborhood Agent site into their own IIS Application Pool.
Each separate Application Pool provides a process boundary so that when a Web Interface site or Program Neighborhood Agent site is assigned to one application pool, problems in other application pools do not affect the application. This ensures that if a Web Interface site or Program Neighborhood Agent site fails, it does not affect the other Web Interface or Program Neighborhood Agent sites running in other application pools.
The process to create an Application Pool for Web Interface or Program Neighborhood Agent site is as follows:
Note: Before performing these changes, ensure that no users are accessing the Web Interface or Program Neighborhood Agent sites because their access will get interrupted. Continue reading “How to Isolate Web Interface or Program Neighborhood Agent Sites into Their Own Application Pool for Best Performance”
Andrew Morgan has released the 2nd version of the popular software to make your old PC into a ThinClient.
Here’s the list of new features and the link to the download site.
ThinKiosk 2.0 is stuffed with new features and supported platforms, here’s a quick list: Continue reading “Thinkiosk 2.0 released”
For a repro of a problem my customer has I ran into the following issue when installing Citrix Web Interface 5.3 (I know that 5.4 is available but for this issue I needed 5.3 ).
After installing default IIS with the IIS 6 Management Compatibility I got a nice blank webpage when visiting the Citrix Web Interface.
When checking the installation/configuration of IIS I noticed that I missed some features in the installation of IIS.
Web Server Common HTTP Features
- Static Content Not Installed
- Directory Browsing Not Installed
- HTTP Errors Not Installed
After installing these components the problem of my blank webpage were gone.