Database availability group server cannot be removed from database

I was decommissioning the old Exchange 2013 environment with Database Availability Group.

I got an error when removing the Exchange servers from the DAG: 

Error: “Database availability group server EXCHANGESERVER cannot be removed from database availability group DAG since it is currently set for datacenter activation mode and it requires at least two mailbox servers.”

I tried again in PowerShell

Remove-DatabaseAvailabilityGroupServer -Identity <DAGName> 

-MailboxServer <ExchangeServer>

Помилка при видаленні Exchange сервера з Database Availability Group

Виводив з експлуатації старе середовище Exchange 2013 з багатьма Database Availability Group.

Отримав повідомлення про помилку під час видалення Exchange серверів з DAG:

Error: “Database availability group server EXCHANGESERVER cannot be removed from database availability group DAG since it is currently set for datacenter activation mode and it requires at least two mailbox servers.”

Я спробував ще раз у PowerShell

[PS]Remove-DatabaseAvailabilityGroupServer -Identity <DAGName> 

-MailboxServer <ExchangeServer>

Multiple Security Updates Released for Exchange Server - March 2021

Microsoft released patches for multiple different on-premises Microsoft Exchange Server zero-day vulnerabilities The vulnerabilities exist in on-premises Exchange Servers 2010, 2013, 2016, and 2019.

More info:
HAFNIUM targeting Exchange Servers with 0-day exploits

SECURITY UPDATES EXCHANGE SERVER - DECEMBER 2020

On December 8, 2020 Microsoft released a number of security updates for Exchange server. Despite the fact that Exchange 2010 is out of support at all, an important security update for Exchange 2010 was released as well.

Exchange version	KB Article	Download
Exchange 2010 SP3 RU31	KB4593467	Download
Exchange 2013 CU23	KB4593466	Download
Exchange 2016 CU17	KB4593465	Download
Exchange 2016 CU18	KB4593465	Download
Exchange 2019 CU6	KB4593465	Download
Exchange 2019 CU7	KB4593465	Download

Link Exchange Online Mailbox with Exchange On-premise

One of my customer have a hybrid exchange environment.

For a new user needs to create AD account and Mailbox on Exchange on-premise.

After creating mailbox and if is needed (depends on Company Police), user mailbox moving to the Exchange Online (Office 365).

It is important to be sure that the right routing address is set, user listed in Address Book and all works fine.

In this case some mailboxes was created wrong.

That means, that there was a AD user on-premise and mailbox was created directly in the Exchange Online.

 

 

 

When on-premise user tried to send message to user whose mailbox was created in Exchange Online directly, he got message:

 

Exchange 2010 - End of Support Is Coming

 

On January 14, 2020, Exchange Server 2010 will reach end of support.

 

 

Additional Information:

https://blogs.technet.microsoft.com/exchange/2018/04/10/exchange-2010-end-of-support-is-coming/

 

 

Outlook Error: There is a problem with the proxy server's security certificate. Outlook is unable to connect to the proxy server (Error Code 80000000)

I had an interesting issue while working on one project. When customers working with Outlook, sometimes some Outlook clients received the following certificate error message:

 

There is a problem with the proxy server's security certificate.
Outlook is unable to connect to the proxy server (Error Code 80000000).

 

 

I want to share my solution on this issue.

Exchange 2010: Change Password with Outlook Web Access

Applies to: Exchange Server 2010

 

Enable change password feature in Outlook Web App:

 

Log on to the Client Access server.

Open Registry Editor

regedit

 

Find registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange OWA

 

Create the following DWORD value if it doesn't already exist: ChangeExpiredPasswordEnabled. The value type will be REG_DWORD

Set the value of ChangeExpiredPasswordEnabled to 1

Restart IIS

iisreset /noforce

 

Note:

You must make this change on each Client Access server that supports Outlook Web App 

 

Exchange: Hide Mailbox from Address List

In organization you might need to hide a mailbox from the GAL for some reason.

For this procedure you may use Exchange Admin Center or the Exchange Management Shell.

Hide mailbox using the Exchange Admin Center:

Select Recipients - Mailboxes

Click edit on the mailbox where you want to hide from the GAL.

 

On the properties page for the user, ensure you are on the General tab/page
Select option "Hide from address lists" then click Save button.

 

 

 

Hide mailbox using the Exchange Management Shell:

 

Set-Mailbox -Identity <UserName> -HiddenFromAddressListsEnabled $true

 

 

To show mailbox using the Exchange Management Shell:

 

Set-Mailbox -Identity <UserName> -HiddenFromAddressListsEnabled $false

 

 

 

 



How to view the version and build number of a Microsoft Exchange Server

Applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016

