? The previous articles describe the single-machine deployment of Exchange Server 2013 preview in a Windows R2 environment. Below, the role deployment will be performed on the basis of Windows Server RC. Exchange Server 2013 reduces the role for the client Access role and the mailbox role, where the UM role and Hub Transport are integrated into client access. Next, we introduce the next environment for this deployment, which is deployed with 5 Windows Server 2012RC servers, deploying two CAS roles and two mailbox roles, one DC, and implementing Dags and Casarray as follows:
dc:192.168.50.3
cas01:192.168.50.10
cas02:192.168.50.11
mailbox01:192.168.50.12 dag replication: 10.0.0.1
mailbox02:192.168.50.13 dag replication: 10.0.0.2
Dag Cluster ip:192.168.50.8
NLB cluster ip:192.168.50.20?
- Mailbox Role Server Installation
- Run the Install-windowsfeature Rsat-adds installation adds administrative tool in Windows PowerShell.
install-windowsfeature rsat-adds?
?
- Next, prepare for the prerequisites for the mailbox role, run the following script in Windows PowerShell to install the appropriate service, and then restart the server.
install-windowsfeature as-http-activation, Desktop-experience, Net-framework-45-features, RPC-over-HTTP-proxy, Rsat-clustering, 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?
?
- Install the following after reboot is complete
Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit?
Microsoft Office, Filter Pack, bit
Microsoft Office $ Filter Pack SP1
- Extending the domain schema to run in Windows PowerShell
./setup/prepareschema/iacceptexchangeserverlicenseterms
?
- Prepare your organization
./setup/preparead/organizationname:contoso/iacceptexchangeserverlicenseterms
- Prepare the domain
./setup/preparedomain:contoso.local/iacceptexchangeserverlicenseterms
- Running Exchange? Setup for installation
- Start copying files
- ? proceed to the next step after agreeing to the license
- ? do not send error reports, next
- Tick the mailbox role that needs to be installed, and then next.
- Select the installation path, next.
- Malicious software protection, enabled.
- Complete the prerequisite check to install.
- Wait for the program to complete and install the second mailbox server in the same way after the end.
- Deploying a Client Access server
- When you install the Client Access server, execute the following script in Windows PowerShell to install the required services and features.
Install-windowsfeature as-http-activation, Desktop-experience, Net-framework-45-features, RPC-over-HTTP-proxy, Rsat-clustering, 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
?
- installation Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit?
- Go to the installation of the Client Access role server with the same installation method as the previous mailbox role, select the Client Access role when selecting the roles, and then install.
?
- After the installation is complete, the mailbox role of Exchange 2013 really accounts for memory, and after the installation of two mailbox roles, it accounts for 20G of memory. After entering the production deployment, it seems to need to greatly improve the hardware configuration ah.
Install Exchange Server on Windows Server 2012