Bill Dotson
Reputable Poster
I know that lots of folks on this list use Citrix to deliver JDE to the desktop, so I'd like to get a very informal survey of your experience. We are on Xe so that is my principle focus now, but I'd like to know what others on newer releases experience too, since we will (presumably) upgrade to a later release sometime in the future. We are using Citrix Metaframe XP SP3/FR3 to deliver the application to the desktop.
On to the questions:
1. In our situation, we deliver JDE as a published application. Do you publish JDE, or do you publish the entire desktop?
2. We have a number of users who frequently run into problems, like their Citrix session gets hung, or sometimes their entire desktop gets hung, when they switch windows between JDE and another application such as Microsoft Word or Outlook. Has anyone else experienced this problem? Were you able to resolve the problem?
3. One user behavior that seems to repeatedly cause problems is having lots of JDE windows open at once. Often, when one of our users reports that their session or desktop is hung, we find that they have 8 or 10 or more JDE windows open, sometimes with the same application open 3 or 4 times (generally different versions, but still the same application). As an experiment, we asked one of our users who has this problem frequently to limit herself to no more than 5 open windows, and not to open the same application more than once. Her problems seemed to disappear for a while, until she just couldn't resist and opened 7 windows, 3 of which were the same application. (Our purchasing department frequently opens up multiple versions of Purchase Order Entry.) In your environment, do your users have lots of open JDE windows, and does it cause them problems? Do they have the same application opened more than once, and does that cause any problems?
4. We have a large number of users who often work from home, so we have allowed third-party print drivers, but we think that's causing some instability - sometimes, winlogon.exe consumes 50% or more of the CPU for a single user session, slowing down all users on the affected server until we can kill the session. Have you experienced problems with third-party print drivers? If so, were you able to resolve the problems? How?
I'm trying to determine if our experience is substantially different than that of other folks. If so, maybe we're doing something wrong, or maybe our users' work patterns are very different than yours. I welcome any and all comments, suggestions, observations, brow-beating, etc., and thank you in advance for your responses.
On to the questions:
1. In our situation, we deliver JDE as a published application. Do you publish JDE, or do you publish the entire desktop?
2. We have a number of users who frequently run into problems, like their Citrix session gets hung, or sometimes their entire desktop gets hung, when they switch windows between JDE and another application such as Microsoft Word or Outlook. Has anyone else experienced this problem? Were you able to resolve the problem?
3. One user behavior that seems to repeatedly cause problems is having lots of JDE windows open at once. Often, when one of our users reports that their session or desktop is hung, we find that they have 8 or 10 or more JDE windows open, sometimes with the same application open 3 or 4 times (generally different versions, but still the same application). As an experiment, we asked one of our users who has this problem frequently to limit herself to no more than 5 open windows, and not to open the same application more than once. Her problems seemed to disappear for a while, until she just couldn't resist and opened 7 windows, 3 of which were the same application. (Our purchasing department frequently opens up multiple versions of Purchase Order Entry.) In your environment, do your users have lots of open JDE windows, and does it cause them problems? Do they have the same application opened more than once, and does that cause any problems?
4. We have a large number of users who often work from home, so we have allowed third-party print drivers, but we think that's causing some instability - sometimes, winlogon.exe consumes 50% or more of the CPU for a single user session, slowing down all users on the affected server until we can kill the session. Have you experienced problems with third-party print drivers? If so, were you able to resolve the problems? How?
I'm trying to determine if our experience is substantially different than that of other folks. If so, maybe we're doing something wrong, or maybe our users' work patterns are very different than yours. I welcome any and all comments, suggestions, observations, brow-beating, etc., and thank you in advance for your responses.