SCCM 2012 Part 2 Notes.docx

(1)

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

App Controller

App Controller provides a unified console that helps you manage public clouds and private clouds, as well as cloud-based virtual machines and services.

Configuration Manager

Configuration Manager provides a comprehensive solution for change and configuration management for the Microsoft platform. It allows you to deploy operating systems, software applications, and software updates; and to monitor and remediate 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. DPM provides out-of-the-box protection for Files and Folders, Exchange Server, SQL Server, Virtual Machine Manager, SharePoint, Hyper-V, and client computers. For large-scale deployments, DPM also allows you to monitor your backups through a central console or remotely.

Endpoint Protection

Endpoint Protection provides an antimalware and security solution for the Microsoft platform.

Operations Manager

Operations Manager provides infrastructure monitoring that is flexible and cost-effective, helps ensure the predictable performance and availability of vital applications, and offers comprehensive monitoring for your datacenter and cloud, both private and public.

Orchestrator

Orchestrator provides orchestration, integration, and automation of IT processes through the creation of runbooks, enabling you to define and standardize best practices and improve

operational efficiency.

In addition, Orchestrator provides Service Provider Foundation, for hosters with

(2)

are available in System Center 2012 Service Pack 1 (SP1).

Service Manager

Service Manager provides an integrated platform for automating and adapting your organization’s IT service management best practices, such as those found in Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). It provides built-in processes for incident and problem resolution, change control, and asset lifecycle management.

Virtual Machine Manager

Virtual Machine Manager (VMM) is a management solution for the virtualized datacenter, enabling you to configure and manage your virtualization host, networking, and storage resources in order to create and deploy virtual machines and services to private clouds that you have created.

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

(3)

 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

(4)

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.

(5)

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

2 out of 2 rated this helpful - Rate this topic

Updated: November 1, 2013

(6)

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

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 Designers. For the procedures on installing integration packs, see How to install an Integration Pack.

(7)

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.

15. Add additional connections if applicable. 16. Click Finish.

(8)

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.

(9)

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

Orchestrator in System Center 2012 SP1

Applies To: System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator

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,

(10)

see the System Center Orchestrator 2012 Privacy Statement http://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. 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 Designers. For the 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.

(11)

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 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. 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

System Center 2012 SP1

(12)

Applies To: System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator

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.

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 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. Register and Deploy 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 Designers. For the 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 different user accounts.

(13)

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.

9. In the Username and Password boxes, type the credentials that Orchestrator will use to 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 server. If you are using the computer name, you can type the NetBIOS name or the fully 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.

(14)

HP iLO and OA Integration Pack for System

Center 2012 - Orchestrator

This topic has not yet been rated - Rate this topic Updated: November 1, 2013

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.

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 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

 System Center 2012 Service Pack 1 (SP1) integration packs require Orchestrator in System 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.

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 Designers. For the procedures on installing integration packs, see How To Install an Integration Pack.

(15)

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.

7. In the Username and Password boxes, type the credentials that Orchestrator will use to 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. 11. Click OK to close the configuration dialog box.

(16)

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

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 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. 5. Click OK to close the configuration dialog box, and then click Finish.

(17)

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. 7. Click OK to close the configuration dialog box, and then click Finish.

HP Operations Manager Integration Pack for

System Center 2012 - Orchestrator

The Integration Pack for HP Operations Manager is an addon 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.

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 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.

(18)

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.

8. Click OK to close the configuration dialog box. 9. Add additional connections if applicable. 10. Click Finish.

HP Operations Manager Integration Pack for

System Center 2012 - Orchestrator

(19)

The Integration Pack for HP Operations Manager is an addon 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.

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 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.

(20)

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.

8. Click OK to close the configuration dialog box. 9. Add additional connections if applicable. 10. Click Finish.

HP Service Manager Integration Pack for

System Center 2012 - Orchestrator

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).

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

(21)

configuring Orchestrator and the HP Service Manager Web Service, refer to the respective product documentation.

 HP Service Manager 7.11 or 9

The following software must be installed on each Runbook Server and Runbook Designer:  Microsoft .NET Framework 3.5 Service Pack 1

 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 2012 - Orchestrator.

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.

(22)

 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 differences in security permissions for different user accounts.

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.

15. Click Test Data Source to confirm connectivity to the database. 16. When the test completes, click OK.

(23)

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.

5. Select the Oracle ODBC driver installed with the Oracle client from the list of available drivers.

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.

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.

2. On the Connections tab, click Add to begin the connection setup. The Connection Configuration dialog box will appear.

3. In the Name box, enter a name for the connection. This could be the name of the HP 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

computer. If you are using the computer name, you can type the NetBIOS name or the fully qualified domain name (FQDN).

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.

9. In the Username and Password boxes, type the credentials that Orchestrator will use to 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

(24)

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. 14. Click OK to close the configuration dialog box, and then click Finish.

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

(25)

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

System Center 2012 - Orchestrator

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

(26)

convenience you want. For more information, see the System Center Orchestrator 2012 Privacy Statement (http://go.microsoft.com/fwlink/?LinkID=216995).

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 product documentation.

 HP Service Manager 7.11 or 9

The following software must be installed on each Runbook Server and Runbook Designer:  Microsoft .NET Framework 3.5 Service Pack 1

 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 2012 - Orchestrator.

(27)

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 differences in security permissions for different user accounts.

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.

4. Select the driver named SQL Server Native Client 10.0 from the list of available drivers.

7. Enter the HP Service Manager database server name or IP address in the Server box. 8. Click Next.

(28)

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.

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.

5. Select the Oracle ODBC driver installed with the Oracle client from the list of available drivers.

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.

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.

2. On the Connections tab, click Add to begin the connection setup. The Connection Configuration dialog box will appear.

3. In the Name box, enter a name for the connection. This could be the name of the HP 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

computer. If you are using the computer name, you can type the NetBIOS name or the fully qualified domain name (FQDN).

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.

(29)

8. Enter the database password in the DB Password box.

9. In the Username and Password boxes, type the credentials that Orchestrator will use to 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. 14. Click OK to close the configuration dialog box, and then click Finish.

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.

(30)

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

(31)

The Integration Pack for IBM Tivoli Netcool/OMNIbus is an addon 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.

Microsoft is committed to protecting your privacy, while delivering software that brings you the 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

System Center 2012 SP1

(32)

Applies To: System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator 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 Statement for System Center 2012 - Orchestrator.

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. 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 installed Runbook Designers. For the procedures on installing integration packs, see How To Install an Integration Pack.