| PrintNumber | ErrorLocation | Error | Correction | DateAdded |
|---|---|---|---|---|
| 2 | pii | First Printing April 2010 | Third Printing June 2010 | 5/18/2010 |
| 2 | pv | Bridgeways Management Packs 61 The Bridgeways VMware ESX Management Pack 62 The Bridgeways Apache Management Pack 68 |
BridgeWays Management Packs 61 The BridgeWays VMware ESX Management Pack 62 The BridgeWays Apache Management Pack 68 |
5/18/2010 |
| 2 | pxv | Additional functionality for the Web console, now able to access the health explorer to drill-down into health of individual components |
Additional functionality for the Web console, now able to access the Health Explorer to drill-down into health of individual components |
5/20/2010 |
| 2 | pxvii | John presented on Microsoft systems management technologies at the Worldwide Partner Conference Denver 2007, ITForum Barcelona 2007, and MMS 2008. | John presented on Microsoft systems management technologies at the Worldwide Partner Conference Denver 2007, ITForum Barcelona 2007, and MMS 2008/2010. | 5/20/2010 |
| 2 | p2 | Therefore, this book takes up where the previous leaves off-with a summary of the SP 1 changes, an in-depth look at the R2 release, and a "deep dive" into some of the key capabilities of OpsMgr 2007 through Cumulative Update 2 (CU2) for R2. | Therefore, this book takes up where the previous leaves off-with a summary of the SP 1 changes, an in-depth look at the R2 release, and a "deep dive" into some of the key capabilities of OpsMgr 2007 through Cross Platform Cumulative Update 2 (CU2) for R2. | 5/25/2010 |
| 2 | p3 | End of page, extra bullet | fixed | 5/25/2010 |
| 2 | p5 | Although management servers are able to support up to 2,000 servers since SP 1, gateways are a welcome alternative in complex, distributed environments, as they forward compressed data from multiple agents to a management server using a sustained connection; the management server then manages the connection to the database. | Although management servers are able to support up to 2,000 agents since SP 1, gateways are a welcome alternative in complex, distributed environments, as they forward compressed data from multiple agents to a management server using a sustained connection; the management server then manages the connection to the database. | 5/25/2010 |
| 2 | p6 | If the RMS fails and there is no backup of the encryption key, you must reinstall the entire management group! SP 1 adds the Secure Storage Backup Wizard at the end of the OpsMgr setup process, displayed in Figure 1.2, providing a backup the RMS encryption key. | If the RMS fails and there is no backup of the encryption key, you must reinstall the entire management group! SP 1 adds the Secure Storage Backup Wizard at the end of the OpsMgr setup process, displayed in Figure 1.2, providing a backup of the RMS encryption key. | 5/25/2010 |
| 2 | p31 | The Unix Action account is a regular login account that can be created with the useradd command. useradd should be in mono font. |
fixed | 5/25/2010 |
| 2 | p36 | Microsoft is creating management pack guides for the Cross Platform Operating systems, available at http://technet.microsoft.com/en-us/library/ee346642.aspx. At the time of writing this chapter, guides are available for the AIX, HP-UX, Red Hat Linux, Solaris, and SUSE Linux Operating Systems. | Microsoft is creating management pack guides for the Cross Platform operating systems, available at http://technet.microsoft.com/en-us/library/ee346642.aspx. At the time of writing this chapter, guides are available for the AIX, HP-UX, Red Hat Linux, Solaris, and SUSE Linux operating systems. | 5/25/2010 |
| 2 | p37 | By filtering on Cross Platform based upon all management packs in the catalog (see Figure 2.14), you will see the four high-level groups CrossPlat management packs are currently split into, as follows: | By filtering on Cross Platform based upon all management packs in the catalog (see Figure 2.14), you will see the four high-level groups the CrossPlat management packs are currently split into, as follows: | 5/25/2010 |
| 2 | p45 | 1. Install FTP server on a Windows server; add the Unix agent installation files to the FTP share; then connect from the Unix system and perform an FTP get of the files. | 1. Install the FTP server on a Windows server; add the Unix agent installation files to the FTP share; then connect from the Unix system and perform an FTP get of the files. | 5/25/2010 |
| 2 | p46 | 3. Once the file is uncompressed, you can install the package using pkgadd: (when prompted to with the y/n to install, choose y): | 3. Once the file is uncompressed, you can install the package using pkgadd: (when prompted to with the y/n to install, choose y): pkgadd is mono font. |
5/25/2010 |
| 2 | p46 | 4. Next, verify the package installed by using the pkginfo command: | 4. Next, verify the package installed by using the pkginfo command: pkginfo is mono font. |
5/25/2010 |
| 2 | p48 | The user community is investigating solutions such as this article, which discusses deploying the OpsMgr CrossPlat agent on Ubuntu: http://www.muscetta.com/2009/05/30/installing-the-opsmgr-2007-r2-scx-agent-on-ubuntu/ . | The user community is investigating solutions such as this article, which discusses deploying the OpsMgr CrossPlat agent on Ubuntu: http://www.muscetta.com/2009/05/30/installing-the-opsmgr-2007-r2-scx-agent-on-ubuntu/. | 5/25/2010 |
| 2 | p49 | To reboot down a Unix/Linux system, you need to sync twice and then init it to the correct level. Sample syntax: | To reboot down a Unix/Linux system, you need to sync twice and then init it to the correct level. Sample syntax: sync is in mono font. |
5/25/2010 |
| 2 | p50 | Issue: The certificate Common Name (CN) does not match. or Issue: The SSL certificate contains a common name (CN) that does not match the hostname. |
Next to or is an extra bullet. |
5/25/2010 |
| 2 | p50-51 | The words “Issue” and Resolution” in the bullets on these 2 pages need to be bold. |
fixed | 5/25/2010 |
| 2 | p51 | Resolution: Many different connectivity issues can cause this, including IPTABLES blocking the connection, SSH not running on the client system, or as occurring during our testing if an invalid user account/password combination were specified when discovering the Unix/Linux system. |
Resolution: Many different connectivity issues can cause this, including IPTABLES blocking the connection, SSH not running on the client system, or as occurred during our testing if an invalid user account/password combination were specified when discovering the Unix/Linux system. |
5/25/2010 |
| 2 | p51 | Resolution: OpsMgr was able to connect to the remote system but was not able to successfully use the root credentials to run the pkgadd command. Verify the root password, and if this continues to fail, attempt a manual CrossPlat agent installation. | Resolution: OpsMgr was able to connect to the remote system but was not able to successfully use the root credentials to run the pkgadd command. Verify the root password, and if this continues to fail, attempt a manual CrossPlat agent installation. |
5/25/2010 |
| 2 | p57 | Figure 2.36 displays the seven-day memory performance history (pages per sec) report for the hadji computer: | Figure 2.36 displays the seven-day memory performance history (pages per sec) report for the hadji computer. | 5/25/2010 |
| 2 | p61-68 | All occurances of “Bridgeways” |
Should be “BridgeWays” | 5/25/2010 |
| 2 | p62 | There have been a number of different solutions including nWorks... | There have been a number of different solutions including nworks... | 5/25/2010 |
| 2 | p98 | Install the components in the following order to: | Install the components in the following order: | 5/25/2010 |
| 2 | p102 | If you are installing Operations Manager 2007 SP 1 on Windows 2008, the authors have written a series of blog articles and videos discussing lessons learned during the installation process. | If you are installing Operations Manager 2007 SP 1 on Windows 2008, the authors have developed a series of blog articles and videos discussing lessons learned during the installation process. | 5/25/2010 |
| 2 | p136 | 7. Do the same for the corresponding report's *.rpdl file. | 7. Do the same for the corresponding report's .rpdl file. | 5/25/2010 |
| 2 | p181 | PS>get-eventlog application| [arrow] where {$_.timegenerated -gt (get-date).addminutes(-25)} |
PS>get-eventlog application| [ccc] where {$_.timegenerated -gt (get-date).addminutes(-25)} [ccc]= code continuation character |
5/26/2010 |
| 2 | p185 | PS>get-agent| [arrow] where{($_.GetFailoverManagementServers()| [arrow] foreach{$_.PrincipalName}) -contains "server_name"} |
PS>get-agent| [ccc] where{($_.GetFailoverManagementServers()| [ccc] foreach{$_.PrincipalName}) -contains "server_name"} [ccc]= code continuation character |
5/26/2010 |
| 2 | p187 | function prompt "PS "+ $(Get-Location).ToString().Replace("%002d","-") + [arrow] "`n" + ">";} } |
function prompt "PS "+ $(Get-Location).ToString().Replace("%002d","-") + [ccc] "`n" + ">";} [ccc]= code continuation character |
5/26/2010 |
| 2 | p187 | PS>get-managementpack| [arrow] where{$_.name -eq "Microsoft.Windows.Server.2003"}|export-managementpack -path C:\ |
PS>get-managementpack| [ccc] where{$_.name -eq "Microsoft.Windows.Server.2003"}|export-managementpack -path C:\ [ccc]= code continuation character |
5/26/2010 |
| 2 | p188 | param($mpFilePath,$outputDir) $assembly = [System.Reflection.Assembly]:: [arrow] LoadWithPartialName("Microsoft.EnterpriseManagement.OperationsManager") $mp = new-object [arrow] Microsoft.EnterpriseManagement.Configuration.ManagementPack($mpFilePath) $mpWriter = new-object [arrow] Microsoft.EnterpriseManagement.Configuration.IO.ManagementPackXmlWriter($outputDir) $mpWriter.WriteManagementPack($mp) |
param($mpFilePath,$outputDir) $assembly = [System.Reflection.Assembly]:: [ccc] LoadWithPartialName("Microsoft.EnterpriseManagement.OperationsManager") $mp = new-object [ccc] Microsoft.EnterpriseManagement.Configuration.ManagementPack($mpFilePath) $mpWriter = new-object [ccc] Microsoft.EnterpriseManagement.Configuration.IO.ManagementPackXmlWriter($outputDir) $mpWriter.WriteManagementPack($mp) [ccc]= code continuation character |
5/26/2010 |
| 2 | p188 | powershell d:\MpToXml.ps1 [arrow] -mpFilePath:'d:\Microsoft.Exchange.Server.2003.Monitoring.mp' -outputDir:'d:\ |
powershell d:\MpToXml.ps1 [ccc] -mpFilePath:'d:\Microsoft.Exchange.Server.2003.Monitoring.mp' -outputDir:'d:\ [ccc]= code continuation character |
5/26/2010 |
| 2 | p193 | Microsoft has tried packaging small and medium business (SMB) solutions for over a decade, beginning with Microsoft BackOffice Server and later BackOffice Small Business Server. | Microsoft has tried packaging small and medium business (SMB) solutions for over a decade, beginning with Microsoft BackOffice Server and later Small Business Server. | 5/26/2010 |
| 2 | p193 | EBS 2008 management is built on Essentials 2007, the hybrid SMB management tool based on OpsMgr 2007. | EBS 2008 management is built on Essentials 2007, the hybrid SMB management tool based on OpsMgr 2007. Note: This product is discontinued by Microsoft effective June 30, 2010. | 5/26/2010 |
| 2 | p196 | <AlertDefinition ID="896e6561-b29d-42b5-b349-a87460c8556f" Default="1" [arrow] Title="Unexpected Shut down" Source="Server"> |
<AlertDefinition ID="896e6561-b29d-42b5-b349-a87460c8556f" Default="1" [ccc] Title="Unexpected Shut down" Source="Server"> [ccc]= code continuation character |
5/26/2010 |
| 2 | p201 | Figure 6.7 shows such a dashboard view open in the Remote OpsMgr Web console as it would be seen by a customer over the Internet. | Figure 6.7 shows such a dashboard view open in the Remote OpsMgr Web console as it would be seen by a customer over the Internet. As mentioned at the beginning of this chapter, EBS 2008 will not be available for purchase after June 30, 2010. Existing customers can take advantage of a limited time upgrade offer to obtain the original component software from the suite for free (Windows Server 2008 Standard Edition, Exchange Server 2007 Standard Edition, and Essentials 2007). See http://www.microsoft.com/ebs for additional information. | 5/26/2010 |
| 2 | p220 | Many installations use the nWorks management pack for... | Many installations use the nworks management pack for ... | 5/26/2010 |
| 2 | p221 | Figure 7.6 lists the useful tasks related to VMware guest VMs that nWorks makes available in the Operations console. | Figure 7.6 lists the useful tasks related to VMware guest VMs that nworks makes available in the Operations console. | 5/26/2010 |
| 2 | p232 | All “nWorks” and “Bridgeways” are capped incorrectly. They should be “nworks” and “BridgeWays.” | fixed | 5/26/2010 |
| 2 | p257-258 | Check for the folder that indicates presence of the application we are [arrow] discovering If (oFSO.FolderExists("c:\program files\ACME\POSBatchProcess\Processing")) [arrow] Then 'Create an instance of the class Set oInst = oDiscoveryData.CreateClassInstance("$MPElement[Name= [arrow] 'Unleashed.POSBatchProcess.Version1.POSJobProcessingServer']$") 'Add properties of the class to the discovered instance Call oInst.AddProperty ("$MPElement[Name= [arrow] 'Windows!Microsoft.Windows.Computer']/PrincipalName$", TargetComputer) Call oInst.AddProperty("$MPElement[Name='System!System.Entity'] [arrow] /DisplayName$", "POS Job Processing Server") call oDiscoveryData.AddInstance(oInst) |
Check for the folder that indicates presence of the application we are [ccc] discovering If (oFSO.FolderExists("c:\program files\ACME\POSBatchProcess\Processing")) [ccc] Then 'Create an instance of the class Set oInst = oDiscoveryData.CreateClassInstance("$MPElement[Name= [ccc] 'Unleashed.POSBatchProcess.Version1.POSJobProcessingServer']$") 'Add properties of the class to the discovered instance Call oInst.AddProperty ("$MPElement[Name= [ccc] 'Windows!Microsoft.Windows.Computer']/PrincipalName$", TargetComputer) Call oInst.AddProperty("$MPElement[Name='System!System.Entity'] [ccc] /DisplayName$", "POS Job Processing Server") call oDiscoveryData.AddInstance(oInst) [ccc]= code continuation character |
5/26/2010 |
| 2 | p267 | Last cell of Table 8.4: These will appear in Distributed Application view. |
These will appear in the Distributed Application view. | 5/26/2010 |
| 2 | p317 | Most distributed environments require users in remote geographical locations to access OpsMgr, who be located in a completely different physical location across a long-distance link. | Most distributed environments require users in remote geographical locations to access OpsMgr, who may be located in a completely different physical location across a long-distance link. | 5/26/2010 |
| 2 | p317 | Captures the Windows user interface and translates it into a form readily converted by RDPWD into the RDP protocol. | Captures the Windows user interface and translates it into a form readily converted by RdpWD into the RDP protocol. | 5/26/2010 |
| 2 | p324 | All code text between <> should be italic. | fixed | 5/26/2010 |
| 2 | p339 | Another important infrastructure update is the new command switches for the adtAdmin cmdlet used to administer ACS. |
Another important infrastructure update is the new command switches for the adtAdmin command used to administer ACS. |
5/26/2010 |
| 2 | p340 | The query syntax is Windows Management Instrumentation (WMI)... Extra space before. |
fixed | 5/26/2010 |
| 2 | p351 | Use the distributed application designer to model this network configuration, as displayed in Figure 9.20. | Use the Distributed Application Designer to model this network configuration, as displayed in Figure 9.20. | 5/26/2010 |
| 2 | p353 | Figure 9.24 shows the Topology view for the Denver Network Link. | Figure 9.24 shows the topology view for the Denver Network Link. | 5/26/2010 |
| 2 | p366 | When authoring in the Operations console, all created objects are written to the management pack eXtended Markup Language (XML) and referenced by system-generated identifiers. | When authoring in the Operations console, all created objects are written to the management pack in eXtended Markup Language (XML) and referenced by system-generated identifiers. | 5/26/2010 |
| 2 | p377 | If this is not the case, errors will be seen during discovery on the RMS. | If this is not the case, errors will be seen on the RMS during discovery. | 5/26/2010 |
| 2 | p391 | For new "by Example" information and updates to existing articles, be sure to check http://ops-mgr.spaces.live.com. The blog will continue to have postings adding to the "by Example" series. | For new "by Example" information and updates to existing articles, be sure to check http://ops-mgr.spaces.live.com and http://systemcentercentral.com/byexample for postings adding to the "by Example" series. | 5/26/2010 |
| 2 | p397 | Closed the alert, but tracking this to see if it recurs on this server. | Closed the alert, but continuing to track this to see if it recurs on this server. | 5/26/2010 |
| 2 | p399 | (You must have the admin utilities installed on the DC for this to work.) | (install the admin utilities on the DC for this to work) | 5/26/2010 |
| 2 | p401 | The alerts have also come in and then auto resolve on their own. | These alerts have also come in and then auto resolve on their own. | 5/26/2010 |
| 2 | p405 | Resolution: Manually close the alert as the domain controller reboot was expected. | Resolution: Manually close the alert as it was expected. | 5/26/2010 |
| 2 | p421 | Resolution: This is a bug in Windows Management Instrumentation (WMI). The BlackBerry MDS Connection Service has a very long ImagePath registry entry. When the health service script runs Select DisplayName, State, Name, StartMode, StartName FROM Win32_Service, a null is returned for StartName because the buffer allocated for the results is too small and the call fails; this can be verified using wbemtest. Connect to the root\cimv2 namespace and run the following query: Select DisplayName, State, Name, StartMode, StartName FROM Win32_Service Not formatted correctly. |
fixed | 5/26/2010 |
| 2 | p426 | This situation has been seen in this environment twice in less than a year. | This situation has been seen in this particular environment twice in less than a year. | 5/26/2010 |
| 2 | p435 | From the details on the event, copied the file path and verified that the system could open the file with notepad. | From the details on the event, copied the file path and verified that the system could open the file with Notepad. | 5/26/2010 |
| 2 | p436 | Read the Management Pack Guide as this covers items to be aware of with the DHCP, such as how DHCP clustering and multicast scopes are not supported. | Read the Management Pack Guide as this covers items to be aware of with DHCP, such as how DHCP clustering and multicast scopes are not supported. | 5/26/2010 |
| 2 | p456 | Maarten also has a series of ACS Deep Dive articles at System Center Central: | Maarten also has a series of ACS “deep dive” articles at System Center Central: | 5/26/2010 |
| 2 | p472 | http://blog.xplatxperts.com/xplat-xperts/ is maintained by Rob Doucette and Michael Guthrie, who work on the Bridgeways management packs at Xandros | http://blog.xplatxperts.com/xplat-xperts/ is maintained by Rob Doucette and Michael Guthrie, who work on the BridgeWays management packs at Xandros | 5/26/2010 |
| 2 | p476 | Chapter 8, "Management Pack Authoring," comes with PowerShell scripts, exTended Markup Language (xml), and Visual Basic scripts to help you do the exercises referred to in this chapter, as follows: | Chapter 8, "Management Pack Authoring," comes with PowerShell scripts, eXtended Markup Language (xml), and Visual Basic scripts to help you do the exercises referred to in this chapter, as follows: | 5/26/2010 |
| 2 | p164-168 | Code continuation character did not convert. | fixed | 5/27/2010 |
| 2 | p211 | Although no details are available yet, the next version of Essential Business Server (EBS) is in development, and Essentials 2010 will likely be the primary management component in EBS. In particular, the new virtualization and updates management features previewed in Essentials 2010 will be welcome and valuable additions to a future EBS suite. | Delete paragraph. | 5/28/2010 |
| 2 | pxv | The next set of chapters discusses intertwined technologies. Chapter 5, "PowerShell Extensions for Op-erations Manager 2007," covers PowerShell and the OpsMgr Shell, Chapter 6, "Management Solutions for Small and Midsize Business," looks at management approaches for smaller-sized businesses, and Chapter 7, "Operations Manager and Virtualization," discusses virtualization. | The next set of chapters discusses intertwined technologies. Chapter 5, "PowerShell Extensions for Op-erations Manager 2007," covers PowerShell and the OpsMgr Shell, Chapter 6, "Management Solutions for Small and Midsize Business," looks at management approaches for smaller-sized businesses, and Chapter 7, "Operations Manager and Virtualization," discusses virtualization in the context of Operation Manager and Microsoft. | 6/1/2010 |
| 2 | pxvi | In keeping with being supplemental to System Center Operations Manager 2007 Unleashed, Appendix A, "OpsMgr R2 by Example," is an update of the OpsMgr by Example series published with the first book, and Appendix B, "Reference URLs," updates reference URLs, with nearly 250 useful links. | In keeping with being supplemental to System Center Operations Manager 2007 Unleashed, Appendix A, "OpsMgr R2 by Example," is an update of the OpsMgr by Example series published with the first book, and Appendix B, "Reference URLs," updates reference URLs, with nearly 300 useful links. | 6/1/2010 |
| 2 | p125 | Begin by running the CU1 version of SRSupgradetool.exe on your SQL Server Reporting Services server. | Begin by running the CU1 version of SRSupgradetool.exe on your SQL Server Reporting Services system. | 6/2/2010 |
| 2 | p133 | In addition to supporting SQL 2008 SP 1 for OpsMgr reporting (discussed in the "Core OpsMgr Component Support" section), OpsMgr 2007 R2 reporting incorporates many new capabilities. | In addition to supporting SQL 2008 SP 1 for OpsMgr reporting (discussed in the "Core OpsMgr Component Support" section), R2 reporting incorporates many new capabilities. | 6/2/2010 |
| 2 | p157 | The online help currently focuses on PowerShell version 2, so some of the documentation may not apply to systems still running version 1, which is the PowerShell version used with Operations Manager SP 1 and R2. | The online help currently focuses on PowerShell version 2, so some of the documentation may not apply to systems still running version 1, which is the PowerShell version used with Operations Manager 2007. | 6/2/2010 |
| 2 | p179 | Let's break down the preceding code snippet line-by-line. | Let's break down the preceding code snippet. | 6/2/2010 |
| 2 | p195 | Define alerts in individual exTended Markup Language (XML) files, placed in a designated folder. | Define alerts in individual eXtended Markup Language (XML) files, placed in a designated folder. | 6/2/2010 |
| 2 | p196 | Using the sample XML code shown here, create the XML file and save it in the %ProgramFiles%\Windows Small Business Server\Data\Monitoring\ExternalAlerts folder on the SBS 2008 server (the 64-bit subdirectory, not the 32 bit one): |
Using the sample XML code shown here, create the XML file and save it in the %ProgramFiles%\Windows Small Business Server\Data\Monitoring\ExternalAlerts folder on the SBS 2008 server (the 64-bit subdirectory, not the 32-bit one): |
6/2/2010 |
| 2 | p204 | Based on the pre-release of Essentials 2010, this will be a quicker and smoother administrator experience, with fewer system resource requirements than the previous version. |
Based on the pre-release version of Essentials 2010, this will be a quicker and smoother administrator experience, with fewer system resource requirements than the previous version. | 6/2/2010 |
| 2 | p204 | Another solution would be to run Essentials 2010 in its own VM, or even two VMs if you elect to host the Essentials databases on an external, pre-existing, or new SQL server. | Another solution would be to run Essentials 2010 in its own VM, or even two VMs if you elect to host the Essentials databases on an external, pre-existing, or new SQL Server. | 6/2/2010 |
| 2 | p209 | You can augment Essentials agent-based monitoring of computers by creating an override that enables a ping monitor in the availability branch of the computer's health explorer. | You can augment Essentials agent-based monitoring of computers by creating an override that enables a ping monitor in the availability branch of the computer's Health Explorer. | 6/2/2010 |
| 2 | p211 | This chapter explored the management aspects and Operations Manager integration scenarios of two shipping Microsoft server products for the small and medium business space: SBS 2008 and EBS 2008. | This chapter explored the management aspects and Operations Manager integration scenarios of two Microsoft server products for the small and medium business space: SBS 2008 and EBS 2008. | 6/2/2010 |
| 2 | p220 | In the ESX management scenario, well-established third-party management packs are avail-able from Veeam, Jalasoft, and Bridgeways that do a great job of monitoring and managing VMware ESX with OpsMgr (Chapter 2, "Unix/Linux Management: Cross Platform Extens-ions," includes a discussion of the Bridgeways management pack). | In the ESX management scenario, well-established third-party management packs are avail-able from Veeam, Jalasoft, and BridgeWays that do a great job of monitoring and managing VMware ESX with OpsMgr (Chapter 2, "Unix/Linux Management: Cross Platform Extens-ions," includes a discussion of the BridgeWays management pack). | 6/2/2010 |
| 2 | p224 | 5. Windows Automated Installation Kit-If not already installed, VMM Server setup installs the Windows Automated Installation Kit (WAIK). You can optionally use WAIK components such as the ImageX capture tool to customize and use the VM provisioning features of VMM. |
5. Windows Automated Installation Kit-If not already installed, VMM server setup installs the Windows Automated Installation Kit (WAIK). You can optionally use WAIK components such as the ImageX capture tool to customize and use the VM provisioning features of VMM. |
6/2/2010 |
| 2 | p229 | Figure 7.13 is the expanded diagram view of the VMM server Tornado's health model. | Figure 7.13 is the expanded Diagram view of the VMM server Tornado's health model. | 6/2/2010 |
| 2 | p229 | When you select objects in the diagram view, you will expose context-sensitive Ac-tion panels listing tasks appropriate to the object. | When you select objects in the Diagram view, you will expose context-sensitive Ac-tion panels listing tasks appropriate to the object. | 6/2/2010 |
| 2 | p229 | FIGURE 7.13 Exploring the health model of the VMM server thorough the diagram view | FIGURE 7.13 Exploring the health model of the VMM server thorough the Diagram view | 6/2/2010 |
| 2 | p235 | Figure 7.19 is the diagram view of a VMM server that includes an ESX host cluster. | Figure 7.19 is the Diagram view of a VMM server that includes an ESX host cluster. | 6/2/2010 |
| 2 | p254 | [arrows] in code should be converted to code continuation characters. | fixed |
6/3/2010 |
| 2 | p255 | Using the /nologo switch with Cscript when testing your scripts; it suppresses the Microsoft copyright message normally echoed to the screen. | Using the /nologo switch with Cscript when testing your scripts will suppress the Microsoft copyright message normally echoed to the screen. | 6/3/2010 |
| 2 | p329 | The MSDB database is used by the SQL Server Agent for scheduling alerts and jobs and by other features such as Service Broker and Database mail. | The MSDB database is used by the SQL Server Agent for scheduling alerts and jobs and by other features such as Service Broker (also known as the SQL Broker) and Database mail. | 6/3/2010 |
| 2 | p329 | This discussion assumes that the .bak file(s) were copied to C:\temp and SQL Server 2008 is used to host the databases: | This discussion assumes that the .bak file(s) were copied to C:\temp and SQL Server 2008 is used to host the databases: | 6/3/2010 |
| 2 | p330 | Table 9-3. Added grid and all Msdb cap. | fixed | 6/3/2010 |
| 2 | p330 | Table 9-3 %Program Files%\Microsoft SQL Server %Windir%\System32\inetsrv\ MetaBack |
%ProgramFiles%\Microsoft SQL Server %windir%\System32\inetsrv\ MetaBack |
6/3/2010 |
| 2 | p340 | ACS noise filters are managed at each local collector by the adtAdmin command with the /getquery or /setquery switch, as discussed in Chapter 15 of System Center Opera System Center Operations Manager 2007 Unleashed. | /getquery and /setquery should be in mono font. | 6/3/2010 |
| 2 | p354 | Figure 9.24 shows the topology view for the Denver Network Link. | Figure 9.24 shows the Topology view for the Denver Network Link. | 6/3/2010 |
| 2 | p355 | 1. Open the existing distributed application with the distributed application designer. | 1. Open the existing distributed application with the Distributed Application Designer. | 6/3/2010 |
| 2 | p399 | http://Cameronfuller.spaces.live.com | http://cameronfuller.spaces.live.com | 6/3/2010 |
| 2 | p405 | Resolution: Manually close the alert as the domain controller reboot was expected. | Resolution: Manually close the alert as the reboot was expected. | 6/3/2010 |
| 2 | p411 | By default, the management pack uses the default action account. | By default, the management pack uses the default Action account. | 6/3/2010 |
| 2 | p475 | http://www.informit.com/store/product.aspx?isbn=0672331179. | http://www.informit.com/store/product.aspx?isbn=0672333414. | 6/3/2010 |
| 3 | pii | Third Printing June 2010 | Fourth Printing August 2011 | 7/26/2011 |
| 3 | pxvi | http://www.informit.com/store/product.aspx?isbn=0672331179. | http://www.informit.com/store/product.aspx?isbn=0672333414. | 7/26/2011 |
| 3 | p3 | * System Center Operations Manager 2007 * System Center Operations Manager 2007 R2 * System Center Data Protection Manager 2007 * System Center Virtual Machine Manager 2008 * System Center Virtual Machine Manager 2008 Management Server License |
* System Center Operations Manager (SCOM) 2007 and SCOM 2007 R2 * System Center Data Protection Manager 2007 * System Center Virtual Machine Manager 2008 * System Center Virtual Machine Manager 2008 Management Server License * System Center Configuration Manager 2007 * System Center Service Manager 2010 |
7/26/2011 |
| 3 | p36 | Click Add to connect to the catalog, as shown in Figure 2.13. | Click Add to connect to the catalog, which brings up the screen displayed in Figure 2.13. | 7/26/2011 |
| 3 | p87 | This list addresses major third-party systems, although a number are currently unavaiable—NetCool being an example. | This list addresses major third-party systems, although a number are currently unavailable—NetCool being an example. | 7/26/2011 |
| 3 | p87 | Step 1: (remove all italic) | fixed | 7/26/2011 |