Citrix StoreFront 2.x - Issues Fixed in This Release
Article ID: CTX138215
Updated On:
Description
Issues Fixed in This Release
StoreFront 2.x
The following issues were fixed in StoreFront 2.x:
StoreFront 2.6
StoreFront 2.6 contains all fixes that were included in Versions 2.0, 2.1, 2.5, and 2.5.2, plus the following, new fixes:
-
Configuration mismatches are created in server group installations by StoreFront console:
Any instance of clicking OK in a dialog box in the StoreFront console writes to the web.config file, even if no changes were made. This configuration change has no impact in standalone StoreFront installations, but server group installations will have configuration mismatches. To resolve this configuration mismatch, you can use the Propagate changes option for the relevant Server Group to force a configuration update.
[#319844]
-
Receiver for HTML5 will fail to load for Chromebook users when local installation is configured:
When the Install locally option is selected for Receiver deployment, delivery of the client software will not succeed for Chromebook users, who will see fatal errors. To properly deliver Receiver for HTML5 for Chromebook users, you must use either the Use Receiver for HTML5 if local install fails or the Always use Receiver for HTML5 option.
[#448101]
StoreFront 2.5.2
StoreFront 2.5.2 contains all fixes that were included in Versions 2.0, 2.1, and 2.5, plus the following, new fixes:
-
Fail to launch a XenApp session from the second delivery site:
The StoreFront server had problems with load balancing between two XenApp farms. When the first farm was completely loaded, StoreFront did not use the second farm and the application launch failed.
[#432279]
-
Enhanced enumeration fails with socket pooling enabled:
Enumeration failed for two or more farms when socket pooling was enabled in the store configuration file.
[#470666 and #458139]
-
Issues with finding the domain controller for a domain:
Slow logon times occurred when geographically distant domain controllers were chosen.
[#479210]
-
Submitting the logon form after the authentication service session timed out results in an HTTP 400 Bad Request:
When the logon form was submitted after the authentication service session timed out, an HTTP 400 Bad Request response was generated preventing the user's credentials from being resubmitted.
[#479200]
-
Directory queries are not thread-safe:
Citrix default Domain Services crashed because the Directory services account look-up was not thread-safe.
[#479188]
StoreFront 2.5
StoreFront 2.5 contains all fixes that were included in Versions 2.0 and 2.1, plus the following, new fixes:
-
Changing an expired password on next logon fails:
When prompted to change a password, client domain users using Windows would not be able to successfully change their passwords because of Windows Server 2003 domain controllers failing to handle the operation correctly. Microsoft has issued an update that resolves this problem. The update is available via Windows Update or may be downloaded from Microsoft support directly at http://support.microsoft.com/kb/2927811.
[#438725]
-
A user with a large number of subscriptions loses the ability to manage subscriptions:
When logging on, users with 353 or more automatic app subscriptions would receive the following error: "Citrix Receiver cannot currently add, remove, or reposition apps."
[#432086]
-
The wrong user name is sometimes shown:
Clients would erroneously display a different username.
[#430823]
-
PNA resource IDs do not match requirements of local launch logic:
PNA resources from XenApp were in a format different than StoreFront's usage. This inconsistency led to slower performance due to excessive ICA connections.
[#429055]
-
Partial wildcard certificates cause issues in the admin console:
The admin console would improperly display configured host names from the IIS bound certificates.
[#424708]
-
Change password option is not available for some users:
Some users were not given the option to reset their password even though they were enabled to do so.
[#416373]
-
Subscription export/import loses subscription properties:
StoreFront was not properly maintaining multiple subscription properties.
[#408668]
-
DAC smart card authentication updated to use domain account services rather than IIS certificate mapping:
Desktop Appliance Connector certificate authentication with smart cards required manual configuration with IIS certificate mappings rather than using the default domain account services.
[#406945]
-
A SAN web server certificate with no CN causes issues for the admin console:
StoreFront admin console was improperly handling common name entries in certificates which would cause console crashes.
[#401815]
-
StoreFront home farms support gives a user access to all farms when they should have access to none:
When a user was configured without access to any farms, all farms were enumerated for that user.
[#400869]
-
The admin console being closed would overwrite some manually applied changes made to the configuration file:
Some manual configuration changes were being lost when the admin console was closed.
[#440946, #424460, #439887, #395155]
StoreFront 2.1
StoreFront 2.1 contains all fixes that were included in Versions 2.0, plus the following, new fixes:
-
Application pre-launch does not occur with Receiver for Windows Enterprise:
XenApp applications are not pre-launched for Receiver for Windows Enterprise users connecting to stores through XenApp Services URLs, even when the pre-launch feature is enabled for an application.
[#423325]
-
Subscription synchronization is delayed when services are restarted:
When the Citrix Peer Resolution Service is restarted, which also causes several other Citrix services to restart, synchronization of users application subscriptions between the servers in a server group can be delayed for up to two hours.
[#413655]
-
Subscription synchronization fails with more than 750 subscriptions:
When the subscription store service contains more than 750 individual application subscription records, the synchronization of subscription information between the servers in a server group fails.
[#413536]
-
StoreFront cannot be deployed if only the .NET Framework Client Profile is installed:
If you install StoreFront on a server on which the Microsoft .NET Framework Client Profile has been installed, rather than the full .NET Framework, you cannot complete the initial configuration of StoreFront.
[#408897]
-
The StoreFront base URL cannot be specified when a certificate provides alternate common names:
When deployed on a server that uses a certificate with alternate common names, StoreFront automatically selects the shortest name to use for the base URL rather than using the fully qualified domain name for the server. However, subsequently attempting to change the base URL to use any of the other common names listed in the certificate fails.
[#404277]
-
Use of a certificate with no common name causes issues in the management console:
The Citrix StoreFront management console does not fall back to using a subject alternative name when a server certificate does not provide a common name. As a result, if you configure Microsoft Internet Information Services (IIS) for HTTPS with such a certificate before you install StoreFront, you cannot complete initial configuration using the management console. If you use a certificate with no common name to configure IIS and StoreFront for HTTPS after installation, you might experience issues when using the management console to perform certain tasks.
[#401815]
-
StoreFront initial configuration cannot be completed when the Windows Firewall service is not running:
When either creating a new deployment or joining an existing server group for a newly installed StoreFront server on which the Windows Firewall service is not running, the operation fails. To resolve this issue, start the Windows Firewall service and try again. Once initial configuration is complete, the Windows Firewall service can be stopped again, if required.
[#401143]
-
StoreFront cannot be upgraded when the Windows Firewall service is not running:
When upgrading from StoreFront 1.2 to StoreFront 2.0 for a server on which the Windows Firewall service is not running, the installation fails with the error message "An error occurred during installation. Please ensure that all the required prerequisites have been installed and run the installer again." To resolve this issue, start the Windows Firewall service and, in the Windows Firewall with Advanced Security console, delete the Citrix Credential Wallet Replication inbound rule, if it exists. Then, run the StoreFront 2.0 installation file to complete the upgrade. Once the upgrade is complete, the Windows Firewall service can be stopped again, if required.
[#400876]
StoreFront 2.0
-
After enabling the requireTokenConsistency parameter in StoreFront's store configuration file (c:\inetpub\wwwroot\Citrix\<StoreName>\Web.config) as described in Knowledge Center article CTX134965, users might not be able to access resources when logging in through Access Gateway.
[#LA2722]
-
StoreFront fails to enumerate virtual desktops assigned to specific client IP addresses.
[#LA2739]
-
With SmartAccess enabled on StoreFront, an error can occur during logoff.
[#LA2843]
-
XenApp Load Balancing policies and load evaluator filters based on client IP addresses are not honored for applications launched using Receiver for Windows 3.x.
[#LA2856]
-
Attempts to authenticate to the Receiver for Web fail for users whose passwords contain angle brackets (<;>).
[#0345698]
-
Attempts to authenticate to the Receiver for Web fail with the following Lightweight Directory Access Protocol (LDAP) exception:
"Could not complete your request"
[#0369721]
