Microsoft Online Services Diagnostics and Logging (MOSDAL)

Los diagnósticos de Microsoft Online Services y el Kit de herramientas de soporte de registro (MOSDAL) realiza diagnósticos de red y recopila información de registro para las aplicaciones que se utilizan para conectarse a la de Microsoft Business Productivity Online Standard Suite (seguridad-S) o a 365 de Microsoft Office, configuración de red y configuración del sistema. Los registros que genera la herramienta de proporcionan datos que ayuda a los profesionales de soporte técnico solucionar otros problemas relacionados con el servicio, red, instalación y configuración. El Kit de herramientas de soporte de MOSDAL recopila los archivos de registro, las claves del registro y opciones de configuración que requerirían mucho tiempo y esfuerzo colección mediante el uso de herramientas independientes.

Descargar: http://www.microsoft.com/download/en/details.aspx?id=626&WT.mc_id=rss_office_365

MOSDAL support toolkit functionality

MOSDAL can be used to run network diagnostics against a particular data center where data resides. Or, MOSDAL can be used to collect system, network, and service-enabled application configuration information, logs, registry keys, file versions, and other related data. Regardless of network diagnostics or data collection execution type, the toolkit always creates a log file that is named MOSDALLog.txt to track progress as the tool runs. MOSDAL takes an average of 8 to 10 minutes to complete data collection and an average of 20 to 25 minutes to complete network diagnostics.
The MOSDAL support toolkit collects information about the configuration of the computer in the context of the user who is currently logged on to the system and who runs the tool. The toolkit can be run by an administrator or by a nonadministrative user.

Network diagnostics

The network diagnostics portion captures network configuration data together with network diagnostics output. Configuration information that is captured includes the computer’s IP address, the subnet mask, the default gateway, the DNS servers, ARP tables, the Host file, static routes, and other similar information.
Network diagnostics data includes output of pings, pathpings, nslookups, port queries, and HTTP server responses for cloud servers in a particular data center. Ping output shows the replies from a particular data center and other well-known Web sites. Pathping traces the route and the reliability of communication links between the customer and a particular Microsoft data center. The support toolkit also individually performs domain name resolution on several Microsoft online cloud servers and other popular Internet Web sites by using each assigned DNS server. Port queries output the port responses from well-known ports for Microsoft online cloud servers. HTTP server responses are the responses that are received from the cloud Web servers that host the services. The tool also performs trace routes to several popular Web sites to make sure that there is no routing issue on the customer’s end.

Data collection

The data collection component of MOSDAL collects data about the user’s system configuration, the network configuration, and the following applications:

• Microsoft .NET Framework
• Microsoft Online Service (Sign In) Client
• Microsoft Live Meeting 2007
• Microsoft Live Meeting Conferencing Add-in for Microsoft Office Outlook 2007
• Windows Internet Explorer 7
• Microsoft Office Communicator 2007 R2
• Microsoft Office Outlook 2003
• Microsoft Office Outlook 2007
• Microsoft Office Outlook 2010
• Microsoft Online Directory Synchronization tool
• Microsoft Online Migration Tool

Prominent data that is collected about the system that will help troubleshoot customer problems include Windows firewall settings, proxy settings, installed applications and hot fixes, event logs, and Msinfo32 output. For each application in this list, MOSDAL verifies that the application is installed and then collects the version number of certain program files, relevant registry keys, configuration files, logs, and other such pertinent data.

Verbose logging

MOSDAL provides eight scripts to enable or disable logging functionality in some service-based applications. They can be used to enable or disable verbose logging functionality of these applications. The scripts can be accessed and run from the Start menu or from the folder where MOSDAL is installed.

• Start menu: Start > All Programs > MOSDAL > Enable-Disable Verbose Logging >
  • Service Client

    Verbose logging of the service client (Sign In) application (SignIn_*.log)

  • Outlook 2003

    Verbose logging of Outlook (Opmlog.log)

  • Outlook 2007

    Verbose logging of Outlook (Opmlog.log)

  • Outlook 2010

    Verbose logging of Outlook (Opmlog.log)

  • Outlook 2003 Connector for Microsoft Online Services

    Verbose logging for Connector

  • Office Communicator 2007

    Verbose logging of Office Communication Online (Communicator-uccapi-*.uccapilog and Communicator.etl)

  • Live Meeting 2007

    Verbose logging of the Live Meeting (LiveMeeting-uccp-0.uccplog)

  • Live Meeting 2007 Addin

    Verbose logging of the Live Meeting Addin for Outlook (*LMAddinsLogFile#.txt)

  • DirSync

    Verbose logging in the application event log

These scripts can be used for troubleshooting by enabling verbose logging for a particular application that may be causing issues, restart the application, reproduce the issue, and then rerun MOSDAL to make sure that all the relevant logs are collected.

Network Diagnostic Configuration

The Network Diagnostics component is configured through a customizable XML file (config.xml) that is stored in the root directory of the application folder. The config.xml file is used to define the different Data Centers and the URL’s where network diagnostics can be performed. The structure of the config.xml file is important to the application, and cannot be altered. Otherwise, MOSDAL will not operate correctly. The XML structure is defined in a read-only, hidden file that is named config-schema.xsd. Any changes to the config.xml file that do not meet the requirements of the schema will cause the application to display an appropriate error message and stop.