Search This Blog
Tuesday, April 21, 2020
Thursday, April 9, 2020
Once more about Skype EWS
http://www.uclabs.blog/2013/01/lync-and-exchange-web-services-ews-and.html
if you have SIP and SMTP (primary) different, then you need to make sure that autodiscover works ok. You can redirect _autodiscover._tcp_smtp.domain to autodiscover.another.smpt.domain 443 if the later is defined and works ok. Then you do not need to worry about UC SAN SSL.
With autodiscover.smpt.domain SFB client will try to connect directly, with SRV you can redirect to another domain.
if you have SIP and SMTP (primary) different, then you need to make sure that autodiscover works ok. You can redirect _autodiscover._tcp_smtp.domain to autodiscover.another.smpt.domain 443 if the later is defined and works ok. Then you do not need to worry about UC SAN SSL.
With autodiscover.smpt.domain SFB client will try to connect directly, with SRV you can redirect to another domain.
Tuesday, April 7, 2020
Audiocodes ACA and KEMP CTP
Audiocodes Certified Associate and KEMP Certified Technical Professional in the pocket!
Wednesday, March 18, 2020
Exchange 2016 CU15 tips
run updatecas.ps1 script to fix OWA and ECP
also check out this
https://social.technet.microsoft.com/Forums/windowsserver/en-US/5259018c-aec7-4490-a500-e1af54798f14/exchange-2013-ecp-error-line-43?forum=exchangesvrgeneral
also check out this
https://social.technet.microsoft.com/Forums/windowsserver/en-US/5259018c-aec7-4490-a500-e1af54798f14/exchange-2013-ecp-error-line-43?forum=exchangesvrgeneral
- Application Settings >> BinSearchFolders
- 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
- Then reset IIS to check this issue.
how to put server in maintenance mode:
https://practical365.com/exchange-server/installing-cumulative-updates-on-exchange-server-2016/
https://www.enowsoftware.com/solutions-engine/exchange-2019-cu4-and-exchange-2016-cu15-explained
# 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
https://www.enowsoftware.com/solutions-engine/exchange-2019-cu4-and-exchange-2016-cu15-explained
# 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:
https://dotnet.microsoft.com/download/dotnet-framework/net48
https://support.microsoft.com/en-us/help/2570538/installing-updates-for-the-microsoft-net-framework-4-can-take-longer-t
https://www.catalog.update.microsoft.com/Search.aspx?q=4486153
Otherwise start Windows installer service is not running as well as go via link below:
https://dotnet.microsoft.com/download/dotnet-framework/net48
https://support.microsoft.com/en-us/help/2570538/installing-updates-for-the-microsoft-net-framework-4-can-take-longer-t
https://www.catalog.update.microsoft.com/Search.aspx?q=4486153
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:
https://practical365.com/exchange-server/no-need-create-connectors-internal-exchange-server-mail-flow/
We see that this server is not cleaning shadow often enough - look for code XQDISCARD
in the hub smtp logs on other servers:
https://docs.microsoft.com/en-us/exchange/mail-flow/transport-high-availability/shadow-redundancy?view=exchserver-2019
https://practical365.com/exchange-server/no-need-create-connectors-internal-exchange-server-mail-flow/
We see that this server is not cleaning shadow often enough - look for code XQDISCARD
in the hub smtp logs on other servers:
https://docs.microsoft.com/en-us/exchange/mail-flow/transport-high-availability/shadow-redundancy?view=exchserver-2019
Tuesday, January 21, 2020
Subscribe to:
Comments (Atom)