Link to home
Start Free TrialLog in
Avatar of NReese
NReese

asked on

Poor enterprise laptop performance (Any Tips?)

Our laptop users are have a productivity rendering experience everyday as they work on their laptop. They have been putting up with it and they are quite used to it as days go by, but I was just curious what other companies configurations look like or what we might be doing wrong? A few traits:

-We are a mixed Novell/AD environment
-We are a mixed 2003/2008 server environment (2003 domain/forest functional level)
-We use folder redirection (User Desktop, My Documents) for our laptop users
-We use roaming profiles for our laptop users and VDI users
-We use PGP Whole Disk Encryption on ALL of our enterprise laptops
-We use Vipre Enterprise Virus Protection/Firewall on all enterprise computers/VDI
-We have not yet implemented Wireless, so all of our laptops still use ethernet

A few things we have tried to make the experience a little better:
-Changing the network provider order to "Microsoft Windows Network, Microsoft Terminal Services, NetWare Services, VMWare View SSO Nework Provider, Web Client Network", which made our Office applications not take a long time to respond and finally come up. +1
-Toggle UNC Path Filter On/Off through Novell Client Properties with no visible gain. +0
-Changing firewall settings (Vipre) +0


So I guess my question is, are their any known conflicts in our setup, a minor tweak that I am missing in Novell/AD, or a common setup that I am unaware of that should be used on ALL laptops? If any more key information is needed, please let me know.
SOLUTION
Avatar of David-Howard
David-Howard

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of NReese
NReese

ASKER

It seems that it might be these *.tmp files that hide inside the profile. Apparently, they are temp files created when a local to server profile connection fails. They are just as big as the ntuser.dat, so they really add to the time the user has to wait when logging in. We will have to find out how to write a script of some sort to delete them on the computer and the server share so that they are no longer part of the profile. I just found this:

http://support.microsoft.com/kb/328607

The profiles are most likely the problem for log in / log out time. But what about all around lag moving from and to applications, especially PGP WDE (which I didn't know was a resource intensive application when the disk is done being encrypted). What exactly does the 'pgpwflt' do in the provider order?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of NReese

ASKER

Thanks for all the information. There are a few things on that list that I wanted to give a try but was not sure if there would be an outcome. I will try to chisel our profiles to make them a bit smaller by getting rid of those temp files and see what else we can do with the info provided until we convert to 100% AD sometime in the near future.