¡Bienvenidos! <SLIDETITLE>Entry Slide</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE></KEYMESSAGE> <SLIDEBUILDS>0</SLIDEBUILDS> <SLIDESCRIPT></SLIDESCRIPT> <SLIDETRANSITION></SLIDETRANSITION> <ADDITIONALINFORMATION> <ITEM></ITEM> </ADDITIONALINFORMATION>

Exchange: Analizador de mejores prácticas (EXBPA)

¿Qué es? Exchange Sever Best Practices Analyzer ‘codifica' los principales problemas de soporte del producto en una herramienta que se puede ejecutar contra una instalación en vivo. La documentación paso por paso le informa cómo resolver cada problema

¿Qué es? La herramienta se puede ejecutar como parte de una ‘verificación de salud' proactiva que expone problemas de disponibilidad o escalabilidad. Además, la herramienta se puede ejecutar como parte de un paso de solución de problemas reactivo para diagnosticar e identificar problemas. La herramienta informará sobre asuntos que están causando problemas en ese momento dentro de la topología, y discrepancias que pudieran causar paros en el futuro.

¿Qué es? La herramienta se puede usar para documentar activamente el diseño y la configuración de la topología de Exchange. Esta información se puede usar para dar seguimiento histórico de una implementación, o proporcionar un ‘inicio rápido' para los administradores y el personal de soporte del producto quienes necesitan analizar el historial y la configuración de una implementación que no les es familiar.

¿Porqué la desarrollamos? Los administradores encuentran difícil mantenerse al día con la documentación que producimos Urgencia Relevancia Los clientes encuentran difícil dar seguimiento al cumplimiento de las mejores prácticas Exchange tiene muchas opciones y encontrar la causa raíz de un problema puede ser un proceso tedioso ~60% de los problemas de Exchange son configuraciones erróneas Tenemos muchas herramientas para reunir información, pero no muchas ofrecen auto análisis

Principios de diseño Concentrarse en el rendimiento, la escalabilidad y la disponibilidad de Exchange Servers ExBPA no verifica la configuración de seguridad Facilitar su ejecución No hay configuraciones complejas Detección automática de todo Permite que se introduzcan múltiples credenciales Sin componentes del lado del servidor que instalar Sin impacto en el rendimiento de Exchange, incluso en períodos pico

Principios de diseño No me deja colgado Mantenerlo actualizado Cada Error | Advertencia | regla no predeterminada tiene un artículo específico que le dice más acerca del problema y cómo detectarlo Mantenerlo actualizado Ofrece cada mes las actualizaciones de mejores prácticas Hace que la herramienta descargue automáticamente las actualizaciones Funciona en todos los ambientes Desde la implementación simple de SBS de un solo servidor hasta la empresa más grande Hace que la herramienta funcionen de manera transparente en redes tanto cerradas como abiertas

Herramientas adicionales ExPTA – Exchange Server Performance Troubleshooting Analyzer Tool ExDSA – Exchange Server Disaster Recovery Analyzer Tool http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyzers/default.mspx

Herramientas similares MBSA – Microsoft Baseline Security Analyzer SQLBPA – Microsoft SQL Server Best Practices Analyzer BPAs para otros productos de Microsoft están por venir

