Microsoft System Center Operations Manager文件

1、operations manager 2007 deployment guidemicrosoft corporationpublished: february, 2008authorchristopher foxinformation in this document, including url and other internet web site references, is subject to change without notice. unless otherwise noted, the companies, organizations, products, domain n

2、ames, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. complying with all applicable copyright law

3、s is the responsibility of the user. without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpos

4、e, without the express written permission of microsoft corporation. microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. except as expressly provided in any written license agreement from microsoft, t

5、he furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.© 2007 microsoft corporation. all rights reserved.microsoft, ms-dos, windows, windows server, windows vista, and activesync are either registered trademarks or t

6、rademarks of microsoft corporation in the united states and/or other countries.all other trademarks are property of their respective owners.revision historyrelease datechangesmarch 2007original release of this guidejuly 2007updated procedures for clustering rms and bug fixesaugust 2007security proce

7、dures fixes and minor updates.february 2008· updated supported cluster configuration for sp1· updated rms clustering procedures for sp1· updated certificate import and gateway server deployment procedures for sp1· updated account planning for reporting and rms for sp1.· bug

8、fixes· added documentation roadmapcontentsroadmap for the operations manager 2007 guides11about the operations manager 2007 deployment guide11operations manager 2007 deployment scenarios12in this section12about operations manager 2007 deployment scenarios12in this section13server role compatibi

9、lity13see also16single server, single management group scenario16operations manager 2007 services18operations manager 2007 server roles18restrictions18gateway server18high availability and redundancy19common uses19ports used19multiple server, single management group scenario19operations ma

10、nager 2007 features21operations manager 2007 server roles21restrictions21installed languages22consolidated views22function22administrative or other business needs22common uses22ports used22connected management groups scenario23operations manager 2007 services24operations manager 

11、2007 server roles25restrictions25common uses25ports used25operations manager 2007 environmental prerequisites26in this section26about operations manager 2007 environmental prerequisites26see also27infrastructure27active directory domain services27domain functional level27forest functional level28dns

12、28security considerations28trust boundaries29kerberos29certificates29certification authority29microsoft certificate services30accounts and groups30role-based security accounts and groups30notification accounts and groups32service accounts33run as accounts33agent and agentless monitoring34clients wit

13、h agents installed34agents inside a trust boundary34discovery34installation34ongoing management35agents outside a trust boundary35manually installed agents36agentless monitoring36deploying operations manager 2007 scenarios36in this section36before deployment36sql server 2005 for operations manager 2

14、00737selecting a sql server 2005 version37sql server 2005 disk subsystem configuration38best practices38sql server version and service packs38sql server 2005 configuration39best practices for sql server configuration for operationsmanager database39sql server broker service39deploying

15、 the single server, single management group scenario39before you start40installing sql server 200540installing operations manager 2007 single server configuration42confirming the health of the management group46deploying reporting in the single server, single management group scenario47ins

16、talling operations manager 2007 reporting single server configuration48confirming the health of reporting services49about audit collection services (acs) in operations manager 200750acs forwarders50acs collector50acs database51see also52acs security in operations manager 200752limited access to

17、 audit events52limited communication for acs forwarders53acs forwarders separated from the acs collector by a firewall53see also53capacity planning for acs53acs collector queue53acs collector memory54acs database recommendations56see also56how to deploy audit collection services (acs)56procedures57s

18、ee also57how to install an acs collector and database58procedures58see also60how to enable acs forwarders in operations manager 200760procedures60see also61deploying client monitoring in the single server, single management group scenario61customer experience improvement program61agentless exception

19、 monitoring62client configuration63deploying the multiple server, single management group scenario63before you start63high-level sql cluster install guidance66installing operations manager 2007 database components in a sql server 2005 cluster67installing the operations manager 2007 op

20、erational database and data warehouse components in a sql server 2005 cluster68using log shipping for the operationsmanager database69deploying a root management server on a windows cluster in operations manager 200769installing rms74installing the secondary management servers76preparing r

