0xc007041d Microsoft Exchange Messaging and Collaboration Services

Issue 1:
0xc007041d - El servicio no ha respondido a la petición o inicio del control en un tiempo adecuado. (EXIFS)
Dispositivo: Programa de instalación de Microsoft Exchange
Nº de Id.: c107041d
Programa de instalación de Microsoft Exchange

Source:
http://www.techrepublic.com/forums/discussions/issues-with-upgrading-from-exchange-2003-standard-to-2003-enterprise/
Ok?the problem seemed to be with Microsoft Exchange Messaging and Collaboration Services since during the reinstall it was showing a red x. Also, from Event ID 1002 as shown below the EXIFS was the main problem. I mentioned this issue again to the last MS Engineer I spoke with and it happens that today he also had a customer with similar problem on SBS 2003 but he said it is most likely the same issue I am having. So he asked to go to:
C:\Windows\System32\Drivers
Rename the following files exifs.sys and exifssmsg.dll. to *.old
After renaming both files I ran the Reinstall of MS Exchange 2003 Enterprise and everything was ok?.the ESM now shows Enterprise and I see Event ID 1217.

Issue 2: Removing Exchange 2003
After that a new error message apperas 0xc0070425
source:
https://support.microsoft.com/en-us/kb/818466
https://support.microsoft.com/en-us/kb/924170


You rename old to dll again and old to sys, and press "Continue"

The installer succesfully uninstall Exchange 2003 from an older on-premise server

Experiencing an OWA HTTP 500 Error?

Source: http://www.msexchange.org/blogs/walther/news/exchange-2010-sp1-experiecing-an-owa-http-500-error-554.html

I’ve seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead of opening the mailbox.


You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom.
So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue.
Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause.
Until later,
Henrik WaltherTechnology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture

I’ve seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead of opening the mailbox.



You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom.
So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue.

Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause.
Until later,
Henrik Walther
Technology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture 

Certificado de federación o autenticación no encontrado / Missing the Microsoft Exchange Server Auth Certificate

Source: http://community.spiceworks.com/topic/512374-missing-the-microsoft-exchange-server-auth-certificate

Error:
Nombre de registro:Application
Origen:        MSExchange Certificate Deployment
Fecha:         06/04/2015 8:19:31
Id. del evento:2005
Categoría de la tarea:General
Nivel:         Advertencia
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        servidor.dominio.com
Descripción:
Certificado de federación o autenticación no encontrado: A65CD35A40A0B21AA53C6EAAED012B184F6201B6. No es posible encontrar el certificado en los sitios locales o vecinos. Confirme que el certificado está disponible en su topología y, si es necesario, restablezca el certificado en la confianza de federación a un certificado válido mediante Set-FederationTrust o Set-AuthConfig.  Es posible que lleve tiempo que el certificado se propague a los sitios locales o vecinos.


Solved:
In fact, I would say that this process not only solved my issue but also got rid of a majority of the little warnings and errors on both my Exchange 2013 and Lync 2013 servers.  they seem to enjoy life more when they can exchange tokens directly with each other.
For a majority of you, you will have the certificate in place, and setting up the integration will be super easy.  If by chance, you do not have the cert, then this is your easy 2 min fix.
1. New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn= Microsoft Exchange Server Auth Certificate" -DomainName "*.yourdomain.com" -FriendlyName "Microsoft Exchange Server Auth Certificate" -Services smtp
Do not accept to replace the SMTP certificate when prompted
2. Note the thumbprint of the new certificate. Let us assume it is 7A39541F8DF58D4821967DD8F899B27410F7C081
3. $a=get-date
4. Set-AuthConfig -NewCertificateThumbprint 7A39541F8DF58D4821967DD8F899B27410F7C081 –NewCertificateEffectiveDate $a
Accept to continue despite the fact that the certificate effective date is not 48 hours into the future
5. Set-AuthConfig –PublishCertificate

6. Make sure to remove any potential reference to the previous certificate (which might not exist anymore) by doing Set-AuthConfig -ClearPreviousCertificate.
you can now get back to finishing up your prereqs:  http://technet.microsoft.com/en-us/library/jj721919.aspx 

Recover a Lost Exchange Server 2013 on a windows server 2012r2

Fuentes: https://technet.microsoft.com/en-us/library/dd876880%28v=exchg.150%29.aspx
Fuentes: https://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx

Casi imposible restaurar en el mismo servidor después de un fallo del instalador del Cumulative Update 7

Al final varios pasos y repeticiones llevaron a un estado funcional, pero incapaz de instalar el antispam de symantec messaging

Si estás presuroso por correr el recover, debes primero Ask your self if you deleted the AD Object corresponding to exchange 2013 server, if you d you'll have a infinite type of errors, until you got the 0x80070005 COM Error on FIPS that cannot be fixed.

So if you run the setup /m:Recoverserver after reading all this things. DONT RUN IF YOU DELETED DE AD OBJECT YOU LL HAVE TO FORMAT

On failed recovery setup you must do this:

- Verify that you re using a Member Server not DC

- If you deleted the AD Object you must reinstall de server with same name and join to domain. 

- And DONT FORGET to ADD it to Builtin Exchnage enterprise Servers and Exchange Server in Exchange OU

I have run on a DC the preparation domain tools again

setup /p /IAcceptExchangeServerLicenseTerms

setup /pad /IAcceptExchangeServerLicenseTerms

setup /ps /IAcceptExchangeServerLicenseTerms

Dont forget the RSAT-ADDS-Tools on Prerequisites

Stop and disable all Exchange Services

Reboot

Cleanup IIS application pools

Cleanup Exchange 

