G
Guest
A user has recently got married and changed name.
She logged in using her new surname, and this worked ok, with her apps
loading, but was not creating a new local profile, it was logging in with her
old profile. Any apps which required logins didn't work.
She had spoken to service desk, who said they needed to change the local
profile name to her new profile and that would solve it. I doubted it so
made a copy of the local profile just in case. The strange thing was the new
XP login was not creating a local profile yet was still logging in.
I renamed the local profile to her new ID, and then asked her to log in. It
logged her in and created another local profile called user.DBG and
everything worked fine.
How did it log in without creating a new profile originally?
Why after renaming the local profile would it then want to create another
profile?
She logged in using her new surname, and this worked ok, with her apps
loading, but was not creating a new local profile, it was logging in with her
old profile. Any apps which required logins didn't work.
She had spoken to service desk, who said they needed to change the local
profile name to her new profile and that would solve it. I doubted it so
made a copy of the local profile just in case. The strange thing was the new
XP login was not creating a local profile yet was still logging in.
I renamed the local profile to her new ID, and then asked her to log in. It
logged her in and created another local profile called user.DBG and
everything worked fine.
How did it log in without creating a new profile originally?
Why after renaming the local profile would it then want to create another
profile?