Exchange Server 2013
Once the requirements are met, it is time to move onto preparing the active directory. This documentation assumes that you will be preparing Server 2012 Active Directory for Exchange 2013 from the first Server. You will need to install features on the Server. Typically , for larger organizations, you will want to have a dedicated server , or even a dedicated server(s) for both the Mailbox role and the Client Access server Role.
After the additional features are installed, add-on components are downloaded and installed.
Exchange Server 2013 Mailbox and Client Access roles require the installation of Windows components. Do this by running the following PowerShell Script:
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,
When you hit Enter , the server will install the specified roles and features.
Once the added roles and features are installed, will want to install the following add on components:
- Microsoft.net framework 4.5(http://go.microsoft.com/fwlink/p/?LinkId=518380)
- Windows Management Framework 4.0(http://go.microsoft.com/fwlink/p/?LinkId=390234)
- Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit (http://go.microsoft.com/fwlink/p/?linkId=258269)
Once these additional features aand add-on componenets are installed, you can install Exchange Server 2013.