Delete all Exchange folders from program files (take care of your edb mailbox)

0x80070005 –E_ACCESS_DENIED

Access denied  by  DCOM security.
The user does not have remote access to the computer through DCOM. Typically, DCOM errors occur when connecting to a remote computer with a different operating system version.
Give the user Remote Launch and Remote Activation permissions in dcomcnfg.  Right-click My Computer-> Properties  Under COM Security, click "Edit Limits" for both sections.  Give the user you want remote access, remote launch, and remote activation.  Then go to DCOM Config, find "Windows Management Instrumentation", and give the user you want Remote Launch and Remote Activation. For more information, see Connecting Between Different Operating Systems

Change Swap to twice of RAM

Register:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine]
"ApplicationBase"="C:\\Windows\\System32\\WindowsPowerShell\\v1.0"
"RuntimeVersion"="v2.0.50727"
"ConsoleHostAssemblyName"="Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil"
"ConsoleHostModuleName"="C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\Microsoft.PowerShell.ConsoleHost.dll"
"PowerShellVersion"="2.0"
"PSCompatibleVersion"="1.0, 2.0"
"CTPVersion"="15"

delete next services (reboot)
FMS
SearchExchangetracing
MSEXCHANGE*
HostConstrollerService

empty IIS and apps (be careful with RPc sites)


create 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Pickup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Setup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\FIP-FS]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\FIP-FS\SQM]

Adding Subnet to Sites and Directory

Stop Firewall Windows

On DC 

Add Windows 2008 R2 SP1

Rerun 

Delete exchange object 

rerun

setup /IacceptExchangeserverLicenseTerms /SourceDir:C:\temp\exch2013\cu7 /m:Recoverserver /InstallWindowsComponents 

------------------------
ENTRE OTROS ERRORES