Arquitectura Una herramienta se ejecuta contra todas las versiones de Exchange Sin soporte para topologías Exchange 5.5 puras Por lo general, usted instala la herramienta en una estación de trabajo de Windows XP y ésta recopila los datos en forma remota No necesita instalar otros componentes en el servidor ExBPA está escrito en código administrado (C#) El modelo de entrada/salida se basa en XML El motor de análisis se basa en XPath

¿Dónde buscamos? Buscamos datos en… Active Directory DNS WMI Registros Metabases Supervisor de rendimiento Archivos en disco Puertos TCP/IP Primer paso de la ejecución – recopilación ExBPA recopila los datos y los coloca en el mismo espacio de nombre Segundo paso de la ejecución – análisis Las configuraciones adicionales se analizan contra las reglas definidas. La verificación entre los datos fuente es posible puesto que los datos están en la misma jerarquía

Cómo funciona Active Directory Expor- tación XML Analizador ExBPA Despachador ExBPA Analizador ExBPA Exchange Server Datos de salida colectores Exchange Server Interfaz ExBPA Reglas de XML Exchange Server Impor- tación

Permisos requeridos Domain Administrator Local Admin on Exchange Server <SLIDETITLE INCLUDE=1>Required Permissions</SLIDETITLE> <KEYWORDS>Permissions; WMI; Exchange Organization</KEYWORDS> <KEYMESSAGE>Permissions required to run ExBPA</KEYMESSAGE> <SLIDEBUILDS>5</SLIDEBUILDS> <SLIDESCRIPT> If these requirements are not met, the tool will still run in many cases, but it might not run with full functionality or it may run unacceptably slow. The Microsoft Exchange Server Best Practices Analyzer can only access the Active Directory directory service and the Exchange servers if you run the tool using credentials that have all the required permissions. To successfully run the Exchange Server Best Practices Analyzer, you must have the following permissions: [BUILD1] Domain Administrator, or a member of the Builtin\Administrators group on the Active Directory server, for enumerating Active Directory information and calling the WMI providers on the domain controller and global catalog servers. [BUILD2] Member of Local Administrators group on each Exchange server for calling the WMI providers and accessing the registry and metabase. [BUILD3] And delegated at least Exchange View Only Permissions on the Exchange organization. Exchange View Only Permissions runas /netonly /user:<domain>\<username> exbpa.exe

Prerequisitos de sistema .NET Framework 1.1 Remote Registry, WMI y Exchange Management 256MB RAM por cada 50 Servidores Exchange <SLIDETITLE INCLUDE=1>System Prerequisites</SLIDETITLE> <KEYWORDS>System Prerequisites; ExBPA</KEYWORDS> <KEYMESSAGE>System requirements for ExBPA</KEYMESSAGE> <SLIDEBUILDS>5</SLIDEBUILDS> <SLIDESCRIPT> For the Exchange Server Best Practices Analyzer to run correctly, .NET Framework 1.1 must be installed on the computer on which you will run the analyzer. [BUILD1] The Internet Information Services Common Files must also be installed on the computer to allow remote metabase access. If the IIS Common Files are not installed, Exchange Server Best Practices Analyzer will run, but will not include any metabase data in the report. If Internet Information Services, IIS Services Admin, or Exchange System Manager are installed on the system, the IIS Common Files are automatically installed. [BUILD2] The computer must have at least 256 MB of RAM. This amount of memory is sufficient for scanning up to 50 Exchange servers. For each addition of up to 50 servers in the Exchange organization, you will need an additional 256 MB of RAM on the computer that is running the tool. For example, if you have between 50 and 100 Exchange servers in your organization, you must have at least 512 MB of RAM on the computer that is running the tool. If you have between 100 and 150 Exchange servers in your organization, you must have at least 768 MB of RAM. 2MB por cada Servidor Exchange Active Directory

Demostración Exchange Best Practices Analyzer Examinando la Organización de Exchange Instalando ExBPA

Funciones de Diágnostico Recolección de Información Pruebas Específicas Generación de Reportes <SLIDETITLE INCLUDE=1>Diagnostic Functions</SLIDETITLE> <KEYWORDS>ExBPA; Registry; Active Directory; Exchange Migrate</KEYWORDS> <KEYMESSAGE>Explain the process that ExBPA executes.</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> As a diagnostics tool, the Exchange Best Practices Analyzer performs three main functions. First it gathers configuration information on the Exchange organization and the Exchange servers from many sources. As was mentioned earlier, this information may come from Active Directory, the server’s registry, or the Exchange metabase, among others. [BUILD1] Next, it performs the test that you specify in the console, Health Check, Connectivity, or Baseline. The health check scans for errors, warnings, non-default configurations, recent changes, and more. The health check compares the results against the database of best practices configuration. You should run a Health Check scan if you want to check the health of your Exchange Organization, or if you want to troubleshoot a particular problem. The Connectivity Test Scan tests network connections and permissions on each Exchange Server that is specified in the scope. You should run a Connectivity Test scan if you suspect a problem with permissions access or if you have firewalls in the topology. The Baseline scan checks for deviations from the baseline values that you set. The report generated by baseline scans will identify any configuration changes made since the initial baseline scan. [BUILD2] After collecting the information you requested, the Analyzer formats the information into an easy to navigate report. Each error or warning is clearly marked and it provides you with suggestions on how to fix any problems it finds. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>There are several ways you can use this information once you have it.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/exchange/downloads/2003/exbpa/overview.mspx</ITEM> </ADDITIONALINFORMATION>

Escenarios de Uso Comparación con mejoras prácticas Comparación de valores predeterminados Reportar cambios recientes Identificar causas de problemas Comparación con Línea Base <SLIDETITLE INCLUDE=1>ExBPA Scenarios</SLIDETITLE> <KEYWORDS>ExBPA; Reports; Best Practices; Troubleshooting</KEYWORDS> <KEYMESSAGE>Suggest several ways to use ExBPA</KEYMESSAGE> <SLIDEBUILDS>4</SLIDEBUILDS> <SLIDESCRIPT> First and foremost, you can use the Exchange Server Best Practices Analyzer to proactively verify that your configuration is set according to recommended best practices. The Exchange Server Best Practices Analyzer uses a configuration file to determine what information to gather from the Exchange Server organization. Each time you launch the analyzer, it will attempt to connect to the Microsoft web site and download the latest best practices rule set. It compares the data that it gathers to this set of rules. For every issue, the Exchange Server Best Practices Analyzer provides three kinds of data: It reports what it found in the Exchange Server organization that it scanned. It provides the recommended configuration. And it provides links to more detailed information about the issue and related topics. [BUILD1] The analyzer also reports all settings that are different from the default settings. [BUILD2] You can create reports containing recent configuration changes. This functionality helps you diagnose problems that are caused by changes in the Exchange Server organization. [BUILD3] Using this information, ExBPA helps you identify the root source of an issue, often before the problem starts to affect the end user. [BUILD4] Finally, the analyzer can compare the current configuration of the Exchange Organization against a baseline configuration you’ve created. In this way, you can keep track of any changes that other Exchange Administrators make to their local servers and correct these changes if they do not follow your architectural plan. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>Now let’s prepare our analyzer to run an initial scan of our Exchange Servers.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://blogs.technet.com/exchange/archive/2005/06/24/406846.aspx</ITEM> </ADDITIONALINFORMATION>

Tipos de reglas Error Advertencia No predeterminado Encontramos algo que está causando, o causará, un problema Ejemplo: No hay un tamaño máximo de mensajes establecido en la organización Advertencia Encontramos algo que parece sospechoso Ejemplo: Un acuerdo de conexión ADC está programado en ‘Nunca’ No predeterminado Encontramos una configuración que se ha cambiado Ejemplo: Uno de los muchos parámetros de almacenamiento ha sido ajustado/debilitado

Tipos de reglas Tiempo Mejor práctica Información Encontramos algo que se cambió durante los últimos durante los últimos 5 días Ejemplo: Se cambió el costo en un conector SMTP Mejor práctica Encontramos que no se siguió una mejor práctica Ejemplo: Los paros de Dr. Watson no se están cargando a Microsoft para su análisis Información Encontramos algo interesante Ejemplo: Su servidor tiene instalados 8 procesadores

Configurando un prueba de ExBPA Establecer un nombre Seleccionar objetos Seleccionar tipo Establecer velocidad <SLIDETITLE INCLUDE=1>Setting Up an ExBPA Scan</SLIDETITLE> <KEYWORDS>ExBPA; Best Practices Scan</KEYWORDS> <KEYMESSAGE>Steps for initiating a scan.</KEYMESSAGE> <SLIDEBUILDS>4</SLIDEBUILDS> <SLIDESCRIPT> Start by creating a unique label on the “Start a New Best Practices Scan” page. If you choose to view an existing report, you can identify the reports by the label that you enter here. [BUILD1] The scope of the scan determines what servers will be scanned. To specify the scope of the scan, select the servers or administrative groups that you want to scan. When setting the scope for the scan, you can select the whole Exchange Server organization, one or more administrative groups, or one or more servers from any administrative group in the organization. [BUILD2] Next, you’ll choose the type of scan to perform, either Health Check, Connectivity Test, or a Baseline scan, as we discussed earlier. [BUILD3] After setting the type of scan, you’ll specify the network speed. The analyzer provides four options to choose from, Fast LAN, LAN, Fast WAN, and WAN. The analyzer will use the network speed setting to estimate the time that is required to complete the scan and to set the time-out value for commands sent by the analyzer. During the scan, the Exchange Server Best Practices Analyzer waits for a response from the servers. If it does not receive a response in the specified time, the Exchange Server Best Practices Analyzer marks the server as unreachable, instead of continuing to wait. On slower networks, the time-out is longer to account for network latency. It is recommended that you select the slowest link in your topology for this setting so that the Analyzer does not time out too quickly.

Demostración Exchange Best Practices Analyzer Ejecutando ExBPA

Información Reportada Baseline Mismatch Full Issues List Detailed View List Detailed View – Full Issues List Best Practice Full Issues List Detailed View List Detailed View – Full Issues List Recent Changes Full Issues List Detailed View List Detailed View – Full Issues List Errors Critical Issues List Full Issues List Detailed View List Detailed View – Full Issues List Information Detailed View List Detailed View – Full Issues List Warning Full Issues List Detailed View List Detailed View – Full Issues List Non-default Configuration Full Issues List Detailed View List Detailed View – Full Issues List <SLIDETITLE INCLUDE=1>Reported Information</SLIDETITLE> <KEYWORDS>Errors; Warnings; Non-Default Configuration; Recent Change; Baseline Mismatch; Information</KEYWORDS> <KEYMESSAGE>Explore the types of information found in the reports.</KEYMESSAGE> <SLIDEBUILDS>6</SLIDEBUILDS> <SLIDESCRIPT> Within each report view, the Microsoft Exchange Server Best Practices Analyzer Tool will display six types of information. An error indicates a critical issue that requires a change for resolution. For example, an instance of a server that is down or a server that is unreachable is an error. Errors will only appear in the Critical Issues list, Full Issues List, Detailed View List, and Detailed View—Full Issues List reports. If you have determined that an identified error is the result of an intentional Exchange architectural decision made by your team, you may disable the rule that creates the error. If you disable an error, the Analyzer will display the error on the Disabled Issues List view. [BUILD1] A warning indicates an issue that is not a recommended best practice. The issue might require a change for resolution, or it might be a known issue that does not require a change in your Exchange Server organization. For example, a service that is not started on a server is a warning. If you disable a warning, it will appear in the Disabled Issues List. [BUILD2] Non-default configuration indicates a setting that has been changed from the default value. If the Analyzer determines that a non-default configuration is an error or a warning, it identifies the non-default configuration with the appropriate error symbol or warning symbol elsewhere in the report, in addition to identifying it as a non-default configuration. You may again disable the detection of individual non-default configuration warnings and these rules will be moved to the Disabled Issues List. [BUILD3] A recent change icon indicates a setting that has changed in the last 48 hours. The Exchange Server Best Practices Analyzer can identify as recent changes only those settings that have a last modified time property. If the Analyzer determines that a recent change setting is an error, a warning, or a non-default configuration, the Analyzer identifies the recent change with the appropriate error symbol, warning symbol, or non-default configuration symbol elsewhere in the report, in addition to identifying it as a recent change.

Respondiendo a los eventos <SLIDETITLE INCLUDE=1>Responding to Issues</SLIDETITLE> <KEYWORDS>ExBPA; Exchange Issues; Troubleshooting</KEYWORDS> <KEYMESSAGE>ExBPA provides information on each issue it identifies.</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> After running a scan on your Exchange organization, you could have issues listed in the report that you want to resolve. If you click an issue, an explanation and three options will be displayed. [BUILD1] The first option will open the help file to the relevant ExBPA Article. The articles correspond to the rules and resulting messages generated by the Analyzer. Each article describes a single error, warning, or non-default configuration message that could be detected by the Exchange Server Best Practices Analyzer. [BUILD2] The second and third options allow you to disable the issue for one or for all servers in the Exchange Organization. Issues that are disabled will not be displayed in the Critical Issues list or the Full Issues list. Again to see the issues you have disabled, go to the Disabled Issues list. From this list, you can re-enable issues so that they will be displayed again in the normal report views. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>The Exchange Server Best Practices Analyzer does not make changes to your Exchange organization to resolve issues. It only displays information about how to resolve issues.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.exchange.tools</ITEM> </ADDITIONALINFORMATION>

Demostración Exchange Best Practices Analyzer Observando la información reportada

Integración con MOM 2005 Microsoft Operations Manager 2005 <SLIDETITLE INCLUDE=1>ExBPA Management Pack</SLIDETITLE> <KEYWORDS>MOM2005; ExBPA; Management Pack</KEYWORDS> <KEYMESSAGE>Introduce the ExBPA Management Pack for MOM2005</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> The ExBPA Management Pack can be used to deploy the Analyzer on computers running Microsoft Exchange Server 5.5, Exchange 2000 Server and Exchange Server 2003. Using a timed event, the tool will run automatically on each server and write any identified performance, scalability and availability issues to the Windows Event Log. The ExBPA Management Pack will interpret these events and generate the appropriate alerts on the MOM Operators Console. [BUILD1] The Management Pack automates the scanning by creating two timed event rules. The first rule runs on the MOM Management Server and collects global organization data from Active Directory. By default, this is scheduled to run once a day at 11:10 p.m. The rule runs a Visual Basic script from MOM, which in turn launches the command-line version of the Analyzer. [BUILD2] The second rule runs the MOM Agent on each server in the Exchange Server Best Practices Analyzer server group. This rule collects information from individual servers using a similar scheduled event at 11:20 p.m. every day. This also runs as a script using the command-line version of the Analyzer. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>To work with MOM 2005, ExBPA must treat the output of its scans differently.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/downloads/details.aspx?familyid=583FA809-F151-4784-AFD4-44D0B7687E6A&displaylang=en</ITEM> </ADDITIONALINFORMATION> Microsoft Operations Manager 2005

ExBPA Management Pack C:\Program Files\ExBPA <SLIDETITLE INCLUDE=1>ExBPA Management Pack Output</SLIDETITLE> <KEYWORDS>MOM2005; ExBPA; Management Pack</KEYWORDS> <KEYMESSAGE>Introduce the ExBPA Management Pack for MOM2005</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> Every time an ExBPA rule runs, a new XML data file is written to the ExBPA programs folder on the local server. As part of the execution script, older data files are automatically cleaned up. At any time, you may see up to two data files in this folder. [BUILD1] The rule created in MOM 2005 uses a command-line switch to tell the Analyzer engine to output the results of the analysis to the Windows Event Log. For each problem found, an event will be written to the Application log on the local server. The content will be similar to what is typically seen when you use the Exchange Server Best Practices Analyzer user interface. [BUILD2] As the events are written to the Application log on each Exchange server, the ExBPA Management Pack will identify Critical Errors and Warnings, and display them on the MOM 2005 Operator Console. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>Now we’ll work with this management pack on our network.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/downloads/details.aspx?familyid=583FA809-F151-4784-AFD4-44D0B7687E6A&displaylang=en</ITEM> </ADDITIONALINFORMATION> C:\Program Files\ExBPA

Demostración Exchange Best Practices Analyzer Integración con MOM 2005

Resumen de la sesión Uso de ExBPA y conocimiento de otras herramientas de BPA Integración con MOM 2005 Considere usar las recomendaciones de ExBPA <SLIDETITLE INCLUDE=1>Summary</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>Summary</KEYMESSAGE> <SLIDEBUILDS>0</SLIDEBUILDS> <SLIDESCRIPT> Throughout this session, we may not have mentioned this, but these tools are free to download from our web site. Go to the Exchange Best Practices Analyzer page on the Exchange Server 2003 web site and download latest version of the Analyzer today. The address is www.microsoft.com/exchange/downloads/2003/ExBPA. While at this site, you’ll also find the ExBPA Management Pack download and additional information and tips on using the Analyzer. [BUILD1] Install the analyzer and explore the features on your own, create a baseline configuration report for your Exchange Organization and schedule a weekly scan so you can keep track of changes made to the Organization. [BUILD2] Make sure you periodically review the results of the scans and implement Analyzer’s suggestions where they make sense for your deployment. Understand that the Articles written for the Analyzer provide general prescriptive guidance, so not every issue it finds will be relevant to your organization. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>To get more information on the products and technologies we have covered today, we have some online resources available that can help</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx</ITEM> </ADDITIONALINFORMATION>

Microsoft Learning Recursos de entrenamiento offline <SLIDETITLE>Microsoft Learning</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>Talk about the eLearning course.</KEYMESSAGE> <SLIDEBUILDS>0</SLIDEBUILDS> <SLIDESCRIPT> Microsoft Learning (formerly Microsoft Training and Certification, and Microsoft Press) develops courseware called Microsoft Official Curriculum (MOC), which includes eLearning, Microsoft Press Books, workshops, clinics, and Microsoft Skills Assessment. MOC is offered in instructor-led environments; it offers comprehensive training courses for IT professionals as well as support and implementation solutions using Microsoft products and technologies. The course that best supports this session is Administering a Microsoft SQL Server 2000 Database, which is currently available. For more information, visit www.microsoft.com/learning. </SLIDESCRIPT> <SLIDETRANSITION>This session is brought to you by TechNet, so what is TechNet?</SLIDETRANSITION> <ADDITIONALINFORMATION><ITEM></ITEM></ADDITIONALINFORMATION> http://www.microsoft.com/learning/

Microsoft eLearning Recursos de entrenamiento online https://www.microsoftelearning.com/

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.