Link to home
Start Free TrialLog in
Avatar of Pkafkas
Pkafkas

asked on

How to disable a user's ability from making changes on their Outlook account settings?

We have Exchange 2010 Sp3 and we are using Outlook 2010 as well.

Apparently a user, needed to access his email while not at his desk so he just added his email to another user's outlook account settings.  This user opened outlook from another workstation (logged on from a Citrix session) and added his email to the Outlook Email Account settings .

The problem was that he did not remove the account after he was done and then the normal user was getting login prompts to enter the correct password for the 'evil' user whenever she opened her outlook program.  I removed the extra user, form the Outlook Email Account settings and then exited out of Outlook and then re-opened outlook.  Problem solved.  or is it.

My question  is how can I prevent any user from making any changes to their outlook settings?  Or can I disable and enable the feature for the times that we need to make changes?  We do have all of the Exchange email accounts on our Exchange server.

Bye the way, I suggested to the user to open a web browser and to browse out to the company Outlook Web Access page for future situations.
ASKER CERTIFIED SOLUTION
Avatar of Brian B
Brian B
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Just educate this user, how to use outlook or OWA from other machine. I am not clear, how configuring outlook for this user is affecting other user. As each user need to login with their own ID and separate profile will be created. I advise you to focus on machine or permission this user have currently, as there is nothing much you can do, if user has permission to login to any system.
Avatar of Pkafkas
Pkafkas

ASKER

So there is no easy way to temporarily disable each user the rights to make changes to their Outlook Program settings (on a Citrix Server).  Because there may be time when one will need to share a 'calendar' or 'task list'.  In these case it may be easier to make those adjustments on the client side.  My point is that some times it will be necessary for the user to make some changes.

But, if I disable those rights then they will not be able to make said changes.  If there is no easy way to temporarily disable.enable those permissions then ... the user education route may be the best road to take.  Does everyone agree?
Bang on. Teach them how to do it right. More important, encourage users to ask IT if they don't know how to do something rather than "guess" and the associated risks with that.