MSExchangeGuru.com

Follow the below steps to install Exchange 2013 RTM

Step 1: Windows Installation

1. Install the windows 2012 server or Windows 2008 R2 SP1.
2. Run the windows update and install all the recommended updates.
3. Join the server to the Domain
4. Restart the server

 

Step 2: Preparing windows server for the Exchange 2013

1. Install the following prerequisites
   

   For Windows 2012:
   

   1. Open Windows PowerShell.
   2. Run the following command to install the required Windows components.
      

      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. Restart the server.
   4. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
      

      http://www.microsoft.com/en-us/download/details.aspx?id=34992

   5. Microsoft Office 2010 Filter Pack 64 bit
      

      http://www.microsoft.com/en-us/download/details.aspx?id=17062
      

   6. Microsoft Office 2010 Filter Pack SP1 64 bit
      

      http://www.microsoft.com/en-us/download/details.aspx?id=26604

   For Windows 2008:

   1. Open Windows PowerShell.
   2. Run the following command to load the Server Manager module.
      

      Import-Module ServerManager
      

   3. Run the following command to install the required Windows components.
      

          Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, 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-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI
      

   4. Restart the server
   5. Microsoft .NET Framework 4.5
      

      http://msdn.microsoft.com/en-us/library/5a4x27ek(VS.110).aspx

   6. Windows Management Framework 3.0
      

      http://www.microsoft.com/en-us/download/details.aspx?id=34595

   7. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
      

      http://www.microsoft.com/en-us/download/details.aspx?id=34992

   8. Microsoft Office 2010 Filter Pack 64 bit
      

      http://www.microsoft.com/en-us/download/details.aspx?id=17062

   9. Microsoft Office 2010 Filter Pack SP1 64 bit
      

      http://www.microsoft.com/en-us/download/details.aspx?id=26604

   10. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
       

       http://support.microsoft.com/?kbid=974405&wa=wsignin1.0

   11. Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)
       

       http://support.microsoft.com/?kbid=2619234

   12. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution)
       

       http://support.microsoft.com/?kbid=2533623

2. Restart the server before next step.
   

 

Step 3: Preparing Active Directory:

           Points to be noted:

-We need to update the schema on the schema master.

-We need to use Schema Admins and Enterprise Admins permission user account for future task.

-We need to update the AD domains in multiple domain environment. We can use different switch for different requirement.

-First deploy Exchange 2013 in the internet facing site then other site.

-Active Directory pepareation Server should have following software installed if it is 2008. 2012 comes ready with it and need to added from roles and features.

•    Microsoft .NET Framework 4.5
•    Windows Management Framework 3.0

 

Steps:

1. Log in to the Member server, open the command prompt with run as administrator and run the following cmdlet to update schema.

-We need to install AD management tool to update schema so that it can read ldf files.  Open powershell with run as administrator and run the below command.

            On 2012:  Install-WindowsFeature RSAT-ADDS

           On 2008: Add-WindowsFeature RSAT-ADDS

-There is no setup.com and it is only setup.exe

           “Setup.exe /prepareschema /IAcceptExchangeServerLicenseTerms”

          

2. Run the below command to update Active Directory

Important: We will not be able install exchange 2010 after this step. See the warning.

“setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms /OrganizationName:”GiveTheORGName””

            

3. Run the below command in every Exchange user domain

 -If we have only one domain then this command is not required.

 -If we have to multiple domain and some of the domain will not use exchange then run the below command in all the exchange domains.

“setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms”

Else run the below command to prepare all domains.

“setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms”

           

Step 4: Exchange 2013 Deployment:

 

        1. Run the setup.exe with run as administrator and click next on the below screen

         

        2. Click next here

        3. Now setup will copy the files and initialize the setup. Click next once setup initialize and you see Introduction page.

 

        4. Select the license term and click next here.

 

        5. Select “Don’t use recommended settings” and click next.

 

        6. Select the Role and click next. I am installing both CAS and MBX on the same server.

       

        7. Select the installation drivedirectory then click next.

 

        8. Change if you wish to do mailware scanning and click next

       

        9. Now Readiness check will run. Once Readiness check completes, click Install

          

        10. I have my lab Exchange on a Domain Controller so I got this warning but in production we should not see any warning or error

 

        11. Now Exchange will Run 14 steps for the Installation. This will take an hour or so depends on the hardware so you can take a lunch break and when you will be back you will see your exchange   server is ready for use.

        12. When you see then below screen, click on finish.

        13. Restart the server

 

        14. Login to OWA for administrator account and test.

 

 

        15. Login to https://yourdomain.com/ECP and check new EAC.

 

This ends the Exchange 2013 Deployment.

 

Prabhat Nigam | MVP Exchange

Team @MSExchangeGuru

Posted April 29th, 2013 under Exchange 2013. RSS 2.0 feed. Leave a response, or trackback.