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!

We received an email this morning from our colleague Stefan Stranger, a former MOM MVP who is now a Microsoft employee. Regrettably, his name was misspelled in Appendix E of the book.

Unfortunately, in a book 1416 pages long (or somewhere around that), as much as we try to eliminate all typos and spelling errors, one or two slip by. Our deep apologies to Stefan for misspelling his name in Appendix E. The good news is his name IS spelled correctly in Chapters 9 and 12, so Stefan you do not need to change your name if you want to show the book to people!

We are in the process of reading through the book looking for errors (typos, spelling errors, etc) - so if you see something, please let us know - just in case we miss it ourselves. The errata is collected and posted at http://www.informit.com/store/product.aspx?isbn=0672329557, and corrections will be included with the 2nd printing of the book.

Thank you!

The official publication date for the OpsMgr 2007 Unleashed book was February 29, 2008. Yet that date came and went, without a book. What happened?

You could say a funny thing happened at the printer, which is actually correct. A little information about how this whole process works, but not too much since we don't want to bore you.

We finished writing the content (including having it tech reviewed) in early November 2007. After the authoring process is complete, the material goes to the publisher where it copy-edited, then goes through page layout and proofreading (plus some other activities). That schedule ran right into the middle of the Christmas holidays, which slowed things down a bit. In mid January, we went into the proofreading cycle; everything was complete and the book was sent out for printing in early February.

Due to a ton of preorders, the publisher decided to increase the number of copies for the first printing. In addition, the book was "just a bit" longer than originally anticipated ... so we had a delay at the printer. The in-stock date, which is when the book is available at the publisher's warehouse, was moved to March 12th, giving us a 2-week delay. (Once its at the publisher, its a matter of bookstores and places like Amazon getting their orders fulfilled.)

Of course, the book is now available, and we are regularly getting emails from people who have received their copies. In fact, we heard from someone in the Netherlands this morning that his copy ordered from Amazon had arrived - so delivery to Europe is happening. Yeah!