George,
There are several other things to consider based on your environment. You
may have an Exchange mailbox left over. You may have a home directory or
user profile left on a file server somewhere. Did they store any files on
your file server that you might want to archive and get rid of?
To find out you can scan through the file servers looking for files where
that user is an owner. I recommend you do this before you remove the user.
Have you granted permissions anywhere in a file system or within Active
Directory that would make this user a direct Trustee? For example, did you
give them direct permissions to a folder on a share somewhere instead of
adding them to a group and then giving the group permissions? If you've
granted that user some permissions, and you delete the user, then you can
create orphaned permissions assignments. I've seen networks that when you
look at the permissions on a folder in a file system you see dozens of
orphaned SIDS in the Access Control List. This is undesirable for more than
one reason.
If you don't know where those permissions assignments may be then you might
need a tool to search for all files and folders controlled by the user. If
you've already deleted the user then you might want a tool that will search
your file system for orphaned SID assignments and clean them up.
There are scripts and tools available to help with this, DSRAZOR for Windows
is one of them. If you want to find out how DSRAZOR can help you locate and
fix these problems then you can take a look at
www.visualclick.com/?source=FSperms011508