I got a windows update settingscontent-ms error, which avoid to start Windows Update Screen (i booted the server after started de "Check for Windows Updates screen"

Here's one way to find what is not working:

cd /d  %LocalAppData%\Packages

dir/a/b/s  *.settingscontent-ms  |  find  "Classic_{36e"  |  clip

Then open a Notepad window and do a Ctrl-o Ctrl-v and Enter

Somehow I think the failure may have more to do with the program which "executes" the .settingcontent-ms  file extension...

C:\Users\Admin\AppData\Local\Packages>assoc .settingcontent-ms
.settingcontent-ms=SettingContent

C:\Users\Admin\AppData\Local\Packages>ftype SettingContent
File type 'SettingContent' not found or no open command associated with it.

What a surprise!  OTOH consistency found in W8's continual obfuscation and unhelpfulness.  ; }

Reset the computer account for the lost server. For detailed steps, see Reset a Computer Account.

Install the proper operating system and name the new server with the same name as the lost server. Recovery won't succeed if the server on which recovery is being performed doesn't have the same name as the lost server.

Join the server to the same domain as the lost server.

Install the necessary prerequisites and operating system components. For details, see Exchange 2013 system requirements and Exchange 2013 prerequisites.

Log on to the server being recovered and open a command prompt.

Navigate to the Exchange 2013 installation files, and run the following command.

1. Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
   

2. After Setup has completed, but before the recovered server is put into production, reconfigure any custom settings that were previously present on the server, and then restart the server.

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, RSAT-ADDS-Tools

Install-WindowsFeature ADLDS

u've installed the operating system roles and features, install the following software in the order shown:


.NET Framework 4.5.2


Windows Management Framework 4.0 (included with Windows Server 2012 R2)


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

ISP Blocked SMTP Traffic on port 25: How do I change the SMTP port on MS Exchange 2007/ 2010 SMTP Send Connector and how to authenticate the send conector with a hosting external user?

Spanish Keywords: El Proveedor de Internet ha  bloqueado el tráfico SMTP en el puerto 25: ¿Cómo cambio el puerto SMTP en Exchange 2007/2010 y cómo configuro la autenticación del conector de envío de Exchange con un usuario externo localizado en nuestro hosting de email.?

Los ISPs en su afán de controlar el SPAM de bots y clientes descuidados en su seguridad, bloquean de manera arbitraria el puerto SMTP saliente de organizaciones e individuos.

En el caso de organizaciones con Exchange 2007 o superior se puede utilizar los conectores de envío de exchange para no utilizar el puerto 25 como destino de las conexiones SMTP, por ejemplo en networksolutions se contrata un hosting con un relay smtp que permite conexiones al puerto 25 (smtp default), 2525 y 587.

Cómo se tiene bloqueado el tráfico SMTP 25, se agrega un Send Conector (conector de envío) normalmente autenticado con una cuenta del hosting.

1. Abre el Shell de Exchange (No la consola, la consola de Shell de Exchange), luego Escribe
Get-SendConnector
2. Obtienes así la lista con los nombres de los conectores de salida. Para cambiar el puerto de conexión predeterminado desde 25 a otros como 2525 o 26 o 587 (clásicos de algunos hosting como godaddy y networksolutions), escribe
Set-SendConnector "Conector Windows Small Business Server" -Port 587

Para agregar el usuario y password para la autenticación en el hosting se edita el conector cambiando las propiedades del conector "Windows Small Business Server" en Organization Configuration - Hub Transport>

En la pestaña Network se marca en "Route mail through the following smarthosts...", se da clic en Add y se agrega por ejemplo mail.hosting.com

Más abajo existe un botón "Change" junto a la opción "SmartHost Authentication"

ingresas las credenciales que pondrías normalmente en Outlook, y en adelante el tráfico smtp será direccionado al puerto alterno y podrá hacer relay con la combiniación de usuario contraseña especificados, saltando el bloqueo del ISP, y permitiendo integrar Exchange con un hosting externo.

Por otro lado se puede configurarse por ejemplo en Windows Small Business Server 2011 el conector POP3 apropiado para descargar el correo, y tener todos los buzones basados en Exchange localmente.

Microsoft Exchange 2010 Mover Libreta de direcciones sin conexión

Escenario:
- Buzones migrados desde 1 servidor Exchange 2003 a un servidor Exchange 2010 (el servidor Exchange 2003 fue eliminado hace tiempo)
- Buzones migrados nuevamente a un hardware nuevo con Exchange 2010
- El error se da al tratar de mover el servidor responsable de la generación de la libreta de direcciones sin conexión

El artículo referido para desinstalar la función de buzones del antiguo Exchange 2010 provee los siguientes pasos: http://technet.microsoft.com/es-ec/library/d0faeb2a-79d3-4ded-aa40-20f3b187b414.aspx

Para desplazar la generación de libretas de direcciones sin conexión mediante la consola de administración de Exchange

1. Abra la consola de administración de Exchange.
2. Expanda sucesivamente Microsoft Exchange, y Configuración de la organización, y después seleccione Mailbox.
3. En el panel de resultados, haga clic en la ficha Libreta de direcciones sin conexión.
4. En la ficha Libreta de direcciones sin conexión, seleccione la libreta de direcciones sin conexión que quiere desplazar. En el panel de acciones, haga clic en Mover.
5. Después de que aparezca el Asistente para mover la libreta de direcciones sin conexión , seleccione el nuevo servidor que alojará la generación de libretas de direcciones sin conexión mediante el botón Examinar y después haga clic en Mover.
6. Para cerrar el asistente, haga clic en Finalizar.
   

Al aplicar el proceso de mover libreta se presenta este error:

Resumen: 1 elemento(s). 0 correcto(s), 1 con error.
Tiempo transcurrido: 00:00:01


Lista de direcciones sin conexión predeterminada
Error

Error:
No se puede establecer la propiedad LastTouchedTime en este objeto porque requiere que el objeto sea de la versión 0.10 (14.0.100.0) o posterior. La versión actual del objeto es 0.0 (6.5.6500.0).
Haga clic aquí para obtener ayuda... http://technet.microsoft.com/es-ES/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.Ex51405F

Intento de ejecución del comando Consola de administración de Exchange:
move-OfflineAddressBook -Identity '\Lista de direcciones sin conexión predeterminada' -Server 'MISERVIDOR'

Tiempo transcurrido: 00:00:01


Fuentes:

• http://blogs.technet.com/b/exchange/archive/2007/01/11/3397719.aspx
• http://exchangeserverpro.com/project-coconut-part-6-finishing-the-job/

Pasos: (The easy way)

1. Configuración de la organización - Buzón de correo - Pestaña "Libreta de direcciones sin conexión"
2. clic derecho en "Lista de direcciones sin conexión predeterminada" y luego Eliminar Todo
3. Botón derecho en el área blanca "Nueva Libreata de Direcciones sin conexión"
4. Nombre: Lista de direcciones sin conexión predeterminada
5. Clic en Examinar: Seleccionar el nuevo servidor de Exchange
6. Marcar el check "Incluir las lista global predeterminada"
7. Marcar el check "Incluir las siguientes listas" y clic en Agregar, seleccionar "Todos los contactos", "todos los grupos" y "Todos los usuarios" si tienes otras listas personalizadas tambièn deberìas agregarlas para que estèn disponibles sin conexión
8. Clic en Siguiente
9. Clic en "Habilitar distribución basada en web", NO MARCAR "distribución basada en carpetas públicas"
10. Finalizar

Es necesario reasignar la nueva libreta de direcciones a cada base de datos de buzones para ello

1. Configuración de la organización - Buzón de correo - Pestaña "Administración de Base de datos"
2. clic derecho en "Mailbox Database xyx0000xx" y luego Propiedades
3. clic en la pestaña "Configuración del cliente" 
4. Junto a la opción "Libreta de direcciones" clic en Examinar y seleccionar "la nueva libreata de direcciones que apunta al servidro nuevo de Exchange"
5. Clic en Aceptar

Con esto podrán tener acceso a la libreta de direcciones sin coneión exclusivamente Outlook 2007 y superiores.

Si necesitas Outlook 2003 o antiguos, deberías marcar "distribución basada en carpetas públicas" y crear una base de datos de Carpetas Públicas en el nuevo servidor de Exchange

saludos.

BADBOY

Exchange 2007 Get Exchange Mailbox Size and export to a external file

Spanish Keywords: Exportar a un archivo de texto la lista y los tamaños de los buzones de Exchange 2007

To get Exchange Mailbox Size sorted by Size (with Item Count by MB)

Get-MailboxStatistics | Sort-Object TotalItemSize -Descending | ft DisplayName,@{label="TotalItemSize(KB)";expression={$_.TotalItemSize.Value.ToKB()}},ItemCount | Out-File c:\windows\temp\test.txt

Now you can use Microsoft Excel to analyze data


refs:
http://technet.microsoft.com/en-us/library/ee176924.aspx

http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/getting-mailbox-statistics-exchange-2007.html

Exchange 2007 OLEDB de Microsoft Exchange no pudo realizar la propagación del esquema en el inicio de la MDB HRESULT = 0xfffffae7.

Nombre de registro:Application

Origen:        EXOLEDB

Fecha:         29/06/2012 10:16:29

Id. del evento:111

Categoría de la tarea:General

Nivel:         Error

Palabras clave:Clásico

Usuario:       No disponible

Equipo:        INFAMATSDC1.infa.local

Descripción:

OLEDB de Microsoft Exchange no pudo realizar la propagación del esquema en el inicio de la MDB HRESULT = 0xfffffae7.

XML de evento:


Microsoft options

http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

Forums Options
http://social.technet.microsoft.com/Forums/en-HK/exchangesvrtransport/thread/b869feb8-0314-4a58-b892-3efec730d30a

Set-PublicFolder -identity "\NON_IPM_SUBTREE\schema-root" -name "schema"
Errors found
set-publicfolder cannot save the object


http://forums.msexchange.org/m_1800474498/mpage_2/printable.htm

braintek -> RE: Issues with Forms and Public folders (26.Nov.2009 4:05:59 PM)

I know I am a little late to this but I too was having this issue. I too upgraded from Exchange 2003 to 2007. Fixing this allowed me to setup the replication between two 2007 servers. I looked through the Offline Address Book. I found 3 entires and EX:/o=First Organization/ou=First Administrative Group wasn't setup. I'm pretty sure I used ADSIedit to remove the last remaining public folders from Exchange2003. Anyhow, I edited the EX:/o=First Organization/ou=First Administrative Group, setup a replication parter (primary server) then setup the Alias and DisplayName on the Exchange General tab. I was then able to add replica's to the other PF's in the list.

MSExchange System Attendant Mailbox Event ID 4001

Nombre de registro:Application

Origen:        MSExchange System Attendant Mailbox

Fecha:         29/06/2012 10:16:20

Id. del evento:4001

Categoría de la tarea:General

Nivel:         Error

Palabras clave:Clásico

Usuario:       No disponible

Equipo:        servidor.domain.local

Descripción:

Error transitorio. El problema podría resolverse en breve. El servicio volverá a intentarlo en 56 segundos. Información de diagnóstico:

No se puede abrir el buzón /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=INFAMATSDC1/cn=Microsoft System Attendant.

Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException: No se puede abrir el buzón /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=INFAMATSDC1/cn=Microsoft System Attendant. ---> Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227)