21、ms cluster resources76creating the rms cluster78creating the virtual rms78preparing an inaccessible management server81testing the cluster installation82uninstalling operations manager 200782deploying stand-alone management servers in the multiple server, single management group scenario83befor

22、e you start84installing a stand-alone management server85troubleshooting tips86deploying reporting in the multiple server, single management group scenario88high-level installation overview88before you start88installing operations manager data warehouse89installing operations manager reporting on a

23、stand-alone server90confirming the health of reporting services92uninstalling operations manager reporting services93deploying acs in the multiple server, single management group scenario93before you start94installing acs on a secondary management server94how to deploy operations manager 2007 acs re

24、porting96before you start96deploying acs reporting97deploying gateway server in the multiple server, single management group scenario97high-level procedure overview98before you start99obtaining computer certificates from microsoft certificate services99distributing the microsoft.enterprisemanagement

25、.gatewayapprovaltool99installing operations manager 2007 gateway server99importing certificates with the momcertimport.exe tool100registering the gateway with the management group100configuring gateway servers for failover between management servers101description101code102comments102deploying t

26、he connected management groups scenario102before you start103creating connected management groups103providing access to connected management groups104operations manager 2007 post-deployment tasks105roadmap for the operations manager 2007 guidesif you are new to operations manager 2007, you can

27、use the following diagram to see the order in which you should read the operations manager 2007 guides. this diagram will be updated as new guides become available.about the operations manager 2007 deployment guidethis guide steps you through the deployment process for system center operations

28、manager 2007. the guide includes the following:·descriptions of three possible deployment scenarios·environmental prerequisites for each scenario·deployment steps for each scenario·post-deployment tasks even though these scenarios are presented as discrete units, your implem

29、entation of operations manager 2007 may consist of two or even all three types of deployments. before using this guide, you should complete the design process. for more information, see the operations manager 2007 design guide at operations manager 2007 deployment scenariosin this sectiona

30、bout operations manager 2007 deployment scenariosdescribes the three general deployment scenarios.single server, single management group scenariodescribes the single server, single management group scenario where all components are installed on one server.multiple server, single management group sce

31、nariodescribes the multiple server, single management group scenario that can offer distribution of server roles, redundancy, and high availability.connected management groups scenariodescribes the connected multiple management groups scenario.about operations manager 2007 deployment scenariosall op

32、erations manager 2007 individual management group deployments will either be an "all-in-one" installation, where all components are loaded on a single server, or a distributed installation, where operations manager server roles are distributed across servers. any number of these can t

33、hen be combined together to form an overall operations manager 2007 infrastructure that consists of multiple management groups. these management groups can then relate to each other in a hierarchical fashion as your business needs dictate. this guide classifies these deployment configurations i

34、nto three scenarios:·single server, single management group: the all-in-one installation·multiple server, single management group: roles distributed across servers·connected management groups: multiple management groups working together to provide monitoring, alerting, and troubleshoo

35、ting servicesthis section of the operations manager 2007 deployment guide describes these scenarios, how they are most commonly used, and any restrictions that may exist with any individual scenario.in this sectionsingle server, single management group scenarioprovides an overview of the operat

36、ions manager 2007 services offered, configuration steps, and an example of this "all-in-one" deployment configuration.multiple server, single management group scenarioprovides an overview of the operations manager 2007 services offered, server roles used, and an example of this d

37、eployment configuration.connected management groups scenarioprovides an overview of the operations manager 2007 services offered, server roles used, and an example of this deployment configuration.this guide helps you in the deployment of operations manager 2007. it does not assist in the

38、design process. before you start deploying operations manager 2007, you should have completed a design plan that includes a mapping of the following:·business and it needs to operations manager 2007 features and functions.·operations manager 2007 features to a server design

39、that supports those features and functions (a topology).·infrastructure services, such as security, directory, network, and storage, to support the server design.·your company's monitoring, alerting, and troubleshooting processes to the set of operations manager 2007 services that

