Your Administrator has made a change and requires you to restart Outlook


I've been getting asked this question a lot lately, and so I thought I would consolidate the conditions that I have been able to identify that will cause the unwelcomed prompt in Outlook:



This may not be a comprehensive list under which conditions may cause this prompt, rather its an aggregation of the scenarios that I have been able to identify.

 

I'd imagine that some of the readers that arrive at this post are here as a result of having Outlook issues. As a gratuitous plug, in case you haven't tried it or are not aware of it, please take a look at the OFFCAT- the Office Configuration and Analysis Tool (available HERE ) that allows you to scan an Office/Outlook installation and review known and potential issues. 

 

You can expect to see the prompt under the following conditions:

 

If the RPCClientAccessServer property changes.

-Cross AD site mailbox moves may trigger this, as each AD site may have a different RPC Client Access Array.

-If you are not using a CAS Array, if the RPC endpoint changes after a mailbox move. An example of this is when a user on the source database has a specific CAS as its RPC endpoint, and the destination of the mailbox move has a different CAS specified as its RPC endpoint.

 

If the Public Folder hierarchy server changes after a mailbox move. (if get-mailboxdatabase|fl identity, publicfolderdatabase are different between source and target databases )

 

If The user does has additional mailboxes open in Outlook where the additional mailboxes do not meet the above conditions when being moved. So, if you have Joe User's mailbox open in Outlook, and they are moved from Server A/DB A, which has an RPC endpoint of CASARRAYA, and they are moved to Server B/DB B, with an RPC endpoint of CASARRAYB, then you will receive the prompt after Joe User's mailbox is moved. There are additional considerations in this scenario, regarding ALLOWCROSSSITERPCACCESS, which are detailed in the EHLO blog post "RPC Client Access Cross-Site Connectivity Changes"

 

If you are on Outlook 2013, and your mailbox is moved from Exchange 2010 to Exchange 2013, and you do not have http://support.microsoft.com/kb/2934750 installed. Key takeaway: keep Outlook up to date, as there are other, earlier hotfixes that also addressed the prompt issue.

 

Certain conditions when you have a CAS/Mailbox server that is also hosting your public folder database:

You can expect to see these prompts when a public folder exists on a multirole server that is part of the Exchange Server 2010 CAS array. This issue occurs because the VIP of the CAS array is being returned to the client instead of the hosting server.

 

The problem arises when an Outlook client connects to the CAS array and initially, if outlook connects to the CAS array member that contains the PF role, then Outlook converges all connections and displays both the Public and Private logons as one single connection (the CAS array name). When the Clients IP address changes, and it Re-connects, if it gets connected to a CAS array member that does not have the PF server, then we get an ECwrong server Response from Exchange, Outlook in its reconnect logic Cannot follow the Redirection Result that contains the correct PF server name, and displays the Error "The Administrator has made a change that requires you restart Outlook"

 

If you use the -DoNotPreserveMailboxSignature parameter with the New-MoveRequest cmdlet

 

Mitigations:

You have the option to completely suppress the dialog:

 

How to suppress the pop-up "The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook" in Outlook 2010

• Uncheck the option “Show Microsoft Exchange Messages” from the Outlook icon on taskbar, and test the behavior.

 

This setting is controlled by the registry value..

HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Display Types\Balloons

Name: Exchange

Type: DWORD

Value: 1 (on) / 0 (off)

 

 

Also see

RPC Client Access Cross-Site Connectivity Changes

http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx

Restart Outlook prompt post Exchange 2010 SP2 rollup 3+

http://blogs.technet.com/b/nawar/archive/2012/09/04/restart-outlook-prompt-post-exchange-2010-sp2-rollup-3.aspx

Obviating Outlook Client Restarts after Mailbox Moves

http://blogs.technet.com/b/exchange/archive/2011/01/24/obviating-outlook-client-restarts-after-mailbox-moves.aspx

 

(Updated to fix link to Offcat)

