NT/2000 network profile problem

[mlee97]

Here at work, my IT dept. just gave me a new profile because they couldn't fix the old one. This causes me quite a bit of aggrevation. I wonder if you guys might have an insight to this problem. I have a roaming profile and my main machine is win2k, others on the network are mixed between nt and win2k. IT claimed that "corrupt profiles are because of the old nt machines" I don't understand this at all since I haven't been on any of the old nt machines lately and I just started getting a login error.

The error states that the profile cannot be loaded because a file that is trying to load into the registry is not a valid registry file.

This profile works ok on all machines except the the main one. No login errors on the others.
I asked if there surely wasn't some log file that would tell them what file was trying to load into the registry, but they said there wasn't. Anybody familier with any of this?

thanks,

[cadetstimp]

If the existing roaming profile on the network was loading on other machines properly then why didn't they just remove the main machine's local copy of the profile and then allow the next login to reload it from the network.

The network roaming profile shouldn't have been recreated if it is downloading properly to other machines.... the problem was something on the main machine preventing a valid roaming profile from loading.

[SpookyEddy]

I find the best solution is to..

a) Redirect everything possible out of the users profile, for example Internet Favorites etc.

b) Add a default profile to the SYSVOL share on a domain controller (assuming Win2k) with all your core settings applied.

That way I can just delete a users profile if it get broken (which happens fairly often) without causing them much grief. To be honest fixing individual issues with peoples profiles really isn't worth the effort for most IT departments. I certainly don't do it as I wouldn't get anything else done

Regards

ed