Performance issue using Citrix

Deborah_Foster

Active Member
We are having a big performance problem on our citrix boxes.
We are running OneWorld B7332 SP 17.1
Our Citrix boxes are on NT 4.0 SP6 running Terminal server.

When a client click on the citrix icon for OneWorld they connect to the network run the script but then it can take upto 5 min for the OneWorld logon screen to appear. Even on the Citrix boxes them selves with no other users connected and clicking on the fat client icon it takes a long time for the sign on screen to appear.

It hasn't always been like this though it took a little longer then a fat client it wasn't many minutes.

Any one have any idea what could be dragging them down so much?
 
Deborah, this has come up before and is solved by adding owdeveloper to the local NT groups. Search the list for owdeveloper to get a more in depth description.

B733.2, SP 15, Oracle 8.1.6, HP 9000
Win2K, Citrix 1.8, NFuse
 
Take a look of OTI-01-0051
Cause
There is a Business Function that calls a Windows Operating System built-in function. This function searches for the OWDEVELOPER group on the local (i.e., TSE server) machine. If that group is not found, it will search the domain in which the TSE server resides. If it still does not find the group, it will search all trusted domains. If the group is not found in these domains and a Windows 2000 environment is being used, the entire Windows 2000 domain will be searched. These searches cause the time delay.

Resolution
Workaround:

1. Ask your Windows NT System Administrator to Create a windows user group on TSE called "OWDeveloper". But Do NOT add any user to OWDeveloper group.

2. The administrator must log out of the WTS window for the addition to become active.





Sergio Vargas
Windows 2000 / SQL2000 / B7333 Xe / SP15.1
 
Re[2]: Performance issue using Citrix

I am sorry for asking but I am confused. The delay we experience is after the
NT logon and between the logon script finishing and the oneworld logon screen
even appearing. Why would it be searching for the owdeveloper group if it
dosen't even know who is logging on? Wouldn't this happen after you type in
your username and password?
Also, this problem seems to be building. It is getting slower with age. It
never took more then a few seconds for the logon screen to appear before.
We do not have the nettrace in the jde.ini file turned on.

Thank you,
Deborah Foster
Business Systems Analyst
Akorn, Inc.
(847) 353-4935
E-mail: [email protected]
 
RE: Re[2]: Performance issue using Citrix

Hello Deb,
Are you using roaming NT profiles? Perhaps the delay is caused by the
profile being copied from a network location to the WTS server.

Brent Marxhausen
DBT, Inc.
cell: 612-804-0306
email: [email protected]
 
Re: Re[2]: Performance issue using Citrix

Deborah,

when a user is logged on to OW through a Citrix environment, OW at times
looks for the OWDEVELOPER group to determine if for example the creation
of versions should be permitted for that user. So you would experience a
delay when you go into Batch versions.
This delay is noticible only (and can go up to 5 minutes) when you have
many domains with some domain controllers over a LAN, because OW looks
for the group in all domains until it finds the group. If you would have
only one domain you should not notice any delay because of this.

In your case, if your problem is aggrevating and if your network
environment did NOT change recently you probably have a different
problem, nothing to do with the OWDEVELOPER group. But then, it wouldn`t
cost you anything to rule out the possibility by creating the group.

Yes, you are right, you should not experience this delay during logon.

Good luck, Gerd
 
Re[2]: Performance issue using Citrix

No we do not use roaming profiles but thanks for reply.


Thank you,
Deborah Foster
Business Systems Analyst
Akorn, Inc.
(847) 353-4935
E-mail: [email protected]
 
RE: Re[2]: Performance issue using Citrix

If the problem does not relate to the local 'owdeveloper' group, try
switching off the virus scanner to see if performance improves. Every
time I hear the word performance in conjunction with OW I always assume
that this is the reason. I had a similar problem with citrix & mcaffee,
and found that i resolved the problem by excluding .dll and .ocx file
extensions and the b7 directory from the scan.
Another thing to check might be odbc tracing? Search for sql.log on your
citrix server... its always the last thing I think of.
Regards,
Kieran Fitzgerald
 
Back
Top