Looking for:
Citrix receiver 4.3 1 |
Citrix receiver 4.3 1
Receiver SSON not working consistently after upgrade to
Support for the unified Citrix Receiver experience. Create and manage featured apps. Configure workspace control. Configure communication time-out duration and retry attempts. Configure user access. Set up highly available multi-site stores. Add a NetScaler Gateway connection. Import a NetScaler Gateway. Configure NetScaler Gateway connection settings. Authenticate using different domains.
Configure beacon points. Advanced configurations. Configure Desktop Appliance sites. Configure Resource Filtering. Configure using configuration files. Configure StoreFront using the configuration files.
Configure Citrix Receiver for Web sites using the configuration files. Secure your StoreFront deployment. Export and import the StoreFront configuration.
StoreFront SDK. Troubleshoot StoreFront. Aviso legal. This article contains the information needed to use NetScaler to load balance two or more StoreFront servers.
This article provides guidance on how to deploy a StoreFront server group containing two or more StoreFront servers in all active load balanced configuration.
Review the section Plan gateway and server certificate usage. Consider the following options before purchasing a certificate from a commercial certificate authority or issuing one from your enterprise CA. Note: When exporting the private key associated with the certificate is not feasible.
Use two separate certificates: one on the NetScaler load balancing vServer and a different certificate on the StoreFront server group nodes. Both certificates must include Subject Alternative Names. Example - storefront. Within your Service Group, select the Members option on the right hand side and add all of the StoreFront server nodes you defined previously in the Servers section. Bind the CA certificate used to sign the server certificate you imported earlier and any other CAs that might be part of the PKI chain of trust.
Select the load balancing method for the vServer. Common choices for StoreFront load balancing are round robin or least connection. Bind the same server and CA certificate you previously bound to the service group, to the load balancing vServer. From within the load balancing vServer menu, select Persistence on the right hand side and set the persistence method to be CookieInsert.
Name the cookie. If a multisite deployment consists of two or more StoreFront server groups located in separate geographic locations, you can replicate subscription data between them using a pull strategy on a repeating schedule. To provide high availability for this service, create a second vServer on each NetScaler in your deployment to load balance TCP port for each of the StoreFront server groups.
When configuring the replication schedule, specify a server group address that matches the subscription synching vServer virtual IP address. Ensure the server group address is the FQDN of the load balancer for the server group at that location. The CitrixSubscriptionsSyncUsers local group contains an access control list of all remote StoreFront servers authorized to pull subscription data from a particular server. For bidirectional subscription synchronization, server B must also be a member of the CitrixSubscriptionsSyncUsers security group on server A to pull subscription data from it.
Import the same certificate and private key that was deployed on the NetScaler load balancing vServer to every StoreFront node in the server group. When you complete the initial StoreFront configuration, join each of the nodes, one after the other, to the server group using the primary node. Propagate the configuration from the primary node to all other server group nodes in the group.
Test the load balanced server group using a client that can contact and resolve the shared FQDN of the load balancer. To enable external monitoring of the run-state of the Windows services on which StoreFront relies for correct operation, use the Citrix Service Monitor Windows service.
This service has no other service dependencies and can monitor and report the failure of other critical StoreFront services. The monitor enables the relative health of a StoreFront server deployment to be determined externally by other Citrix components, such as NetScaler. Note: Only a single instance of a monitor can exist within a Storefront deployment. To perform a quick test on the new monitor, enter the following URL into the browser on the StoreFront server or any other machine with network access to the StoreFront server.
The browser should return an XML summary of the status of every Storefront service. If you have configured the NetScaler Gateway vServer and load balancing vServer on the same NetScaler appliance, internal domain users might experience issues when trying to access the StoreFront load balanced host base URL directly rather than passing through the NetScaler Gateway vServer.
This triggers StoreFront attempt to use the AGBasic protocol to perform NetScaler Gateway silent authentication, rather than actually prompting the user to log on with their domain credentials. In previous versions of Storefront such as 2. This ensures that Receiver for Web always communicates with the StoreFront services on the same server in a load balanced deployment.
If the base FQDN were to resolve to the load balancer, the load balancer could potentially send the traffic to a different StoreFront server in the group, leading to authentication failure. This does not bypass the load balancer except when Receiver for Web attempts to contact the Store service residing on the same server as itself.
You can set loopback options using PowerShell. Currently, we have v3. This feature is not working in Receiver v4. I also notice the following different behaviors in Receiver 4. After reading up on this further, I realize that this is by default. However, the Receiver will not reconnect sessions at Windows logon; I tried creating the same entry under the HKCU key, but it does not fix it either. Something weird that I noticed is if I lock my machine, then unlock it, my sessions will reconnect.
I am having the exact same issue; will not reconnect a XenApp session when logging on to a computer, be that the same computer or a different one.
However, like your situation, if the user locks and the unlocks the machine the session is reconnected. Very odd. GPO specifying StoreFront account; and reconnect behaviour Control when Receiver attempts to reconnect to existing sessions. I can confirm if we Refresh Apps Refresh , or open another application WinLogon the session is reconnected. The engineer that I am working with at Citrix was able to reproduce the same issue in his lab. It took me two weeks, but I finally got an offline engineer to take the case, so I should be hearing back next week with a helpful update.
I will post an update once I hear back from them. Prior to the issue being reproduced I thought that is was an issue with my environment, most likely with the Receiver, but perhaps with the Store on the Storefront side.
However, between you and the engineer having the same issue, I no longer think it is an issue with my environment. Also, for testing purposes, I created a test Store, but I had the same issue. I also noticed the issue with WSCReconnectMode set to 4, sessions will not auto reconnect when the Receiver is launched.
Actually, it appears that the only setting that IS working is the default setting of 3. Not yet. The escalation engineer that I was working with last week is getting the Product engineering group involved. Have you tried creating a test Storefront store one that is clean without any customizations and pointing to that? I have already tried both, but I am not ready to rule out Storefront yet. Citrix tested it also with the same results. We are having the same issue. As a workaround we have done what doggates referenced but I would rather it just work the way it is supposed to.
Any information from Citrix on your ticket fmazzuc? Here is the final response that I received from Citrix as to what the issue is. I was told that it may be addressed in the next release of the Receiver:. Fortunately we can manually execute the command line selfservices. Here is what I found in my final round of testing, before implementing the work around the same one that was mentioned by doggates :. The testing was successful.
When I place the following command in the Start Menu, the Desktop s launch at logon. Also, I disabled Workspace Control completely.
Part of the problem with sessions not launching at logon, was that if you locked and unlocked your machine it WOULD launch disconnected sessions. So I pushed out an update via the Registry and set Workspace Control to 0 disabled.
I just put the following command in the Startup folder for All Users. Also, I just wanted to revisit the testing that you and I performed last week. After we finished testing last week, I ran a few more rounds of tests. I was actually able to get it working pretty consistently using the method that you recommended. I created a GPO and included the following variables in it.
Value Name: Self-service. When all of this was done, it seemed to be working OK. As a result, a disconnected desktop would launch 2 times, once for each Store configured in the registry.
Technically, the GPO would not get applied until after 1 the existing Receiver was uninstalled, 2 the Receiver Cleanup utility was run, and 3 the Citrix Receiver was reinstalled. However, I determined that the duplicate store issue would have opened up a whole new set of testing, and I did not want to go down that road, so I abandoned this method.
I just wanted to let you know that I was finally having some success with the method we used. One of my customer has CVAD environment this is new setup and had exact similar issue.
After Disabling "Control when Receiver attempts to reconnect to existing sessions" in the group policy, the issue was fixed.
No comments:
Post a Comment