Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win2K roaming Profiles corrupted on PIII pcs!!!!

Status
Not open for further replies.

ngoulain

MIS
Aug 8, 2002
2
MG
Hi,
I set up win2000 Pro clients on HP PCs (PIII and PIV) but on PIIIs roaming profiles are always corrupted. Is it a bug on PIII processors or something else? Need help cos I'm stuck!!!

Ngoulain.
 
What makes you think its the P3 processor that is the root of the problem?

What events are generated that cause you to belive that this is the case?
 
I've delt with corrupted roaming profiles before, but it had nothing to do with the type of processor. Most cases its the users fault. They modify or try to install or save something wrong. Perhaps the accounts arn't restricted in an area where they should be.
I'm curious aswell, why do you think its a processor issue?

Steve
Sys.Admin.
 
Hello every body,
the problem is that when I set up Win2K pro on HP PIII,roaming profiles are corrupted.
More exactly, when users log off, the system can't copy all files into the server because of insufficient ressources system.
Before, I think that the problem are issued of permissions and I changed all the permissions on the server as Full Control but the problem still remains.
PS: all client users have locally power users permissions.
need some help!!!!!!!!
Ngoulain
 
Hello ngoulain!
Try looking into the event viewer to see what entries are being recorded about this user. You may see something reguarding the inability of a section of the registry to unload in a period of time.
When the system records an error such as: " insufficient ressources system" , the resources it maybe refering to are of the type found in the performance monitor. Objects such as Memory, pages/sec, etc. Try running the performance monitor program. First create a baseline log and then try a running log while a user shutdowns in your attempts to recreate the profile corruption. Then review the generated logs trying to narrow down which system resources are the underlying cause of the corruption.

Cheers!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top