Should I worry at all about Local Profile Size?

  • Thread starter Thread starter Sandy Wood
  • Start date Start date
S

Sandy Wood

All of our XP systems are networked and we recently started seeing some
workstations that had corrupted user profile symptoms. We also had a few
systems that displayed some slow login times also.

I our infinite wisdom (or not) we thought that maybe user's local profile
sizes might be the issue so we scripted some commands to clean up user's
profiles by removing old TEMP folder data as well as Internet Temp files.

After a bit more research, it appears that local profile size may not really
be an issue to slow computer performance either logging on or shutting down;
as opposed to roaming profiles.

Does anyone have any thoughts in this area?
 
Sandy said:
All of our XP systems are networked and we recently started seeing
some workstations that had corrupted user profile symptoms. We also
had a few systems that displayed some slow login times also.

I our infinite wisdom (or not) we thought that maybe user's local
profile sizes might be the issue so we scripted some commands to
clean up user's profiles by removing old TEMP folder data as well
as Internet Temp files.

After a bit more research, it appears that local profile size may
not really be an issue to slow computer performance either logging
on or shutting down; as opposed to roaming profiles.

Does anyone have any thoughts in this area?

Corrupt profiles - sure.
Roaming profiles - sure.

Non-corrupt local profiles - maybe. If they have installed and changed and
enormous about of data and perhaps have gotten some shortcuts to apps that
don't exists any longer on the desktop/in the start menu - particularly to
networked items.

Easy test. Find someone who is logging in slowly. Reboot their computer,
logon first as someone with admin privs and rename their profile directory
to .old, then log out and have them logon. The first logon *may* take some
time. Once they are fully logged in - reboot and have them logon again. If
it is faster - you know it is something in the profile - fix accordingly.

To put the machine back the way it was - reboot, logon as someone with admin
privs and rename the new profile to something like .002 and then rename the
old profile to its original name and log out. Have the user log back in.
 
Back
Top