|
not so my friend because @ the site that I work at, I have witnessed this with my own two eyes-- all the AD accounts logged into every machine on the AD domain have the naming convention residing @ c:\documents and settings\name............ in that fashion and this takes place when a user logs into a machine for the first time on any particular machine AND what I'm trying to convey to you is: every once in a while, XP decides to deviate from that naming convention and add an additional profile with the same naming fashion, only with the .DOMAIN extension stuck to the end of the profile name. And my question is NOT why the deviation (because I already know that that is probably because something caused ntuser.dat to became corrupt and XP rebuilt an additional profile on the fly so that there were no exact duplications), but rather what caused it. Thus far, my only three work arounds have been either delete both profiles and let XP rebuild a new fresh one,copying ntuser.dat, ntuser.ini and such into a new profile and renaming, or make the machine leave and rejoin the domain. I have like 6000 machines to manage, & this is turning into an administrative nightmare when XP usage of profile management decides to be different and then I run into problems with End-Users accesing Profile Favorites, reloading Java applets, unavailable e-mail, Microsoft Office templates unavailable.. etc. I would love to spend my time doing other administration.
|