To view the version and build number of a Microsoft Exchange Server run the following command in the Exchange Management Shell

[PS] Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion, ServerRole

But what if you don't have easy access to EMS, or you want to check the version of the Exchange Server your mailbox is hosted?

Як подивитись версію та номер збірки Microsoft Exchange Server

Застосовується до: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016

Щоб переглянути версію та номер збірки Microsoft Exchange Server, виконайте таку команду в Exchange Management Shell

 

[PS] Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion, ServerRole

  

 

Get Exchange Install Path

If you don't know path where Exchange Server installed on the server, you may use environment variable called “ExchangeInstallPath”.

Exchange creates environment variable “ExchangeInstallPath” which holds the install path for Exchange on a given server.

This can be accessed via Powershell using:

 

[PS]$env:ExchangeInstallPath

This can be useful in scripts.
 

How to Publish Outlook Calendar as Internet Calendar

Enable Internet calendar publishing.

• Internet calendar publishing. Part 1.
• Internet calendar publishing. Part 2.

 

Pre-requisites

• You will need to have access to Outlook for Windows
• You must have direct access to the Calendar (mailbox) you want to publish

Publishing

 

1. Open Outlook

 

Internet calendar publishing. Part 2.

Enable Internet calendar publishing.

• Internet calendar publishing. Part 1.

Add the sharing policy "Internet Calendar Publishing" to a user mailbox
 

Exchange Admin Center

Mailboxes - Mailbox features - Sharing policy - Internet Calendar Publishing

 

Exchange Management Shell

[PS]Set-Mailbox -Identity <user name> -SharingPolicy "Internet Calendar Publishing"

Example:

[PS]Set-Mailbox Andriy.Zarevych -SharingPolicy "Internet Calendar Publishing"

To view user  sharing policy use:

[PS]Get-Mailbox <user name> | Format-List SharingPolicy

Example:

[PS]Get-Mailbox Andriy.Zarevych | Format-List SharingPolicy

 

 

Internet calendar publishing. Part 1.

Users in Microsoft Exchange Server organizations can share calendar availability (free/busy) information with users in non-Exchange organizations and other individuals with Internet access. Internet calendar publishing provides increased flexibility and increases the number of users who can share calendar availability information.

 

You can use sharing policies to control how users in your Exchange organization share calendar information with users outside your organization.

 

For enable internet calendar publishing need to do some steps.

 

Tips of the day #1706

Tip of the day #1706-1

Use Windows PowerShell to change the UPN suffix for all users
Change all company.local suffixes to company.com

Import-Module ActiveDirectory

Example 1.
$LocalUsers = Get-ADUser -Filter {UserPrincipalName -like '*company.local'} -Properties userPrincipalName -ResultSetSize $null

$LocalUsers | foreach {$newUpn = $_.UserPrincipalName.Replace("company.local","company.com"); $_ | Set-ADUser -UserPrincipalName $newUpn}

Rename and Move an Exchange Mailbox Database

To rename the default database running the following command:
[PS] C:/>Set-Mailbox "Mailbox Database 12453789" -Name "MailBoxDB-2"


Move the database files:
[PS] C:/> Move-DatabasePath -Name "MailBoxDB-2" -EdbFilePath "D:/MailBoxDB/MailBoxDB-2/MailBoxDB-2.edb" -LogFolderPath "E:/MailBoxDBLogs/MailBoxDB-2"

Exchange 2007 - end of life on April 11th

11 квітня завершується підтримка Exchange Server 2007.
Також завершується підтримка інших продуктів Office 2007.

Детальніше за посиланнями:

Exchange 2007 reaches end of life on April 11th. What’s your plan to move?

Exchange 2007 End of Life Roadmap

Setting Distribution Groups Default OU in Exchange 2010/2013/2016

When we creating a Mail Distribution Group in the Exchange Shell or Exchange Admin Center, we are given the option to choose which Organizational Unit (OU) in Active Directory (AD) we want the Distribution Group to be created.

Exchange 2013

Change a Universal Distribution Group to a Universal Security Group in Exchange 2010/2013

Let's convert Mail Distribution Group to Mail Enabled Security Group.

Оpen ADUC and take properties of the Group, then change the Group type from Distribution



to Security

Now in Exchange Admin Center we have a Mail Universal Security Group instead of a Mail Universal Distribution Group

 
 
 
 
 
 
 
 
Let’s use this group to set permissions. Start Outlook and add this group to set permissions to my Calendar folder.
 
Add this group to the Calendar folder and press ok.
 
If you see the Deny circle sign on the distribution group

 
 
You receive an error message in Outlook when you try to set permissions for a distribution group on a mailbox folder in Exchange Server