Resolution:

Anyway the solution was to update the drivers to the most current version and then turn off "Offload Checksum" option on the NIC. Once I did this, all my AD Replication errors and Exchange Errors went away

MSExchangeFBPublish event 8207, error 0x80070005

Exchange 2007 MSExchangeFBPublish event 8207, error 0x80070005 Source: http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/0c512322-0c8e-4e74-90c4-145996fdfafb/
every 50 minutes

For some reason, the "CN=Public Folders" was under:
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com

when it should be under:
CN=Folder Hierarchies,CN=Exchange Administrative Group (...),CN=Administrative Groups,CN=company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com

The "CN=FolderHierarchies" [msExchPublicFolderTreeContainer] didn't even exist!

Navegas hasta CN=Exchange Administrative Group (...),CN=Administrative Groups,CN=company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com

• Boton derecho para crear el objeto con ADSIEdit cuándo pregunta el tipo de objeto marcas:

msExchPublicFolderTreeContainer

• El nombre es solamente:

Folder Hierarchies

Luego navegas a CN=Exchange Administrative Group (...),CN=Administrative Groups,CN=company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com

• Das right clic sobre "CN=Public Folders" y le das clic en Mover

Luego navegas en la pantalla Mover hasta CN=Exchange Administrative Group (...),CN=Administrative Groups,CN=company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com
y das clic en aceptar

Reinicias Information Store
net stop msexchangeis
net start msexchangeis

The error has gone.

MAPI exception network error Migrating Exchange 2003 to 2010 on Windows SBS 2011

Fuente: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26444649.html 
Hello.

I finally found a solution.

Simply turn off the RPC filter in ISA 2004. Then is Local move request function without uninstalling ISA server.

Problem is in different RPC specification between W2k3, W2k3SP1, W2k3SP2...

I found some patches from MS, but in my case on it no longer matters.

http://social.technet.microsoft.com/Forums/en/exchange2010/thread/724ac92a-ee7f-40e0-9d7e-6d88b76dd1e5
As I migrate mailboxes from 2003 to 2010 I'm finding that when a move fails due to exceeding the baditem limit, the problem items are almost always calendar items from years back.

.\MoveMailbox –Identity user -TargetDatabase 'Mailbox Database 2012040517' -BadItemLimit 999999

MSExchangeSA - id 9188 Código de error '80072020

- Para resolverlo descarga el Exchange 2003 SP2
- Descomrpimelo
- Sobre el controlador de dominio de raíz ejecuta Z:\E3SP2ESP\setup\i386\update.exe /forestprep
- luego en el controlador del dominio donde está instalado exchange Z:\E3SP2ESP\setup\i386\update.exe /domainprep


Tipo de suceso: Error
Origen del suceso: MSExchangeSA
Categoría del suceso: General
Id. suceso: 9188
Fecha: 13/Feb/2012
Hora: 12:06:31
Usuario: No disponible
Equipo: PROLIANTML330
Descripción:
El Operador de sistema de Microsoft Exchange no pudo leer la información de pertenencia del grupo 'cn=Exchange Domain Servers,cn=Users,dc=metrocaruio,dc=local'. Código de error '80072020'.

Compruebe si el equipo local es miembro del grupo. Si no lo es, detenga todos los servicios de Microsoft Exchange, agregue el equipo local al grupo manualmente y reinicie todos los servicios.

Para más información, haga clic en http://www.microsoft.com/contentredirect.asp.

Troubleshooting ExMerge Issues: Store 'MSPST MS' was not opened Store 'MSEMS' was not opened

Troubleshooting ExMerge Issues:

Edit exmerge.ini and "uncomment" erase ";" at the beggining of the following locale Spanish lines:

; Spanish
LocalisedExchangeServerServiceName=Almacén de mensajes de Microsoft Exchange

; Spanish
LocalisedExchangeServerServiceName=Almacén de mensajes de Microsoft Exchange

Take a look to this article to set a group with the correct permissions to copy MDBDATA to PST http://support.microsoft.com/kb/292509

How to move Exchange 2000 to new hardware and keep the same server name

Basado en: http://support.microsoft.com/kb/297289

NO SIRVE PARA CONTROLADORES DE DOMINIO, SOLO PARA SERVIDORES DE EXCHANGE INDEPENDIENTES

1. To move Exchange 2000 to new hardware:
   Verify that the databases are in a "Clean Shutdown" state. To do this, type the following command at a command prompt:
   eseutil /mh database name.edb
   Make an offline backup copy of the .edb files and the .stm files for each database. You can then copy these files into the same locations on the new server after the new server is built.


2. Document the existing locations of databases and transaction logs. You will have to re-create these locations on the new system.


3. Take the existing server offline. o añade un disco duro nuevo


4. Reset the machine account for the Exchange 2000 server:
   Start Active Directory Users and Computers.
   Locate the Exchange 2000 server machine account, right-click the machine account, and then click Reset Account. (saca un system state del domain controller para deshacer cualquier cosa que falle)


5. Bring the new server online and use the same server name. (instala en otra partición u otro disco duro), configura la tarjeta de red apuntando al dns correctamente y el sufijo en el registro de dns igualmente


6. Use an Exchange 2000 Full Administrator account to log on to the new server. (o sea unele al dominio)


7. Install any components that Exchange 2000 requires, such as Internet Information Services (IIS) and the appropriate Microsoft Windows 2000 Server service packs. Note After you install the SMTP service, set the SMTP service to disabled until the Exchange installation is complete. This will prevent this server from receiving mail until Exchange is functioning properly. (cierra el puerto en el firewall o en el antispam) en brightmail Consola - Administration - Host Name - clic en Pause message scanning and delivery. Instala el service pack mas actual y si tienes tiempo el rollup y los demas updates criticos y de seguirdad, pon el antivirus con proteccion de red preferible


8. Use an Exchange 2000 Full Administrator account to log on to the new server.


9. Run Exchange 2000 Setup with the following parameter:
   Setup /disasterrecovery Make sure that you click Action-Disaster Recovery for the Messaging and Collaboration services and the Exchange System Management Tools.


10. When Setup is complete, install the Exchange 2000 service pack that was installed on the existing server by using the update.exe /disasterrecovery switch.


11. (this section is useless)
    If the following registry key does not already exist, add a DWORD value and the following registry string based on the service pack value:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup
    DWORD value name: ServicePackBuildHexadecimal value: number
    The number varies based on the service pack:
    The hexadecimal number for the retail, released version without a service pack is 1141.
    The hexadecimal number for Service Pack 1 is 1268.
    The hexadecimal number for Service Pack 2 is 1682.
    The hexadecimal number for Service Pack 3 is 1869.
    


12. Install any Exchange 2000 post-service pack hotfixes that were installed on the existing server.
13. Remove all transaction log files that were created during the installation of Exchange. For example, remove E00xxxxx.log and E00.log. Then, restore or copy the files that you backed up in step 1.
14. Just copy mdbdata to the new server use the original location, to replay all unconfirmed transactions.
    
15. Mount all of the stores after the restoration is complete. Make sure that clients can connect and that mail can flow. Edit "Unmount settings"
    

More reading.

