Your SlideShare is downloading. ×
0
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Exchange2010
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Exchange2010

1,210

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,210
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Exchange 2010 has been re-engineered around the concept of continuous availability, in which the architecture has changed so that automatic failover protection is now provided at the individual mailbox database level instead of at the server level. In Exchange 2010, this is known as database mobility. The continuous availability architecture built into Exchange 2010 provides new benefits for organizations and their messaging administrators:Multiple server roles can co-exist on servers that provide high availability. This enables small organizations to deploy a two-server configuration provides full redundancy of mailbox data, while also providing redundant Client Access and Hub Transport services.An administrator no longer needs to build a failover cluster in order to achieve high availability. Failover clusters are now created by Exchange 2010 in a way that is invisible to the administrator. Unlike previous versions of Exchange clusters which used an Exchange-provided cluster resource DLL named ExRes.dll, Exchange 2010 no longer needs or uses a cluster resource DLL. Exchange 2010 uses only a small portion of the failover cluster components, namely, its heartbeat capabilities and the cluster database, in order to provide database mobility.Administrators can add high availability to their Exchange 2010 environment after Exchange has been deployed, without having to uninstall Exchange and then re-deploy in a highly availability configuration.Exchange 2010 provides a view of the event stream that combines the events from the operating system with the events from Exchange.Because storage group objects no longer exist in Exchange 2010, and because mailbox databases are portable across all Exchange 2010 Mailbox servers, it is very easy to move databases when neededA database availability group (DAG) is a set of up to 16 Mailbox servers that provide automatic database-level recovery from failures that affect individual databases. Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it works with the other servers in the DAG to provide automatic recovery from failures that affect mailbox databases, such as a disk failure or server failure.When an administrator creates a DAG, it is initially empty, and an object is created in Active Directory that represents the DAG. The directory object is used to store relevant information about the DAG, such as server membership information. When an administrator adds the first server to a DAG, a failover cluster is automatically created for the DAG. In addition, the infrastructure that monitors the servers for network or server failures is initiated. The failover cluster heartbeat mechanism and cluster database are then used to track and manage information about the DAG that can change quickly, such as database mount status, replication status, and last mounted location
  • http://technet.microsoft.com/en-us/library/dd297955(EXCHG.140).aspx
  • http://technet.microsoft.com/en-us/library/aa996600(EXCHG.140).aspx
  • http://technet.microsoft.com/en-us/library/dd298027(EXCHG.140).aspx
  • Transcript

    • 1. Exchange 2010<br />Antonio Soto<br />Director Operaciones España y Portugal<br />Solid Quality Mentors<br />asoto@solidq.com<br />
    • 2. Agenda<br />La nueva Exchange Management Console<br />Novedades Outlook Web Access<br />Mejoras en la Arquitectura de Bases de Datos<br />Nuevas Funcionalidades de Alta Disponibilidad<br />Políticas de Mensajería y Compliance<br />Funcionalidades de Mensajería Unificada y Correo por Voz<br />Novedades en Buzones y destinatarios<br />
    • 3. La nueva EMC<br />La gestión de bbdd se ha movido al nodo de organización<br />Registro de Comandos PowerShell<br />Posibilidad de Añadir Bosques de Exchange<br />Es posible enviar emails<br />
    • 4. DEMO<br />EMC<br />
    • 5. Novedades OWA<br />Soporte Multilenguaje<br />Vista en modo conversación<br />Envío de SMS<br />Posibilidad de adjuntar mensajes<br />Favoritos<br />Integración con Web Management Interface<br />
    • 6. DEMO<br />OWA<br />
    • 7. Mejoras en la Arquitectura de Bases de Datos<br />Los Grupos de Almacenamiento dejan de existir<br />Las bases de datos no dependen del objeto servidor<br />Se gestiona desde la organización<br />Mejoras en el esquema<br />Refactorización de tablas: Mejor rendimiento<br />
    • 8. DEMO<br />Almacenamiento<br />
    • 9. Alta Disponibilidad<br />Desaparecen<br />Local continuous replication (LCR)<br />Single copy clusters (SCC)<br />Clustered mailbox servers<br />DatabaseMobility<br />Failover automático a nivel de base de datos de buzones<br />Los roles pueden coexistir<br />Puede configurarse en cualquier momento<br />CCR y SCR dan lugar a DatabaseAvailabilityGroup (DAG)<br />Hasta 16 servidores de buzón que proporcionan recuperación automática de fallos a nivel de base de datos<br />
    • 10. Alta Disponibilidad (II)<br />Copias de Bases de Datos de buzón<br />Bases de Datos deben de tener un nombre único a nivel de organización<br />Registros de transacciones se replican en otros servidores<br />Podemos utilizar cualquier copia para backup<br />
    • 11. Demo<br />Copias de Bases de Datos<br />
    • 12. Políticas de Mensajería y Compliance (I)<br />Políticas de Retención<br />Tags de Retención<br />Tags de Políticas de Retención<br />Tags de Políticas Predeterminado<br />Tags Personales<br />Autotagging<br />
    • 13. Políticas de Mensajería y Compliance (II)<br />Descubrimiento<br />Rol de Discovery Management<br />Búsquedas en todos los buzones<br />Basado en Exchange Search<br />
    • 14. Políticas de Mensajería y Compliance (III)<br />ControlPointEncryption<br />Permite la aplicación de plantilla RMS a mensajes durante el transporte<br />No reenvío<br />Confidencial en Internet<br />AD RMS Prelicensing Agent<br />
    • 15. Demo<br />Políticas de Mensajería y Compliance<br />
    • 16. Mensajería Unificada <br />Los usuarios pueden crear y personalizar sus “auto-attendants”<br />Soporte de ASR para todos los packs de lenguaje<br />Los avisos de Voice Mail tienen un resumen de su contenido<br />Integración de Voice Mail con ControlPoint<br />Los mensajes de voz no pueden salir del correo<br />
    • 17. Funcionalidades de Buzón y Destinatarios<br />Movimiento de buzones en línea<br />Gestión de Permisos de carpetas de buzones<br />
    • 18. Resumen<br />La nueva Exchange Management Console<br />Novedades Outlook Web Access<br />Mejoras en la Arquitectura de Bases de Datos<br />Nuevas Funcionalidades de Alta Disponibilidad<br />Políticas de Mensajería y Compliance<br />Funcionalidades de Mensajería Unificada y Correo por Voz<br />Novedades en Buzones y destinatarios<br />
    • 19. Gracias!!<br />Antonio Soto<br />Director Operaciones España y Portugal<br />Solid Quality Mentors<br />asoto@solidq.com<br />

    ×