"Lanwench [MVP - Exchange]" wrote:

> Jeremy Church wrote:
> > "Lanwench [MVP - Exchange]"
> > <lanwe***@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> > message news:%23dfIHurJFHA.3076@tk2msftngp13.phx.gbl...
> >> Jeremy Church wrote:
> >>> I have a client that has somewhat of a high turnover rate on a
> >>> couple different positions in their company.
> >>> Security and documents need to be transfered to that user so instead
> >>> of adding a new user, I change the current user name and their
> >>> security settings and documents are appropriately applied or moved.
> >>>
> >>> When that new user logs in, they see the old user's name in Outlook.
> >>> They also use Blackberry on a few computers.  The Desktop software
> >>> sees the mailbox as being the name of the original user, not the
> >>> current one.  It's almost like the mailbox name never changes, even
> >>> though the user name does. Everything works, except for the username
> >>> on different items within programs that access the Exchange mailbox.
> >>>
> >>> I have looked high and low in Active Directory and the Exchange
> >>> System Manager for this problem. I have search Microsoft support
> >>> for this problem, but did not find anything.  I have not opened a
> >>> case with MS because there is really nothing "broken" and I didn't
> >>> want to burn a case on something like that.  I have attempted
> >>> deleting the user's profile thinking it might be something specific
> >>> to that profile, but even with a clean profile, the problem is
> >>> still there.  This leads me to believe it is something on the
> >>> Exchange server or in Active Directory.
> >>>
> >>> Has anyone else seen or even noticed this?  Does anyone know how to
> >>> solve this or of know of a KB article that has a solution?
> >>>
> >>> Thanks
> >>
> >> To back up a bit - I would nearly always go for 'create a new
> >> user/mailbox' over renaming an old one....it's easy to grant the new
> >> user full mailbox access to the old mailbox, and rights to the old
> >> user's home directory/etc . You have to change a lot of other stuff
> >> every time if you rename, as you're seeing. I'm way too lazy to
> >> bother with all of it myself and find that my method works pretty
> >> well. The new user can copy out what they need from the file server
> >> & Exchange mailbox as needed - they can add the secondary mailbox to
> >> their OL profile to make it easy to see.
> >>
> >> As to Outlook - either create a new mail profile or modify it so you
> >> change the username in there - properties of the Exchange Server
> >> service. Re BB desktop software, don't know, but I suspect you need
> >> to create a new profile in there if it doesn't come over after
> >> changing Outlook.
> >>
> >> Again, I do not bother. My $.02.
> >>
> >>
> >
> > Thanks for your reply.
>
> No prob - inline.
> >
> > I didn't figure creating a new user would be the lazy way.  If I do
> > that, then I have to copy all the files so the new user can see them,
>
> Copy from where to where? You can grant the user permissions to the old
> user's homedir & they can access it using a UNC path.
>
> > do the mailbox thing like you said,
>
> >  there would be a lot of
> > permissions that would have to be set on the server for that user
> > too.
>
> Not a big deal if you use groups instead of assigning permissions to
> individual user accounts - I always use groups.
>
> > Also, most of these users know how to set their own permissions
> > on files, but never give permissions to the administrator.
>
> This is a company policy issue.
>
> >  This can
> > cause quite a bit of confusion if I take ownership of the files etc.
> > I can go on and on about all the little things that have to change to
> > add a new user.  Anyway, if that's the way it has to be, so be it.  I
> > just want to know why I can't change a user name and have the old
> > user name completely go away.
>
> You can. I just find it's a lot more tedious.
> >
> > Here is another point of view.  The "correct" way, at least how I see
> > it, is a user is more of a position in the company and not an actual
> > person.
>
> That's not the way I see things, but that's just my preference. The *data*
> is company property & the appropriate parties need permissions to whatever
> there is.
>
> > If the person moves on and another takes their place, the
> > permissions given to that user should carry over to the new user
> > seemlessly.  This includes the person's old email, old files, access
> > to certain files and folders on the server(s) etc.  I would prefer to
> > change names when a position is changed from one user to another.
> >
> > Is there a way to make the old user completely go away?
>
> Yes, mostly. You have to change:
>
> Username
> Display name
> Alias
> E-mail address(es)
> Home directory folder name & share if you use individual shares
> Windows profile (or leave the old name & just accept that it has to stick
> around)
> Outlook profile (either recreate or modify to change the mailbox it points
> to)
>
> As I said, I think it's a *lot* easier to just create a new user, add them
> to the appropriate groups (for both file system access and any public
> folder/mailbox permissions) and grant them full mailbox permissions to the
> ex-user's mailbox (if this is actually needed - if so, it's often just for a
> limited time), and also to the ex-user's  home directory - or, copy the old
> homedir data to theirs & make sure they have permissions. This takes me just
> a couple of minutes.
>
> It's entirely your choice how you do this.
>
> >
> > Thanks again
>
> If he gives permission to the user's mailbox doesn't he have to keep the old account active so they can access the mailbox? We disabled accounts of users that are no longer with the company but still need access to that mailbox and even giving them full control of the mailbox they can't access it as long as the primary account is disabled. Is there a way around that?
>