Table of contents
Here we will be setting up three servers (instances) all using a Template, this will cause problems later as the servers will be recognized as the same. Since they are all templates they have all the same SID number that needs to be changed. This can be achieved by looking under problems (see title problems) these and other error that you may encounter will be under the same heading, these are not in any particular order. One just added them as one encountered them.
Setting up STMP mailserver Setting up on windows server 2016, Since we are not starting from the start and assuming that you read “logging in and setting up of instances” we will continue from there:
First click on the windows icon and go to the server manager icon this will bring up
Click add roles and features, this will bring up this menu.
Notice the name will be changed for simplistic and more informative computer name.
Keeping it as Role-based or feature-based installation
Checking the IP address from the lab environment making sure that they match, if you have more than one server appearing.
Selecting nothing (in server roles) leaving everything as is press [Next]
Notice also that Include management tools (if applicable) is checked this will automatically add IIS (webserver) and management console.
Leaving all as is. this as seen above in Kuva 6 and in kuva 7 that they are automatically marked when choosing STMP server
Press [Install] this takes a couple of minutes
After reboot I renamed the server from SomeLongNameThatWasThere to MailServer1.
Here instead of DC2 (MailServer1)
Join the server to the network too.
When using remote server it may revert back to the name of the server itself (see below) don’t let this alarm you. but if errors do happen remove the MAILSERVER1\ part of the username and try with just Administrator.
Now that both DC1 and DC2 are connected to the mailserver1,
After reboot we go to Server manager > local server
There we press the Play button >
from the [SMTP virtual Server we right click and press options
Make sure that the enable logging Is marked in.
Next tab over to the Access tab making sure that the Anonymous access is ticked under the Authentication tab [Ok]
The reason why its 127.0.0.1 is that the server itself can only relay messages and prevents the SMTP server from being an open relay to send unsolicited emails thus being blacklisted.
Leaving as is.
Make sure that Anonymous access is clicked
Under the advanced tab
Everything is in working order.
Press [Ok] and [Ok] to exit.
Setting up to be automatic, so when you bootup the server it will boot up too
Now that we got our server up and running its time to download Exchange 2016 from the Microsoft (or other sight) one will notice that one doesn’t have the privileges to download.
This could also be filed under problems as With IE downloading is something one has to add, its not standard, But left it here as this must be changed to download and isn’t as such an error or problem that you must overcome.
This is because it is disabled by default one must change the settings.
Go to internet explorer -> tools on the right corner.
Select Custom level, scroll down about halfway to enable downloads
Try again to download, works
One will also notice that it will not be a nice neat file in downloads or where ever you save it unless you create a folder for the download.
At the time of writing one was using server2016 and the CU update 09
Open the folder and open or execute exchange server this just runs and disappears. then we ran setup further on down the list.
Then it will ask for to connect to the internet to download updates as required. If updates are needed or the download is out of date then Microsoft will download the updates. Then an introduction and welcome text to the exchange server. all the time pressing [next]
License agreement accepting and pressing [next]
Using recommended settings, and letting exchange check online for solutions [Use recommended settings]
On the next section Server Role Selection, As you select Mailbox everything else gets blanked out. make sure to tick the install automatic updates,
After this Exchange organization appears with a random name ‘First Organization’ I suggest leaving as is.
Then Malware Protection Settings, This can be disabled in the future but better leaving it as default. [No]
Sometimes the case is that Updates need to be installed before anything is done, If needed one must install and reboot the system Or errors will be logged,
You may get this error. (also shown in Problems Readiness check errors,) this may be a result of directly logging into the server itself and not through DC1. So we are going to try it again via DC1.
We are going to be logging into DC1 as the head of the forest and not as a lone server ie WindowMail/Administrator See DC1 controller of all servers under DC1 and DC2 setup.doc
Now that all is setup log into DC1 ->server manager -> All servers right click on Mailserver1 Remote desktop connection. via DC1.
That brings you onto a login screen. into Mailserver1 and repeat the steps from Check for updates.
https://www.microsoft.com this will download CU 9 update for windows server 2016.
To save time and paper, there are 15 steps in this process. All takes time each steps takes about 10-20 minutes. Where at the end you should have Congratulations you set up Exchange 2016 server (After installation the server did complain of low memory. we can solve this in Problems -> memory Low
For the first time. After REBOOTING the server. Logging in through DC1 (but I’m sure that going directly to mailserver is the same)
Xen servertools are automatically installed into the server (least this was the result when one tried to install, One got the Fix replace option instead of install, which proved that one had it already. But working on the school It is pre-installed. simply click on the paperclip and scroll down to the xen-pv-drv.iso and [ok] This is the first in the list so not to difficult to find. Then go to your Mailserver Under [computer] Devices and drives.
Wait to finish loading, This is to ensure that it is installed and working correctly. Choosing repair, enforces the user in the knowledge that it is installed correctly. Giving the confidence that if errors do arise, this is not the cause.
Go to Server manager -> local server. in Properties for server Here it’s the same for DC1 DC2 and MailServer1
Click on not activated Put in the Code given to you by your lecturer.
That’s it done. Congratulations you now have a working Smtp server.
Now that we have installed and booted up our SMTP server it’s time to start to get email working, this is done through the newly installed Exchange server 2016 (CU9)
Open this, the first thing I got was a Security problem, Click continue to this site (not recommended)
That will open the Exchange Administrative Center, (from now on it will be called the EAC for short).
One has to start off with Administrator, I tried to put in one of my users But it didn’t like it. Next as you go through this for the first time you will notice that you are going back and forth. Following a manual http:// docs.microsoft.com.
Using User mailbox is for standalone mailserver according to (doc.microsoft.com accessed 14 nov). and the other easier linked mailbox as we have a domain controller with people already as users.
Fill in the usual information the ones with an Asterix * is mandatory but all the rest isn’t.
Navigate to mail flow, As one see, this is still in the setup stage, we are skipping around to make sure that we don’t forget anything, Going from top to bottom does make sense, but reading instructions, they have requisites to be done before hand, thus the jumping.
From mail flow, send connectors, (seen above in fig. 2) Click add + this starts the wizard. Give the connection a meaning name eg, Outbound_traffic (no spaces) select the third option, internet. [Next]
Click add + again, Add the server that was created at the start of this project. [Next]
This brings you onto authentication leaving this blank for now. [Next]
After this, this will bring you back to (fig.2)
where you then Click add + again, automatically bringing up
Press [add] then next and [Finish] resulting in having (fig2) filled out.
As one finishes Mail flow, Recipients, (see below) the two major parts in the whole email disregarding security (at this moment) As we just want to get the mailserver up and running. then we can go back and get all the security in place. Since this is a standalone server in a virtual network, we are confident that no risk will come to it.
Just fill in the language and time zone and finish.
Now that we have one of the mail severs created, one must connect to the outside world, in this project we are connecting to another domain. For the sake of clarity we will call them A and B before starting one should explain that we will be doing this twice from A to B and then from B to A. In this case we are logging in as 10.208.0.8 or mail3server.
Go to Start and Exchange Server 2016 -> Exchange Administrative Center. Here this will bring you to a explorer page in which you will have to login.
Click on the continue to this website ( not recommended) and login with administrator name and password.
Since all of the servers were templates, these are all the same and thus cannot be connected to each other unless different, changing the SID code in the pc will create the uniqueness between each of the servers. allowing them to be connected.
When starting Administrator exists by default, adding extra clients to access the mail, At the moment adding extra clients will just allow us to send mails between all the clients in the @secondmserver domain.
We are starting with
Don’t forget to have the tick mark in the generalize box (notice one doesn’t have it, and had to repeat the process)
Here we see, no domains connected in or out of the domain A (secondMServer) pressing the add sign and adding the name of the server that you are working from,
User tried to leave blank, to see the outcome, as seen adding a server is mandatory.
Again clicking on the plus sign
Adding the IP address of the mailserver in this case 10.208.0.8
..Will result in this
Kuva 70 says 10.208.0.8
All the time pressing [next]
Nothing to change here on this screen. leaving the smart host authentication as [none]
Choosing SMTP (Simple Mail Transfer Protocol) the name of the Server fully qualified name, always domain.com leaving cost as 1 (default)
Giving us this,
Giving us this, the domain that you are working from. So no typing necessary. clicking [Finish]
Resulting in this
Now this is done one must add a receiving domain
Next, we go back to the Exchange Admin center, Virtual directories and Servers. choosing owa in the screen to edit
Bring one to the server that you wish to connect to, in this case its Mailserver.com
Once this is done, all that is required is a reboot from the IIS server. At the time all servers had updates to be performed thus all servers were rebooted.
This is the halfway point as one must do it all again on the other side from B to A
The setting up of this email with the wizard was/is self-explanatory one doesn’t really need text to follow, but with windows there are always complications, the biggest problem was with internet explorer and allowing the email page to appear. getting information for that was a Lecturer question as so no real documentation for that. But having an idea on how “it” was. on retrospect. Seemingly not too hard to complete. but the question is how to improve the process. as adding too much information just drowns the user but putting in too little leaves the user searching for more information. Thus, creating manuals to record the processes taken whilst setting up the server(s)
To overcome this, I must change the SID of my server
Go to windows Powershell
Using whoami /all
Save the data in XXXXX.txt in my case its SIDmailserver.txt saving the data to compare to later result.
Open the windows start and in run
Don’t forget to click the Generalize button or the SID will not change
This is where it will reboot, one WILL have to login via the Lab to finish off the installation THEN one can log in remotely
Compare SID codes to see if it worked At this stage you will not be able to login via remote so all will be done via the lab
And a final Customise settings.
putting in Administrator Password and end Reboot
User Name SID
User Name SID
And continue where you left off.
To get rid of these errors at the start and (below not shown, kuva 52) one needs to restart the process in DC1 under server manager – other servers – mailserver1. This will get rid of the first set of problem
To get rid of these problems we need to download the links provided
Error A (Managed API 4.0) is a matter of downloading and installing.
This will download and one will see the prompts on the screen. Just follow the instruction on the screen and everything should work.
Error B) ServerGuiMgmtInfraNotInstalled isn’t implemented in windows server 2016 yet. But has been patched or fixed in the Cumulative Update 9 has solved those problems.
According to the website https://docs.microsoft.com this isn’t implemented yet in 2016 but make sure that everything is up to date and there are no other problems
https://www.microsoft.com download and save the .iso and open as is. Then run like the normal exchange 2016 server.
Remember to reboot after to prevent errors from taking place.
also always choose a reason for rebooting.
Shown here is CU8 and not 9 as supposed to be.
go to https://www.microsoft.com/en-us/download/details . This should get rid of the problem
This will take some time about 30 mins.
Changing the instance in the Lab environment. from there you need to change.
Before starting you must shutdown your server (1) before continuing, by choosing the first icon in the list then (2) Here you change the instance on the first attempt it only show s small, medium and large,
but if you choose again it will show custom.
This then takes awhile to reboot the server. This then will sort out your memory issues.
Go to the windows start tab under find type cmd. this will get you to the dos command prompt. From there you type slmgr /skms 172.28.111.67. This information was shared from the lecturer.
Then slmgr /ato see (Kuva 71)
Type exit to exit from the program.
https://www.microsoft.com/en-us/download/details.aspx?id=56718 CU 9 for windows server 2016
https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-160/jj556583(v=exchg.160) ServerGuiMgmtInfraNotInstalled error
were all from the server that one installed. kindly donated from Windows.