1. 296788 (http://support.microsoft.com/kb/296788/ ) Offline backup and restoration procedures for Exchange

ZIMBRA AND EXCHANGE COEXISTENCE on a unique domain.com

OBJETIVO: Tener ciertos usuarios en Exchange y ciertos usuarios en Zimbra para un solo dominio dela empresa llamado dominio.com, hasta migrar todos de exchange a Zimbra o viceversa

Exchange Settings
Configuracion de la organizacion - Transporte de Concentradores - dominios aceptados
Cambiar de autorizado (authoritative) a Retransmision de Internet



Configuracion de la organizacion - Transporte de Concentradores - Conectores de Envío


Agregar el dominio de la empresa, si existen otros conectores no hay que tocarlos



Reenviar al servidor Zimbra el mail del dominio.com de usuarios que no se encuentren en el exchange (IP)





SOURCE:
http://www.zimbra.com/forums/administrators/1609-domain-coexistence-print.html

Configuring Zimbra as the Slave
-------------------------------

The slave system needs to accept mail for accounts that live on the
slave, but must forward all other mail for accounts on this domain to
the master.

You can accomplish this piece of mail routing by saying:

$ zmprov md dominio.com zimbraMailCatchAllAddress @dominio.com
$ zmprov md dominio.com zimbraMailCatchAllForwardingAddress @dominio.com
$ zmprov md example.com zimbraMailTransport smtp:EXCHANGEIPADDRESS

The first two commands (in combination) tell Zimbra postfix to accept
all addresses in the @dominio.com domain as valid addresses.

The third command establishes default mail routing for the domain.

Make sure to configure XCHANGEIPADDRESS para aceptar correos relay de Zimbra Server y viceversa

All these commands require that after running the whole set of them,
you do:

$ postfix stop
$ postfix start

Spam is Not Detected When Symantec Mail Security for Microsoft Exchange (SMSMSE) Transport Agents are Low Priority

Article: TECH95584

|

Created: 2009-01-17

|

Updated: 2011-03-18

Source:
http://www.symantec.com/business/support/index?page=content&id=TECH95584

Problem

Symantec Message Security for Microsoft Exchange (SMSMSE) is not detecting spam despite detecting content filtering and virus violations.


Premium Anti Spam "spam scans" number on the SMSMSE homepage never changes.

Conditions

• SMSMSE has been configured to scan messages even if marked with SCL value of minus one (-1). See the following article for details: Messages not Scanned for Spam When Marked by Microsoft Exchange with an AntiSpam X-Header. Transport Agent Debug Log Shows Message: "Whitelisted by other, bypass SPA".
  
• Microsoft's AntiSpam agents are installed and have a higher priority then the SMSMSE agents.
  
  To verify this follow these steps:
  1. On the Exchange server open the Exchange Management Shell
  2. At the prompt type the command "Get-TransportAgent". The results should look like the following:
  Identity Enabled Priority
  -------- ------- --------
  Transport Rule Agent True 1
  Journaling Agent True 2
  AD RMS Prelicensing Agent False 3
  Connection Filtering Agent True 4
  Content Filter Agent True 5
  Sender Id Agent True 6
  Sender Filter Agent True 7
  Recipient Filter Agent True 8
  SMSMSERoutingAgent True 9
  SMSMSESMTPAgent True 10
  Protocol Analysis Agent True 11
  3. If the SMSMSE agents have a lower priority (being lower on the list and having a higher priority number), this conditions is met.

Environment

• Exchange 2007/2010

Cause

If the Microsoft's AntiSpam agents have a higher priority than SMSMSE AntiSpam agents, the message may not be passed to the Premium AntiSpam scanner for verification. If Premium AntiSpam is partially working, but not detecting all spam emails, please review the following document: Title: 'Premium AntiSpam for Symantec Mail Security for Microsoft Exchange fails to detect spam' Document ID: 2007020615531854 > Web URL: http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2007020615531854?Open&seg=ent

Solution

Configure the Agents to grant the SMSMSE agent a higher priority.

• Set the SMSMSE Agents to higher priority than the Exchange AntiSpam agents:
  At the Exchange management shell, run the following 2 commands:
  1. Set-transportagent –identity “SMSMSESMTPAgent” –priority 4
  2. Set-transportagent –identity “SMSMSERoutingAgent” –priority 5
• Restart the Microsoft Exchange Transport service

OR

• Disable the built in Exchange agents by running the following 5 commands:
  At the Exchange management shell, run the following 2 commands:
  1. disable-transportagent -identity "Connection Filtering Agent"
  2. disable-transportagent -identity "Sender Id Agent"
  3. disable-transportagent -identity "Sender Filter Agent"
  4. disable-transportagent -identity "Recipient Filter Agent"
  5. disable-transportagent -identity "Protocol Analysis Agent"
• Restart the Microsoft Exchange Transport service

You might encounter an error when executing the commands about not being able to edit the config file. This can be resolved by opening the Exchange Management Console as administrator and executing the commands again.

Issues i'll have detected on my server several weeks after we deleted Exchange Server 2003 Server

Nombre de registro:Application
Origen: ExchangeStoreDB
Fecha: 30/03/2011 11:28:04
Id. del evento:231
Categoría de la tarea:Recuperación de la base de datos
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: SERVIDOR.rosalux.local
Descripción:
En '30/03/2011 11:28:02', la copia de base de datos 'Public Folder Database 0051838069' de este servidor detectó un error durante la operación de montaje. Para obtener información, consulte el registro de eventos del servidor para eventos "ExchangeStoreDb" o "msexchangerepl". La operación de montaje se reintentará automáticamente.

Nombre de registro:Application
Origen: MSExchangeRepl
Fecha: 30/03/2011 11:28:02
Id. del evento:3154
Categoría de la tarea:Servicio
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: SERVIDOR.rosalux.local
Descripción:
Active Manager no pudo montar la base de datos Public Folder Database 0051838069 en el servidor SERVIDOR.rosalux.local. Error: Una operación de Active Manager produjo un error transitorio. Vuelva a intentar la operación. Error No se pudo realizar la acción de la base de datos. Error: Error transitorio durante una operación de base de datos. Error: MapiExceptionADPropertyError: Unable to mount database. (hr=0x80004005, ec=2418)

Nombre de registro:Application
Origen: MSExchangeIS
Fecha: 30/03/2011 11:28:02
Id. del evento:9519
Categoría de la tarea:General
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: SERVIDOR.rosalux.local
Descripción:
Error al iniciar la base de datos 830f5aa5-ed91-4272-a6c8-f0faed76cac3: 0x972.
Look up of DB Info failed.

Artículo modificado en este blog
http://technet.microsoft.com/en-us/library/bb727370%28EXCHG.80,printer%29.aspx

MSExchangeIS 9519 0x972: Public Folders Container Deleted, or Missing Required Attributes

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707¹.]

Topic Last Modified: 2010-11-29

The Microsoft Exchange Database Troubleshooter Tool detected one or more MSExchangeIS 9519 events with error code 0x972 in the Application log. This indicates a failure of public folder databases to mount because the Public Folders container has been deleted or is missing needed attributes.

Explanation

---

This error can occur when the Public Folders container has been deleted from Active Directory, or if the affected Public Store is not configured to use the Public Folders container, that is, the value for the Public Folder containers msExchOwningPFTreeBL attribute does not point to the Public Store. The most likely cause for this error is that the Administrative Group that contained the Public Folders container was deleted without the Public Folders container first being moved to a new Administrative Group.

User Action

---

To resolve this issue, use the ADSI Edit, or a similar tool, to determine whether the Public Folders container exists and the msExchOwningPFTreeBL attribute is properly configured to point to the relevant Public Store.