40、 you plan to implement.for complete guidance in developing an operations manager design plan, see the operations manager 2007 design guide at server role compatibilityan operations manager 2007 management group can provide a multitude of services. these services can be distributed to speci

41、fic servers, thereby classifying a server into a specific role. not all server roles and services are typically deployed onto the same server. the following table lists the compatibilities and dependencies and if the role can be installed on a failover cluster. server rolerequirements and compatibil

42、itiescan be placed in a failover clusteroperational databasesql server 2005 sp1 or sp2. this role can be co-deployed with all server roles in the single server, single management group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed as a stan

43、d-alone or co-deployed with other databases.yes, n+1 clusteraudit collection services (acs) databasesql server 2005 sp1 or sp2. this role can be co-deployed with all server roles in the single server, single management group scenario (gateway and management server roles are excluded); otherwise

44、, it is most commonly deployed in a stand-alone configuration for performance purposes.yes, n+1 clusterreporting data warehouse databasesql server 2005 sp1 or sp2. this role can be co-deployed with all server roles in the single server, single management group scenario (gateway and management s

45、erver roles are excluded); otherwise, it is most commonly deployed with the reporting database or in a stand-alone configuration for performance purposes.yes, n+1 clusterreporting databasededicated sql server reporting services instance; not on a domain controller. this role can be co-deployed with

46、all server roles in the single server, single management group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed with the reporting data warehouse database or in a stand-alone configuration for performance purposes.sql reporting services database on

47、ly. n+1 clusterroot management server (rms)not compatible with management server or gateway server role. this role is co-deployed with all server roles in the single server, single management group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed i

48、nto a n+1 active-passive-passive cluster with no other roles on the cluster.yes, n+1 cluster, no other roles on the clustermanagement server (ms)not compatible with root management server. this role is not deployed in the single server, single management server scenario. it is most commonly deployed

49、 in a stand-alone configuration, noadministrator consolewindows server 2003 or windows xp or windows vista.n/aacs collectorthis role is co-deployed with all other server roles in the single server, single management group scenario (gateway and management server roles are excluded); otherwi

50、se, it must be co-deployed with the management server role. it can be combined with gateway server and audit database.nogateway servercan be co-deployed with acs collector only, cannot be combined with management server; must be a domain member.noweb console serverwindows server 2003.n/aagentau

51、tomatically deployed to root management server and management server in a management group. deployable to all other roles in managemement group.n/anote for more information about sql reporting services database installed on a cluster, see see alsosingle server, single management group scenariothe si

52、ngle server, single management group scenario combines all the management group roles that can coexist onto a single instance of the microsoft® windows server® 2003 operating system running as a member server in an active directory® domain. this instance can be on dedicated hardw

53、are or on a virtual computer. the operations console can be deployed to computers other than the single server, and the web console is accessed via a browser. agents are then typically deployed to a limited number of devices depending on the capacity of the server that operations manager is deployed

54、 on.operations manager 2007 servicesdue to the coexistence limitations defined in the about operations manager 2007 deployment scenarios, not all operations manager 2007 services and server roles are available. the single server, single management group configuration supports the following

55、 services:·monitoring and alerting·reporting (available in the operations console but not in the web console)·audit collection·agentless exception management ·data (accessed by using the web console and the operations console) operations manager 2007 server rolesthe sin

56、gle server, single management group configuration combines these server roles:·audit collection services (acs) collector·acs database·acs forwarder·operational database·operations console·reporting data warehouse database·reporting database·reporting server

57、83;root management server·web console server·commandshellrestrictionsthe single server, single management group configuration is the easiest to deploy, but there are limitations to its capabilities and therefore limitations to what it is commonly used for.gateway serverthis configuration d

58、oes not include the gateway server role. because of this, all monitored devices must be in the same active directory domain as the management server or you must use certificates on both the managed computer and the management server to provide for mutual authentication.high availability and redundancythe single server, single management group resides on a single set of har