Posted on

Difference Between Incremental and Differential Backups in Exchange Server

In Exchange Server, database backup is essential to prevent loss of data in case of disaster or unforeseen incidents, such as power outage, server failure, natural calamities, etc. At the same time, it is also important to decide on the data backup method as it is not practical to take a full data backup every time, considering the resources needed, the time to take backups daily, and the cost. So, you can choose between incremental and differential backup methods for taking frequent and regular database backups in Exchange Server.

In this article, we will discuss the differences between incremental and differential backup methods to help you decide which one to choose based on your needs. 

Posted on

How To Put Exchange Server in Maintenance Mode

Administrators must put the Exchange Server in maintenance mode while updating and making changes to the server to avoid data loss or other issues. If the changes or any security/cumulative updates are applied to the server without putting the server into maintenance mode, it can lead to database corruption or server failure.

In this article, we discuss the Exchange Maintenance Mode, its importance, and the steps to put the Exchange Server into maintenance mode. We also mention steps to disable maintenance mode once the server update or upgrade is completed.

Posted on

Exchange 2016 CU17 Shows Incorrect Name In Add/Remove Programs RRS feed

Hello Support,

Our Current Exchange Server 2016 (CU3) was running and last week upgraded to Latest CU17

Issue we have noticed below:

After installing Exchange 2016 CU17,we have notice that there is a cosmetic issue with how the update is listed in Add/Remove programs. In the screenshot below, note that Exchange 2016 Cumulative Update 3 is listed, but the version number is not the CU17 version number.
i.e:-

For reference the versions of the relevant CUs are shown below. Note that the above screenshot shows the CU17 version, but the text string shows CU3.

Exchange 2016 CU3 is 15.01.0544.027
Exchange 2016 CU17 is 15.01.2044.004
as the version information shown in Exchange Management Shell is correct. On the Exchange server, we can check the version information using something like:

Note that PowerShell shows the correct version information for CU17 15.01.2044.004

This issue is discussed in KB XXX Cumulative Update 3 appears in Programs and Features after you install Exchange Server 2016 Cumulative Update 17.

Also in our vulnerability tools show CU3 in Outdated version,

Please advise

Posted on

Active Sync warning

Hello,

It appears we started receiving errors similar to the one below since last week on our Exchange Server 2016. A staff member stated he was receiving emails normally on his PC but not on his phone.

This server has been set up since November 2019 without any issues. The default ports in the firewall were added as part of the Exchange installation.

I have seen information online that suggest doing a variety of things such as creating registry keys, change the page file to installed memory and a number of other steps indicated here: https://docs.microsoft.com/en-us/archive/blogs/david231/for-exchange-2010-and-2013-do-this-before-calling-microsoft

Are all of these steps really required to resolve the issue? The KB905013 does not appear available after doing an online search

I see https://social.technet.microsoft.com/wiki/contents/articles/35919.event-id-1040-on-exchange-servers.aspx about changing the heartbeat interval value in the web.config file but should this really be necessary if there hasnt been an issue before now? Is modifying this file recommended?

Log Name: Application
Source: MSExchange ActiveSync

Date: 9/22/2020 11:45:51 AM

Event ID: 1040

Task Category: Requests

Level: Warning

Keywords: Classic

User: N/A

Computer: Server.Domain.com

Description:

The average of the most recent heartbeat intervals [505] for request [Ping] used by clients is less than or equal to [540].

Make sure that your firewall configuration is set to work correctly with Exchange ActiveSync and direct push technology. Specifically, make sure that your firewall is configured so that requests to Exchange ActiveSync do not expire before they have the opportunity to be processed.

For more information about how to configure firewall settings when using Exchange ActiveSync, see Microsoft Knowledge Base article 905013, "Enterprise Firewall Configuration for Exchange ActiveSync Direct Push Technology" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=905013).

Event Xml: