Verify Exchange Server installations
After you install Exchange Server 2016 or Exchange Server 2019, we recommend that you verify the installation by running the Get-ExchangeServer cmdlet and by reviewing the Exchange Setup log. If the setup process fails or errors occur during installation, you can use the Setup log to find the source of the problem.
To verify that Exchange installed successfully, run the following commands in the Exchange Management Shell. To open the Exchange Management Shell, see Open the Exchange Management Shell.
This command returns a summary list of the names, Active Directory sites, Exchange server roles, Exchange editions, and Exchange versions of all Exchange servers in the organization.
This example returns additional details about the Exchange server named Mailbox01.
Get-ExchangeServer -Identity Mailbox01 | Format-List
For detailed syntax and parameter information, see Get-ExchangeServer.
Review the Windows Application log and the Exchange Setup log
Exchange Setup logs events in the Application log of the Windows Server. This log contains a history of each action that the system takes during Exchange setup and any errors that occurred (By default, the logging method is set to Verbose). You can use the Windows Event Viewer to find the messages related to Exchange setup.
The Exchange Setup log is available at <system drive>:\ExchangeSetupLogs\ExchangeSetup.log (<system drive> is the drive where Windows is installed). The Setup log tracks the progress of every task during the Exchange installation and configuration. The file contains information about the status of the prerequisite and system readiness checks before installation starts, the application installation progress, and the configuration changes that are made to the system. Check this log file to verify that Exchange was installed as expected.
We recommend that you start your review of the Windows Application log and/or the Exchange Setup log by searching for errors. If you find an error entry, read the associated text to determine the cause of the error.
Send feedback about: