Author: Noel Alvarez

Microsoft Exchange Server 2016 – Mailbox Server Role Interactive Installation

June 15, 2018
EmailMicrosoft Exchange Server 2016

Microsoft Exchange Server 2016 may be installed using the graphical user interface (GUI) or Windows PowerShell. Below you will find a step-by-step tutorial outlining the GUI installation of Microsoft Exchange Server 2016.

  1. Right click the setup.exe file and select Run as administrator.
  2. On the Check for Updates? dialog box select Connect to the Internet and check for updates then click next.
  3. On the Downloading Updates… dialog box click next.
  4. On the Introduction dialog box click next.
  5. On the License Agreement dialog box select I accept the terms in the license agreement then click next.
  6. On the Recommended Settings dialog box select Use recommended settings then click next.
  7. On the Sever Role Selection dialog box select Mailbox role then click next.
  8. On the Installation Space and Location dialog box specify the installation path of your choice.
  9. On the Exchange Organization dialog box specify the name of the Exchange Organization then click next.
  10. On the Malware Protection Settings dialog box, under the Disable malware scanning. option select No then click next.
  11. On the Readiness Checks dialog box click install.
  12. On the Setup Completed dialog box click finish.
  13. Reboot the server.

Microsoft Exchange Server 2016 – Mailbox Server Role Prerequisites

June 15, 2018
EmailMicrosoft Exchange Server 2016Microsoft Windows PowerShellScripting

The Microsoft Exchange Server 2016 Mailbox Server role prerequisites may be installed during the graphical user interface (GUI) installation of the Mailbox Server role. Additionally, and recommended, you may use the process below to install the required prerequisites on the server that will be hosting the Mailbox Server role. These include installing operating system features, preparing Microsoft Active Directory (AD), installation Microsoft .NET Framework 4.5.2, and installing Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit.

  1. Right click Windows PowerShell and select Run as Administrator.
  2. Use the following cmdlet to install the required features, then reboot the server.
    1. Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
  3. Use the Install-WindowsFeature RSAT-ADDS cmdlet to prepare Microsoft Active Directory.
  4. Right click the Microsoft .NET Framework 4.5.2 executable file and select Run as administrator.
  5. On the .NET Framework 4.5.2 Setup dialog box select the check box that states I have read and accept the license terms., then click Install.
  6. On the Do you want Setup to close your programs? dialog  box click Yes.
  7. On the Installation is Complete dialog box click Finish.
  8. Right click the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit executable file and select Run as administrator.
  9. On the Microsoft Unified Communications Managed API 4.0, Runtime Setup dialog box click Next >.
  10. On the Microsoft Unified Communications Managed API 4.0, Runtime Setup dialog box select the check box that states I have read and accept the license terms., then click Install.
  11. On the Installation is Complete dialog box click Finish.

Microsoft Exchange Server 2016 – Mailbox Enabled User Command Line Configuration

June 15, 2018
AutomationEmailMicrosoft Active DirectoryMicrosoft Exchange Management ShellMicrosoft Exchange Server 2016Scripting

You may use the following Microsoft Exchange Management Shell (EMS) cmdlet to configure a Mailbox-Enabled User in Microsoft Exchange Server 2016.

Enable-Mailbox -Identity User

Microsoft Exchange Server 2016 – Product Key Command Line Configuration

June 15, 2018
AutomationEmailMicrosoft Exchange Management ShellMicrosoft Exchange Server 2016Scripting

You may use the following Microsoft Exchange Management Shell (EMS) cmdlet to enter the product key for Microsoft Exchange Server 2016.

Set-ExchangeServer –identity ‘<server>’ -ProductKey <product key>

Microsoft Exchange Server 2016 – Send Connector Command Line Configuration

June 15, 2018
AutomationEmailMicrosoft Exchange Management ShellMicrosoft Exchange Server 2016Scripting

The Send Connector in Microsoft Exchange Server 2016 is am object that contains the configuration information for sending email from the Exchange organization. You may use the following commands in the Microsoft Exchange Management Shell (EMS) to configure a send connector for all outbound traffic.

New-SendConnector -name “Default Internet”
-AddressSpaces “*” -DNSRoutingEnabled $true
-SourceTransportServers “Server” -Usage Internet

Microsoft Exchange Server 2016 – Email Address Policy Command Line Configuration

June 15, 2018
AutomationEmailMicrosoft Exchange Management ShellMicrosoft Exchange Server 2016Scripting

You may use the following commands in the Microsoft Exchange Management Shell (EMS) to create and configure an email address policy in Microsoft Exchange Server 2016.

New-EmailAddressPolicy -Name PolicyName
-EnabledPrimarySMTPAddressTemplate “SMTP:%g.%[email protected]”
-IncludedRecipients AllRecipients -Priority 1 |
Update-EmailAddressPolicy

Microsoft Exchange Server 2016 – SMTP Domain Command Line Configuration

June 15, 2018
AutomationEmailMicrosoft Active DirectoryMicrosoft Exchange Management ShellMicrosoft Exchange Server 2016Scripting

By default Microsoft Exchange Server 2016 configures a default accepted domain and email address policy using the fully qualified domain name (FQDN) of the Microsoft Active Directory (AD) domain into which it is installed. If necessary, you may use the following commands in the Microsoft Exchange Management Shell (EMS) to create an SMTP domain for Microsoft Exchange Server 2016. Note that you may change the -MakeDefault value to $false if you do not want it to be used as the default SMTP domain for the email address.

New-AcceptedDomain -Name domain.com
-DomainName *.domain.com
-DomainType authoritative |
Set-AcceptedDomain -MakeDefault $true

Microsoft Exchange Server 2016 – Offline Address Book Command Line Configuration

June 15, 2018
AutomationEmailMicrosoft Exchange Management ShellMicrosoft Exchange Server 2016Scripting

You may use the following command in Microsoft Exchange Management Shell (EMS) to associate the default Offline Address Book (OAB) with the mailbox database(s).

Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook “\Default Offline Address Book”

Microsoft Exchange Server 2016 – Mailbox Server Role Command Line Installation

June 15, 2018
AutomationEmailMicrosoft Active DirectoryMicrosoft Exchange Server 2016Microsoft Windows PowerShellScripting

You may use the following commands to install the Microsoft Exchange Server 2016 Mailbox Server role from the command line.

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms /OrganizaionName:
“<Organization Name>”
Setup.exe /mode:install /role:Mailbox /IAcceptExchangeServerLicenseTerms

Microsoft Exchange Server 2016 – Autodiscover DNS Lookup

May 30, 2018
Domain Name SystemMicrosoft Exchange Server 2016

The autodiscover service is critical to the proper functioning of a Microsoft Exchange Server 2016 infrastructure. Additionally, the autodiscover service may be utilized using SCP for domain joined clients or DNS records for external clients. The DNS records and associated URLs will be utilized, in the order below, to find the autodiscover XML file. More information regarding autodiscover may be found here.

A or CNAME (https://domain.com/Autodiscover/Autodiscover.xml)

A or CNAME (https://autodiscover.domain.com/Autodiscover/Autodiscover.xml)

A or CNAME (http://autodiscover.domain.com/Autodiscover/Autodiscover.xml)

SRV (autodiscover._tcp.domain.com)