Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to find a way to disable the Out of Office functionality inside Outlook 2010 when run against Exchange 2003 (SP2).

I've loaded the 2010 ADMX files onto my DC and imported them into a new template, nothing obvious sticks out in browsing the policy, searching the ADMX file directly, or Google.

In Outlook 2003, I believe I can disable the Control ID (or some call control ID?) and for Outlook 2003 that ID is 5621 (I believe - that's from memory, not relevant to this post, but it's something like that) but for Outlook 2010 I can't seem to locate the ID.

I have downloaded a large compilation of Excel spreadsheets which detail A TON of features, buttons, toggles, etc. for Outlook & Office, and they seem to list everything EXCEPT OOF functions.

My OVERALL goal here is to standardize OOF language per internal policy, and it is a policy which needs to be strictly enforced. The language however needs to contain dynamic information, such as who would receive forwarded mail and what the expected return date is. This prevents using things such as ADSI and just blasting everything with the same property and waiting for them to hit "On/Off".

I do have a web page created which I intend to publish as part of our internal policy to direct users to a simple SharePoint page which will host a VERY simple for containing Return Date, simple GAL lookup and previews the expected output.

However, that is predicated on the fact I can disable OOF functions within Outlook, thus forcing them to use my SharePoint page. (I'll disable it in OWA after I tackle this hurdle, I realize the loophole already :) )

Upgrading to newer Exchange isn't feasible at this point, where I believe this problem is easily solved with PS scripts.

I have confirmed that disabling other control/command IDs using a test GPO does reach my client almost immediately and is able to control exactly what I intend, so my complication isn't with the application of the GPO, it is rather identifying what ID I am to disable.

Just to re-clarify - I am looking to disable the button under "File", shown under Account Information & Account Settings that is called "Automatic Replies". I think if I can find a way to disable this button, that'll get me a long way toward my goal.

I'm not concerned with the 3% of the user population that'll figure out a way around, I'm looking for a rather simple disable/discouragement from using native functionality which doesn't fit our need, currently, and redirect them to something which does.

Sorry for the long post - trying to fit as much detail in as possible to minimize back and forth.

Anyone have any ideas how I could accomplish what I'm after?

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.