Comments (22)

  1. Vytas {MSFT} says:

    @Subversive: I think that is a good start, as the situation you describe, all parties, should be on the same platform (either all on prem, or all in O365).

  2. Vytas {MSFT} says:

    @HowardRichards – thanks, link fixed

  3. Vytas {MSFT} says:

    Perhaps, are your servers multirole?:
    Certain conditions when you have a CAS/Mailbox server that is also hosting your public folder database:

    You can expect to see these prompts when a public folder exists on a multirole server that is part of the Exchange Server 2010 CAS array. This issue occurs because the VIP of the CAS array is being returned to the client instead of the hosting server.

    The problem arises when an Outlook client connects to the CAS array and initially, if outlook connects to the CAS array member that contains the PF role, then Outlook converges all connections and displays both the Public and Private logons as one single connection
    (the CAS array name). When the Clients IP address changes, and it Re-connects, if it gets connected to a CAS array member that does not have the PF server, then we get an ECwrong server Response from Exchange, Outlook in its reconnect logic Cannot follow the
    Redirection Result that contains the correct PF server name, and displays the Error "The Administrator has made a change that requires you restart Outlook"

  4. Vytas {MSFT} says:

    @Alex
    There is no suggestion to suppress the prompts as a long term solution. It is simply presented so that you as an admin know that you can do so. I’m not going to take that decision for you. Given the list of conditions that can cause this issue, most of which
    require some investigation or troubleshooting to get to the root cause, some admins may find it useful and helpful that they can disable the prompts so that they conduct their troubleshooting steps.

  5. Vytas {MSFT} says:

    Fixed Offcat link to KB 2812744

  6. Me says:

    Thanks
    very helpful and comprehensive list

  7. Howard says:

    Your OFFCAT Link is broken

  8. Subversive says:

    We are seeing this recurring over and over on a user (they are quite frustrated). We have a hybrid exchange/Office 365 setup, and she has 3 mailboxes which she has permissions on added to her outlook. Her mailbox has not been migrated to the cloud, but
    the 3 mailboxes attached to her outlook profile have been. I'm assuming it's something to do with this. Do you think my assumption is right?

    Any ideas, or should I just suppress the popup with the registry key until she gets migrated in a few weeks?

  9. JensDK says:

    Learned something today. Thanks 🙂

  10. alex says:

    Sorry, but to suggest to suppress these pop-ups is not very professional. I understand that as a temporary solution to get it out of the users face, yes, but for a long term solution these things should always be tackled at the root cause.

  11. Duder says:

    OFFCAT link is down. Thanks for the post.

  12. jay c says:

    I see this message periodically on my own computer. We have a single site with 2 CAS & 2 Mailbox servers. It happened this morning, but no mailboxes or databases have been moved, and no configuration changes have been made. Do you have any thoughts on
    what might be the cause of the message?

  13. sandeep says:

    If we turn off the notifications will the users still be connected to Exchange via outlook or will outlook que all the emails in the outbox?

  14. jay c says:

    Thanks, Vytas. My CAS are also Hub Transport servers, but my Mailbox servers are single-role. In other words, no Client Access Server hosts any databases at all.

  15. Vasu Thadaka says:

    Thanks

  16. Sourav Saha says:

    Thanks brother …………… 🙂

  17. Greg Lambert says:

    Just wanted to mention that suppressing the balloon messages does not seem to stop this message from popping up. We're on Exchange 2013 with Office 2013

  18. alex says:

    This does not apply to Office 2013; first; in the registry the value does not exist under 14.0 but under 15.0; second after switching it off (was already set to off), the error still appears.

  19. HR Raihan says:

    Can I know before restarting what change happened ?

  20. Hi,

    I had this issue and what helped was this fix:

    The resolution in this case was to drill down to the properties of the Mailbox Database in ADSIEDIT & set the value of “msExchHomePublicMDB” to be blank. Afterwards, a restart of the Information Store Service resolved the issue.

    https://social.technet.microsoft.com/Forums/exchange/en-US/d22a6288-8a1f-4bdc-a8d5-bcfe68e5609d/false-prompt-in-outlook-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you?forum=exchange2010

  21. DeeTroit says:

    It appears that in 2016 CU7 the parameter -DoNotPreserveMailboxSignature is being overridden from False to True whenever you move a mailbox from a DB version earlier than CU7 to a CU7 version. This can happen with moves from 2013 to 2016 or even moves within 2016 CU6 to CU7. This of course also affects shared calendars and other folders that may be referenced in the mailbox that have been moved. This of course can cause many prompts per client over the migration period.

Skip to main content