Configure Automatic Replies for an user in Exchange 2010 – Using Exchange Control Panel (ECP)
In previous versions of Exchange, you would need to access the user’s mailbox to be able to do this. Without access to the mailbox, you can’t modify data in it.
Two ways for an exchange/domain administrator to access an user mailbox:
- Grant yourself full Access mailbox permission to the user’s mailbox.
- Change the user’s password and log in as the user.
The first option grants the administrator access to all of the data in the user’s mailbox.
The second option grants the administrator access to all of the data that the user account can access within your company and locks the user out of his own user account.
Configure auto-reply options using the ECP
In Exchange 2010 SP1, you can configure auto-reply options for your users without using either of the above options.
Login to ECP through owa as Administrator or member of that group. Click options (right side top) and select “See all options”, From this screen, where “Manage Myself”, click “Another User” -> select the user you want and double click on the user. This will open his mail option ECP, and click “Tell people you’re on vacation” -> and select Automatic Replies and fillout the information and click Save.
Configure auto-reply options using the Shell Command
This command schedules internal and external auto-replies
Example, if a user is going on leave from 11/11/2011 to 12/10/2011: (MM/DD/YYYY format)
Set-MailboxAutoReplyConfiguration firstname.lastname@example.org –AutoReplyState Scheduled –StartTime “11/11/2011” –EndTime “12/110/2011” –ExternalMessage “External OOF message here” –InternalMessage “Internal OOF message here”
For detailed syntax and parameter descriptions, see Set-MailboxAutoReplyConfiguration (Applies to Exchange Server 2010 SP1).
This command retrieves auto-reply settings for a mailbox.
This command disables auto-reply configured for a mailbox:
Set-MailboxAutoReplyConfiguration email@example.com –AutoReplyState Disabled –ExternalMessage $null –InternalMessage $null
No comments yet.