Guys, I'd like to get your input on something. With PNAgent and XA 4.5 and users that roam from say computerA to computerB and vice versa. Has anyone seen an issue where clicking on the application again freezes on occasion? In other words, user moves from computerA to computerB and clicks on the published app icon from computerB. The session disappears from computerA and appears on computerB. That is the way it is supposed to work with smooth roaming. However, I have seen on occasion that the PNAgent client freezes while it is trying to reconnect to the session. This happens only if you use the icons as opposed to the "Reconnect Sessions" option. The reconnect sessions options always works. Can anybody comment on this? Does everybody use the "Reconnect Sessions" options instead of clicking the published app icons? I would appreciate your feedback on this. Thanks.
Hi Duke,
We find it works well all the time when we connect via Web Interface (via a splash screen), whereas if we use PN shortcuts to the farm from the client, we have re-connection issues.
On our new XenApp5 \ Win2008 farm we're seeing re-connections using a brand new session rather than the old \ disconnected session, which we're currently looking into.
Using 11.x of the client helps with a lot of niggly problems with connections too.
Regards,Mark
Mark,
Thanks for your comment. Can you elaborate a bit on the reconnection issues you're having with the PNAgent? It does seem to work better with Web Interface for us too when you click the "Reconnect Sessions" button from Web Interface.
I've seen problems when using connections from the Citrix client, using PN shortcuts to the desktop published app, and you expect to connect and grab your old or disconnected session, but instead you get a brand new session. This never happens when connecting via our splash screen using web interface.
I'm not sure this is what you're seeing, but it seem to me that custom connections that don't go via web interface occassionally also seem to hang to our XenApp5 farm. We've got a call logged with Citrix on this, but of course if you mention PN from the client, Citrix no longer support this in the 11.1 onwards clients.
Regards,
Mark
Sorry, I mean Citrix don't support PN in the client from 11.2.
Thanks, Mark. We are not using the PN client. We are using the client that used to be known as PNAgent. Now it is known as Xenpp Plugin (Services Site).
Basically, what I was asking the community is why the "Reconnect Sessions" options from the PNAgent menu always works reconnecting right back to applications when users move between computers. On the other had, if the user moves and clicks on the icons instead on the new computer, the reconnection might fail and it will freeze the session while it is trying to reconnect. Using "Reconnect Sessions" always works fine.
The users I work with are not trained to use the Reconnection Sessions option from the menu. Instead, they like to click on the shortcut Desktop icons. I would like to have a solution for this that makes it work also if users reconnect via the icons.
Thanks.
Are your PNAgents/XennApp Plugins configured to launch at Windows login? I would think if they were then you could avoid this issue. When the user moves to ComputerB and launches the agent then all sessions are reconnected automatically. That is, of course, if you have it configured that way in your WI console.
v5.2 - Site >> Session Options >> Workspace Control
-----------------------Matt Mustain, CCA, MCP
Good point. If the user has access to more than one published app though, the auto login won't work will it?
Guys, thanks for the suggestion. Matt, sometimes they user is already logged on both PCs at once and travels back and forth. The user is already logged on so I don't think the setting will have any effect in this situation.
I am still encountering this issue. When the user moves between computers and clicks on the Desktop icons, reconnecting to sessions freezes often. However, if the user right-clicks on the PNAgent and selects "Reconnect Sessions" there is no problem. If anyone can offer more information on this, please feel free to share.
Have you tried allowing only one instance of the application for each user? That is found under Advanced >> Limits for each application.
If that is used then the user will receive a message "You already have an instance of this application open and are not allowed to run more than one instance." That might clue them into clicking "reconnect." That probably isn't the ideal solution but it might help until we can find a better answer.
Matt, that is a good workaround, but knowing my users I know that will be an issue since they will want to keep clicking on the app icons. I would really, really like to get to the bottom of this. Thank you for making that suggestion.
Well it should certainly work using the normal connection method, as it does with the 'reconnect' method. I wondered what happens in the following circumstances:
Just thinking out loud here, to try and narrow it down.
Good suggestions. I will take a couple of days going over those and will post back results. Thank you.
No worries - sure, let me know how you get on.