Somone please help me before I go MAD! I am currently working in a very mixed environment, doing some Novell and IP migration work. They have 3xWin2K/Citrix (NO Active Directory) servers, a number of NT4 servers (acting as Domain Controllers, File Servers, print servers etc.) and some Novell 3.12 and 4 File servers. The site uses NT roaming profiles, and on the whole things work well, apart from the Domain Administrator account. When I log in to a NT system using Administrator, everything seems OK, but when I LOG OFF up to 50 NTUSER.POL.TMP files can be created itterativly - i.e. NTUSER.POL.TMP , NTUSER.POL.TMP.TMP, NTUSER.POL.TMP.TMP.TMP etc. I can confirm that no one else is logging off using this account at the same time. Anyway, the next time you log in, it can't load the profile. This is sending me round the twist, and I can find no reference to this kind of problem anywhere on technet or other forums..... Anyone have any idea what is going on here? Regards, Paul Fletcher

I've encountered the same problem. I'm still trying to fix it. Only way that profiles stay active is by giving Domain Admin rights. Please let me know if you could get any help.

So far the only way to stop this problem is removing roaming profile on the administrator account. I'm still working on the same problem but so far this had helped to not create tmp files.

I have seen the problem too. It is reported by Microsoft at the following location http://support.microsoft.com/default.aspx?scid=kb;EN-US;q271518 It is caused by swapping between Windows 2000 and NT 4 workstations. Easiset solution is to delete them in the Logon script on Windows 2000. Alan C

I hate these tmp-extensions. It is really driving you mad. I have the problems now for some months and nobody could help me till now. Sometimes you begin to hate microsoft!

I´ve encountered the same problem, and the only way to resolve it is, make yourself the owner of the local- and serverbased Profile-folder. Than you have to rename the Serverfolder to .old (not to .bak) than you can delete the local Profil-folder and the user must create new settings. Attention!! the involved User should not be logged on to any Computer. You now can delete the Local Profile remote, using your commandline : delprof /c:\\ /q I hope this solves your Problem ( for a while ;) ) Delprof is included in the Server Resouce-kit

Apply new userenv.dll file dated 12/07/2000. Read Microsoft article Q271518