none
Exchange 2016, Maintenance Mode

    Question

  • hello all,

    I see that the script StartDAGServerMaintenance Mode only stop the HighAvailibitity. Is this right to shutdown the Server.

    and what does this mean: Is this because we have only 2 Servers?

            MX1:
            Database 'User' does not have enough copies configured to meet the validation criteria.
            ') (Database='DB1', Reason='There were maintenance prerequisite check failures for database 'DB1' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1. Expected Redundancy Count: 2. Detailed error(s):


            MX1:
            Database 'DB1' does not have enough copies configured to meet the validation criteria.
            ') (Database='DB2', Reason='There were maintenance prerequisite check failures for database 'DB2' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1. Expected Redundancy Count: 2. Detailed error(s):

    [PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Get-ServerComponentState mx1 | ft component, state -autosize

    Component                     State
    ---------                     -----
    ServerWideOffline            Active
    HubTransport                 Active
    FrontendTransport            Active
    Monitoring                   Active
    RecoveryActionsEnabled       Active
    AutoDiscoverProxy            Active
    ActiveSyncProxy              Active
    EcpProxy                     Active
    EwsProxy                     Active
    ImapProxy                    Active
    OabProxy                     Active
    OwaProxy                     Active
    PopProxy                     Active
    PushNotificationsProxy       Active
    RpsProxy                     Active
    RwsProxy                     Active
    RpcProxy                     Active
    UMCallRouter                 Active
    XropProxy                    Active
    HttpProxyAvailabilityGroup   Active
    ForwardSyncDaemon          Inactive
    ProvisioningRps            Inactive
    MapiProxy                    Active
    EdgeTransport                Active
    HighAvailability           Inactive
    SharedCache                  Active
    MailboxDeliveryProxy         Active
    RoutingUpdates               Active
    RestProxy                    Active
    DefaultProxy                 Active


    Chris


    Thursday, July 14, 2016 5:32 PM

Answers

  • My understanding is that script is depreciated.

    Here's an article for Exchange 2013, I think it's still valid for Exchange 2016.

    http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-2013-maintenance-mode.html


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by jim-xuModerator Wednesday, July 27, 2016 10:40 AM
    • Marked as answer by -- Chris -- Wednesday, July 27, 2016 11:02 AM
    Thursday, July 14, 2016 5:56 PM
    Moderator
  • Hi Chris,

    Welcome to our forum.

    By this issue, please run the following command to find FWS, then check the connection between FWS and DAG members:

    Get-DatabaseAvailabilityGroup <DAG Name> | FL *witness*

    Then run the following command to check DAG network:

    Get-DatabaseAvailabilityGroupNetwork –Identity <DAG name>

    And test database replication for DAG members:

    Test-ReplicationHealth –Identity <Servername>

    In addition, please run AD replication manually, then to have a try.

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    • Marked as answer by -- Chris -- Wednesday, July 27, 2016 11:02 AM
    Friday, July 15, 2016 6:10 AM
    Moderator
  • Thanks for answer

    Ed Crowley write. Should we also stop

    HubTransport  and ServerWideOffline ???

    DatabaseCopyActivationDisabledAndMoveNow

    DatabaseCopyAutoActivationPolicy

    ---

    http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-2013-maintenance-mode.html

    As with the script, Maintenance Mode is used to tell Exchange that a particular server should not be available to service clients. In a mailbox server, an administrator will typically perform a switchover to another server (if the server to be put in maintenance mode is hosting active database copies) and then use the Set-MailboxServer and Set-ServerComponentState cmdlet to put it into maintenance mode, preventing the active copies from being activated and disabling the Transport services:

    Set-ServerComponentState <> -Component HubTransport -State Draining -Requester Maintenance

    Suspend-ClusterNode <>

    Set-MailboxServer <> -DatabaseCopyActivationDisabledAndMoveNow $True (this can be done manually by moving the active database copy(ies) to another server)

    Set-MailboxServer <> -DatabaseCopyAutoActivationPolicy Blocked

    Set-ServerComponentState <> -Component ServerWideOffline -State Inactive -Requester Maintenance

    This cmdlet also applies to Client Access Servers which, when placed into maintenance mode, stops the server from acknowledging load balancer heartbeats and disables all proxy services.

    Set-ServerComponentState <> -Component ServerWideOffline -State Inactive -Requester Maintenance


    Chris

    • Marked as answer by -- Chris -- Wednesday, July 27, 2016 11:02 AM
    Friday, July 15, 2016 6:51 AM

All replies

  • My understanding is that script is depreciated.

    Here's an article for Exchange 2013, I think it's still valid for Exchange 2016.

    http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-2013-maintenance-mode.html


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by jim-xuModerator Wednesday, July 27, 2016 10:40 AM
    • Marked as answer by -- Chris -- Wednesday, July 27, 2016 11:02 AM
    Thursday, July 14, 2016 5:56 PM
    Moderator
  • Hi Chris,

    Welcome to our forum.

    By this issue, please run the following command to find FWS, then check the connection between FWS and DAG members:

    Get-DatabaseAvailabilityGroup <DAG Name> | FL *witness*

    Then run the following command to check DAG network:

    Get-DatabaseAvailabilityGroupNetwork –Identity <DAG name>

    And test database replication for DAG members:

    Test-ReplicationHealth –Identity <Servername>

    In addition, please run AD replication manually, then to have a try.

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    • Marked as answer by -- Chris -- Wednesday, July 27, 2016 11:02 AM
    Friday, July 15, 2016 6:10 AM
    Moderator
  • Thanks for answer

    Ed Crowley write. Should we also stop

    HubTransport  and ServerWideOffline ???

    DatabaseCopyActivationDisabledAndMoveNow

    DatabaseCopyAutoActivationPolicy

    ---

    http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-2013-maintenance-mode.html

    As with the script, Maintenance Mode is used to tell Exchange that a particular server should not be available to service clients. In a mailbox server, an administrator will typically perform a switchover to another server (if the server to be put in maintenance mode is hosting active database copies) and then use the Set-MailboxServer and Set-ServerComponentState cmdlet to put it into maintenance mode, preventing the active copies from being activated and disabling the Transport services:

    Set-ServerComponentState <> -Component HubTransport -State Draining -Requester Maintenance

    Suspend-ClusterNode <>

    Set-MailboxServer <> -DatabaseCopyActivationDisabledAndMoveNow $True (this can be done manually by moving the active database copy(ies) to another server)

    Set-MailboxServer <> -DatabaseCopyAutoActivationPolicy Blocked

    Set-ServerComponentState <> -Component ServerWideOffline -State Inactive -Requester Maintenance

    This cmdlet also applies to Client Access Servers which, when placed into maintenance mode, stops the server from acknowledging load balancer heartbeats and disables all proxy services.

    Set-ServerComponentState <> -Component ServerWideOffline -State Inactive -Requester Maintenance


    Chris

    • Marked as answer by -- Chris -- Wednesday, July 27, 2016 11:02 AM
    Friday, July 15, 2016 6:51 AM
  • Hi chris,

    You should stop all server components, include HubTransport, ServerWideOffline and so on.

    If the issue persist, please refer to my steps to troubleshoot DAG.

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Saturday, July 16, 2016 7:36 AM
    Moderator
  • I'm confused... if the script is depreciated why has it been included in the Exchange 2016 $exscripts\StartDagServerMaintenenance.ps1
    Thursday, January 19, 2017 1:12 AM
  • None of us know the answer to that, sorry.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, January 19, 2017 5:29 AM
    Moderator
  • :) Thanks Ed

    Thursday, January 19, 2017 7:19 AM
  • You're welcome.  Happy to have helped.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, January 19, 2017 7:23 AM
    Moderator