Change Windows 2000 AD user name

Environment: Windows 2000, SP4, active directory, Exchange 2000.
We have just hired our 6th executive assistant within the last 6 years.  I would like to come up with a solution which will address this change and all future changes.
Let's say our current user's name is Sally Smith and our new user's name is Mary Jones.
I am thinking of creating a user in AD named 'assistant'.  The user would log on to the domain with the name of 'assistant'.  

Our company would not want emails from this user being sent out as from 'assistant' but I do not want to have to go through the name change every year or so.  This user must be able to access all emails and documents that have been previously sent/received to the prior executive assistant.

So should I set up the user with the user name of 'assistant', assign email address of 'reception@ourcompany.com', assign the display name of the user's actual name?
jhinsonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

isaman07Commented:
Yes, that is logical thing to do;
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
naldiianCommented:
What do you mean by name change every year or so? You are not just creating a new account for the new user each time to get a new person? Any access the user account needs for things other than Excahnge would be handled by group memberships in the domain, and for the Exchange mailbox you could just add access to the new person as needed.

I would recommend the following:
1. Create a user account named Reception or something similar in the domain and then give them an Exchange mailbox. Nobody should use this account directly.
2. Create your assistant's account using their name as a normal user each time - once a year is not much to worry about. Add them to the necessary group(s) for access to the common resources they need.
3. Grant them access to the Reception mailbox, but also give them their own mailbox for things they may need to do specific to them. Always good for each person to have their own mailbox, as they may move to other duties at a later time and this will make the receptionist mail and fucntionality separate from the person.
4. Have both mailboxes opened in Outlook, but configure the user's mail client to normally send from the intended Reception name as you mentioned.

I prefer this idea to renaming an account and the like, as this allows the account to remain and be disabled if the person leaves. You never know if you may want to review what someone had access to or actions they have taken, and if those things change with the new person, you will have a difficult time telling when various permissions were granted or changed.

Each user should always have thier own account...


Andy
0
pHppCommented:
Yes. Any user should have their own account to be able to track backwards in time to see what they have been doing etc. There is a benefit of doing what you meantioned but still I think as above the best solution is own accounts for each user and creating a new user once a year isn't much if you create rights using groups in your filesystem instead of putting in the user in the ACL.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.