Caution:
If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP tool, or another LDAP version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server 2003, Exchange Server 2003 or Exchange Server 2007, or both. Modify Active Directory object attributes at your own risk.

To determine the cause of the error

1. Using ADSI Edit or a similar tool, locate each administrative group object in Active Directory.

   The Administrative Group object can be found at:

   CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups,CN=Administrative group

2. Expand each Administrative Group and check for the existence of a CN=Folder Hierarchies container. If the CN=Folder Hierarchies container exists, highlight the container and verify that a CN=Public Folders object exists in the right-hand pane. If no CN=Public Folders object exists under any Administrative Group, move on to Solution 1, Recreate Folder Hierarchies and Public Folders containers. If you do find a CN=Public Folders container, proceed to step 3.

3. Right-click the CN=Public Folders object, and then click Properties.

4. In the Attributes list, select the msExchOwningPFTreeBL attribute, and then click Edit.

5. Make sure that the affected Public Folder Store is shown in the Values list. If it is not listed, proceed to Solution 2.

Solution 1: Recreate Folder Hierarchies and Public Folders containers

1. Use ADSI Edit or a similar tool to locate and expand Exchange Administrative Group (FYDIBOHF23SPDLT).

   The Exchange Administrative Group (FYDIBOHF23SPDLT) object can be found at:

   CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups

2. Right-click the Exchange Administrative Group (FYDIBOHF23SPDLT) object, click New, and then click Object.

3. In the Select a class list, select msExchPublicFolderTreeContainer, and then click Next.

4. In the Value box, type Folder Hierarchies, click Next, and then Finish.

5. Right-click the newly created Folder Hierarchies object, click New, and then click Object.

6. In the Select a class list, select msExchPFTree, and then click Next.

7. In the Value box, type Public Folders, and then click Next.

8. Click More Attributes.

9. In the Select a class list, select msExchPFTreeType,and then click Next.

10. In the Edit Attribute box, type 1, click Set, click OK, and then click Finish.

11. To assign the Public Folders container to each Public Store, right-click the Public Folders container, and then select Properties.

12. In the Attributes list, select distinguishedName, and then click Edit.

13. Copy the contents of the Value box to the clipboard, and then click Cancel.

14. For each server exhibiting the MSExchangeIS 9519 event that has error code 0x972, navigate to the Public Folder Store object. The default location for this object is:

    CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Servers, CN=ServerName, CN=InformationStore, CN=Second Storage Group.

15. If ou didn't find this key CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Servers, CN=ServerName, CN=InformationStore, CN=Second Storage Group. try looking on CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Servers, CN=ServerName, CN=Databases, CN=Public Folder Database nnnnnn. You probably deleted something via ADSI Edit when your removed legacy Exchange 2003 Servers from Active Directory.
    

16. Right-click the Public Folder Store object, and then click Properties.

17. In the Attributes list, select msExchOwningPFTree, and then click Edit.

18. Paste the value that you copied to the clipboard in step 13 into the Value box, and then click OK two times to finish.

19. Repeat steps 15 through 17 for each server that exhibits the MSExchangeIS 9519 event that has error code 0x972.

20. Restart the Microsoft Exchange Information Store service on the affected servers.

Solution 2: Repopulating the value of the msExchOwningPFTreeBL attribute for the Public Folders container object

1. Use ADSI Edit or a similar tool to locate the Public Folders object in Active Directory.

   The Public Folders object can be found at:

   CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups,CN=Administrative group,CN=Folder Hierarchies,CN=Public Folders

2. Right-click the Public Folders container, and then click Properties.

3. In the Attributes list, select distinguishedName, and then click Edit.

4. Copy the contents of the Value box to the clipboard, and then click Cancel.

5. For each server that exhibits the MSExchangeIS 9519 event that has error code 0x972, navigate to the Public Folder Store object. The default location for this object is:

   CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Servers, CN=ServerName, CN=InformationStore, CN=Second Storage Group.

6. Right-click the Public Folder Store object, and then click Properties.

7. In the Attributes list, select msExchOwningPFTree, and then click Edit.

8. Paste the value that you copied to the clipboard in step 4 into the Value box, and then click OK two times to finish.

9. Repeat steps 6 through 8 for each server that exhibits the MSExchangeIS 9519 event that has error code 0x972.

10. Restart the Microsoft Exchange Information Store service on the affected servers.

Links Table

¹http://go.microsoft.com/fwlink/?linkid=34707

Setup a Certification Authority to Issue a Certificate with Windows Server and enable RPC over HTTP on Exchange 2007 and Exchange 2010

Spanish Keywords:

Trabaja para Exchange 2010 y Exchange 2007
Primer Paso: Deshabilitar Outlook Anywhere

1. Abre la consola de Exchange
2. Navega en el árbol de la consola hasta llegar a "Configuración de Servidor" - "Acceso de Cliente"
3. Dentro de Acceso de Cliente, haz clic derecho en el nombre del servidor y escoge "Deshabilitar Outlook Anywhere" (si no tienes esta opción, no escojas "Habilitar Outlook Anywhere")
4. Cierra la consola de Exchange
5. (para Windows 2008) Clic en Inicio abre las Herramientas Administrativas - "Administrador del Servidor", navega hasta "Características", da clic en "Quitar Características" y desmarca "RPC sobre el proxy de HTTP"
6. REINICIA (no es broma)

Segundo Paso: Validar que tengas una entidad certificadora en el dominio y que tenga las opciones de certificación vía Web habilitadas

