Installation of Exchange with failed outlook connectivity

Question

Installation of Exchange with failed outlook connectivity

Bjarne Petersen 20

Dear community.

I've installed Exchange server on my lab on a Hyper-V machine.

At first all but a few services did not start. As my home lab is major slow, I take it that it is because of startup speed and dependicies.

After I leave the VM start and leave it for somewhile I need about six minutes to get the rdp protocol fully initiated and Server Manager ready.

I then start all exchange related services including:

MSComplianceAudit
HostcontrollerService
NettcpActivator

As far as I can tell all required services are running.

I am using the build-in domain administrator account to test connectivity with outlook and send a mail. Unfortunately until sofar no luck.

Can anybody help me? Must I manually create mailboxes on the server, perhaps?

Yours sincerely,

0 comments

3 answers

Your answer

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Hi @Bjarne Petersen

If Marcin Policht’s suggestion does not resolve the issue, please consider the following.

Installing Exchange Server does not automatically create a usable mailbox for the built-in domain administrator account. While the account exists in Active Directory, it cannot access Outlook unless an Exchange mailbox has been created or enabled for it.

To help narrow down the issue, could you please provide the following information?

In the Exchange Admin Center, under Recipients > Mailboxes, do you see the domain administrator account listed?
In the Exchange Management Shell, run the following command and let us know the results:
```
   Get-Mailbox
```
Does it return any mailboxes?
Are you able to sign in to Outlook on the Web (OWA) using the test account, or do you receive an error message?
Please verify that the default mailbox database is mounted by running:
```
   Get-MailboxDatabase | ft Name,Mounted
```
What is the output?

In addition, Exchange Server requires several post-installation configuration steps before Outlook clients can connect successfully. These include configuring client access services, Autodiscover, certificates, and mail flow. Until these tasks are completed, Outlook connectivity issues can occur even when the Exchange installation itself has completed successfully. For more information, please refer to Configure mail flow and client access on Exchange servers

Regarding the services you mentioned, HostControllerService and MSComplianceAudit can sometimes take longer to start, particularly in lab environments or on servers with limited resources. A delayed startup by itself does not necessarily indicate an issue.

Please know that while our initial response might not resolve the issue right away, your input is incredibly valuable. With a bit more detail, we’ll work together to find the best solution for you.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Bjarne Petersen 20 Reputation points

2026-07-28T23:02:23.9066667+00:00

Good day @Anonymous ,

1 In the Exchange Admin Center, under Recipients > Mailboxes, do you see the domain administrator account listed> Yes, the administrator account is listed.

2 In the Exchange Management Shell, run the following command and let us know the results >> The administrator mailbox is listed and the discoverysearchmailbox is listed.

3 Are you able to sign in to Outlook on the Web (OWA) using the test account, or do you receive an error message?>>> No, the exchange server has, for lab reasons, not a presence on the internet.

4 Please verify that the default mailbox database is mounted by running>>>> The mailbox database that is returned is:

Mailbox Database 0880952701

As I have read and understood your reply I am reading both your https://learn.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/configure-mail-flow-and-client-access and @Marcin Policht https://marklewis.blog/2020/11/06/adding-exchange-server-to-the-lab/provided links and at first glance these will occupy me for a while, still. While updating this request with the valuable input asked for.

I think I did all the above as far as I can tell.

I recreated a test profile in Control Panel > Mail

Networking connection took a bit more time then I would expect.
The settings for the administrator mail were pretty fast verified.
The connection to the mail server took maybe even longer but in the end was succesful.

Yet, I still can not send a mail to myself. (The administrator account sending a test mail to itself)

Yours sincerely,

Bjarne Petersen

Answer 3

You might be better off testing this in Azure (assuming you have an Azure subscription) by simply following https://learn.microsoft.com/en-us/exchange/plan-and-deploy/deploy-new-installations/create-azure-test-environments

Otherwise, adjust the steps provided in the walkthrough to match your own lab environment or refer to https://marklewis.blog/2020/11/06/adding-exchange-server-to-the-lab/

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin