Install: Instalacion exchange 2010 Powershell


  1. Preparar el esquema para soportar exchange

Desde CMD, nos vamos a la unidad del DVD y ejecutamos

  • Setup /prepareSchema (desde el maestro de esquema, para poder modificar el esquema)
  • Setup /PrepareAD /OrganizationName:<Your-Organization-Name>
  • Setup /preparedomain (PREPARA TODOS LOS DOMINIOS DEL BOSQUE)

  1. Instalar los feautures necesarios de Windows para poder instalar luego los roles de exchange

El primer paso es importar el modulo serverManager. No obstante con la versión Exchange 2010 SP1, desde el modo grafico, podemos instalar los roles de Exchange, que desde ahí nos dejara que previamente instale la features

  • Import-Module ServerManager

    Si fueramos actualizar con un service pack

    For mailbox servers that are members of a Database Availability Group, remember that Exchange includes a script called StartDagServerMaintenance.ps1

    1. Run the script to prepare a DAG server member for maintenance.

    .\StartDagServerMaintenance -ServerName “EXSERVER1”

    2. When maintenance is done, run the other script to bring the server back online within the DAG.

    .\StopDagServerMaintenance -ServerName “EXSERVER1

El segundo paso es instalar las características,. Dependiendo que rol de Exchange instalaremos, ejecutaremos uno u otro. Por ejemplo para instalar los 3 roles típicos, se necesitan estas features

  • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy

Esta es la tabla de roles de Windows a instalar. Mas info en http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2

Role Combination Add-WindowsFeature command
Client Access, Hub Transport, and the Mailbox role Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy
Client Access Role Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy
Hub Transport Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server
Edge Transport Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS

También podemos instalar esta Feautures de Windows del modo antiguo. Con los script que están en el DVD , en la carpeta scripts. El “-ip” significa i=install y p=desde un fichero xml.

  • ServerManagerCMD –ip <XML file_en carpeta Scripts>    //
    • Exchange-all.xml – this xml file has all components for all Exchange Server roles, it should be used when you are installing CAS/HUB/MBX and UM on the same box.
    • Exchange-base.xml – this xml contains only the information to install the RSAT-ADDS which is a base component for all roles.
    • Exchange-cas.xml, Exchange-edge.xml, exchange-hub.xml, exchange-mbx.xml and exchange-um.xml files – Each file is for a specific role, if you want to use a single role, for example CAS you should use only Exchange-cas.xml. If you want to use a server as CAS and HUB you can apply Exchange-cas.xml and Exchange-hub.xml.
    • Exchange-typical.xml – Install all components required in a typical installation (CAS, Hub ,MBX)
  1. Configura Net.TCP

Set the start up type of Net.Tcp Port Sharing Service to automatic (this is required for successful completion of CAS role installation)

  • Set-Service NetTcpPortsharing -Startuptype Automatic
  1. Instalar filter pack (necesario para MBX y CAS)

Para Exchange 2010 SP2 es la versión Filter Pack 2.0


  1. Instalar Exchnge por comandos

Ejecutamos desde el setup del cd o por entorno grafico

  • Setup.com /mode:install /role:Mailbox,HubTransport
  • Setup.com /mode:install /r:M,H
Estos son las nomenclaturas
  • HubTransport, HT, or H
  • Mailbox, MB, or M
  • ClientAccess, CA, or C
  • EdgeTransport, ET, or E
  • UnifiedMessaging, UM, or U

Por ejemplo instalar el MailBox y Hub Transport lo podemos hacer de dos maneras

  • Setup /r:MB,HT,CA,ET,UM        //instala todos los rolees (ET es por separado)
  • Setup.com /mode:install /role:Mailbox,HubTransport
  • Setup.com /mode:install /r:M,H,C,E    //instala o agregaMailbox, Hub Transport, Client Acces, Edge Transport

El /mode:uninstall elimina un rol, o el Exchange server si no especificamos el rol

El /mode:upgrade es si ya tenemos una versión de Exchange y queremos actualizarla a una mas nueva

 

Install Windows Server 2008 R2 prerequisites for Exchange

 

To installed Exchange 2010 on Windows 2008 R2, you must install the Windows Server 2008 R2 operating system prerequisites as shown below.

On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.

On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Import-Module ServerManager

  • Use the Add-WindowsFeature cmdlet to install the necessary operating system components:
  1. For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
  2. For a server that will host the Client Access, Hub Transport, Mailbox, and Unified Messaging server roles:

    Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy,Desktop-Experience –Restart
  3. For a server that will host the Client Access and Hub Transport server roles:

    Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
  4. For a server that will host the Hub Transport and Mailbox server roles:Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server –Restart
  5. For a server that will host the Client Access and Mailbox server roles:Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
  6. For a server that will host only the Client Access role:Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
  7. For a server that will host the Hub Transport or the Mailbox role:Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server –Restart
  8. For a server that will host only the Unified Messaging role:Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Desktop-Experience –Restart
  9. For a server that will host the Edge Transport role:

    Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS –Restart

    1. On servers that will have the Client Access Server role installed, after the system has restarted, log on as an administrator, open an elevated Windows PowerShell console, and configure the Net.Tcp Port Sharing Service for Automatic startup by running the following command:

      Set-Service NetTcpPortSharing -StartupType Automatic

Be the first to comment

Leave a Reply