Renaming account leaves traces

  • Thread starter Thread starter Gis Bun
  • Start date Start date
G

Gis Bun

Hi. On a Server 2003 R2 SP2 domain, a user [I'll call him John] left the
company but a new user [I'll call him Bob] joined. Since Bob would be doing
the same functions as John and because a PC that John used had a special
configuration, the account was renamed from John to Bob in the ADUC.

While everything shows up as Bob there are still certain things that will
show John's name on that specifically configured PC. An example would be
John's name for My Documents [in one view it will say John's Documents] and
the local path will be something like C:\Documents And Settings\John .

Is there anyway way of renaming anything with John's name in it - aside from
deleting the local profile - which would be a bad idea because of the
configuration?

Thanks
 
Gis Bun said:
Hi. On a Server 2003 R2 SP2 domain, a user [I'll call him John] left
the company but a new user [I'll call him Bob] joined. Since Bob
would be doing the same functions as John and because a PC that John
used had a special configuration, the account was renamed from John
to Bob in the ADUC.

While everything shows up as Bob there are still certain things that
will show John's name on that specifically configured PC. An example
would be John's name for My Documents [in one view it will say John's
Documents] and the local path will be something like C:\Documents And
Settings\John .

Is there anyway way of renaming anything with John's name in it -
aside from deleting the local profile - which would be a bad idea
because of the configuration?

Thanks

I don't recommend renaming, for precisely these reasons. You will either
need to leave it be, or delete the local profile and recreate it. You should
be using folder redirection anyway - the fact that there's a "special"
workstation shouldn't make a lick of difference.

Here's what I do when people leave:

1. Change the password ASAP
2. (Presuming you use Exchange) Remove the user from any DLs of which he/she
was member
3. (Presuming you use Exchange) Log into the user's mailbox using OWA to set
up a simple OOF -


Thanks for your message. Note that as of <date>,
User Name is no longer at Company X.
Please call our main office at (800) 555-1212
for further information. Thank you.


4. (Presuming you use Exchange) Grant Full Mailbox Rights to the user's
replacement, and show him/her how to open the mailbox as a secondary one in
Outlook. Then they can open/see see all items - to copy/move out what he/she
wishes and deal with new mail coming in. I do not grant
send as or send on behalf of rights - I have the user remove the sending
address from the from field if he/she is replying to a message in the other
inbox. But you could instead use Send on Behalf Of if you prefer. The new
user can send out a broadcast message to whomever he/she needs to.

5. Move the old user's My Documents to a subfolder of his/her replacement's
....since I use folder redidirection this is all done easily on the server.
\\server\users\olduser1\my documents is moved to \\server\users\newuser\my
documents\Old user's documents

6. (Presuming you use Exchange) After a period of time, remove the old
user's valid SMTP addresses (change to something nonsensical like
(e-mail address removed) in his/her ADUC properties,
so it doesn't receive any more Internet mail

7. (Presuming you use Exchange) After even more time, have the replacement
user remove the secondary mailbox in Outlook, once they've gotten what they
need moved out to their own.

8. (Presuming you use Exchange) Hide the old user's mailbox from the address
list (Exchange Advanced tab in ADUC) for a while before deleting it. I do
this for about 6 mos, usually, because invariably someone will come back and
want something they've already asked me to delete!

If you don't use Exchange, move the PST file somewhere safe on the hard
drive, log in as the new user, set up an Outlook profile, move the PST file
back to wherever you wish on the hard drive, & set it up as the delivery
location for your new mail profile. I don't like PST files - I don't really
support them, as I work with Exchange, but this may apply to you
 
Lanwench said:
Gis Bun said:
Hi. On a Server 2003 R2 SP2 domain, a user [I'll call him John] left
the company but a new user [I'll call him Bob] joined. Since Bob
would be doing the same functions as John and because a PC that John
used had a special configuration, the account was renamed from John
to Bob in the ADUC.

While everything shows up as Bob there are still certain things that
will show John's name on that specifically configured PC. An example
would be John's name for My Documents [in one view it will say John's
Documents] and the local path will be something like C:\Documents And
Settings\John .

Is there anyway way of renaming anything with John's name in it -
aside from deleting the local profile - which would be a bad idea
because of the configuration?

Thanks

I don't recommend renaming, for precisely these reasons. You will either
need to leave it be, or delete the local profile and recreate it. You should
be using folder redirection anyway - the fact that there's a "special"
workstation shouldn't make a lick of difference.

Here's what I do when people leave:

1. Change the password ASAP
2. (Presuming you use Exchange) Remove the user from any DLs of which he/she
was member
:
We don't use Exchange - snipped.
:
If you don't use Exchange, move the PST file somewhere safe on the hard
drive, log in as the new user, set up an Outlook profile, move the PST file
back to wherever you wish on the hard drive, & set it up as the delivery
location for your new mail profile. I don't like PST files - I don't really
support them, as I work with Exchange, but this may apply to you

But I guess outside of deleting the account from the PC, there is no way of
removing the traces then....

Obviously if someone left the company, the password is change....

Gis
 
Gis Bun said:
Lanwench said:
Gis Bun said:
Hi. On a Server 2003 R2 SP2 domain, a user [I'll call him John] left
the company but a new user [I'll call him Bob] joined. Since Bob
would be doing the same functions as John and because a PC that John
used had a special configuration, the account was renamed from John
to Bob in the ADUC.

While everything shows up as Bob there are still certain things that
will show John's name on that specifically configured PC. An example
would be John's name for My Documents [in one view it will say
John's Documents] and the local path will be something like
C:\Documents And Settings\John .

Is there anyway way of renaming anything with John's name in it -
aside from deleting the local profile - which would be a bad idea
because of the configuration?

Thanks

I don't recommend renaming, for precisely these reasons. You will
either need to leave it be, or delete the local profile and recreate
it. You should be using folder redirection anyway - the fact that
there's a "special" workstation shouldn't make a lick of difference.

Here's what I do when people leave:

1. Change the password ASAP
2. (Presuming you use Exchange) Remove the user from any DLs of
which he/she was member
We don't use Exchange - snipped.
If you don't use Exchange, move the PST file somewhere safe on the
hard drive, log in as the new user, set up an Outlook profile, move
the PST file back to wherever you wish on the hard drive, & set it
up as the delivery location for your new mail profile. I don't like
PST files - I don't really support them, as I work with Exchange,
but this may apply to you

But I guess outside of deleting the account from the PC, there is no
way of removing the traces then....

There's no account on the PC. There's a *profile* on the PC. And unless
you're using roaming profiles, you can't delete this without significant
pain.
Obviously if someone left the company, the password is change....

Gis

Just create new users when you get new staff. It's a lot easier.
 
Back
Top