1. (para Windows 2008) Clic en Inicio abre las Herramientas Administrativas - "Administrador del Servidor", navega hasta "Funciones", en el lado derecho da clic en "Agregar Función", verifica que esté marcado lo siguiente: "Servicios de Certificate Server de Active Directory", y en los servicios de función esté marcado: "Entidad de Certificación" e "Inscripción web de entidad de certificación", si al poner continuar te solicitan otro requisitos de IIS da clic en Continuar y Finaliza el asistente
2. Si encuentras que los servicios de Certificate Server ya están instalados en el servidor prueba que la "Inscripción web de entidad de certificación" esté activada poniendo https://localhost/certsrv, si no responde ve nuevamente al "Administrador de Servidor", navega en la función de "Servicio de Certificate Server de Active Directory" y a la derecha encontrarás "Agregar servicios de función", da clic allí y luego marca "Inscripción web de entidad de certificación"
3. Si te pide reiniciar, no dudes en hacerlo
4. Al regresar prueba que puedas acceder al https://localhost/certsrv

Tercer Paso: Crear el certificado de Exchange para que funcione con un nombre principal y varios alias internos/externos

1. (para Windows 2008) Clic en Inicio, "Todos los Programas", "Microsoft Exchange 200x", abre el que dice "Exchange Management Shell"
2. Cuándo tengas acceso al Shell de Exchange, ejecuta el siguiente comando:
   
   New-ExchangeCertificate -GenerateRequest -Domainname mail.dominio.com, servidor.dominio.local, autodiscover.dominio.com, servidor -FriendlyName mail.dominio.com -PrivateKeyExportable: $True
   (al dar Enter con el teclado obtendrás un texto similar al siguiente, copia ese texto en el Portapapeles o en un documento nuevo del Bloc de Notas, no cierres la consola de comandos de Exchange)

-----BEGIN NEW CERTIFICATE REQUEST-----MIID/zCCAucCAQAwGzEZMBcGA1UEAwwQbWFpbC5kb21pbmlvLmNvbTCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALyY0mqutdzu07iQBYB3A0FVCvJfOZeq
CkM+y6cIBVYt0zf8SsdqXVXxmT2IcXsABKpBDfMgHibswSBZOmIt360RmpFp6b7q
-----END NEW CERTIFICATE REQUEST-----
Ojo que debes cambiar el comando de la siguiente forma:

• dominio.com (es tu dominio externo)
• dominio.local (es tu dominio interno)
• mail.dominio.com (nombre válido que debe responder a tu dirección pública, firewall o proxy, pregunta a tu isp o ingresa a www.cualesmiip.com para ver si el apuntador es correcto puedes usar http://centralops.net/co/DomainDossier.aspx y colocar el "mail.dominio.com" para ver si responde tu ip pública)
• servidor (nombre NETBIOS interno del servidor)
• servidor.dominio.local (nombre FQDN interno del servidor)

[PS] C:\Windows\System32>certreq -submit -attrib "CertificateTemplate:WebServer"
 c:\certreq.txt

Cuarto Paso: Crear el certificado a partir de la solicitud

1. Entra en https://localhost/certsrv
2. Da clic en "Solicitar un certificado"
3. En la siguiente Pantalla escoge "Solicitud Avanzada de Certificado"
4. En la siguiente Pantalla escoge: "Enviar una solicitud de certificado con un archivo codificado en base64 CMC o PKCS #10 o una solicitud de renovación con un archivo codificado en base64 PKCS #7."
5. Pega el contenido del texto en el bloc de notas en el casillero que dice: "Guardar Solicitud", debes incluir TODO incluyendo las lìneas -----BEGIN NEW CERTIFICATE REQUEST----------END NEW CERTIFICATE REQUEST-----
6. En Plantilla de certificado escoge: Servidor Web y luego da clic en "Enviar"
7. En la pantalla Siguiente da clic en "Descargar Certificado", por favor grábalo en la raíz del disco c:\certnew.req

Quinto Paso: Importar certificado a Exchange y activar los servicios de Exchange con el certificado

1. De vuelta en la consola de comandos de exchange y con el certificado anterior emitido corre el siguiente comando:

Import-ExchangeCertificate -path c:\certnew.cer  | Enable-ExchangeCertificate -Services IIS, SMTP, POP, IMAP
2. Si te consulta por "està seguro de reemplazar los certificados" confirmalos aceptando el cuadro de diálogo con el botón "Si"

Sexto Paso: Para poder Re-Habilitar Outlook Anywhere

1. (para Windows 2008) Clic en Inicio abre las Herramientas Administrativas - "Administrador del Servidor", navega hasta "Características", da clic en "Agregar Características" y marca "RPC sobre el proxy de HTTP", si te pide reiniciar hazlo sin dudar
2. Abre la consola de Exchange
3. Navega en el árbol de la consola hasta llegar a "Configuración de Servidor" - "Acceso de Cliente"
4. Dentro de Acceso de Cliente, haz clic derecho en el nombre del servidor y escoje "Habilitar Outlook Anywhere"
5. DEBES ESPERAR 15 minutos para poder conectar clientes via RPC desde IPADs, Outlook, etc. para clientes fuera del dominio con Windows debes exportar el certificado de la CA

Con estos procedimientos evitas los mensajes de error de certificado de Outlook 2007 cuándo se conecta a un servidor de exchange que también tiene Outlook Web App, Outlook Anywhere y donde el nombre del equipo y el del dominio interno no coincide con el del alias de internet. Desde el paso 3 se deberá ejecutar en todos los servidores de exchange del dominio, o dominios hijos de modo que se valide contra la misma entidad certificadora aunque se puede instalar una CA por dominio, no es necesaria.