0% loss
It comes down to forwarding the DNS of Vimexx to Ziggo's own IP address.
Then you only have 1 cable from the router directly to the server.

The following is the normal existing situation and then everything has internet.
But then you can't have that forged DNS at your disposal

   
If you go from the router with only 1 cable to that server, you can have that DNS at your disposal.
But only when the server is configured and the clients have internet, you can reconnect the rest from that hub.
As long as that doesn't work, the rest has no internet.

Below you see 2 servers because it is not recommended to configure Exchange and the company server on 1 machine
To configure the Mailflow, the Wan needs to be connected directly to
the Exchange server, because the domain is forwarded to the DNS of that server.
Instead of having that server directly behind it, we just need a hub.

Disadvantage is that if the Exchange does not have a network, the rest will not work either.
Upgrading to Ziggo Business Pro provides 5 IP addresses so you can connect multiple servers to it.
This means that you also need to create a number of subdomains and then you need to activate LD-LDS (Lightweight Directory) as a role.
But that has probably already happened because that's why you get a remark with the yellow flag that ADAM is not enumerated and that refers to the fact that you have not yet created subdomains.

Below is a possible solution, but it means that the server has to work.
With restart or if the server is still being configured the rest has no internet.

Netwerk agemeen = Network general

You can also only use the Exchange with Server 2016 (on 1 machine) with a hub/switch.

If you forward Ziggo's IP address to the server, you can use the network as it is now.

But you can also ask what the costs are of having that mailflow taken care of by another company.
To maintain a mail server the company needs a specialist and that costs time and money.
Outsourcing this can even lead to considerable savings.

 Because we have another problem.
With the upgrade of the version Windows1903 to 1909 it went completely wrong.
We set the data to D so that on C there is only the OS with the programs.
OneDrive has also been moved to D.
And then it went wrong.
The testers had already warned about it, but those warnings were ignored.

With the upgrade of 1909 OneDrive on C was expected.
However, it was on a different partition. (D)
Omdt that was not on C was assumed that nothing was stored there in OneDrive.
And that was synchronized with the cloud and nothing was synchronized with nothing.

Everything gone in the cloud.
Then connect to OneDrive on that other partition and synchronize it with nothing.
It took another 14 days before the rollout was stopped.
And the response of M$:
We will try to retrieve your data, but cannot guarantee it.
Fine, and then you can go to the employer with that info.
Data loss is job loss. That is unforgivable.

Back to the mailboxes of Outlook.
The story above is to understand the following and to be able to estimate the risks.
Until Office 2013 the mail was stored in an Outlook.pst file.
Had you moved the documents to the D then that file was also on the D under Documents/Outlook
So you could put an (older) image back without any risk of losing mail.
Since Office 2016 they use a link with Office 365 and your mail is also stored in the cloud.
Then you no longer have a PST file but an OST file which is set to C and cannot be moved.
You can create a folder on D and then you can create a symbolic link from that OST on C to that folder on D.

That is 1 direction of traffic.

Then you get a copy of C on D but if there is still old mail in that D folder, it will not go to C.
And then the big question.
If you put an image of 6 months old back on C the cloud will put that 6 months mail back in that folder, or is it assumed that you deleted 6 months mail yourself and synchronized it with the cloud, so that mail is lost?

What do you think?
It is plausible that the old mail on D is not synchronized with C and also not with the cloud.

With this information you then have enough arguments to convince the employer that this mail handling (mail flow) is better handled by an external party.
First of all, it costs a lot of time (and money) to install and maintain a mail server.

Time that prevents you from doing other things.
And the employer has to hire a specialist and that also costs more.
Then there is the hacking risk that confidential mail will end up on the street.
It is therefore advisable to request a quote from an external party for the handling of that mail flow.

Server 2016 can be installed on a server without forwarding.

For the preparations for Exchange and Exchange itself.
Then you need to connect that hard disk to the server behind with that forged DNS and you could configure the mail flow.
With the disadvantage that the rest has no internet.
We are not going to do that.
Continue with the rest of the installation and see how far you get.

Forwarding the Ziggo Wan to the DNS of the Exchange server.

Now you are going to configure the mail account.
Actually it should be via mailflow, but we use 2 mailboxes from the domain kompserver.nl which is registered at Vimexx.
This to prevent that the rest has no internet during the configuration of server 2016.
Click on Outlook
Then you can activate an account right away.

On client Bert follow the instructions below and on Ernie it will become ernie@kompserver.nl.



Click m More settings and then on advaced.



SMTP should also be web.0105.zxcs.nl with port 587, but with that router from Ziggo it doesn't work.
Then but port 25 unencrypted.

Send a mail to yourself to check
If it doesn't work, see if Work Offline is dark.
In Outlook 2016 and higher there is an annoying bug so the program goes offline and then you won't receive any mail and you can't send anything.
Sometimes you wonder if that M$ is still someone who can think logically, or if they only employ idiots.

Click on send/recieve all folders, and then on that work ofline icon.

Storage data on server

Work Folders in Windows Server 2016

That goes largely well, but goes wrong with entering the email address.


HTTPS is indicated, but there is no SSL certificate available.
Then you can create an administrative SSL certificate.



No Video? Click here

Client  access to own shared folder on server

Follow the instructions for the Client  access to own shared folder on server and also keep that Z as a shared folder partition.
 
The maximum size for individual files is 10 GB by default.
There is no storage limit per user, although administrators can use File Server Resource Manager's quota functionality to implement quotas.
You can also decide to directly reserve 100 gb for each client.