PrintNumber	ErrorLocation	Error	Correction	DateAdded
1	pii	First Printing July 2011	TBD e-product: with corrections in July 2013	2/15/2012
1	pxvi	Mark has been a frequent presenter on OIS at MMS, TechEd (U.S., ZA, and AE), and numerous internal Microsoft conferences.	Mark has been a frequent presenter on OIS at MMS, TechEd (U.S., AU, and NZ), and numerous internal Microsoft conferences.	8/12/2013
1	p8	Bringing your data center together using OIS can make you that IT hero you always wanted to be!	Furthermore, bringing your data center together using OIS can make you that IT hero you always wanted to be!	8/12/2013
1	p9	What OIS brings to the table is its data bus technology.	What OIS brings to the table is its Data Bus technology.	8/12/2013
1	p13	Automate the remediation of alerts . Orchestrate incident management through to resolution . Integrate Service Manager with third-party IT service management (ITSM) tools for service desk synchronization . Integrate across monitoring tools, service desks, and CMDBs . Facilitate ITIL or MOF best practice processes	. Automate the remediation of alerts. . Orchestrate incident management through to resolution. . Integrate Service Manager with third-party IT service management (ITSM) tools for service desk synchronization. . Integrate across monitoring tools, service desks, and CMDBs. . Facilitate ITIL or MOF best practice processes.M	8/12/2013
1	p30	Figure 2.1 text is hard to read.	Image enhanced to improved readability.	8/12/2013
1	p30	Figure 2.1 text is hard to read.	Image enhanced to improved readability.	8/12/2013
1	p48	The Management Server is a required component for design time, as discussed in the “OIS Client” section earlier in this chapter and is useful during installation time.	The Management Server is a required component for design time, as discussed in the “OIS Client” section earlier in this chapter, and is useful during installation time.	8/12/2013
1	p56	Figure 3.1 text is hard to read.	Image enhanced to improved readability.	8/12/2013
1	p56	After the Check In button is pressed, the OIS Client contacts the Management Service so the policy can be written to the datastore. In this scenario, the Management Service acts as a proxy or broker so the OIS Client machines do not access the datastore directly—as doing so would mean every author would require write access to the various database tables.	After the Check In button is pressed, the OIS Client contacts the Management Server so the policy can be written to the datastore. In this scenario, the Management Server acts as a proxy or broker so the OIS Client machines do not access the datastore directly—as doing so would mean every author would require write access to the various database tables.	8/12/2013
1	p57	This policy data, which is loosely formatted eXtended Markup Language (XML) data, is taken by the Management Service and written into the datastore.	This policy data, which is loosely formatted eXtended Markup Language (XML) data, is taken by the Management Server and written into the datastore.	8/12/2013
1	p57	After the Management Service writes the policy to the datastore, nothing else happens as part of the transaction.	After the Management Server writes the policy to the datastore, nothing else happens as part of the transaction.	8/12/2013
1	p60	In a default configuration, if you have an Action Server with 40 Monitored Policies running, this only leaves room for 10 ad hoc policies, assuming all 40 monitored policies were idle and had not created new policies to replace them.	In a default configuration, if you have an Action Server with 40 monitored policies running, this only leaves room for 10 ad hoc policies, assuming all 40 monitored policies were idle and had not created new policies to replace them.	8/13/2013
1	p61	When checking the Action Server logs or the Policy logs, you might see errors such as Out of Memory or Not Enough Storage.	When checking the Action Server logs or the policy logs, you might see errors such as Out of Memory or Not Enough Storage.	8/13/2013
1	p73	. No policy or state data is shared between installations. . Requires manual effort to import or export policies. . Installations have potential to become out of sync with one another.	. No policy or state data is shared between installations . Requires manual effort to import or export policies . Installations have potential to become out of sync with one another	8/13/2013
1	p77-78	Figures 3.13-3-15 text hard to read.	Image enhanced to improved readability.	8/13/2013
1	p81	Windows Installer 3.1 to install OIS and its components, integration packs, and so on. (This is not required for the Operator console.)	Windows Installer 3.1 to install OIS and its components, integration packs, and so on. (This is not required for the Operator Console.)	8/13/2013
1	p88	Although Oracle is supported with OIS 6.3, it is unknown whether that support will continue after Microsoft rebrands the product.	Although Oracle is supported with OIS 6.3, that support will not continue after Microsoft rebrands the product	8/13/2013
1	p94	After you patch the Management Server and update it with the 6.3 version of the foundation objects, resume the normal installation process.	After you patch the Management Server and update it with the 6.3 version of the Foundation objects, resume the normal installation process.	8/13/2013
1	p94	1. Open Deployment Manager found at Start -> All Program -> Opalis Software\Opalis Integration Server.	1. Open Deployment Manager found at Start -> All Program -> Opalis Software -> Opalis Integration Server.	8/13/2013
1	p102	1. Open Deployment Manager found in Start -> All Programs -> Opalis Software -> Opalis Integration Server.	1. Open Deployment Manager found in Start -> All Programs -> Opalis Software -> Opalis Integration Server.	8/13/2013
1	p105	5. Launch OpalisIntegrationServer_FoundationObjects.msi by issuing the following command: msiexec.exe /i “< location>\OpalisIntegrationServer_FoundationObjects.msi” /qn ALLUSERS=1./	5. Launch OpalisIntegrationServer_FoundationObjects.msi by issuing the following command: msiexec.exe /i “<location>\OpalisIntegrationServer_FoundationObjects.msi” /qn ALLUSERS=1./	8/13/2013
1	p163	For a video tutorial on the Query Database object, refer to Charles Joy’s TechNet blog post for “8 Minute Demo - Query Database Object (SQL)” at http://blogs.technet.com/b/charlesjoy/archive/2010/08/30/8-minute-demo-query-database-object-sql.aspx.	bad break fixed.	8/13/2013
1	p169	A video tutorial on the Invoke Web Services object is available at the TechNet blog post, “8 Minute Demo - Invoke Web Services Object,” located at http://blogs.technet.com/b/charlesjoy/archive/2010/08/16/8-minute-demo-invoke-web-services-object.aspx).	A video tutorial on the Invoke Web Services object is available at the TechNet blog post, “8 Minute Demo - Invoke Web Services Object,” located at http://blogs.technet.com/b/charlesjoy/archive/2010/08/16/8-minute-demo-invoke-web-services-object.aspx.	8/13/2013
1	p177	Figure 6.28 shows the four workflow control objects in the OIS client workspace.	Figure 6.28 shows the four Workflow Control objects in the OIS client workspace.	8/13/2013
1	p190	Figure 6.41 shows an example of a small legacy policy that contains all three legacy (SMTP) email objects.	Figure 6.41 shows an example of a small legacy policy that contains all three Legacy (SMTP) email objects.	8/13/2013
1	p222	For more information on creation and usage of Variables, as well as how to leverage some dynamic “Special Variables” (NOW() and %ENVVAR%), refer to Chapter 5 as well as the OIS TechNet Library entry for Using Variables available at http://technet.microsoft.com/en-us/library/gg440631.aspx. /	For more information on creation and usage of Variables, as well as how to leverage some dynamic “Special Variables” (NOW() and %ENVVAR%), refer to Chapter 5 as well as the OIS TechNet Library entry for Using Variables available at http://technet.microsoft.com/en-us/library/gg440631.aspx. /	8/13/2013
1	p224	This functionality is built-in within OIS and referred to as Self-Monitoring.	This functionality is built-in within OIS and referred to as Self-Monitoring.	8/13/2013
1	p234	For more information about this IP, it is fully documented with a User Guide at http://opalis.codeplex.com/releases/46978/download/126591 and a Usage Guide, located at http://opalis.codeplex.com/releases/46978/download/141994.	Bad break fixed.	8/13/2013
1	p279	You also need the SOAP(Simple Object Access Protocol)-API Capability Word right assigned to the user account associated with the IP.	You also need the SOAP (Simple Object Access Protocol)-API Capability Word right assigned to the user account associated with the IP.	8/13/2013
1	p310	1.1. Conditional Link (Branch Router Down)—The filtering logic in this link registers a match when the health state published by the Monitor State object equals Critical. 1.2. Conditional Link (Branch Router Up)—The filtering logic in this link registers a match when the health state published by the Monitor State object equals Healthy. j	Formatting fixed	8/13/2013
1	p313	One of the System Center Integration Packs (IPs) bundled with Opalis Integration Server (OIS) 6.3, the Microsoft System Center Service Manager (SCSM) IP allows administrators to automate Hyper-V and VMware virtualization activities from OIS via Service Manager 2010.	One of the System Center Integration Packs (IPs) bundled with Opalis Integration Server (OIS) 6.3, the Microsoft System Center Service Manager (SCSM) IP allows administrators to automate common IT business practices.	8/13/2013
1	p327	5.1. Filter Relationship Link—This link object is used to filter the results of the Get Relationship object. The Get Relationship object returns two manual activities related to the change request so the two items need to be filtered for the one that is required. Using the link, the relationship class is filtered for where the Relationship Class equals Contains Activity, as displayed in Figure 10.16. This ensures that only the manual activity for the change request is passed to the next object in the policy.	Formatting fixed.	8/13/2013
1	p334	You might have noticed that Refresh Client is missing from the permissions table.	You might have noticed that Refresh Client is missing from Table 11.1.	8/13/2013
1	p338	Each policy illustrated in this section uses two or more objects from the SCCM IP	Each policy illustrated in the following sections uses two or more objects from the SCCM IP.	8/13/2013
1	p342	3.1 Conditional Link (Write Status)—If the Result Count value from Get Software Update Compliance is not 0, it is presumed that at least one value is present. This is an easy way to determine a status is returned. Matching this result, the policy continues down to the Append Line object in step 4, writing the computer name and status to a text file. 3.2 Conditional Link (Write Unknown)—A Result Count with a value of 0 indicates that Get Software Update Compliance failed as no results are returned. Matching this result, the policy activity branches to the Append Line object in step 5, which writes the computer name and a statically assigned value of Unknown.	Formatting fixed.	8/13/2013
1	p353	Take into consideration when using Create VM from VM that the source VM must be stopped prior to initiating the cloning operation.	Take into consideration when using the Create VM from VM object that the source VM must be stopped prior to initiating the cloning operation.	8/13/2013
1	p355	See http://technet.microsoft.com/en-us/library/gg440611.aspx for additional information on the Update Disk object.	Bad break fixed	8/14/2013
1	p355	This object is used to change a variety of properties of an existing VM, such as Performance Resource Optimization (PRO) settings, install Virtualization Guest Services, or changes VM quota points used in self-service quota calculations.	This object is used to change a variety of properties of an existing VM, such as Performance Resource Optimization (PRO) settings, install Virtualization Guest Services, or change VM quota points used in self-service quota calculations.	8/14/2013
1	p357	4.1. Conditional Link (No VM)—Although the color of the link is green (because this is the success path of the policy), the filter on this link is configured to register a match when the Compare Values object reports failure. This is because you only want the policy to continue with the VM provisioning process if a VM by this name does not already exist. 4.2. Conditional Link (VM Already Exists)—Although the color of the link is red (because this is the failure path of the policy), the filter on this link is configured to register a match when the Compare Values object reports success. This is because you do not want the policy to continue with the VM provisioning process if a VM by this name already exists. 4.3. VM Already Exists—This Append Line object writes an entry to the error log indicating a VM by the name contained in vmrequest.txt already exists, and the policy terminates.	Formatting fixed	8/14/2013
1	p358	Be sure to Enter (Hyper-V) Host, VM name, path, and Source Template Name applicable to your environment in the properties of this object.	Be sure to enter (Hyper-V) Host, VM name, path, and Source Template Name applicable to your environment in the properties of this object.	8/14/2013
1	p358	5.1. Conditional Link (VM Created)—This link connects the Create VM from Template and Create New Disk objects. If the Create VM from Template object returns success, configuration of the new VM continues. 5.2. Conditional Link (Create VM Failed)—This link connects the Create VM from Template and Create VM Failed objects. If the Create VM from Template object returns failure, the logic on this link registers a match and triggers the next object in this failure branch of the policy. 5.3. Create VM Failed—This is a renamed Append Line object that logs an event to the same error log mentioned earlier and writes an event indicating that creation of the VM failed.	Formatting fixed	8/14/2013
1	p359	Figure 12.7  Define Properties used by the object	Figure 12.7  Define Properties Used by the Object	8/14/2013
1	p361	2.1. Conditional Link (Apply Updates)—If the checkpoint is successful, the link triggers the next object in the workflow. 3. Apply Updates—This renamed Trigger Policy object calls a separate update management workflow to apply the latest hotfixes to the targeted VM. The Trigger policy object is configured to publish data from the child policy indicating whether updates were applied to the VM successfully. For a refresher on how to configure data publishing between policies, refer to Chapter 5, “Policy Basics.” 3.1. Conditional Link (Update Success)—If the Trigger Policy object returns published data from the Apply Updates child policy indicating updates were applied to the VM successfully, the policy activity continues down this branch of the policy to log an event indicating a successful result. 3.2. Conditional Link (Update Failed)—If the Trigger Policy object returns published data from the Apply Updates child policy indicating updates were applied to the VM successfully, the policy activity continues down this failure branch and attempts to return the VM to a known good state.d	Formatting fixed	8/14/2013
1	p363	1. Custom Start—This policy begins with a Custom Start object, allowing the policy to be initiated from outside OIS or from other policies as part of a larger workflow. This custom start object is configured with a single parameter called VMName,	Comma at end should not be italized.	8/14/2013
1	p364	3.1. Conditional Link (Shut Down Successful)—If Shut Down VM completes successfully, policy activity continues down this branch. 3.2. Conditional Link (Clean Shut Down Failed)—If Shut Down VM returns failure, policy activity continues down this failure branch.	Formatting fixed	8/14/2013
1	p371	This object is used to take a backup of a protected data source that can be used to restore from.	This object is used to take a backup of a protected data source that can later be used to restore from.	8/14/2013
1	p384	Configure this information on the Details tab: . Query—Select BME.DisplayName, MTH.BaseManagedEntityId From BaseManagedEntity BME Inner Join MT_HealthService MTH on BME.BaseManagedEntityId=MTH.BaseManagedEntityId where BME.DisplayName like ‘{Targetname from “Custom Start”}.odyssey.com%’	Configure this information on the Details tab: Inner Join MT_HealthService MTH on BME.BaseManagedEntityId=MTH.BaseManagedEntityId where BME.DisplayName like ‘{Targetname from “Custom Start”}.odyssey.com%’	8/15/2013
1	p387	2.1. Conditional Link (No VM)—Although the color of the link is green (as this is the success path of the policy), the filter on this link is configured to register a match when the Get VM object returns Number of Objects equal to zero. This is because you want the policy to continue with the VM provisioning process only if a VM by this name does not already exist. 2.2 Conditional Link (VM Already Exists)—If the Get VM object returns “Number of Objects” greater than zero, then the VM already exists, so the policy follows this failure branch, updates the CR with a status of Failed, and the policy terminates. l	Formatting fixed.	8/15/2013
1	p388	2.3. Update CR with Error—As shown in Figure 14.6, this renamed Update Object object updates the CR to reflect a status of Failed.s	Formatting fixed.	8/15/2013
1	p389	3.1. Conditional Link (VM Created)—This link connects the Create VM from Template and Create New Disk objects. If the Create VM from Template object returns success, configuration of the new VM continues. 3.2. Conditional Link (Create VM Failed)—This link connects the Create VM from Template and Update CR with Error objects. If the Create VM from Template object returns failure, the logic on this link registers a match and triggers the next object in this failure branch of the policy. 3.3. Update CR with Error—This is a renamed Update Object object that updates the CR to reflect a status of Failed. 3.4. Conditional Link (VM Created)—This link connects the Create VM from Template and Update CR with Success objects. If the Create VM from Template object returns success, the default link logic registers a match and triggers the Update CR with Success object. 3.5. Update CR with Success—This is a renamed Update Object object that updates the CR with a note indicating this step of the policy has completed successfully.	Formatting fixed.	8/15/2013
1	p393	3. User Already Exists?—After importing the Windows 2008 R2 Active Directory PowerShell module, this Run .Net Script object (displayed in Figure 14.11) runs a 3.1 Conditional Link (User Exists)—If the value returned in OPD_Exists in object 3 (refer to Figure 14.8) equals true (indicating a user by this name already exists), activity is directed down this failure branch, the CR updates as Failed, and the workflow terminates.i PowerShell script to determine if a user account with the name retrieved from the file already exists.a	Text after 3.1 should be with 3 and the formatting of 3.1 fixed.	8/15/2013
1	p394	4.1 Conditional Link (Acct Create Failed)—If the Create New User object returns failure for any reason, activity is directed down this failure branch, the CR updates as Failed, and the workflow terminates. 5. User Exists—This step is intended to confirm that the Create New User object achieved the desired result. This Run .Net Script object runs the same PowerShell script as object 3 to determine if a user account with the name retrieved from the file already exists in Active Directory. There is one value published from this object, which is OPD_Exists. The value of OPD_Exists is either true (if the account already exists) or false if it does not. 5.1 Conditional Link (Failure - Escalate)—If the value returned in OPD_Exists in object 3 equals false (indicating the user account does not exist), activity is directed down this failure branch, the CR updates as Failed, and the workflow terminates. If the checkpoint is successful, the link triggers the next object in the workflow.	Formatting fixed.	8/15/2013
1	p457	This is why you only see two available Classes in the Add Configuration dialog, although all classes are listed Class picker at the QIK object level.	This is why you only see two available classes in the Add Configuration dialog, although all classes are listed Class picker at the QIK object level.	8/15/2013
1	p477	Policy and object execution log data Data is never purged from these tables unless explicitly requested or scheduled by the user; even then, only policy and object execution log data can be purged. All other data items remain untouched. You can purge the data using the OIS Client, as Microsoft does not support direct manipulation of the objects within the OIS database.	Policy and object execution log data Data is never purged from these tables unless explicitly requested or scheduled by the user; even then, only policy and object execution log data can be purged. All other data items remain untouched. You can purge the data using the OIS Client, as Microsoft does not support direct manipulation of the objects within the OIS database.	8/15/2013
1	p487	Yes. Policies all have a schedule function in the properties tab.	Yes. Policies all have a schedule function in the Properties tab.	8/15/2013
1	p495	CodePlex offers community software for OIS, including sample workflows, objects, and code, at http://opalis.codeplex.com/.	bad break fixed	8/15/2013
1	p498	The OOC installation requires a considerable amount of supporting software prior to installation. The list of the required files and download links is available at http://technet.microsoft.com/en-us/library/gg440750.aspx. .	bad break fixed	8/15/2013
1	p499	Marcel Zehner at SCSMFAQ.ch has built and made available a new Opalis integration pack for Service Manager. For details, see http://blog.scsmfaq.ch/2011/04/02/ opalis-integration-pack-extension-for-service-manager//. Marcel plans to upload the IP to CodePlex and the TechNet gallery (http://gallery.technet.microsoft.com). c	Marcel Zehner at SCSMFAQ.ch has built and made available a new Opalis integration pack for Service Manager. For details, see http://blog.scsmfaq.ch/2011/04/02/ opalis-integration-pack-extension-for-service-manager/. Marcel plans to upload the IP to CodePlex and the TechNet gallery (http://gallery.technet.microsoft.com). c	8/15/2013