none
Need to re-do Outlook profiles everytime Exchange Server is rebooted RRS feed

  • Question

  • Hello,

    I have an Exchange Server 2010 SP3 that had hardware failure a month ago. We were able to bring back from the backup and get it operational again. We have about 250 Outlook 2016 computers.

    Ever since we were able to restore the server, everytime we reboot, the Outlook profiles give out the following error:

    Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. Microsoft Exchange Information service in your profile is missing the required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service.

    Then I delete the current profile, create a new one, and the users are able to log in to Outlook.

    No issues on OWA or mobile.

    I have weeded out all of the Event Viewer errors, and corrected them. But nothing seems to fix this.

    Has anyone faced this before?


    Anser Leon

    Thursday, September 19, 2019 3:45 PM

Answers

  • Hi Anser Leon,

    Agree with Edward, something may be broken during restoring from Snapshots.

    According to official article Exchange 2013 virtualization, it mentions that it’s not recommended to use snapshot in Exchange.

    >>Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it's running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren't application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn't supported.

    Moreover, Exchange Server 2010 will reach end of support on October 13, 2020. The easiest way is to build a new server.

    You could check the steps in following article:

    Exchange Deployment Assistant

    How to Move Mailboxes in Exchange Server 2010

    fastest way to migrate exchange 2010 mailboxes to another exchange 2010 server in same domain [closed]

    (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)

    Regards

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 20, 2019 9:19 AM

All replies

  • Hi

    Was a snapshot of the server restored or did you do a recovery install and then just attach the .edb files?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, September 19, 2019 5:27 PM
    Owner
  • A snapshot of the server was restored using our backup software, ShadowProtect.  

    Anser Leon

    Thursday, September 19, 2019 5:31 PM
  • Snapshots are not supported by Microsoft unfortunately. You restoring data back to a point in time which causes problems.

    You might have to build a new server and move the mailboxes or build a new server on Exchange 2013/2016 and migrate off.


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, September 19, 2019 5:46 PM
    Owner
  • Hi Anser Leon,

    Agree with Edward, something may be broken during restoring from Snapshots.

    According to official article Exchange 2013 virtualization, it mentions that it’s not recommended to use snapshot in Exchange.

    >>Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it's running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren't application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn't supported.

    Moreover, Exchange Server 2010 will reach end of support on October 13, 2020. The easiest way is to build a new server.

    You could check the steps in following article:

    Exchange Deployment Assistant

    How to Move Mailboxes in Exchange Server 2010

    fastest way to migrate exchange 2010 mailboxes to another exchange 2010 server in same domain [closed]

    (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)

    Regards

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 20, 2019 9:19 AM
  • Thanks for marking my reply as answer. I’m pleased to know that the information is helpful to you.

     

    Here I will provide a brief summary of this post for your information.

     

    Issue Symptom:

    Restore Exchange from Snapshots. After that, every time we reboot, the Outlook profiles give out the following error:

    Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. Microsoft Exchange Information service in your profile is missing the required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service.

     

    (Possible) Cause:

    It’s not recommended to use snapshot in Exchange.

     

    Solution:

    Build a new server or upgrade Exchange 2010 to Exchange 2016/2019, Exchange Online

     

    Reference Links:

    Exchange Deployment Assistant

    How to Move Mailboxes in Exchange Server 2010

    fastest way to migrate exchange 2010 mailboxes to another exchange 2010 server in same domain [closed]

    Thursday, September 26, 2019 5:46 AM