Exchange - Revision history

Aleks at 14:40, 18 January 2024

2024-01-18T14:40:39Z

← Older revision		Revision as of 15:40, 18 January 2024
Line 4:		Line 4:

	https://piszczynski.com/ExchangePowershell		https://piszczynski.com/ExchangePowershell

			== Exchange Update ==
			[https://learn.microsoft.com/en-us/exchange/plan-and-deploy/install-cumulative-updates?view=exchserver-2019#what-do-you-need-to-know-before-you-begin Exchange CU update article]

	== Exchange issues ==		== Exchange issues ==

Aleks: /* Exchange issues */

2023-12-05T11:02:14Z

Exchange issues

← Older revision		Revision as of 12:02, 5 December 2023
Line 25:		Line 25:

	<source lang="powershell">Get-ClusterResource \| Start-ClusterResource</source>		<source lang="powershell">Get-ClusterResource \| Start-ClusterResource</source>

			=== Issue after update ===
			If there are issues after updates run the script to rebuild OWA and ECP:[https://learn.microsoft.com/en-us/exchange/troubleshoot/client-connectivity/owa-stops-working-after-update Link to MS Learn article]

	----		----
	Issues with mail queue:		Issues with mail queue:

Aleks: /* Exchange Migration - Hybrid */

2023-11-16T21:15:40Z

Exchange Migration - Hybrid

← Older revision		Revision as of 22:15, 16 November 2023
Line 125:		Line 125:

	Error when moving mailboxes and need to run mailbox as a different migration batch? Remove the mailbox from the batch:		Error when moving mailboxes and need to run mailbox as a different migration batch? Remove the mailbox from the batch:
	*Get-MoveRequest -Identity 'tony@contoso.com'		<syntaxhighlight lang="powershell" line>Get-MoveRequest -Identity 'tony@contoso.com'
	*Remove-MoveRequest -Identity 'tony@contoso.com'		Remove-MoveRequest -Identity 'tony@contoso.com'</syntaxhighlight>


	Migrate Exchange Database to new location(will dismount database and move files to new location):		Migrate Exchange Database to new location(will dismount database and move files to new location):
	*Move-databasepath -identity "Mailbox Database" -edbfilepath "I:\Mailbox Database\mailbox database.edb"		<syntaxhighlight lang="powershell">Move-databasepath -identity "Mailbox Database" -edbfilepath "I:\Mailbox Database\mailbox database.edb"</syntaxhighlight>

Aleks: /* Exchange search + Search Index */

2023-11-16T21:14:51Z

Exchange search + Search Index

← Older revision		Revision as of 22:14, 16 November 2023
Line 102:		Line 102:

	Test exchange search:		Test exchange search:
	*Test-ExchangeSearch -MailboxDatabase DB02		<syntaxhighlight lang="powershell">Test-ExchangeSearch -MailboxDatabase DB02</syntaxhighlight>

	----		----
	Rebuild the Content Index if required, if server is in a DAG try to reseed from other database. if not:		Rebuild the Content Index if required, if server is in a DAG try to reseed from other database. if not:
	Stop exchange services:		Stop exchange services:
	*Stop-Service MSExchangeFastSearch; Stop-Service HostControllerService		<syntaxhighlight lang="powershell">Stop-Service MSExchangeFastSearch; Stop-Service HostControllerService</syntaxhighlight>


	Delete the GUID-named folder that contains the content index files - this will be in the exchange databases folder and will be in a sub folder with a GUID for a name - you will need to delete the folder.		Delete the GUID-named folder that contains the content index files - this will be in the exchange databases folder and will be in a sub folder with a GUID for a name - you will need to delete the folder.

	You can find the correct folder name using a script that is provided by Microsoft in the exchange program files scripts folder - getsearchindexfordatabase.ps1 eg:		You can find the correct folder name using a script that is provided by Microsoft in the exchange program files scripts folder - getsearchindexfordatabase.ps1 eg:
	*.\getsearchindexfordatabase.ps1 mailbox		<syntaxhighlight lang="powershell".\getsearchindexfordatabase.ps1 mailbox></syntaxhighlight>


	Start the exchange services to rebuild the index:		Start the exchange services to rebuild the index:
	*Start-Service MSExchangeFastSearch; Start-Service HostControllerService		<syntaxhighlight lang="powershell">Start-Service MSExchangeFastSearch; Start-Service HostControllerService</syntaxhighlight>


	Doing the "Get-MailboxDatabaseCopyStatus -Server <exchangeserver> \| ft -auto" command again will show you the status of the indexing		Doing the "Get-MailboxDatabaseCopyStatus -Server <exchangeserver> \| ft -auto" command again will show you the status of the indexing

Aleks: /* Exchange Connectors */

2023-11-16T21:13:15Z

Exchange Connectors

← Older revision		Revision as of 22:13, 16 November 2023
Line 66:		Line 66:
	== Exchange Connectors ==		== Exchange Connectors ==

	If throttling is ~~occuring~~ on a specific connector we can increase the allowed connections:		If throttling is occurring on a specific connector we can increase the allowed connections:

	To check the current limit (20 by default), run the following cmdlet and look for MaxInboundConnectionPerSource:		To check the current limit (20 by default), run the following cmdlet and look for MaxInboundConnectionPerSource:<syntaxhighlight lang="powershell">
	Get-ReceiveConnector \| Select MaxInbound*		Get-ReceiveConnector \| Select MaxInbound
			</syntaxhighlight>To increase the limit, you have to use the Exchange Management Shell:<syntaxhighlight lang="powershell">
	To increase the limit, you have to use the Exchange Management Shell:		Set-ReceiveConnector -MaxInboundConnectionPerSource 500 -MaxInboundConnectionPercentagePerSource 100
	*Set-ReceiveConnector -MaxInboundConnectionPerSource 500 -MaxInboundConnectionPercentagePerSource 100		</syntaxhighlight>Send and receive connectors can be either frontend or hub transport.

	Send and receive connectors can be either frontend or hub transport.

	----		----
Line 81:		Line 79:
	For exchange 2016 relay connector will need to be frontend transport type connector		For exchange 2016 relay connector will need to be frontend transport type connector

	To allow for annomous relays you will need to add ad permissions to the relay connector:		To allow for annomous relays you will need to add ad permissions to the relay connector:<syntaxhighlight lang="powershell">
	*Get-ReceiveConnector "EXSERVER\Anon Relay EXSERVER" \| Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Recipient		Get-ReceiveConnector "EXSERVER\Anon Relay EXSERVER" \| Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Recipient
			</syntaxhighlight>

	===Exchange Connector Certificate===		===Exchange Connector Certificate===
	When updating exchange certificate you may need to apply the new cert to the send connectors (Usually outbound to O365)		When updating exchange certificate you may need to apply the new cert to the send connectors (Usually outbound to O365)

	Get the exchange certificate and apply it to the connector:		Get the exchange certificate and apply it to the connector:<syntaxhighlight lang="powershell" line="1">
	<~~pre~~>
	$cert = Get-ExchangeCertificate -Thumbprint <new cert thumbprint>		$cert = Get-ExchangeCertificate -Thumbprint <new cert thumbprint>
	$certname = "<i>$($cert.Issuer)<s>$($cert.Subject)"		$certname = "<i>$($cert.Issuer)<s>$($cert.Subject)"
	Set-SendConnector -Identity <send connector identity> -TLSCertificateName $certname		Set-SendConnector -Identity <send connector identity> -TLSCertificateName $certname
	</~~pre~~>		</syntaxhighlight>

	== Exchange search + Search Index ==		== Exchange search + Search Index ==

	If search is not running in OWA or in exchange mailboxes check the search index on databases:		If search is not running in OWA or in exchange mailboxes check the search index on databases:<syntaxhighlight lang="powershell" line="1">
	*Get-MailboxDatabaseCopyStatus -Server <exchangeserver> \| ft -auto		Get-MailboxDatabaseCopyStatus -Server <exchangeserver> \| ft -auto
	**Get-MailboxDatabaseCopyStatus -Server <exchangeserver> \| Where {$_.ContentIndexState -ne "Healthy"} \| Select name,ContentIndexState,ContentIndexErrorMessage		Get-MailboxDatabaseCopyStatus -Server <exchangeserver> \| Where {$_.ContentIndexState -ne "Healthy"} \| Select name,ContentIndexState,ContentIndexErrorMessage
			</syntaxhighlight>
	----		----
	Check exchange search services		Check exchange search services

Aleks: /* Exchange Configuration */

2023-11-16T21:09:14Z

Exchange Configuration

← Older revision		Revision as of 22:09, 16 November 2023
Line 62:		Line 62:

	example of external connection setup command:		example of external connection setup command:
	<source lang="powershell">>Set-ImapSettings -ExternalConnectionSettings "mail.contoso.com:993:SSL","mail.contoso.com:143:TLS" -X509CertificateName mail.contoso.com<?source>		<source lang="powershell">Set-ImapSettings -ExternalConnectionSettings "mail.contoso.com:993:SSL","mail.contoso.com:143:TLS" -X509CertificateName mail.contoso.com</source>

	== Exchange Connectors ==		== Exchange Connectors ==

Aleks: /* Exchange Configuration */

2023-11-16T21:08:45Z

Exchange Configuration

← Older revision		Revision as of 22:08, 16 November 2023
Line 62:		Line 62:

	example of external connection setup command:		example of external connection setup command:
	*Set-ImapSettings -ExternalConnectionSettings "mail.contoso.com:993:SSL","mail.contoso.com:143:TLS" -X509CertificateName mail.contoso.com		<source lang="powershell">>Set-ImapSettings -ExternalConnectionSettings "mail.contoso.com:993:SSL","mail.contoso.com:143:TLS" -X509CertificateName mail.contoso.com<?source>


	== Exchange Connectors ==		== Exchange Connectors ==

Aleks: /* Exchange issues */

2023-11-16T21:07:50Z

Exchange issues

← Older revision		Revision as of 22:07, 16 November 2023
Line 8:		Line 8:
	Check the Database availability groups cmdlet - use to find out if exchange server is the Primary or Secondary		Check the Database availability groups cmdlet - use to find out if exchange server is the Primary or Secondary

	*Get-DatabaseAvailabilityGroup		<source lang="powershell">Get-DatabaseAvailabilityGroup</source>

	You can get all the details you need by using the following command:		You can get all the details you need by using the following command:

	*Get-DatabaseAvailabilityGroup \| fl		<source lang="powershell">Get-DatabaseAvailabilityGroup \| fl</source>

	*Get-DatabaseAvailabilityGroup -status		<source lang="powershell">Get-DatabaseAvailabilityGroup -status</source>

	Sometimes the witness will fail, you can check the status of the witness by using the cluster resource cmdlet:		Sometimes the witness will fail, you can check the status of the witness by using the cluster resource cmdlet:

	*ipmo failoverclusters		<source lang="powershell">ipmo failoverclusters</source>

	*Get-ClusterResource		<source lang="powershell">Get-ClusterResource</source>

	This will tell you where the witness stores the file. If the DAG finds the resource unrelibale it might mark it as failed - you can restart this by using start-cluster resource:		This will tell you where the witness stores the file. If the DAG finds the resource unrelibale it might mark it as failed - you can restart this by using start-cluster resource:

	*Get-ClusterResource \| Start-ClusterResource		<source lang="powershell">Get-ClusterResource \| Start-ClusterResource</source>
	----		----
	Issues with mail queue:		Issues with mail queue:
	*use Exchange toolbox to open queue viewer		<source lang="powershell">use Exchange toolbox to open queue viewer</source>

	This will let you know if there are issues with incoming or outgoing emails.		This will let you know if there are issues with incoming or outgoing emails.
	----		----
	Get info on server setup:		Get info on server setup:
	*Get-TransportConfig		<source lang="powershell">Get-TransportConfig</source>
	*Get-TransportServer -Identity <servername> \| fl		<source lang="powershell">Get-TransportServer -Identity <servername> \| fl</source>
	----		----
	Show Database copy status between the exchange servers in a DAG:		Show Database copy status between the exchange servers in a DAG:
	Get-MailboxDatabaseCopyStatus \| sort name \| ft -autosize		<source lang="powershell">Get-MailboxDatabaseCopyStatus <source lang="powershell"> \| sort name \| ft -autosize</source>
	----		----
	Get Server that may be experiencing backpressure		Get Server that may be experiencing backpressure
	*Get-MailboxServer \| foreach {Get-EventLog -ComputerName $_.Name -Source MSExchangeTransport -LogName Application -After (Get-Date).AddDays(-1) \| where {$_.EventID -eq "15004"}}		<source lang="powershell">Get-MailboxServer \| foreach {Get-EventLog -ComputerName $_.Name -Source MSExchangeTransport -LogName Application -After (Get-Date).AddDays(-1) \| where {$_.EventID -eq "15004"}}</source>
	----		----
	Check for failed messages:		Check for failed messages:
	*Get-MessageTrackingLog -Start "9/27/2021 13:00:00" -ResultSize unlimited \| ? {$_.EventID -eq "Fail"}		<source lang="powershell">Get-MessageTrackingLog -Start "9/27/2021 13:00:00" -ResultSize unlimited \| ? {$_.EventID -eq "Fail"}</source>

	== Exchange Log Drive filling ==		== Exchange Log Drive filling ==

Aleks: 23 revisions imported

2023-11-15T20:32:01Z

23 revisions imported

← Older revision	Revision as of 21:32, 15 November 2023
(No difference)

piszczynski>Aleks at 09:27, 9 November 2023

2023-11-09T09:27:49Z

← Older revision		Revision as of 10:27, 9 November 2023
Line 126:		Line 126:
	*Get-MoveRequest -Identity 'tony@contoso.com'		*Get-MoveRequest -Identity 'tony@contoso.com'
	*Remove-MoveRequest -Identity 'tony@contoso.com'		*Remove-MoveRequest -Identity 'tony@contoso.com'

			Migrate Exchange Database to new location(will dismount database and move files to new location):
			*Move-databasepath -identity "Mailbox Database" -edbfilepath "I:\Mailbox Database\mailbox database.edb"