SCCM 2012 Part 2 Notes

System Center Technical Documentation
Library
Microsoft System Center solutions can help you capture and aggregate knowledge about your
infrastructure, policies, processes, and best practices so that your IT staff can build manageable
systems and automate operations.
System Center 2012
Configuration Manager
Configuration Manager provides a

App Controller comprehensive solution for change and
configuration management for the Microsoft
App Controller provides a unified console that platform. It allows you to deploy operating
helps you manage public clouds and private systems, software applications, and software
clouds, as well as cloud-based virtual machines updates; and to monitor and remediate
and services. computers for compliance settings. With
Configuration Manager, you can also monitor
hardware and software inventory, and remotely
administer computers.
Data Protection Manager
Data Protection Manager (DPM) is a backup

and recovery solution for Microsoft workloads. Endpoint Protection
DPM provides out-of-the-box protection for
Files and Folders, Exchange Server, SQL Endpoint Protection provides an antimalware
Server, Virtual Machine Manager, SharePoint, and security solution for the Microsoft
Hyper-V, and client computers. For large-scale platform.
deployments, DPM also allows you to monitor
your backups through a central console or
remotely.
Orchestrator
Operations Manager
Orchestrator provides orchestration, integration,
and automation of IT processes through the
Operations Manager provides infrastructure
creation of runbooks, enabling you to define and
monitoring that is flexible and cost-effective,
standardize best practices and improve
helps ensure the predictable performance and
operational efficiency.
availability of vital applications, and offers
comprehensive monitoring for your datacenter
In addition, Orchestrator provides Service
and cloud, both private and public.
Provider Foundation, for hosters with
infrastructure as a service (IaaS) capabilities that
are available in System Center 2012 Service
Pack 1 (SP1).
Service Manager
Virtual Machine Manager
Service Manager provides an integrated
platform for automating and adapting your Virtual Machine Manager (VMM) is a
organization’s IT service management best management solution for the virtualized
practices, such as those found in Microsoft datacenter, enabling you to configure and
Operations Framework (MOF) and Information manage your virtualization host, networking,
Technology Infrastructure Library (ITIL). It and storage resources in order to create and
provides built-in processes for incident and deploy virtual machines and services to private
problem resolution, change control, and asset clouds that you have created.
lifecycle management.
Unified Installer
The Unified Installer is a tool that enables a single user-interface (UI) experience for the
installation of seven System Center 2012 components. The Unified Installer provides a means of
distributed installation from a central point using the existing Setup program of each component.
Unified Installer is not compatible with System Center 2012 SP1.
System Center Packs
 Operations Manager Management Pack Guides
 System Center Orchestrator 2012 Integration Packs
 System Center Cloud Services Process Pack
Previous System Center Products
 System Center Configuration Manager 2007
 System Center Data Protection Manager 2010
 System Center Essentials 2010
 Opalis Integration Server 6.3
 System Center Operations Manager 2007 R2
 System Center Service Manager 2010 SP1
 System Center Virtual Machine Manager 2008 and Virtual Machine Manager 2008 R2
Related Sites
 IT Training and Certification Resources

 System Center Downloads
 System Center Troubleshooting and Support
 System Center Community
 System Center TechCenter Home
 Integration Packs for System Center 2012

- Orchestrator
 18 out of 29 rated this helpful - Rate this topic
 Updated: November 1, 2013
 Applies To: System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator
 System Center 2012 - Orchestrator includes over 41 built-in workflow standard activities
that perform a wide variety of functions. You can expand Orchestrator’s functionality and
ability to integrate with other Microsoft and third-party platforms and products by
installing integration packs. Integration packs for Orchestrator contain additional
activities that extend the functionality of Orchestrator.
 You can download integration packs from the Microsoft Download Center. Each
integration pack has a guide that provides installation instructions, describes any known
issues, and includes reference information for all of the activities supported by the
integration pack.
 For more information about the integration packs for the System Center 2012
components, see the System Center 2012 Integration Guide.
 Microsoft provides integration packs for all of the System Center products, as well as
other Microsoft and third party products and technologies.
 The following integration packs are available:
 Active Directory Integration Pack for System Center 2012 - Orchestrator
 Exchange Admin Integration Pack for Orchestrator in System Center 2012 SP1
 Exchange Users Integration Pack for Orchestrator in System Center 2012 SP1
 FTP Integration Pack for Orchestrator in System Center 2012 SP1
 HP iLO and OA Integration Pack for System Center 2012 - Orchestrator
 HP Operations Manager Integration Pack for System Center 2012 - Orchestrator
 HP Service Manager Integration Pack for System Center 2012 - Orchestrator
 IBM Tivoli Netcool/OMNIbus Integration Pack for System Center 2012 - Orchestrator
 Representational State Transfer (REST) Integration Pack Guide for Orchestrator in
System Center 2012 SP1
 System Center Integration Pack for Microsoft SharePoint
 Windows Azure Integration Pack for Orchestrator in System Center 2012 SP1
 VMware vSphere Integration Pack for System Center 2012 - Orchestrator
 Integration Packs for System Center
Active Directory Integration Pack for System
Center 2012 - Orchestrator
1 out of 3 rated this helpful - Rate this topic
Updated: November 1, 2013
Applies To: System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator, System
Center 2012 SP1 - Orchestrator
The Integration Pack for Active Directory is an add-on for System Center 2012 - Orchestrator
that enables you to automate common Active Directory management functions.
Microsoft is committed to protecting your privacy, while delivering software that brings you the
performance, power, and convenience you want. For more Orchestrator-related privacy
information, see the Privacy Statement for System Center 2012 – Orchestrator.
System Requirements
Before you can install the Integration Pack for Active Directory, you must first install and
configure the following listed software. For more information about how to install and configure
Orchestrator and Active Directory, refer to the respective product documentation.
 System Center 2012 integration packs require System Center 2012 - Orchestrator.
 System Center 2012 Service Pack 1 (SP1) integration packs require Orchestrator in System
Center 2012 Service Pack 1 (SP1).
 Windows Server 2012 Active Directory (for System Center 2012 Service Pack 1 (SP1) integration
packs only), Windows Server 2008 R2 Active Directory, Windows Server 2008 Active Directory,
Windows Server 2003 R2 Active Directory, or Windows Server 2003 Active Directory.
Downloading the Integration Pack
To download this integration pack, see Active Directory Integration Pack for System Center
2012 - Orchestrator.
Registering and Deploying the Integration Pack
After you download the integration pack file, you must register it with the Orchestrator
management server and then deploy it to runbook servers and Runbook Designer. For specific
procedures, see How To Install an Integration Pack.
Configuring the Active Directory Connections
An Active Directory connection is a reusable link between Orchestrator and an Active Directory
domain controller. You can specify as many connections as you require to create links to
multiple domain controllers. You can also create multiple connections to the same domain
controller to allow for differences in security permissions for different user accounts.
To set up an Active Directory connection
1. In the Runbook Designer, click Options, and then click Active Directory. The Active
Directory dialog box appears.
2. On the Configurations tab, click Add to begin the connection setup. The Add
Configuration dialog box appears.
3. In the Name box, enter a name for the connection. This could be the name of the Active
Directory domain, or a descriptive name to distinguish the type of connection.
4. Click the ellipsis button (...) next to the Type box and select Microsoft Active Directory
Domain Configuration. Click OK.
5. In the Configuration User Name and Configuration Password boxes, type the
credentials that Orchestrator will use to log on to Active Directory. This user account
must have the authority to perform the actions in any runbook where the connection is
used.
6. In the Configuration Domain Controller Name (FQDN) box type the fully qualified
name of the domain or domain controller for the connection.
7. In the Configuration Default Parent Container box, type the default Distinguished
Name for an Organizational Unit or Common Name. This default will be used when an
activity such as Create User or Create Computer does not specify the Container
Distinguished Name.
Examples of Configuration Default Parent Container include the following:

CN=Users, DC=mydomain, DC=com and OU=MyOU, DC=mydomain, DC=com
8. Click OK to close the configuration dialog box.

9. Add additional connections if applicable.
10. Click Finish.
Exchange Admin Integration Pack for

Orchestrator in System Center 2012 SP1
Applies To: System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator
Integration packs are add-ons for System Center 2012 - Orchestrator, a component of System
Center 2012 Service Pack 1 (SP1). Integration packs help to optimize IT operations across
heterogeneous environments. They enable you to design runbooks in Orchestrator that use
activities performed by other System Center components, other Microsoft products, and other
third party products.
The Integration Pack for Exchange Admin helps to facilitate the automation of Exchange
administration tasks, such as mailbox management, for on-premise, remote, or cloud-based
environments in Microsoft Exchange and Office 365.
Microsoft is committed to protecting your privacy while delivering software that brings you the
performance, power, and convenience you want. For more information about Orchestrator-
related privacy, see the System Center Orchestrator 2012 Privacy Statement.
System requirements
Before you implement the Integration Pack for Exchange Admin, the following listed software
must be installed. For more information about installing and configuring Orchestrator and the
Exchange Admin Integration Pack, refer to the respective product documentation.
 System Center 2012 - Orchestrator or Orchestrator in System Center 2012 SP1
 Microsoft .NET Framework 3.5 Service Pack 1
 Microsoft Exchange 2010 Service Pack 2 or Microsoft Exchange 2012 or Microsoft Exchange
