Instalacion de Exchange Server 2013 (Parte 1)

Gracias a los Licensiados Victor Diaz Guerra y Profe. Joel Rosario (Ambos Ingenieros de la Nube en 365.

Instalacion de EXS 2013 (Parte 1)

Thursday, September 3, 2015

11:18 PM

Instalacion de Exchange Server 2013 (Parte 1)

 

SEP. 3, 2015 – VICTOR DIAZ GUERRA

 

1.- Preparación de Active Directory.

 

Tareas en el Controlador de Dominio.

 

SO: Windows Server 2012 R2

FQDN: dc1.vdg.local

IP: 192.168.0.205

 

Instalar los siguientes componentes en el Controlador de Dominio Primario:

 

  • .NET Framework 4.5.2

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

 

  • Windows Management Framework 4.0 (incluida en Windows Server 2012 R2)

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

 

Ejecutar Windows PowerShell como administrador para instalar el paquete de administración de herramientas remotas.

 

 

Para Windows Server 2012 R2 o Windows Server 2012, ejecute el comando siguiente.

 

Install-WindowsFeature RSAT-ADDS

 

 

 

Tareas en el Servidor de Exchange.

 

SO: Windows Server 2012 R2

FQDN: ex1.vdg.local

IP: 192.168.0.207

 

Los requisitos previos necesarios para instalar Exchange 2013 en un equipo con Windows Server 2012 R2 o Windows Server 2012 varían en función de los roles de Exchange que se desee instalar.

 

Roles de servidor de acceso de cliente y de buzón

 

Este procedimiento aplica a los siguientes escenarios:

 

  • Instalar solo el rol de servidor Buzón de correo en un equipo.
  • Instalar únicamente el rol de servidor de acceso de cliente en un equipo.
  • Instalar los roles de servidor Buzón de correo y Acceso de clientes en el mismo equipo.

 

Instalar los roles y las características necesarias de Windows:

 

  1. Abra Windows PowerShell como Administrator.
  2. Ejecute el siguiente comando para instalar los componentes necesarios de Windows.

 

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

 

 

 

Nota:
En caso necesario reiniciar este servidor para completar el proceso de instalacion de los componentes.

 

Una vez instalados los roles del sistema operativo y las características, instalar entonces componentes siguientes siguiendo el orden indicado:

 

  1. .NET Framework 4.5.2

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

 

  1. Windows Management Framework 4.0 (incluida en Windows Server 2012 R2)

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

 

  1. Microsoft Unified Communications Managed API 4.0, Runtime principal de 64 bits

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

 

 

 

2.- Extender el esquema del Active Directory.

 

Tareas en el Controlador de Dominio.

 

SO: Windows Server 2012 R2

FQDN: dc1.vdg.local

IP: 192.168.0.205

 

Descargar la actualizacion acumulativa mas reciente para Exchange Server 2013:

 

http://social.technet.microsoft.com/wiki/contents/articles/15776.exchange-server-2013-build-numbers-with-cumulative-updates.aspx

 

Exchange Server 2013 Cumulative Update

 

Product Name Build Number Date

[mm/dd/yyyy]

KB
 Microsoft Exchange Server 2013 RTM  15.0.516.32  12/03/2012  
 Exchange Server 2013 Cumulative Update 1 (CU1)  15.0.620.29  04/02/2013  KB2816900
 Exchange Server 2013 Cumulative Update 2 (CU2)  15.0.712.24  07/09/2013  KB2859928
 Exchange Server 2013 Cumulative Update 3 (CU3)  15.0.775.38  11/25/2013  KB2892464
 Exchange Server 2013 Service Pack 1 (SP1 aka CU4)  15.0.847.32  02/25/2014  KB2926248
 Exchange Server 2013 Cumulative Update 5 (CU5)  15.0.913.22  05/27/2014  KB2936880
 Exchange Server 2013 Cumulative Update 6 (CU6)  15.0.995.29  08/26/2014  KB2961810
 Exchange Server 2013 Cumulative Update 7 (CU7) ​ 15.0.1044.25  12/09/2014  ​KB2986485
 Exchange Server 2013 Cumulative Update 8 (CU8) ​ 15.0.1076.9  03/17/2015  ​KB3030080
 Exchange Server 2013 Cumulative Update 9 (CU9)  15.0.1104.5  06/16/2015  KB3049849

 

Nota:
En este escenario de ejemplo se descargo la version de actualizacion acumulativa 9 de Exchange Server 2013.

 

 

Extendiendo el esquema del Directorio Activo:

 

  • Abra una ventana del símbolo del sistema de Windows desde la ubicación donde descargó los archivos de instalación de Exchange.

 

 

 

  • Para extender el esquema, ejecute el comando siguiente.

 

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

 

 

Preparando el Directorio Activo:

 

  • Abra una ventana del símbolo del sistema de Windows y vaya a la ubicación donde descargó los archivos de instalación de Exchange.

 

  • Ejecute el comando siguiente:

 

Setup.exe /PrepareAD /OrganizationName:”<organization name>” /IAcceptExchangeServerLicenseTerms

 

Para encontrar el nombre de la organizacion ejecutamos “Active Directory Sites and Services” en las herramientas administrativas del sistema.

 

 

 

Quedando de esta manera el comando final para este escenario de ejemplo:

 

Setup.exe /PrepareAD /OrganizationName:“Default-First-Site-Name” /IAcceptExchangeServerLicenseTerms

 

 

Preparando todos los dominios del bosque de Active Directory:

 

  • Abra una ventana del símbolo del sistema de Windows y vaya a la ubicación donde descargó los archivos de instalación de Exchange.

 

  • Ejecute el comando siguiente:

 

Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms

 

 

 

 

 

 

 

Created with Microsoft OneNote 2016.

Configure Internet Mail Flow through a subscribed Edge Transport Server

Wednesday, June 1, 2016

2:36 PM

https://technet.microsoft.com/en-us/library/bb738158(v=exchg.160).aspx

 

Configure Internet mail flow through a subscribed Edge Transport server

 

Applies to: Exchange Server 2013

Topic Last Modified: 2015-04-08

 

To establish Internet mail through an Edge Transport server, subscribe the Edge Transport server to an Active Directory site. This automatically creates the two Send connectors required for Internet mail flow:

 

  • A Send connector configured to send outbound email to all Internet domains.

 

  • A Send connector configured to send inbound email from the Edge Transport server to an Exchange 2013 Mailbox server.

 

If you don’t want to subscribe the Edge Transport server to an Active Directory site, it’s possible to manually create the Send connectors required to establish mail flow between the Mailbox server and the Edge Transport server. For more information, see Configure Internet mail flow through an Edge Transport server without using EdgeSync. However, we recommend you subscribe the Edge Transport server to the Active Directory site whenever possible.

 

 

Before you begin

 

  • Estimated time to complete: 20 minutes.

 

  • You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the “EdgeSync” entry and the “Edge Transport servers” in the Mail flow permissions

 

  • Before you subscribe an Edge Transport server to your organization, you will first need to configure authoritative domains and email address policies for your Exchange organization.

 

  • Enable the secure LDAP port 50636/TCP through the firewall separating your perimeter network from the Exchange organization. The Edge Transport server needs to be able to communicate with all Exchange 2013 Mailbox servers in the subscribed Active Directory site.

 

 

Tip:
Having problems? Ask for help in the Exchange forums. Visit the forums at Exchange Server, Exchange Online, or Exchange Online Protection.

 

 

Configure Internet mail flow through a subscribed Edge Transport server

 

  1. On the Edge Transport server, create the Edge Subscription file using the following syntax.

 

New-EdgeSubscription -FileName <FileName>.xml [-Force]

The following example creates an Edge Subscription file named EdgeSubscriptionInfo.xml in the folder C:\My Documents. The Force parameter suppresses prompts confirming commands that will be disabled and warnings that configuration data will be overwritten on the Edge Transport server.

 

New-EdgeSubscription -FileName “C:\My Documents\EdgeSubscriptionInfo.xml” -Force

 

  1. Copy the resulting Edge Subscription file to a Mailbox server in the Active Directory site you’re subscribing the Edge Transport server

 

  1. On the Mailbox server, to import the Edge Subscription file, use the following syntax.

 

New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path “<FileName>.xml” -Encoding Byte -ReadCount 0)) -Site <SiteName>

This example imports the Edge Subscription file named EdgeSubscriptionInfo.xml from the folder D:\Data, and subscribes the Edge Transport server to the Active Directory site named “Default-First-Site-Name“.

 

New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path “D:\Data\EdgeSubscriptionInfo.xml” -Encoding Byte -ReadCount 0)) -Site “Default-First-Site-Name”

 

Note:
You can use the CreateInternetSendConnector or CreateInboundSendConnector parameters to prevent one or both of the required Send connectors from being automatically created. For more information, see Edge Subscriptions.

 

  1. On the Mailbox server, run the following command to start the first EdgeSync synchronization.

 

Start-EdgeSynchronization

 

  1. When you’re finished, we strongly recommend you delete the Edge Subscription file from both the Edge Transport server and from the Mailbox server. The Edge Subscription file contains information about credentials used during the LDAP communication process.

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *