Search This Blog

Wednesday, March 18, 2020

Exchange 2016 CU15 tips

run updatecas.ps1 script to fix OWA and ECP
also check out this

  1. Application Settings >> BinSearchFolders
  2. Change the path with C:\Program Files\Microsoft\Exchange Server\V15\bin;C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents;C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin
  3. Then reset IIS to check this issue.

how to put server in maintenance mode:

# start maintenance on the computer

$Computer = $ENV:ComputerName
Set-ServerComponentState $Computer -Component HubTransport -State Draining -Requester Maintenance
Redirect-Message -Server $Computer -Target

# Prevent DAG member becoming PAM
Suspend-ClusterNode $Computer

# Move all Mailbox Databases and prevent hosting copies on current server
Set-MailboxServer $Computer -DatabaseCopyActivationDisabledAndMoveNow $True
Set-MailboxServer $Computer -DatabaseCopyAutoActivationPolicy Blocked

# Put the Exchange 2013 server in Maintenance Mode:
Set-ServerComponentState $Computer -Component ServerWideOffline -State Inactive -Requester Maintenance
# verify

Get-ServerComponentState $Computer | ft Component,State –Autosize

# stop maintenance on the computer

$Computer = $ENV:ComputerName
Set-ServerComponentState $Computer -Component ServerWideOffline -State Active -Requester Maintenance
Resume-ClusterNode $Computer
Set-MailboxServer $Computer -DatabaseCopyActivationDisabledAndMoveNow $False
Set-MailboxServer $Computer -DatabaseCopyAutoActivationPolicy Unrestricted
Set-ServerComponentState $Computer -Component HubTransport -State Active -Requester MaintenanceRestart-Service MSExchangeTransport
Restart-Service MSExchangeFrontEndTransport

Get-ServerComponentState $Computer | ft Component,State –Autosize

.net 4.8 is slow

First of all it is slow, yes, wait up to 30 minutes...

Otherwise start Windows installer service is not running as well as go via link below:

Thursday, March 5, 2020

Exchange internal relay must not include Exchange DAG servers

We see some issues with Shadow queue accumulating on one of the servers, it seems to be related to the fact that Exchange servers have been added to internal FrontEnd relay connector:

We see that this server is not cleaning shadow often enough - look for code XQDISCARD
in the hub smtp logs on other servers: