Very strange admin account rename issue

Ok, this is a weird one. I'm at an office where I did not make the master
image, and I had no problems ghosting it to 300+ machines. But now I'm
putting them all out at the desks, and logging in to finish the config when I
noticed this:

I log on locally the first time with the local admin account, call it ABCDE.
When I go to C:\documents and settings I notice I have an ABCDE folder, and
an Administrator folder.

Open gpedit and browse to the Local Security Options and "Rename
administrator account" is set to ABCDE as one would expect. This is always
how we do it. But normally when I rename the admin account, call it LMNOP,
the profile that it uses is still Administrator in Docs and Settings (If I
wanted the profile itself renamed to LMNOP I would have to manually rename
it).

So I ask, how in the heck do I have a profile for the built in local admin
account named ABCDE in docs and settings, AND and profile named Administrator
that doesn't ever get used anymore?

Thanks a bunch....I know it's a bit confusing what I just typed

First thing I'd make sure of is that the Administrator foder isn't being
used by some program or other which fails to use the proper method of
accessing userdata, but instead sets absolute-paths to profile contents. If a
program of this kind found its way into the default profile, this would
result in the previous profile-folder re-appearing when the user is renamed.

"WILLIAM" wrote:

> I log on locally the first time with the local admin account, call it ABCDE.
> When I go to C:\documents and settings I notice I have an ABCDE folder,
> and an Administrator folder.
>