Online/Office 365
 Microsoft Exchange Management Shell
 Microsoft PowerShell 2.0
 Microsoft WinRM 2.0
To download the Exchange Admin Integration Pack, see the Download Center site.
Register and Deploy the Integration Pack
management server and then deploy it to runbook servers and Runbook Designers. For the
procedures on installing integration packs, see How to install an Integration Pack.
Configure the Exchange Admin Integration Pack connections
A connection establishes a reusable link between and an Exchange server. You can specify as
many connections as you require to create links to multiple servers. You can also create multiple
connections to the same server to allow for differences in security permissions for different user
accounts.
To set up an Exchange Configuration connection
1. In the Orchestrator Runbook Designer, click Options, and then click Exchange
Admin. The Exchange Admin dialog box appears.
3. In the Name box, enter a name for the connection. This can be the name of the Exchange
server or a descriptive name to differentiate the type of connection.
4. Click the (…) button and select Exchange Configuration.
5. In the Exchange Server Host box, type the name or IP address of the Exchange server.
To use a computer name, you can type the NetBIOS name or the fully qualified domain
name (FQDN).
6. In the Exchange Server Port box, enter the port that is used to communicate with the
Exchange server. If you use SSL, be sure to select the appropriate port.
7. In the Exchange PowerShell Application box, enter the application name segment of
the connection URI.
8. In the Exchange User Name and Exchange User Password boxes, type the credentials
that Orchestrator will use to log on to the Exchange environment. The configured user
must have the appropriate Exchange permissions.
9. Configure the Exchange Environment as necessary for connecting to an On-Premise
installation or to Office.
10. Set the Use SSL property to True to have all communication between the runbook server
and the Exchange server encrypted over HTTPS.
11. If you use SSL, the Skip CA Check property specifies whether the client does not
validate that the server certificate is signed by a trusted certification authority (CA).
12. If you use SSL, the Skip CN Check property specifies that the certificate common name
(CN) of the server does not need to match the hostname of the server.
13. If you use SSL, the Skip Revocation Check property specifies whether the revocation
status of the server certificate will not be checked for validity.
14. Click OK.
16. Click Finish.
Configure Windows PowerShell and WinRM for the Exchange Admin
Integration Pack
To configure 32-bit PowerShell to run scripts
1. On the computer where Orchestrator runbooks are executed, make sure that 32-bit
PowerShell scripts can be run:
1. Start Windows PowerShell (x86) command line.
2. To determine whether PowerShell 32-bit scripts can be executed, run the following
command:
Copy
Get-ExecutionPolicy
3. If Execution Policy is Restricted, you must change it to RemoteSigned. Run the

following command:
Copy
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
To configure remote PowerShell rights for the Exchange user
1. The configured user must be granted remote PowerShell rights on the Exchange server:
1. On the Exchange server, start the Exchange Management Shell.
2. To determine whether the user has remote PowerShell rights, run the following
command and check the value in the RemotePowerShellEnabled field:
Copy
Get-User <UserName>
3. To grant the user remote PowerShell rights, run the following command:
Copy
Set-User <UserName> -RemotePowerShellEnabled $true
To configure Windows PowerShell to allow Basic Authentication on the Exchange server
1. On the Exchange server, make sure that PowerShell Basic Authentication is enabled:
2. Start Internet Information Services (IIS) Manager.
3. Navigate to the PowerShell site.
4. Open the Authentication settings.
5. Make sure Basic Authentication is enabled.
To configure WinRM for HTTP unencrypted communication
1. On the machine where Orchestrator runbooks are executed, configure WinRM trusted
hosts and to allow unencrypted traffic:
1. Open the Local Group Policy user interface: Windows Start Button > Run > gpedit.msc.
2. Navigate to Local Computer Policy > Computer Configuration > Administrative

Templates > Windows Components > Windows Remote Management (WinRM) >
WinRM Client.
3. Make sure that Allow unencrypted traffic is Enabled.
4. Add the targeted computer that runs Exchange Server to the Trusted Hosts list.
2. On the Exchange server, make sure that PowerShell does not require SSL:
1. Start Internet Information Services (IIS) Manager.
2. Navigate to the PowerShell site.
3. Open SSL Settings.
4. Make sure that the Require SSL check box is not selected.
Exchange Users Integration Pack for

Integration packs are add-ons for Orchestrator, a component of System Center 2012 Service Pack
1 (SP1). Integration packs optimize IT operations across various environments. They enable you
to design runbooks in Orchestrator that use activities performed by other System Center
components, other Microsoft products, and third party products. The Integration Pack for
Exchange Users facilitates the automation of user-centric tasks, such as actions to send email
messages, create appointments, or update tasks.
Microsoft is committed to protecting your privacy while delivering software that brings you the
performance, power, and convenience you want. For Orchestrator-related privacy information,
see the System Center Orchestrator 2012 Privacy Statementhttp://technet.microsoft.com/en-
us/library/.
System Requirements
Prior to implementing the Exchange Users Integration Pack, the following listed software must
be installed and configured. For more information about installing and configuring Orchestrator
and the Exchange Users Integration Pack, refer to the respective product documentation.
 System Center 2012 - Orchestrator
 Microsoft .NET Framework 3.5
 Microsoft Exchange 2010 Service Pack 1 or Microsoft Exchange 2013 or Microsoft Exchange
Online/Office 365
To download this the Exchange Users Integration Pack, go to the Download Center site.
procedures on installing integration packs, see How to Install an Integration Pack.
Configuring the Exchange Users Integration Pack Connections
A connection establishes a reusable link between the Orchestrator and an Exchange server. You
can specify as many connections as necessary to create links to multiple servers. You can also
create multiple connections to the same server to allow for differences in security permissions for
different user accounts.
The integration pack supports two types of Exchange configurations: the basic Exchange
Configuration connection and the Exchange Item Type configuration.
The basic Exchange Configuration contains connection information that is used by activities
where the item type is either implicit or not required, such as the Send E-Mail and Delete Item
activities.
To set up an Exchange Configuration connection
1. In the Orchestrator Runbook Designer, click Options, and then click Exchange User.
The Exchange User dialog box appears.
3. In the Name box, enter a name for the connection. This can be the name of the computer
running Exchange Server or a descriptive name to distinguish the type of connection.
4. In the Type box, select Exchange Configuration.
5. In the Exchange Server Address box, type the name or IP address of the Exchange
server. If you are using the computer name, you can type the NetBIOS name or the fully
qualified domain name (FQDN). You may leave the Exchange Server Address box
empty if you enable the Use Autodiscover option.
6. In the Username and Password boxes, type the credentials that Orchestrator will use to
connect to the Exchange server.
7. In the Domain box, type the name of the domain that will authorize access.
8. In the Timeout box, enter a timeout value or leave the default.
9. Click OK.
10. Add any additional connections if applicable, and then click Finish.
The Exchange Item Type Configuration contains connection information and lets users specify
an Exchange item type. The Exchange Item Configuration activity is used by activities that
dynamically generate optional and required properties, filter and published data, as is the case
with the Create Item and Get Item activities.
To set up a Exchange Item Type connection
1. In the Orchestrator Runbook Designer, click Options, and then click Exchange User.
The Exchange User dialog box appears.
3. In the Name box, enter a name for the connection. This can be the name of the Exchange
server or a descriptive name to distinguish the type of connection.
4. In the Type box, select Exchange Configuration (Item Activity).
5. In the Exchange Server Address box, type the name or IP address of the Exchange
qualified domain name (FQDN). You may leave the Exchange Server Address box
empty if you enable the Use Autodiscover option.
connect to the Exchange server.
7. In the Domain box, type the name of the domain that will authorize access.
8. In the Timeout box, enter a timeout value or leave the default.
9. In the Item Type box, enter a valid Exchange Item Type.
10. Add any additional connections if applicable, and then click Finish.
FTP Integration Pack for Orchestrator in

