-
论坛网址：https://dianbai.wiki（可微信分享）、https://0668.es、https://0668.cc（全加密访问）
英语随便发! (1人在浏览)
- 主题发起人 安臣
- 开始时间
- 注册
- 2004-08-16
- 帖子
- 7,441
- 反馈评分
- 65
- 点数
- 71
The Microsoft Exchange Server Best Practices Analyzer Tool automatically examines an Exchange Server deployment and determines if the configuration is set according to Microsoft best practices. You can install the tool on a client computer that is running Microsoft .NET Framework 1.1. With the proper network access, the tool can examine all your Active Directory directory service and Exchange servers to:
Generate a list of issues, such as suboptimal configuration settings or unsupported or nonrecommended options.
Judge the general health of a system
Help troubleshoot specific problems
You can run the tool against an entire deployment, just a specific server, or a set of servers.
Exchange Server Best Practices Analyzer examines servers running Exchange 2000 Server and Exchange Server 2003 as well as Exchange Server 5.5 servers when they are part of a mixed-mode topology. It cannot examine a pure Exchange Server 5.5 deployment.
Download Exchange Server Best Practices Analyzer from the Microsoft Download Center.
State-of-the-Art Expert System Analysis
Exchange Server Best Practices Analyzer has several components that act together as an expert system to verify a deployment’s overall health. This component model produces a highly flexible and adaptable tool. What those components are and how they fit together is illustrated in the following diagram.
Figure 1.1 Components of Exchange Server Best Practices Analyzer
See full-sized image.
Exchange Server Best Practices Analyzer is composed of a core set of libraries that contain:
A dispatcher
A set of collectors for gathering data from a deployment
An analyzer that processes rules on the collected data and generates issues based on the results
The dispatcher is driven by a configuration file that contains:
All the settings it needs to gather
The rules it needs to analyze the settings
The dispatcher then creates a data file that contains all the data gathered and the issues found. These libraries are wrapped in a user interface (UI) so that you can easily execute a scan and examine the results. The UI also has online Help links to assist you both in using the tool and troubleshooting any reported issues.
Component Descriptions
Exchange Server Best Practices Analyzer is composed of the following components.
Configuration. This is an XML file that contains information about all the:
Configuration settings and tests that the tool accesses
Rules that determine whether the data retrieved meets Microsoft best practices
This configuration file is modified on a frequent basis as the data and rules are refined over time. You can set Exchange Server Best Practices Analyzer to automatically look for and download the latest version of the configuration file prior to a run. Or, for closed networks that do not have Internet access, you can use a local copy of the configuration file.
Help. The Help file is a standard Help document, but like the configuration file, the tool can be configured to download the latest version prior to a run or to use a local copy.
Detailed articles. Several hundred detailed articles have been created to explain the various errors and warnings that this tool generates. You can use Exchange Server Best Practices Analyzer to access the articles on the Web, or you can use local copies.
Dispatcher. The dispatcher is the core of Exchange Server Best Practices Analyzer and is responsible for four steps:
Runs through the configuration file
Initializes collectors, which retrieve data or run tests
Starts the analyzer, which executes the rules contained in the configuration file
Generates a list of issues based on the rules
Collectors. For each type of data you retrieve, a collector does the retrieval. For example, the Directory collector retrieves properties from Active Directory. A collector can also execute tests rather than retrieve configuration information. An example of this kind of collector is the Protocol collector, which you can use to send verbs over specific ports and to save the response.
Analyzer. The analyzer is the rules engine. Using XPath-type references, it can compare retrieved values across several properties and generate messages based on those values. For instance, you might use it to look at the amount of RAM on a server and check to see if the /3GB operating system setting is correct for the hardware configuration.
ExBPA core engine. ExBPA is the name of the binary. The core engine consists of the dispatcher, a set of collectors, and the analyzer.
UI. You can execute the core engine through one of two UIs:
Command line version, which you can use for scripting the execution
Graphical user interface (GUI) to execute a run and examine the results
Data file. All the data that this tool retrieves and all the messages that it generates based on its analysis are saved in an XML data file. This file can then be viewed immediately or at a later time for historical information. You can use the GUI to view the analysis as well as all the data that led to the analysis, creating a system snapshot for capturing a point-in-time configuration of a deployment.
Generate a list of issues, such as suboptimal configuration settings or unsupported or nonrecommended options.
Judge the general health of a system
Help troubleshoot specific problems
You can run the tool against an entire deployment, just a specific server, or a set of servers.
Exchange Server Best Practices Analyzer examines servers running Exchange 2000 Server and Exchange Server 2003 as well as Exchange Server 5.5 servers when they are part of a mixed-mode topology. It cannot examine a pure Exchange Server 5.5 deployment.
Download Exchange Server Best Practices Analyzer from the Microsoft Download Center.
State-of-the-Art Expert System Analysis
Exchange Server Best Practices Analyzer has several components that act together as an expert system to verify a deployment’s overall health. This component model produces a highly flexible and adaptable tool. What those components are and how they fit together is illustrated in the following diagram.
Figure 1.1 Components of Exchange Server Best Practices Analyzer
See full-sized image.
Exchange Server Best Practices Analyzer is composed of a core set of libraries that contain:
A dispatcher
A set of collectors for gathering data from a deployment
An analyzer that processes rules on the collected data and generates issues based on the results
The dispatcher is driven by a configuration file that contains:
All the settings it needs to gather
The rules it needs to analyze the settings
The dispatcher then creates a data file that contains all the data gathered and the issues found. These libraries are wrapped in a user interface (UI) so that you can easily execute a scan and examine the results. The UI also has online Help links to assist you both in using the tool and troubleshooting any reported issues.
Component Descriptions
Exchange Server Best Practices Analyzer is composed of the following components.
Configuration. This is an XML file that contains information about all the:
Configuration settings and tests that the tool accesses
Rules that determine whether the data retrieved meets Microsoft best practices
This configuration file is modified on a frequent basis as the data and rules are refined over time. You can set Exchange Server Best Practices Analyzer to automatically look for and download the latest version of the configuration file prior to a run. Or, for closed networks that do not have Internet access, you can use a local copy of the configuration file.
Help. The Help file is a standard Help document, but like the configuration file, the tool can be configured to download the latest version prior to a run or to use a local copy.
Detailed articles. Several hundred detailed articles have been created to explain the various errors and warnings that this tool generates. You can use Exchange Server Best Practices Analyzer to access the articles on the Web, or you can use local copies.
Dispatcher. The dispatcher is the core of Exchange Server Best Practices Analyzer and is responsible for four steps:
Runs through the configuration file
Initializes collectors, which retrieve data or run tests
Starts the analyzer, which executes the rules contained in the configuration file
Generates a list of issues based on the rules
Collectors. For each type of data you retrieve, a collector does the retrieval. For example, the Directory collector retrieves properties from Active Directory. A collector can also execute tests rather than retrieve configuration information. An example of this kind of collector is the Protocol collector, which you can use to send verbs over specific ports and to save the response.
Analyzer. The analyzer is the rules engine. Using XPath-type references, it can compare retrieved values across several properties and generate messages based on those values. For instance, you might use it to look at the amount of RAM on a server and check to see if the /3GB operating system setting is correct for the hardware configuration.
ExBPA core engine. ExBPA is the name of the binary. The core engine consists of the dispatcher, a set of collectors, and the analyzer.
UI. You can execute the core engine through one of two UIs:
Command line version, which you can use for scripting the execution
Graphical user interface (GUI) to execute a run and examine the results
Data file. All the data that this tool retrieves and all the messages that it generates based on its analysis are saved in an XML data file. This file can then be viewed immediately or at a later time for historical information. You can use the GUI to view the analysis as well as all the data that led to the analysis, creating a system snapshot for capturing a point-in-time configuration of a deployment.
- 注册
- 2004-10-29
- 帖子
- 2,035
- 反馈评分
- 0
- 点数
- 61
- 年龄
- 45
- 性别
- 男
创始人说的话,我本人做了个翻译!请大家读读.
微软交换伺候器最好地自动地练习分析者工具调查一个交换伺候器配置而且决定如果结构被依照微软设定最好练习。 你能安装在一部正在跑微软的客户计算机上的工具结构 1.1.。藉由适当的网络通路，工具能调查你所有的活跃目录目录服务并且交换伺候器:
产生一连串的议题, 像是次最佳的结构设定或不支持或非推荐了选项。
判断系统的一般健康
帮忙修理特定的问题
你能跑对抗一个整个的配置工具, 只是一个特定的伺候器 , 或一组伺候器。
当他们是一个混合- 模态地志学的部份时候，最交换伺候器分析者所调查的练习跑交换 2000 伺候器和交换伺候器 2003 连同交换伺候器 5.5 伺候器的伺候器。 资讯科技不能够调查一个纯粹的交换伺候器 5.5 配置。最下载交换伺候器练习来自微软下载中心的分析者。
艺术级专家系统分析
交换伺候器最好练习分析者有一些成份行为一起当查证配置的全部健康的一个专家系统。 这一个成份模型生产一个高度有柔性和能适应的工具。 什么那些成份是，而且他们如何结合在下列的图表中被举例。
交换伺候器的图 1.1 成份最好练习分析者,见到标准尺寸的图像。
交换伺候器最好练习分析者由包含的图书馆的核心组组成:
一个发送者
聚集来自一个配置的数据一组搜集家
一个处理关于收集成的数据规则，而且产生以结果为基础的议题分析者
发送者被一个包含的结构文件驱使:
规则它需要分析设定
发送者然后产生一个包含所有的数据数据文件聚集而且议题发现。 这些图书馆被装进一个使用者接口 (UI) ，以便你能容易地运行扫描而且调查结果。UI 也有在线帮忙联编协助你两个使用工具而且修理任何报告了议题。
成份描述
交换伺候器最好练习分析者由下列的成份组成。
结构。 这是一个包含关于的资讯可扩展标示语言文件所有的那:
结构设定和测试工具存取
决定数据是否取回会微软最好的规则练习
这一个结构文件以时常发生的方式被修正如数据，而且规则随着时间的过去被精炼。你能最设定交换伺候器练习自动地在～之前奔跑找寻而且下载最新版结构申请的分析者。 或,对于不让英特网存取的关闭网络，你能使用结构文件的地方副本。
帮忙。 帮忙文件是一个标准帮助证明, 但是像结构文件，工具能配置成在～之前奔跑下载最新版本并且使用地方副本。
详细的文章。一些百个详细的文章已经被产生解释各种不同的错误和警告这一个工具产生。 你能最使用交换伺候器练习存取在网络上的文章分析者,或你能使用地方副本。
发送者。 发送者是交换伺候器的核心最好练习分析者并且负责四个步骤:
奔跑经过结构申请
设定搜集家初值, 取回数据，或跑测试
开始分析者, 运行被包含在结构文件的规则
产生一连串的以规则为基础的议题
搜集家。 对于每个类型的数据你取回,一位搜集家做取回。 举例来说，目录搜集家取回来自活跃的目录财产。 一位搜集家也能运行测试并非取回结构数据。 一个这种搜集家的例子是记录搜集家, 你能使用送在特性港口上的动词并且解救回应。
分析者。 分析者是准则引擎。 使用 XPath- 类型的叁考,它能比较取回横过一些财产的价值而且产生以那些价值为基础的信息。 举例来说，你可能使用它在伺候器和检查上审查随机存取储存器的数量见到如果那 /3 GB 操作系统人设定对硬件结构是正确的。
ExBPA 核心引擎。 ExBPA 是二进的名字。 核心引擎有发送者，一组搜集家 , 和分析者。
UI。 你能经过二 UIs 之一运行核心引擎:
命令线版本, 你能为手写体实行使用
图解式的使用者接口 (图形用户接口) 运行奔跑而且调查结果
数据申请。 所有的这一个工具取回的数据和所有的信息它产生基于它的分析在一个可扩展标示语言数据文件中被解救。 然后这一个文件能被立刻或在稍后为历史的数据看。 你能使用图形用户接口看分析和所有的导致分析的数据,为取得点创造一个系统迅速射击- 及时一个配置的结构。
微软交换伺候器最好地自动地练习分析者工具调查一个交换伺候器配置而且决定如果结构被依照微软设定最好练习。 你能安装在一部正在跑微软的客户计算机上的工具结构 1.1.。藉由适当的网络通路，工具能调查你所有的活跃目录目录服务并且交换伺候器:
产生一连串的议题, 像是次最佳的结构设定或不支持或非推荐了选项。
判断系统的一般健康
帮忙修理特定的问题
你能跑对抗一个整个的配置工具, 只是一个特定的伺候器 , 或一组伺候器。
当他们是一个混合- 模态地志学的部份时候，最交换伺候器分析者所调查的练习跑交换 2000 伺候器和交换伺候器 2003 连同交换伺候器 5.5 伺候器的伺候器。 资讯科技不能够调查一个纯粹的交换伺候器 5.5 配置。最下载交换伺候器练习来自微软下载中心的分析者。
艺术级专家系统分析
交换伺候器最好练习分析者有一些成份行为一起当查证配置的全部健康的一个专家系统。 这一个成份模型生产一个高度有柔性和能适应的工具。 什么那些成份是，而且他们如何结合在下列的图表中被举例。
交换伺候器的图 1.1 成份最好练习分析者,见到标准尺寸的图像。
交换伺候器最好练习分析者由包含的图书馆的核心组组成:
一个发送者
聚集来自一个配置的数据一组搜集家
一个处理关于收集成的数据规则，而且产生以结果为基础的议题分析者
发送者被一个包含的结构文件驱使:
规则它需要分析设定
发送者然后产生一个包含所有的数据数据文件聚集而且议题发现。 这些图书馆被装进一个使用者接口 (UI) ，以便你能容易地运行扫描而且调查结果。UI 也有在线帮忙联编协助你两个使用工具而且修理任何报告了议题。
成份描述
交换伺候器最好练习分析者由下列的成份组成。
结构。 这是一个包含关于的资讯可扩展标示语言文件所有的那:
结构设定和测试工具存取
决定数据是否取回会微软最好的规则练习
这一个结构文件以时常发生的方式被修正如数据，而且规则随着时间的过去被精炼。你能最设定交换伺候器练习自动地在～之前奔跑找寻而且下载最新版结构申请的分析者。 或,对于不让英特网存取的关闭网络，你能使用结构文件的地方副本。
帮忙。 帮忙文件是一个标准帮助证明, 但是像结构文件，工具能配置成在～之前奔跑下载最新版本并且使用地方副本。
详细的文章。一些百个详细的文章已经被产生解释各种不同的错误和警告这一个工具产生。 你能最使用交换伺候器练习存取在网络上的文章分析者,或你能使用地方副本。
发送者。 发送者是交换伺候器的核心最好练习分析者并且负责四个步骤:
奔跑经过结构申请
设定搜集家初值, 取回数据，或跑测试
开始分析者, 运行被包含在结构文件的规则
产生一连串的以规则为基础的议题
搜集家。 对于每个类型的数据你取回,一位搜集家做取回。 举例来说，目录搜集家取回来自活跃的目录财产。 一位搜集家也能运行测试并非取回结构数据。 一个这种搜集家的例子是记录搜集家, 你能使用送在特性港口上的动词并且解救回应。
分析者。 分析者是准则引擎。 使用 XPath- 类型的叁考,它能比较取回横过一些财产的价值而且产生以那些价值为基础的信息。 举例来说，你可能使用它在伺候器和检查上审查随机存取储存器的数量见到如果那 /3 GB 操作系统人设定对硬件结构是正确的。
ExBPA 核心引擎。 ExBPA 是二进的名字。 核心引擎有发送者，一组搜集家 , 和分析者。
UI。 你能经过二 UIs 之一运行核心引擎:
命令线版本, 你能为手写体实行使用
图解式的使用者接口 (图形用户接口) 运行奔跑而且调查结果
数据申请。 所有的这一个工具取回的数据和所有的信息它产生基于它的分析在一个可扩展标示语言数据文件中被解救。 然后这一个文件能被立刻或在稍后为历史的数据看。 你能使用图形用户接口看分析和所有的导致分析的数据,为取得点创造一个系统迅速射击- 及时一个配置的结构。
