Operations Manager 2007 Unleashed errata – Chapter 3

Although we tried very hard to be perfect, it didn’t quite work out. A question was raised about some of the content in Chapter 3 which didn’t seem quite consistent with other places in the book. The following changes will be posted as errata (http://www.informit.com/store/product.aspx?isbn=0672329557) once the link on that page is corrected, and included in the second printing of the Unleashed book.

This area of discussion is in regards to communication between the management servers and the databases.

The last paragraph on page 106 of the book states:

The OpsMgr SDK service is found in the services list of all management servers. However, the service is disabled unless the server is also the RMS. This service and the OpsMgr Config service, described next, are both found only on management servers. All data Windows flowing to and from the Operations database is transported via the OpsMgr SDK service running on the RMS.

The italicized sentence (last one in the paragraph) will be removed. While the SDK service is involved, it does not mean that all data changes flow through the RMS (due to using Run As accounts on the other management servers). Since this sentence is confusing, we will strike it.

On page 108, the "Communications" section, third paragraph, currently states:

The logic in Table 3.1 is diagrammed in Figure 3.5. A quick study of the communication paths verifies the criticality of the RMS in an OpsMgr 2007 management group. The RMS is clearly the communications nexus for the monitoring organization, with most features of OpsMgr unavailable if the RMS is down or inaccessible. Of course, the RMS depends completely on its connection to the Operations database to function.

This paragraph will be updated to say (the italicized sentence will be added):

The logic in Table 3.1 is diagrammed in Figure 3.5. A quick study of the communication paths verifies the criticality of the RMS in an OpsMgr 2007 management group. The RMS is clearly the communications nexus for the monitoring organization, with most features of OpsMgr unavailable if the RMS is down or inaccessible. For example, you cannot open new Operations Manager console sessions or perform discoveries if the RMS is down. Of course, the RMS depends completely on its connection to the Operations database to function.

The third change to this topic involves the graphic on page 110, Figure 3.5, which has an arrow left out. Table 3.1 on page 109 covers the same information, and the table IS correct. Figure 3.5 needs to have a note added that says

(Not shown: Management Server to Data Warehouse DB, OLE 1433)

Preferably the note will go in the white space to the right of the Data Warehouse icon.

We have just completed reading through all 1416 pages  looking for changes for the next printing, reading the entire book in a short space of time was a project all by itself!

Advertisements
This entry was posted in Books. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s