Integration packs are add-ons for Orchestrator, a component of System Center 2012 Service Pack
1 (SP1), that can help you optimize IT operations across heterogeneous environments. You can
design runbooks in Orchestrator that use activities performed by other System Center
components, other Microsoft products, and by third party products. The Integration Pack for FTP
enables you to automate FTP operations which include creating a folder, deleting a file or folder,
downloading, uploading, file and folder listing and synchronization.
performance, power, and convenience you want. For more information, see the System Center
Orchestrator 2012 Privacy Statement (http://go.microsoft.com/fwlink/?LinkID=216995).
System Requirements
The Integration Pack for FTP requires the following software to be installed and configured prior
to implementing the integration. For more information about installing and configuring
Orchestrator and FTP, refer to the respective product documentation.
 Orchestrator in System Center 2012 SP1
 FTP server
Download the Integration Pack
To download the FTP integration pack, see the Download Center site.
procedures on installing integration packs, see How To Install an Integration Pack.
Configuring the FTP Connections
A connection establishes a reusable link between Orchestrator and an FTP server. You can create
as many connections as you require specifying links to multiple FTP servers. You can also create
multiple connections to the same server to allow for differences in security permissions for
To set up an FTP connection
1. In the Orchestrator Runbook Designer, click Options, and then click FTP. The FTP
dialog box appears.
3. In the Name box, enter a name for the connection. This can be the name of the FTP
server, or a descriptive name to distinguish the type of connection.
4. In the Type box, click the … button and select a configuration type.
5. In the Connection Type box, click the … button and select a connection type.
6. In the Transfer Type (FTP) box, click the … button and select a transfer type. This
configuration property applies to FTP only. This property can be left empty when the
connection type is SSH File Transfer Protocol (SFTP).
Note
Orchestrator does not support SFTP on computers that run Windows.
7. In the Server box, type the name or IP address of the FTP server. If you are using the
computer name, you can type the NetBIOS name or the fully qualified domain name
(FQDN).
8. In the Port box, type the port number for the selected connection type.
connect to the FTP server.
10. In the Timeout box, type the amount of time in seconds before an FTP operation will
time out.
11. In the Certificate Path (FTP) box, type the path to a certificate. This configuration
property applies to FTP only. This configuration property is optional and can be left
empty.
12. In the Certificate Password (FTP) box, type the password for the certificate. This
configuration property applies to FTP only. This configuration property is optional and
can be left empty.
13. In the HTTP Proxy Server (FTP) box, type the name of IP address of the HTTP proxy
qualified domain name (FQDN). This configuration property applies to FTP only. This
configuration property is optional and can be left empty.
14. In the HTTP Proxy Port (FTP) box, type the port number for the HTTP proxy server.
This configuration property applies to FTP only. This configuration property is optional
and can be left empty.
15. In the HTTP Proxy Username (FTP) and HTTP Proxy Password (FTP), type the
credentials that Orchestrator will used to connect to the HTTP proxy server. This
configuration property applies to FTP only. This configuration property is optional and
can be left empty.
16. Click OK to close the configuration dialog box, and then click Finish.
HP iLO and OA Integration Pack for System
Center 2012 - Orchestrator
This topic has not yet been rated - Rate this topic
Applies To: System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator
The Integration Pack for HP iLO and OA is an add-on for System Center 2012 - Orchestrator
that enables you to automate HP iLO and OA commands.
performance, power, and convenience you want. For more information, see the System Center
Orchestrator 2012 Privacy Statement (http://go.microsoft.com/fwlink/?LinkID=216995).
System Requirements
The Integration Pack for HP iLO and OA requires the following software to be installed and
configured prior to implementing the integration. For more information about installing and
configuring Orchestrator and HP iLO and OA, refer to the respective product documentation.
 System Center 2012 integration packs require System Center 2012 - Orchestrator
Center 2012 Service Pack 1 (SP1)
 HP iLO 2
 HP iLO 3
 HP OA firmware 3.31
To download this integration pack, see HP iLO and OA Integration Pack for System Center 2012
- Orchestrator.
management server and then deploy it to Runbook servers and Runbook Designers. For the
Default Credentials
Default credentials are used to store a common set of credentials that can be selected when
configuring a HP iLO and OA connection.
To set up default credentials
1. In the Runbook Designer, click the Options menu, and select HP iLO and OA. The HP
iLO and OA dialog box appears.
2. On the Connections tab, click Default credentials to begin the setup. The Default
credentials dialog box appears.
3. In the User name box, enter a default user name.
4. In the Password box, enter a default password.
5. In the Key box, enter a default key Or click the ellipsis (…) button to browse and select a
Key.
6. Click OK to close the default credentials dialog box.
Configuring the HP iLO and OA Connections
A connection establishes a reusable link between Orchestrator and a HP iLO and OA system.
You can create as many connections as you require to specify links to multiple systems running
HP iLO and OA. You can also create multiple connections to the same system to allow for
differences in security permissions for different user accounts.
To set up a HP iLO and OA connection
1. In the Runbook Designer, click Options, and then click HP iLO and OA. The HP iLO
and OA dialog box appears.
2. On the Connections tab, click Add to begin the connection setup. The Connection
dialog box appears.
3. In the Name box, enter a name for the connection. This could be the name of the HP iLO
and OA system or a descriptive name to distinguish the type of connection.
4. In the Address box, type the name or IP address of the HP iLO and OA system. If you
are using the computer name, you can type the NetBIOS name or the fully qualified
domain name (FQDN).
5. In the Port box, type the number of the HP iLO and OA system.
6. Select Use default credentials to apply the default credentials to this connection. If you
do this, then you can skip the next two steps.
connect to the HP iLO and OA system.
8. In the Private Key box, optionally specify the SSH key used to connect to the HP iLO
and OA system.
9. In the Attempts box, enter the number or times a command will attempt before failing.
10. In the Time between attempts box, enter the number in seconds between each attempt.
12. Select the connection and click the Test button. Test connection succeeded will appear
when the connection is valid. Click Finish.
Exporting and Importing Connections
Connections can be exported and imported into the connections list.
To export a connection
2. On the Connections tab, click Export to begin the export. The Save As dialog box
appears.
3. In the File name box, enter a name for the export file.
4. Click Save to export.
5. Click OK to close the configuration dialog box and then click Finish.
To import a connection
2. On the Connections tab, click Import to begin the import. The Open dialog box
appears.
3. In the File name box, enter a name for the import file.
4. Click Open to import.
5. Click OK to close the configuration dialog box and then click Finish.
Configuring the HP iLO and OA Groups
A group establishes a reusable list of connections between Orchestrator and a HP iLO and OA
systems. You can create as many groups as you require to specify lists to multiple systems
running HP iLO and OA.
To set up a HP iLO and OA group
2. On the Groups tab, click Add to begin the group setup. The Managed group dialog box
appears.
3. In the Group name box, enter a name for the group. This could be a descriptive name to
distinguish the type of group.
4. In the Available list, press the Ctrl button while clicking on the connections to select
multiple connections. Press the >> button to move the connections to the Selected list.
To batch update credentials on a group
2. On the Groups tab, select a group and click Batch credential update.
3. In the User name box, enter a new user name or leave blank to keep original.
4. In the Password box, enter a new password or leave blank to keep original.
5. In the Key box, enter a new key or leave blank to keep original.
6. In the Port box, enter a new port or leave blank to keep original.
HP Operations Manager Integration Pack for

System Center 2012 - Orchestrator
The Integration Pack for HP Operations Manager is an add-on for System Center 2012 -
Orchestrator that enables you to automate the consolidation and correlation of fault and
performance events across you entire physical and virtual IT infrastructure.
performance, power, and convenience you want. For more information, see the Privacy
Statement for System Center 2012 - Orchestrator.
System Requirements
The Integration Pack for HP Operations Manager requires the following software to be installed
and configured prior to implementing the integration. For more information about installing and
configuring Orchestrator and the HP Operations Manager application, refer to the respective
product documentation.
 HP Operations Manager 9.x

To download this integration pack, see HP Operations Manager Integration Pack for System
Center 2012 - Orchestrator.
Configuring the HP Operations Manager Connections
A connection establishes a reusable link between Orchestrator and an HP Operations Manager

server. You can create as many connections as you require to specify links to multiple servers
running HP Operations Manager. You can also create multiple connections to the same server to
allow for differences in security permissions for different user accounts.
To set up an HP Operations Manager configuration
1. In the Runbook Designer, click the Options menu, and select HP Operations Manager.
The HP Operations Manager dialog box appears.
3. In the Name box, enter a name for the connection. This could be the name of the HP
Operations Manager server or a descriptive name to distinguish the type of connection.
4. Click the ellipsis button (…) next to the Type field and then select HPOM
Configuration.
5. In the HPOM Host box, type the name or IP address of the HP Operations Manager
computer. If you are using the computer name, you can type the NetBIOS name or the
fully qualified domain name (FQDN).
6. In the HPOM Port box, type the port used to connect to the HP Operations Manager
computer. By default the HPOM Port is set to 443.
7. In the HPOM Username and HPOM Password boxes, type the credentials that
Orchestrator will use to connect to the HP Operations Manager server. When a
connection is used for a Launch Tool activity, an HPOM Administrator account must be
used. All other activities can use an HPOM User account.
10. Click Finish.
HP Operations Manager Integration Pack for

The Integration Pack for HP Operations Manager is an add-on for System Center 2012 -
Orchestrator that enables you to automate the consolidation and correlation of fault and
performance events across you entire physical and virtual IT infrastructure.
System Requirements
The Integration Pack for HP Operations Manager requires the following software to be installed
and configured prior to implementing the integration. For more information about installing and
configuring Orchestrator and the HP Operations Manager application, refer to the respective
 HP Operations Manager 9.x
To download this integration pack, see HP Operations Manager Integration Pack for System
Center 2012 - Orchestrator.
Configuring the HP Operations Manager Connections
A connection establishes a reusable link between Orchestrator and an HP Operations Manager

server. You can create as many connections as you require to specify links to multiple servers
running HP Operations Manager. You can also create multiple connections to the same server to
allow for differences in security permissions for different user accounts.
To set up an HP Operations Manager configuration
1. In the Runbook Designer, click the Options menu, and select HP Operations Manager.
The HP Operations Manager dialog box appears.
Operations Manager server or a descriptive name to distinguish the type of connection.
4. Click the ellipsis button (…) next to the Type field and then select HPOM
Configuration.
5. In the HPOM Host box, type the name or IP address of the HP Operations Manager
6. In the HPOM Port box, type the port used to connect to the HP Operations Manager
computer. By default the HPOM Port is set to 443.
7. In the HPOM Username and HPOM Password boxes, type the credentials that
Orchestrator will use to connect to the HP Operations Manager server. When a
connection is used for a Launch Tool activity, an HPOM Administrator account must be
used. All other activities can use an HPOM User account.
10. Click Finish.
HP Service Manager Integration Pack for

The integration pack for HP Service Manager is an add-on for Orchestrator in System Center
2012 Service Pack 1 (SP1) and System Center 2012 - Orchestrator that enables you to retrieve,
create, update and monitor tickets in HP Service Manager. Microsoft is committed to protecting
your privacy, while delivering software that brings you the performance, power, and
convenience you want. For more information, see the System Center Orchestrator 2012 Privacy
Statement (http://go.microsoft.com/fwlink/?LinkID=216995).
System Requirements
The integration pack for HP Service Manager requires the following software to be installed and
configured to implementing the integration. For more information about installing and
configuring Orchestrator and the HP Service Manager Web Service, refer to the respective
 HP Service Manager 7.11 or 9
The following software must be installed on each Runbook Server and Runbook Designer:
 Microsoft SQL Server Native Client ODBC driver (Installed with SQL Server Management Tools)
 For access to the HP Service Manager database on SQL Server:
o Microsoft SQL Server Native Client ODBC driver (Installed with SQL Server Management
Tools)
 For access to the HP Service Manager database on Oracle:
o Oracle Client (Net Configuration Assistant)
o Oracle ODBC driver
To download this integration pack, see HP Service Manager Integration Pack for System Center
Preparing to connect to the HP Service Manager Server
 Make a record of the HP Service Manager server name and port number used to connect the HP
Service Manager client.
 For all HP Service Manager servers that you plan to connect to you must create an ODBC data
source name (DSN) on each Client and Runbook server. Both SQL Server Native and Oracle ODBC
connections are supported. See Configuring the HP Service Manager Connections.
 The licensing model for the components of HP Service Manager varies depending on the version
installed. Consult the HP product documentation to determine which components are licensed
separately. This integration pack requires HP Service Manager SOAP web service access to
operate correctly. Ensure that this component is installed and licensed, if necessary.
 Ensure that the user configured to access the HP Service Manager server has been assigned the
SOAP-API CAPABILITY WORD in the HP Service Manager system. Depending on the version of HP
Service Manager, it may be necessary to purchase extra licensing to enable the SOAP-API
CAPABILITY WORD. Consult your HP Sales Representative for further information about
licensing.
Configuring the HP Service Manager Connections
A connection establishes a reusable link between Orchestrator and a HP Service Manager server.
You can create as many connections as you require specifying links to multiple servers running
HP Service Manager. You can also create multiple connections to the same server to allow for
The HP Service Manager integration pack requires a connection to the HP Service Manager SQL
Server Database when designing runbooks in the Runbook Designer. A valid ODBC connection
must be configured before setting up the HP Service Manager connection in the Runbook
Designer.
To set up a SQL Server ODBC connection
1. Open the ODBC Data Source Administrator Utility (32-bit). To access this utility,
click Start, Run, and then type \Windows\SysWOW64\odbcad32.exe in the Open box.
Click OK.
2. In the ODBC Data Source Administrator, click the System DSN tab.
3. Click Add.
4. Select the driver named SQL Server Native Client 10.0 from the list of available
drivers.
5. Click Finish.
6. Enter a new name and description for the data source.
7. Enter the HP Service Manager database server name or IP address in the Server box.
8. Click Next.
9. Select the appropriate authentication method for the database server and enter valid
credentials.
10. Click Next.
11. Ensure the check box Change the default database to: is selected.
12. In the drop-down list below the check box select the HP Service Manager database.
13. Click Next.
14. Click Finish.
15. Click Test Data Source to confirm connectivity to the database.
16. When the test completes, click OK.
17. Click OK.
Setting up an Oracle ODBC Connection
1. Configure an Oracle Net Service name using the Oracle Net Configuration Assistant. For
more information on this step refer to the relevant Oracle product documentation.
2. Open the ODBC Data Source Administrator Utility (32-bit). To access this utility, click
Start, then Run, and then type \Windows\SysWOW64\odbcad32.exe in the Open box.
Click OK.
4. Click Add.
5. Select the Oracle ODBC driver installed with the Oracle client from the list of available
drivers.
6. Click Finish.
8. Enter the TNS Service Name for the HP Service Manager database as configured in the
Net Configuration Assistant.
9. Test the connection, supplying credentials if necessary.
credentials.
11. Click OK.
12. Click OK to close the ODBC Data Source Administrator.
To set up a HP Service Manager connection
1. In the Runbook Designer, click the Options menu, and select HP Service Manager. The
HP Service Manager dialog box appears.
Configuration dialog box will appear.
Service Manager server or a descriptive name to distinguish the type of connection.
4. In the Server Address box, type the name or IP address of the HP Service Manager
5. In the Polling Interval box, enter the how often, in minutes, you want to check the state
of the HP Service Manager connection.
6. In the ODBC DSN box, type the name of the ODBC data source from one of the
previous procedures.
7. Enter the database user name in the DB Username box.
8. Enter the database password in the DB Password box.
connect to the HP Service Manager server.
10. Click Test Connection. When the message "Connected Successfully" appears, click OK.
11. In the connection list dialog, select the newly created connection by clicking the
appropriate item in the list.
12. Click the Refresh Field Cache button to retrieve and store the custom configuration
from the HP Service Manager server. This operation may take a few minutes to complete
and is essential to allow the integration pack to connect correctly to a new HP Service
Manager server.
13. Add additional connections to other HP Service Manager servers, if applicable.
Tip
For the DB Username and DB Password – If your HPSM database is on a computer running Windows
server and you set up your ODBC DSN with Windows authentication, then you can enter anything in for
the username and password because the fields are required only not to be blank in order for the Test
Connection button to work.
If you are using SQL Server authentication, then you must have the username and password for the
HPSM SQL Server database. The user must have read/write access to the database via the DSN
connection.
Exposing Required Fields
If an activity reports an error and indicates that a required field must be specified but the IP does
not provide the field in the user interface, the field must be exposed through the HP Service
Manager Web service API. To expose the field complete the following procedure:
To expose a required field
1. Open the HP Service Manager client.

2. Connect to the desired HP Service Manager server.
3. In the System Navigator, navigate to Tailoring Tools, then Web Services, then WSDL
Configuration and double click the WSDL Configuration option.
4. In the External Access Definition dialog click the Search button to list all available
objects.
5. Select the required object from the object list.
6. Select the Fields tab.
7. Scroll to the bottom of the Field List.
8. Enter the database name of the field to be exposed in the Field column.
9. Enter the name which the web service will refer to this field in the Caption column.
10. Ensure the data type is correct in the Type column.
11. Click Save at the top of the page to save the message.
Known Issues
 The Test Connection button cannot be used to validate Service Manager 7.1 web service
connections if the HP ServiceCenter 6.2 web service has been disabled.
 Certain permissions are required when dealing with Change tickets. These permissions are
specified by assigning a user a Change Management Profile. While a user can have more than
one profile, it can only belong to one profile per session. If the user is assigned more than one
Change Management Profile it will automatically use the first profile in alphabetical order. To
avoid confusion it is recommended that the user configured for use with the integration pack is
only assigned one Change Management Profile.
 The user configured for use with the integration pack must have its time zone preferences set to
Greenwich/Universal with a date format of mm/dd/yy.
 In certain versions of HP Service Manager the list of available categories when creating an
incident displays Change yet choosing it causes the object to fail with the following message.
Please provide a valid category. This is a known issue with the HP Service Manager server.
Ensure that the fields are visible to the web service (See Troubleshooting) and that the HP
Service Manager server is patched to the latest version.
 The Set as default button available in the Create Entry, Update Entry and Close Entry activities
may report an error when clicked. Use the following procedure to work around this issue.
1. Note the file path in the error message. For example,

C:\Users\[CurrentUser]\AppData\Local\Microsoft\System Center
2012\Orchestrator\IntegrationPacks\HPServiceManager\[GUID]\defaultFields.xml
2. Ensure that each of the folders in the file path exists exactly as shown in the error
message.
3. Create any missing folders if necessary.
if the Runbook Designer is launched by a user without administrative privileges on the

computer. In the current version of the integration pack, ensure that the user has sufficient
permissions to write to the %COMMONPROGRAMFILES(x86)%\Microsoft System Center
2012\Orchestrator\Extensions\Support\HPServiceManager\ directory.
HP Service Manager Integration Pack for

The integration pack for HP Service Manager is an add-on for Orchestrator in System Center
2012 Service Pack 1 (SP1) and System Center 2012 - Orchestrator that enables you to retrieve,
create, update and monitor tickets in HP Service Manager. Microsoft is committed to protecting
your privacy, while delivering software that brings you the performance, power, and
convenience you want. For more information, see the System Center Orchestrator 2012 Privacy
Statement (http://go.microsoft.com/fwlink/?LinkID=216995).
System Requirements
The integration pack for HP Service Manager requires the following software to be installed and
configured to implementing the integration. For more information about installing and
configuring Orchestrator and the HP Service Manager Web Service, refer to the respective
 HP Service Manager 7.11 or 9
The following software must be installed on each Runbook Server and Runbook Designer:
 Microsoft SQL Server Native Client ODBC driver (Installed with SQL Server Management Tools)
 For access to the HP Service Manager database on SQL Server:
o Microsoft SQL Server Native Client ODBC driver (Installed with SQL Server Management
Tools)
 For access to the HP Service Manager database on Oracle:
o Oracle Client (Net Configuration Assistant)
o Oracle ODBC driver
To download this integration pack, see HP Service Manager Integration Pack for System Center
Preparing to connect to the HP Service Manager Server
 Make a record of the HP Service Manager server name and port number used to connect the HP
Service Manager client.
 For all HP Service Manager servers that you plan to connect to you must create an ODBC data
source name (DSN) on each Client and Runbook server. Both SQL Server Native and Oracle ODBC
connections are supported. See Configuring the HP Service Manager Connections.
 The licensing model for the components of HP Service Manager varies depending on the version
installed. Consult the HP product documentation to determine which components are licensed
separately. This integration pack requires HP Service Manager SOAP web service access to
operate correctly. Ensure that this component is installed and licensed, if necessary.
 Ensure that the user configured to access the HP Service Manager server has been assigned the
SOAP-API CAPABILITY WORD in the HP Service Manager system. Depending on the version of HP
Service Manager, it may be necessary to purchase extra licensing to enable the SOAP-API
CAPABILITY WORD. Consult your HP Sales Representative for further information about
licensing.
Configuring the HP Service Manager Connections
A connection establishes a reusable link between Orchestrator and a HP Service Manager server.
You can create as many connections as you require specifying links to multiple servers running
HP Service Manager. You can also create multiple connections to the same server to allow for
The HP Service Manager integration pack requires a connection to the HP Service Manager SQL
Server Database when designing runbooks in the Runbook Designer. A valid ODBC connection
must be configured before setting up the HP Service Manager connection in the Runbook
Designer.
To set up a SQL Server ODBC connection
1. Open the ODBC Data Source Administrator Utility (32-bit). To access this utility,
click Start, Run, and then type \Windows\SysWOW64\odbcad32.exe in the Open box.
Click OK.
3. Click Add.
4. Select the driver named SQL Server Native Client 10.0 from the list of available
drivers.
5. Click Finish.
7. Enter the HP Service Manager database server name or IP address in the Server box.
8. Click Next.
credentials.
10. Click Next.
11. Ensure the check box Change the default database to: is selected.
12. In the drop-down list below the check box select the HP Service Manager database.
13. Click Next.
14. Click Finish.
15. Click Test Data Source to confirm connectivity to the database.
16. When the test completes, click OK.
17. Click OK.
Setting up an Oracle ODBC Connection
1. Configure an Oracle Net Service name using the Oracle Net Configuration Assistant. For
more information on this step refer to the relevant Oracle product documentation.
2. Open the ODBC Data Source Administrator Utility (32-bit). To access this utility, click
Start, then Run, and then type \Windows\SysWOW64\odbcad32.exe in the Open box.
Click OK.
4. Click Add.
5. Select the Oracle ODBC driver installed with the Oracle client from the list of available
drivers.
6. Click Finish.
8. Enter the TNS Service Name for the HP Service Manager database as configured in the
Net Configuration Assistant.
9. Test the connection, supplying credentials if necessary.
credentials.
11. Click OK.
12. Click OK to close the ODBC Data Source Administrator.
To set up a HP Service Manager connection
1. In the Runbook Designer, click the Options menu, and select HP Service Manager. The
HP Service Manager dialog box appears.
Configuration dialog box will appear.
Service Manager server or a descriptive name to distinguish the type of connection.
4. In the Server Address box, type the name or IP address of the HP Service Manager
5. In the Polling Interval box, enter the how often, in minutes, you want to check the state
of the HP Service Manager connection.
6. In the ODBC DSN box, type the name of the ODBC data source from one of the
previous procedures.
7. Enter the database user name in the DB Username box.
8. Enter the database password in the DB Password box.
connect to the HP Service Manager server.
10. Click Test Connection. When the message "Connected Successfully" appears, click OK.
11. In the connection list dialog, select the newly created connection by clicking the
appropriate item in the list.
12. Click the Refresh Field Cache button to retrieve and store the custom configuration
from the HP Service Manager server. This operation may take a few minutes to complete
and is essential to allow the integration pack to connect correctly to a new HP Service
Manager server.
13. Add additional connections to other HP Service Manager servers, if applicable.
Tip
For the DB Username and DB Password – If your HPSM database is on a computer running Windows
server and you set up your ODBC DSN with Windows authentication, then you can enter anything in for
the username and password because the fields are required only not to be blank in order for the Test
Connection button to work.
If you are using SQL Server authentication, then you must have the username and password for the
HPSM SQL Server database. The user must have read/write access to the database via the DSN
connection.
Exposing Required Fields
If an activity reports an error and indicates that a required field must be specified but the IP does
not provide the field in the user interface, the field must be exposed through the HP Service
Manager Web service API. To expose the field complete the following procedure:
To expose a required field
1. Open the HP Service Manager client.

2. Connect to the desired HP Service Manager server.
3. In the System Navigator, navigate to Tailoring Tools, then Web Services, then WSDL
Configuration and double click the WSDL Configuration option.
4. In the External Access Definition dialog click the Search button to list all available
objects.
5. Select the required object from the object list.
6. Select the Fields tab.
7. Scroll to the bottom of the Field List.
8. Enter the database name of the field to be exposed in the Field column.
9. Enter the name which the web service will refer to this field in the Caption column.
10. Ensure the data type is correct in the Type column.
11. Click Save at the top of the page to save the message.
Known Issues
 The Test Connection button cannot be used to validate Service Manager 7.1 web service
connections if the HP ServiceCenter 6.2 web service has been disabled.
 Certain permissions are required when dealing with Change tickets. These permissions are
specified by assigning a user a Change Management Profile. While a user can have more than
one profile, it can only belong to one profile per session. If the user is assigned more than one
Change Management Profile it will automatically use the first profile in alphabetical order. To
avoid confusion it is recommended that the user configured for use with the integration pack is
only assigned one Change Management Profile.
 The user configured for use with the integration pack must have its time zone preferences set to
Greenwich/Universal with a date format of mm/dd/yy.
 In certain versions of HP Service Manager the list of available categories when creating an
incident displays Change yet choosing it causes the object to fail with the following message.
Please provide a valid category. This is a known issue with the HP Service Manager server.
Ensure that the fields are visible to the web service (See Troubleshooting) and that the HP
Service Manager server is patched to the latest version.
 The Set as default button available in the Create Entry, Update Entry and Close Entry activities
may report an error when clicked. Use the following procedure to work around this issue.
1. Note the file path in the error message. For example,

C:\Users\[CurrentUser]\AppData\Local\Microsoft\System Center
2012\Orchestrator\IntegrationPacks\HPServiceManager\[GUID]\defaultFields.xml
2. Ensure that each of the folders in the file path exists exactly as shown in the error
message.
3. Create any missing folders if necessary.
if the Runbook Designer is launched by a user without administrative privileges on the

computer. In the current version of the integration pack, ensure that the user has sufficient
permissions to write to the %COMMONPROGRAMFILES(x86)%\Microsoft System Center
2012\Orchestrator\Extensions\Support\HPServiceManager\ directory.
IBM Tivoli Netcool/OMNIbus Integration

Pack for System Center 2012 - Orchestrator
The Integration Pack for IBM Tivoli Netcool/OMNIbus is an add-on for System Center 2012 -
Orchestrator that enables you to automate responses to alerts raised within IBM Tivoli
Netcool/OMNIbus. You can combine these automated responses, or activities, with the standard
activities found in Orchestrator.
performance, power, and convenience you want. For more information, see Privacy Statement
for System Center 2012 - Orchestrator Release Candidate
(http://go.microsoft.com/fwlink/?LinkID=216995).
Known Issues
The following section contains additional information about this integration pack for IBM Tivoli
Netcool/OMNIbus.
 If the target Netcool server is not SSL-enabled, Orchestrator can stop responding when you
attempt to test the connection using SSL.
Once you make a connection attempt, either by clicking Test Connection or by opening the
properties of a Netcool/Omnibus activity, the initial configuration settings are used and all
subsequent changes have no effect. The JDBC drivers used to communicate with the
Netcool/Omnibus ObjectServer do not recognize changes to SSL system properties once
initialized.
Workaround: In order to modify the Trust store path and Trust store password fields, restart
the Runbook Designer.
 When importing runbooks generated in Opalis, you need to open each Netcool activity in the
Runbook Designer, and re-select the desired Connection. Enter the data again, and then click OK
to update the published data for the activity. Note that the DateTime type properties return
data with a long datestamp format.
Representational State Transfer (REST)

Integration Pack Guide for Orchestrator in
The integration pack for Representational State Transfer (REST) is an add-on for Orchestrator in
System Center 2012 Service Pack 1 (SP1) that enables you to create activities within runbooks
that make requests to REST web services to get data or perform functions.
Microsoft is committed to protecting your privacy. For more information, see the Privacy
System Requirements
The integration pack for REST requires that the following software is installed and configured
before implementing the integration. For more information about installing and configuring
Orchestrator, refer to the respective product documentation.
 Orchestrator in System Center 2012 SP1
Caution
Depending on the communication protocol used, data that is passed to 3rd party systems could be
intercepted from the wire and tampered with; for example, when the protocol between the Policy
Module and the 3rd party product is HTTP. The user is responsible for choosing a secure protocol, such
as HTTPS, for all data transmissions between Orchestrator and any other product.
To download this integration pack, see System Center Integration Packs.
management server and then deploy it to runbook servers and installed Runbook Designers. For
the procedures on installing integration packs, see How To Install an Integration Pack.
System Center Integration Pack for

Microsoft SharePoint
Integration packs are add-ons for Orchestrator, a component of Microsoft System Center 2012,
that helps you optimize IT operations across heterogeneous environments. They enable you to
design runbooks in Orchestrator that use activities performed by other System Center
components, other Microsoft products, and by non-Microsoft products.
The System Center Integration Pack for Microsoft SharePoint enables the automation of
common tasks in SharePoint, for example, to create list items, to upload and download
documents, and to monitor a list for changes.
performance, power, and convenience that you want. For more information, see the System
Center Orchestrator 2012 Privacy Statement.
System Requirements
The integration pack for SharePoint requires the following software to be installed and
configured before you implement the integration. For more information about installing and
configuring System Center 2012 and the Integration Pack for SharePoint, refer to the respective
 System Center 2012 R2 Orchestrator
 Microsoft .NET Framework 4
 Microsoft SharePoint 2013
To download this integration pack, see the Microsoft Download Center.
procedures about how to install integration packs, see How to install an Integration Pack.
Configuring the SharePoint Integration Pack Connections
A connection establishes a reusable link between Orchestrator and a SharePoint site. You can
create as many connections as you require to specify links to multiple sites. You can also create
multiple connections to the same server to allow for differences in security permissions for
To set up an SharePoint connection
1. In the Orchestrator Runbook Designer, click Options, and then click SharePoint. The
SharePoint dialog box appears.
Entry dialog box appears.
3. In the Name box, enter a name for the connection. This name can be the name of the
SharePoint site or a descriptive name to distinguish the type of connection.
4. In the Type box, select SharePoint Configuration.
5. In the SharePoint Site box, enter the URL of the SharePoint site that you want to
integrate with.
6. In the User Name and Password boxes, enter the credentials that Orchestrator will use to
connect to the SharePoint site.
7. In the Domain box, enter the name of the domain to authorize access.
8. In the Default Monitor Interval box, enter a time-out value, in seconds, or keep the
default value.
9. In the Default Maximum Items box, enter a maximum value, or keep the default value.
10. Click OK.
11. Add additional connections, if applicable, and then click Finish.
VMware vSphere Integration Pack for

The integration pack for VMware vSphere is an add-on for System Center 2012 - Orchestrator
that assists you in automating actions in VMware vSphere, enabling full management of your
virtualized computing infrastructure.
Statement for System Center 2012 - Orchestrator
Known Issues
You might see the following issues when using this VMware vSphere integration pack.
 The Set VM Networks activity supports VMs with a maximum of four network adapters. If you
use this activity on a VM with more than four adapters, you will see an “Index was out of range”
error.
 The Reconfigure VM activity provides an options list for the number of CPUs ranging from 1 to 4,
even if the vSphere server supports VMs with more than 4 CPUs. To work around this limitation,
you can enter the valid number in the field manually.
 In the Add Network Adapter activity, you can manually enter any Network label for the adapter.
This network will be applied to the adapter in vSphere even if it is unavailable or does not exist.
 The Create VM activity does not provide an option to browse for valid networks for each of the
NIC properties.
 In the Reconfigure VM activity, the return values of After Power On Script, After Resume Script,
Before Guest Standby Script, and Before Guest Standby Script do not match the input values
supplied.
 The Add VM Disk activity does not provide the option to browse for available data stores.
 The Set VM CD/DVD to ISO Image activity can be supplied with a Relative File Path to a non-
existent file. The activity completes successfully rather than producing an error message.
 The Clone Windows VM and Clone Linux VM activities do not filter unavailable resource pools
from the Resource Pool Path browser.
 The Clone Windows VM and Clone Linux VM activities do not filter source VMs based on their
guest operating system.
 If you inadvertently import the Opalis global configurations, you might see the following errors:
o When adding or editing configurations:
Failed to load the assembly containing the service class
o When editing the properties of any vSphere activity:
Failed to load the assembly containing the service class
Runtime Error! …
This application has requested the Runtime to terminate it in an
unusual way. Please contact the application’s support tem for
more information.
 If you attempt to start a VM that is already powered on by using the Start VM activity, supplying
a Timeout value of greater than 2,147,483 will cause the integration pack to report success even
though the vSphere server indicates that the VM cannot be started.
 Exporting workflows that contain vSphere activities from Opalis Integration Server 6.3 and
importing them into Orchestrator corrupts vSphere configurations stored in Orchestrator. To
address this issue, omit the global configurations from the import process, and then manually
create the matching configurations in Orchestrator.
Workaround: Use the following steps when exporting and importing Opalis workflows.
Warning
It is highly recommended that you perform a full backup of the Orchestrator database before
importing runbooks. Importing global configurations from another system can overwrite local
changes or leave the Orchestrator database in an unstable state. If the Runbook Designer or
runbook server exhibit problems after performing a runbook import, restore the Orchestrator
database from the backup.
 Stage 1: Export the Opalis workflows and import them into Orchestrator.
1. Export the workflows from Opalis Integration Server Client using the conventional
method. No changes to this process are required.
2. In the Orchestrator Runbook Designer, import the runbooks to the appropriate location
using the Import option from the folder context menu or the Actions item from the
main menu.
3. In the Import dialog, select the file the location of the .ois_export file.
4. Configure the options under Import the following global settings as necessary for your
runbooks.
5. Ensure that the Import global configurations checkbox is not checked. This will prevent
Opalis global configurations from being imported into Orchestrator.
6. Click Finish.
Stage 2: After the workflows are imported, create new vSphere configurations:
7. Record the details of the vSphere configuration settings used by the exported workflows
from the source Opalis 6.3 system. These can be found in the Options -> VMWare vSphere item
in the main menu of the Opalis Integration server client.
Note the Name, Server, User, Password, and SSL property values for each vSphere
configuration. The Name of the configuration is case-sensitive.
8. In the Orchestrator Runbook Designer, create a new vSphere configuration for each
configuration used by the imported runbooks.
1. Click Options, and then click VMWare vSphere to open the Prerequisite
Configuration window.
2. Click Add to add a new configuration.
3. Enter the name for the configuration as it appeared in the Opalis 6.3 system.
Note the Name field is case-sensitive.
4. Select the configuration Type of vSphere Setting.
5. Enter the Server, User, Password, and SSL property values as recorded from the
Opalis 6.3 system.
The Port and Webservice Timeout settings can be left blank at this stage.
6. Click OK to save your changes and create a new configuration.
9. Repeat step 2 for all the configurations used by the imported runbooks.
10. When you have created all the configurations used by the imported runbooks, click
Finish on the Prerequisite Configurations window.
11. Test that the imported runbooks run successfully.
 The activity Get Resource Pool Runtime Info fails with an empty Resource Pool (without any
VMs under it). The error summary is “StartIndex cannot be less than zero. Parameter name:
startIndex.”
 When clicking on a vSphere activity in the Runbook Tester, the following error may appear:
“Error
Details: password
Exception: IntegrationPackException
Target site: ServiceBase.Design”
This message can be safely ignored; however, the options list of various properties will not be
automatically populated in the Runbook Tester. If required, the value of these properties may
be edited manually.
Windows Azure Integration Pack for

Published: October 19, 2012

The Integration Pack for Windows Azure is an add-on for Orchestrator in System Center 2012
Service Pack 1 (SP1) that enables you to automate Windows Azure operations related to
certificates, deployments, cloud services, storage, and virtual machines using the '2012-03-01'
version of the Windows Azure Service Management REST API.
related privacy, see the System Center Orchestrator 2012 Privacy Statement
System Requirements
Before you install the Integration Pack for Windows Azure, the folliwing listed software must be
installed and configured. For more information about installing and configuring Orchestrator and
Windows Azure, refer to the respective product documentation.
 Orchestrator in System Center 2012 Service Pack 1 (SP1)
 Windows Azure
To download the Windows Azure integration pack, see the Microsoft Download Center site.
Configure the Windows Azure Connections
A connection establishes a reusable link between Orchestrator and Windows Azure. You can
specify as many connections as you require to create links to multiple Windows Azure
subscriptions.
To set up a Windows Azure connection
1. In the Runbook Designer, click Options, and then click Windows Azure. The Windows
Azure dialog box appears.
3. In the Name box, enter a name for the connection. This could be the name of the
Windows Azure subscription, or a descriptive name to differentiate the type of
connection.
4. In the Type box, click the … button and select a connection type.
5. In the Subscription ID box, enter the subscription ID of the Windows Azure subscription
to connect to.
6. In the PFX File Path box, click the … button and select the management certificate file
associated with this Windows Azure subscription.Note: Your certificate file enables
authentication of requests to your Windows Azure subscription, and so should be stored
in a non-public folder to prevent unauthorized access.
7. In the PFX File Password box, enter the password of the management certificate file
associated with this Windows Azure subscription.
Windows Azure Integration Pack for

Published: October 19, 2012
The Integration Pack for Windows Azure is an add-on for Orchestrator in System Center 2012
Service Pack 1 (SP1) that enables you to automate Windows Azure operations related to
certificates, deployments, cloud services, storage, and virtual machines using the '2012-03-01'
version of the Windows Azure Service Management REST API.
related privacy, see the System Center Orchestrator 2012 Privacy Statement
System Requirements
Before you install the Integration Pack for Windows Azure, the folliwing listed software must be
installed and configured. For more information about installing and configuring Orchestrator and
Windows Azure, refer to the respective product documentation.
 Orchestrator in System Center 2012 Service Pack 1 (SP1)

 Windows Azure
To download the Windows Azure integration pack, see the Microsoft Download Center site.
Configure the Windows Azure Connections
A connection establishes a reusable link between Orchestrator and Windows Azure. You can
specify as many connections as you require to create links to multiple Windows Azure
subscriptions.
To set up a Windows Azure connection
1. In the Runbook Designer, click Options, and then click Windows Azure. The Windows
Azure dialog box appears.
3. In the Name box, enter a name for the connection. This could be the name of the
Windows Azure subscription, or a descriptive name to differentiate the type of
connection.
4. In the Type box, click the … button and select a connection type.
5. In the Subscription ID box, enter the subscription ID of the Windows Azure subscription
to connect to.
6. In the PFX File Path box, click the … button and select the management certificate file
associated with this Windows Azure subscription.Note: Your certificate file enables
authentication of requests to your Windows Azure subscription, and so should be stored
in a non-public folder to prevent unauthorized access.
7. In the PFX File Password box, enter the password of the management certificate file
associated with this Windows Azure subscription.
Integration Packs for System Center


Important
In System Center 2012 SP1, you can run:
 A System Center 2012 integration pack on a System Center 2012 component.
 A System Center 2012 SP1 integration pack on a System Center 2012 SP1 component.
No other configurations are supported.
For more information about the integration packs for the System Center 2012 components, see
the System Center 2012 Integration Guide.
System Center
Integration packs are available for the following previous versions of System Center products:
System Center Integration Pack for System Center Configuration Manager 2007
System Center Integration Pack for System Center Data Protection Manager 2010
System Center Integration Pack for System Center Operations Manager 2007 R2
System Center Integration Pack for System Center Service Manager 2010
System Center Integration Pack for System Center Virtual Machine Manager 2008 R2
System Center 2012 and System Center 2012 Service Pack 1 (SP1)
Integration packs are available for the following System Center 2012 and System Center 2012
SP1 components:
System Center Integration Pack for System Center 2012 Configuration Manager
System Center Integration Pack for System Center 2012 Data Protection Manager
System Center Integration Pack for System Center 2012 Operations Manager
System Center Integration Pack for System Center 2012 Service Manager
System Center Integration Pack for System Center 2012 Virtual Machine Manager
What's New in System Center 2012 R2
Operations Manager
Fabric Monitoring
A close integration between System Center 2012 R2 Virtual Machine Manager and System
Center 2012 R2 Operations Manager introduces System Center cloud monitoring of virtual
layers for private cloud environments. To get this new functionality, use the System Center 2012
Management Pack for System Center 2012 R2 Virtual Machine Manager Dashboard, which is
imported automatically when you integrate Operations Manager and Virtual Machine Manager.
For information about how to integrate Operations Manager and Virtual Machine Manager, see
Configuring Operations Manager Integration with VMM.
Fabric Health Dashboard – Monitoring the Health of Private Clouds
The Fabric Health Dashboard shows a detailed overview of the health of your private clouds and
the fabric that services those clouds. The dashboard helps you answer questions like “What is the
health of my clouds and the fabric serving those clouds?”
To view the Fabric Health Dashboard, click Monitoring, and in Cloud Health Dashboard,
click Cloud Health. Select the cloud you want to investigate, and then, in the Tasks pane, click
Fabric Health Dashboard.
For each cloud, the Fabric Health Dashboard displays these aspects of the fabric:
 Host State: monitors the health state of the hosting groups or the computing aspects of the
cloud, such as CPU, memory, disks, and network adapters
 Storage Pools State File Share and LUN State: monitors the health state of the storage aspect of
fabric for issues, such as disk space capacity and allocation
 Network Node State: utilizes network monitoring in Operations Manager and displays the
health state of network nodes (devices) that are relevant for the cloud you selected. Only
physical network devices within one hop from the hosts are shown. To see the physical network
devices, you must enable the Network Monitoring feature of Operations Manager and monitor
the physical network devices connected to the hosts. Virtual networks are not shown in the
dashboard.
The Active Alerts and Number of VMs fields on this dashboard help indicate which issues are
having the greatest impact on your cloud and can help you prioritize your work.
Fabric Monitoring Diagram View – Displays Health States of Cloud and On-Premise
Environments
The Diagram view gives you a diagram of the entire infrastructure and shows the health state of
each part of the fabric. The Diagram view helps you answer questions, such as “What is the
health of my entire fabric?” Improvements to the diagram ensure that health rolls up and that the
relevant fabric components are part of the Diagram View.
To Open Diagram View, click Monitoring, and in Microsoft System Center Virtual Machine
Manager Views, click Diagram View for the environment you want to see displayed as a
diagram.
Microsoft Monitoring Agent
Microsoft Monitoring Agent is a new agent that replaces the Operations Manager Agent and
combines .NET Application Performance Monitoring (APM) in System Center with the full
functionality of Visual Studio IntelliTrace Collector for gathering full application profiling
traces. Microsoft Monitoring Agent can collect traces on demand or can be left running, which
monitors applications and collects traces continuously.
Microsoft Monitoring Agent can be used together with Operations Manager or can be used as a
standalone tool for monitoring web applications written with Microsoft .NET Framework. In
both cases, the operator can direct the agent to save application traces in an IntelliTrace log
format that can be opened in Visual Studio Ultimate. The log contains detailed information about
application failures and performance issues.
You can use Windows PowerShell commands to start and stop monitoring and collect
IntelliTrace logs from web applications that are running on Internet Information Services (IIS).
To open IntelliTrace logs generated from APM exceptions and APM performance events, you
can use Visual Studio. For more information, see Monitoring with Microsoft Monitoring Agent.
Integrating Operations Manager with Development Processes (DevOps)
Here are two important changes to the DevOps functionality in System Center 2012 R2
Operations Manager:
New Alert Fields of TFS Work Item ID and TFS Work Item Owner
In System Center 2012 R2 Operations Manager, you can synchronize Operations Manager alerts
and Team Foundation Server (TFS) work items. When synchronization is enabled, IT operations
can then assign alerts to the engineering team. Assigning an alert to engineering creates a new
work item in TFS. The workflow will track and synchronize any changes that are made to TFS
work items and any associated Operations Manager alerts.
Integration between System Center 2012 Service Pack 1 (SP1) and TFS used the Ticket ID and
Owner fields of the Operations Manager alert to store and display which work item is associated
with an alert and who it is assigned to. Beginning in System Center 2012 R2 Operations
Manager, two new alert fields, TFS Work Item ID and TFS Work Item Owner, hold these values.
These fields are read-only in the Operations Manager console to prevent accidental changes of
the values that are controlled in TFS.
If you previously personalized any standard alert views or created your own alert views in
System Center 2012 SP1 using Ticket ID and Owner fields to display TFS information, you must
replace those fields with the TFS Work Item ID and TFS Work Item Owner fields to continue
displaying the same information. The previous Ticket ID and Owner fields are still used for
synchronization of alerts with incidents in Service Manager Alert Connector.
Note
You can now use Operations Manager integration with TFS in the same environment with the Service
Manager Alert Connector.
Conversion of Application Performance Monitoring (APM) Performance Events to

IntelliTrace format
This monitoring capability now allows the opening of APM performance events from Visual
Studio IDE as if the performance event was captured during the IntelliTrace historical debugging
session. Tightly integrated with TFS Work Item Synchronization Management Pack, this
capability instantaneously brings generated IntelliTrace logs to TFS work items assigned to
engineering. This can result in streamlining communications between IT Operations and
Development and enriching the development experience with analysis of root causes of the
application failure, reducing the mean time to recovery (MTTR) for the problems detected by
APM.
Support for IPv6
In System Center 2012 R2 Operations Manager the Operations console can take IPv6 addresses
as input for Network Discovery and display IPv6 addresses in the network-related views.
Java Application Performance Monitoring
The System Center 2012 Management Pack for Java Application Performance Monitoring lets
you monitor Java application performance and exception events by using Operations Manager
Application Advisor. You can set method and resource timing for performance events, stack
traces for exception events, and set Java specific counters (such as Average Request Time and
Requests Per Second) for events. Additionally, you get Operations Manager level alerting on
Java application server counters. You can download the management pack from the Microsoft
Download Center.
System Center Advisor
System Center Advisor is an online service that analyzes installations of Microsoft server
software. With the latest preview version of Advisor, you can now view Advisor alerts in the
Operations Manager Operations console.
Advisor collects data from your installations, analyzes it, and generates alerts that identify
potential issues (such as missing security patches) or deviations from identified best practices
with regard to configuration and usage. Advisor also provides both current and historical views
of the configuration of servers in your environment. Ultimately, Advisor recommendations help
you proactively avoid configuration problems, reduce downtime, improve performance, and
resolve issues faster. For more information about Advisor, see Viewing System Center Advisor
Alerts and Advisor online help
UNIX and Linux Monitoring
UNIX and Linux agents for Operations Manager are now based on the Open Management
Infrastructure (OMI) open-source CIM Object Manager.
Debian GNU/Linux 7 is now supported by the Universal Linux agents and Management Packs.
Release Notes for Operations Manager in

System Center 2012 R2
Advisor Monitoring Server group reserved for Advisor Connector use only
Description: The Microsoft System Center Advisor Monitoring Server group is reserved for the
control of agents that are included into the Advisor Connector. This group should not be
modified or added to the Advisor Managed list.
Workaround: This is by design.
.NET Framework required for enabling Advisor Connector on agents
Description: To enable the Advisor Connector on Operations Manager agent computers,

Microsoft .NET Framework must first be installed.
Workaround: For agents running Windows Server 2008 R2 and earlier, install .Net Framework
3.5 SP1. For agents running Windows Server 2012 and newer, install .Net Framework 4.0 or
higher.
ASP.NET Web API data producers not installed if Microsoft .NET Framework
4.x not installed first
Description: If you install an Operations Manager for System Center 2012 R2 agent on a
computer that does not have Microsoft .NET Framework 4.x previously installed, some data
producers for the ASP.NET Web API will not be installed. If you later install the Microsoft
.NET Framework 4.x on the computer and try to monitor an application that uses the ASP.NET
Web API with the application monitoring feature, the applicable data producers will still be
missing, and monitoring for that application will not work.
Workaround: This is by design. To restore the missing data producers, the agent should be re-
installed after Microsoft .NET Framework 4.x has been installed on the computer.
You must import management packs in order to use Application Performance

Monitoring with Windows Server 2012 R2
Description: You must import the Windows Server 2012 R2 and IIS 8 management packs in
order to use Application Performance Monitoring (APM) with Windows Server 2012 R2.
Workaround: System Center 2012 R2 Operations Manager includes APM support for Windows
Server 2012 R2 and IIS8 (Internet Information Services 8). However, In order for this feature to
work you must import the following set of monitoring packs:
 Microsoft.Windows.Server.2012.R2.Discovery.mp
 Microsoft.Windows.Server.Library version 6.0.6989.0 or newer
 Microsoft.Windows.Server.2012.Discovery version 6.0.6989.0 or newer
 Microsoft.Windows.InternetInformationServices.CommonLibrary version 7.0.8862.0 or newer
 Microsoft.Windows.InternetInformationServices.2012 version 7.0.8862.0 or newer
This is a new version of the IIS8 management pack. Do NOT use the
Microsoft.Windows.InternetInformationServices.6.2 management pack, which was part of the
"Windows 8 beta management pack release". Remove the
Microsoft.Windows.InternetInformationServices.6.2 management pack if you had previously
imported it.
 Microsoft.SystemCenter.Apm.Web.IIS8
This is in the /ManagementPacks folder of the System Center 2012 – Operations Manager
media, and is the equivalent of the Microsoft.SystemCenter.Apm.Web.IIS7 management pack
which was previously (and still is) used for IIS7.
WCFServerAsyncBeginProducer cannot be found on agent after upgrade
Description: During upgrade from System Center 2012 to System Center 2012 R2, a new
System Center 2012 R2 agent which is configured for APM monitoring will still receive OLD
configuration settings from a management group which has not yet been upgraded, and might log
an 'information' event (ID 1295) in the event log with the following message:
Cannot find producer

"Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation.InstrumentationCla
ss.WCFServerAsyncBeginProducer of assembly
Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation,
Version=7.0.5000.0, Culture=Neutral, PublicKeyToken=9396306c2be7fcc4,
processorArchitecture=MSIL" in assembly
Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation,
Version=7.0.5000.0, Culture=Neutral, PublicKeyToken=9396306c2be7fcc4,
processorArchitecture=MSIL, producer is inaccessible due to access level or producer has an
incorrect signature. Please see documentation for details.
Workaround: None. This event is by design. Everything else in APM works normally, and this
event message can be safely ignored.
After upgrade the web console does not work due to IIS becoming corrupt
Description: While upgrading to System Center 2012 R2, Operations Manager, if the upgrade
breaks the web console, you can encounter a Runtime Error: Server Error in
‘/OperationsManager’ Application. In the application log on the web console server, you will
see an event with an exception message: Could not load type
'System.ServiceModel.Activation.HttpModule'.
For example, as part of the upgrade process you are prompted to add “HTTP Activation” to the
role services of the Operating System. This leaves IIS in a semi-broken state, and requires a re-
registration of ASP.NET in IIS to correct. This can occur anytime you add any IIS components
after ASP.NET.
Workaround: Re-register ASP.NET in IIS.
 On Windows Server 2008 R2 SP1, run the following in an elevated CMD:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -i -
enable
 On Windows Server 2012, run the following in an elevated CMD:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -r
Using sudo elevation with Solaris operating systems requires a configuration
change if sudo executable is not in an expected path
Description: If you want to use sudo elevation on a computer running Solaris, and the sudo
executable is not in an expected path, you need to create a link to the correct path. Operations
Manager will look for the sudo executable in the path /opt/sfw/bin, and then in the path /usr/bin.
If sudo is not installed in one of these paths, a link is required.
Workaround: The UNIX and Linux agent installation script creates the symbolic link
/etc/opt/microsoft/scx/conf/sudodir to the folder expected to contain sudo. The agent
uses this symbolic link to access sudo. The installation script automatically creates the symbolic
link, so no action is needed for standard UNIX and Linux configurations. However, if sudo is
installed in a non-standard location, you should change the symbolic link to point to the folder
where sudo is installed. If you change the symbolic link, its value is maintained for uninstall, re-
install, and upgrade operations with the agent.

SCCM 2012 Part 2 Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SCCM 2012 Part 2 Notes

Uploaded by

Copyright:

Available Formats

System Center Technical Documentation

System Center 2012

Configuration Manager provides a

Data Protection Manager (DPM) is a backup

System Center Packs

 Operations Manager Management Pack Guides

 System Center Orchestrator 2012 Integration Packs

 System Center Cloud Services Process Pack

Previous System Center Products

 System Center Configuration Manager 2007

 System Center Data Protection Manager 2010

 System Center Essentials 2010

 Opalis Integration Server 6.3

 System Center Operations Manager 2007 R2

 System Center Service Manager 2010 SP1

 IT Training and Certification Resources

 System Center Troubleshooting and Support

 System Center Community

 System Center TechCenter Home

 Integration Packs for System Center 2012

Updated: November 1, 2013

Downloading the Integration Pack

Registering and Deploying the Integration Pack

To set up an Active Directory connection

Examples of Configuration Default Parent Container include the following:

8. Click OK to close the configuration dialog box.

Exchange Admin Integration Pack for

Updated: November 1, 2013

 System Center 2012 - Orchestrator or Orchestrator in System Center 2012 SP1

 Microsoft .NET Framework 3.5 Service Pack 1

 Microsoft Exchange Management Shell

 Microsoft PowerShell 2.0

 Microsoft WinRM 2.0

Downloading the Integration Pack

Register and Deploy the Integration Pack

To set up an Exchange Configuration connection

3. If Execution Policy is Restricted, you must change it to RemoteSigned. Run the

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

To configure remote PowerShell rights for the Exchange user

Set-User <UserName> -RemotePowerShellEnabled $true

To configure Windows PowerShell to allow Basic Authentication on the Exchange server

To configure WinRM for HTTP unencrypted communication

2. Navigate to Local Computer Policy > Computer Configuration > Administrative

3. Make sure that Allow unencrypted traffic is Enabled.

2. Navigate to the PowerShell site.

3. Open SSL Settings.

Exchange Users Integration Pack for

Updated: November 1, 2013

 System Center 2012 - Orchestrator

 Microsoft .NET Framework 3.5

Downloading the Integration Pack

Registering and Deploying the Integration Pack

Configuring the Exchange Users Integration Pack Connections

To set up an Exchange Configuration connection

To set up a Exchange Item Type connection

FTP Integration Pack for Orchestrator in

 Orchestrator in System Center 2012 SP1

Download the Integration Pack

Register and Deploy the Integration Pack

Configuring the FTP Connections

Orchestrator does not support SFTP on computers that run Windows.

Updated: November 1, 2013

Downloading the Integration Pack

Registering and Deploying the Integration Pack