Exchange Server – Bunthoeurn

Enable Online Archive

//// connect to exchange online powershell ///// Install exchange online management More Details:https://docs.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-protection-powershell?view=exchange-ps Connect to exchange online powershell with MFA Set-ExecutionPolicy RemoteSignedInstall-Module -Name ExchangeOnlineManagementImport-Module ExchangeOnlineManagementGet-Module ExchangeOnlineManagementUpdate-Module -Name ExchangeOnlineManagement Connect-ExchangeOnline -UserPrincipalName sin@domain.com -DelegatedOrganization youdomain.onmicrosoft.com /////// get retentionpolicy info /////// Get-Mailbox | FL RetentionPolicy /// get retentionholdeenable /////////// make it is set to false ////Get-Mailbox “sin@domain.com” |

How to Fix Exchange Mailbox Quarantine Issue?

Exchange Server can connect with numerous client systems at the same time and fulfil their requirement sufficiently. Each client creates a thread with the Server to ask for the resources constantly. When some threads freeze and start to consume the CPU power more than necessary for a longer period, then Exchange puts such mailboxes to

How to check if my environment is hybrid?

Problem: You need to check if the environment you are working with is cloud-only, purely on-premises or if it implements any hybrid configuration. Solution: The hybrid environment in most cases refers to an Office 365 tenant perpetually connected with an on-premises infrastructure. Active Directory synchronization The primary feature that is being implemented in hybrid environments

get AD Version

# Exchange Schema Version $sc = (Get-ADRootDSE).SchemaNamingContext $ob = “CN=ms-Exch-Schema-Version-Pt,” + $sc Write-Output “RangeUpper: $((Get-ADObject $ob -pr rangeUpper).rangeUpper)” # Exchange Object Version (domain) $dc = (Get-ADRootDSE).DefaultNamingContext $ob = “CN=Microsoft Exchange System Objects,” + $dc Write-Output “ObjectVersion (Default): $((Get-ADObject $ob -pr objectVersion).objectVersion)” # Exchange Object Version (forest) $cc = (Get-ADRootDSE).ConfigurationNamingContext $fl = “(objectClass=msExchOrganizationContainer)” Write-Output “ObjectVersion (Configuration):

Exchange Schema version

Exchange version rangeUpper objectVersion(Default) objectVersion(Configuration) Exchange 2016 CU23 15334 13243 16223 Exchange 2016 CU22 15334 13242 16222 Exchange 2016 CU21 15334 13241 16221 Exchange 2016 CU20 15333 13240 16220 Exchange 2016 CU19 15333 13239 16219 Exchange 2016 CU18 15332 13238 16218 Exchange 2016 CU17 15332 13237 16217 Exchange 2016 CU16 15332 13237 16217 Exchange 2016

Outlook client prompt to enter password

Outlook client prompt to enter password, we need to double check on the virtual directory configuration for all server. Exchange Server Virtual Directories setting. It is a root cause that Outlook prompt for password when Outlook client has been switched from one Exchange Server to another Exchange Server by Load Balancer .[PS] C:\Windows\system32>Get-ClientAccessServer -Identity EX01

Exchange schema versions (up to date list)

The following tables are a comprehensive collection of the Microsoft Exchange Server schema versions. The tables show the Exchange objects in Active Directory that get updated each time you install a new version of Exchange. Compare the object versions you see with the values in the tables below to verify that the version of Exchange

Server Error in ‘/owa’ Application

ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1 Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the

Exchange ECP and OWA error after update cu/su 22

After upgrading Exchange server to the latest patch or CU, we found the error page after login to ECP or OWA. OWA will be showing a login screen that says ‘bad request’ after entering credentials and ECP will be showing “Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0 …” Resolution 1. Open IIS Manager. Expand Sites

Access to the path is denied, Upgrade Exchange CU20 to CU22

For this case have to rename/remove web.config.bak. it’s located in c:\inetpub\wwwroot\web.config.bak system.UnauthorizeAccessException: Access to the path is denied.

Bunthoeurn

Category: Exchange Server