Middle-tier and login times

Chris

unread,

Dec 2, 2009, 8:07:54 AM12/2/09

to

Hi all: Sorry if this is the wrong forum for this post.

I am working on improving user login times. Many users (not
including myself) think a 2 minute login sequence is too
long. One option I have is to go client-less but I have NO
EXPERIENCE with this. Currently we use NW client 4.91 sp5
and zenworks 7.0.1.x. Groupwise Notify also loads.

Does logging in via middle-tier server decrease login
times?

Thanks for the help, Chris.

Shaun Pond

unread,

Dec 2, 2009, 8:23:30 AM12/2/09

to

Chris,

logging in via middle tier will usually only make it take longer, as
NCP requests have to be converted to/from html. 2 minutes is a silly
long time for login, have you done any work to identify where the
slowness is coming from?

--

Shaun Pond

Chris

unread,

Dec 2, 2009, 12:19:03 PM12/2/09

to

I am currently working on it and have a thread in the
windows client forum (with Andrew). What kind of login
times should we be looking at? FYI, we run nwclient
4.91sp5, zenworks 7.0.1.x, GR 7 client. We use roaming
profiles too.

What I do see is that following hitting OK at the login
dialog I see about a 30 - 60 second dead period where all
that is present is a blank blue screen. Once that is over
things preceed fairly quickly - login scripts run (5 seconds
top), groupwise notify loads, followed by zenworks (
probably 20 seconds, we do a lot with zen ).

I am not exactly sure where to begin to identity the issue.
The dead period following the login dialog is definitelyan
issue. Any suggestions?

Chris

>>> On 12/2/2009 at 8:23 AM, in message
<VA.0000cf5...@no-mx.forums.novell.com>, Shaun

Shaun Pond

unread,

Dec 3, 2009, 3:16:09 AM12/3/09

to

Chris,

slow login can be the result of hundreds of different things: it's
important to identify where the delay is coming form before you can
attempt to remove it: for example, if you do a workstation-only login,
how fast is that? What do you have associated to the user and
workstation in terms of policies, applications? My usual
troubleshooting method is to remove everything one by one until the
problem goes away, then add them back until it breaks, and there's the
most likely culprit.

--

Shaun Pond

Chris

unread,

Dec 3, 2009, 7:49:22 AM12/3/09

to

Shaun: Found out my roaming profile had grown to over 30 MB
with a total profile size of over 150 MB. I limit what gets
uploaded in the roaming profile but that still grows over
time. I wacked my profile, started over, and cut my login
times by one third. I now am seeing login times off around
35 seconds. Roaming profiles are nice, but they are
definitely a double edge sword.

Chris

>>> On 12/3/2009 at 3:16 AM, in message
<VA.0000cf6...@no-mx.forums.novell.com>, Shaun

Shaun Pond

unread,

Dec 3, 2009, 8:02:43 AM12/3/09

to

Chris,

one common thing to exclude is the desktop: stops issues when users
drag a file to the desktop instead of a shortcut :)

--

Shaun Pond

Sami Kapanen

unread,

Dec 10, 2009, 8:25:44 AM12/10/09

to

Chris wrote:
> Shaun: Found out my roaming profile had grown to over 30 MB
> with a total profile size of over 150 MB. I limit what gets
> uploaded in the roaming profile but that still grows over
> time. I wacked my profile, started over, and cut my login
> times by one third. I now am seeing login times off around
> 35 seconds. Roaming profiles are nice, but they are
> definitely a double edge sword.

Sure is..
We gave up on roaming profiles few years back, students are using
mandatory and staff local profiles.

-sk