SCCM 2012 Part 2 Notes.docx

8/14/2019 SCCM 2012 Part 2 Notes.docx

1/48

System Center Technical Documentation

Library

Microsoft System Center solutions can help you capture and aggregate knowledge about yourinfrastructure, 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 thathelps you manage public clouds and private

clouds, as well as cloud-based virtual machines

and services.

Configuration Manager

Configuration Manager provides acomprehensive solution for change and

configuration management for the Microsoftplatform. It allows you to deploy operatingsystems, software applications, and software

updates; and to monitor and remediate

computers for compliance settings. With

Configuration Manager, you can also monitorhardware 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 forFiles and Folders, Exchange Server, SQL

Server, Virtual Machine Manager, SharePoint,

Hyper-V, and client computers. For large-scaledeployments, 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 datacenterand cloud, both private and public.

Orchestrator

Orchestrator provides orchestration, integration,

and automation of IT processes through thecreation of runbooks, enabling you to define and

standardize best practices and improve

operational efficiency.

In addition, Orchestrator providesService

Provider Foundation,for hosters withinfrastructure as a service (IaaS) capabilities that
http://go.microsoft.com/fwlink/?LinkId=231694http://go.microsoft.com/fwlink/?LinkId=231694http://go.microsoft.com/fwlink/p/?LinkId=231675http://go.microsoft.com/fwlink/p/?LinkId=231675http://go.microsoft.com/fwlink/p/?LinkId=239439http://go.microsoft.com/fwlink/p/?LinkId=239439http://go.microsoft.com/fwlink/p/?LinkID=231673http://go.microsoft.com/fwlink/p/?LinkID=231673http://go.microsoft.com/fwlink/p/?LinkId=231676http://go.microsoft.com/fwlink/p/?LinkId=231676http://go.microsoft.com/fwlink/p/?LinkId=231677http://go.microsoft.com/fwlink/p/?LinkId=231677http://technet.microsoft.com/en-us/library/jj642895.aspxhttp://technet.microsoft.com/en-us/library/jj642895.aspxhttp://technet.microsoft.com/en-us/library/jj642895.aspxhttp://technet.microsoft.com/en-us/library/jj642895.aspxhttp://technet.microsoft.com/en-us/library/jj642895.aspxhttp://technet.microsoft.com/en-us/library/jj642895.aspxhttp://go.microsoft.com/fwlink/p/?LinkId=231677http://go.microsoft.com/fwlink/p/?LinkId=231676http://go.microsoft.com/fwlink/p/?LinkID=231673http://go.microsoft.com/fwlink/p/?LinkId=239439http://go.microsoft.com/fwlink/p/?LinkId=231675http://go.microsoft.com/fwlink/?LinkId=231694


2/48

are available in System Center 2012 ServicePack 1 (SP1).

Service Manager

Service Manager provides an integrated

platform for automating and adapting yourorganizations IT service management best

practices, such as those found in MicrosoftOperations Framework (MOF) and Information

Technology Infrastructure Library (ITIL). It

provides built-in processes for incident and

problem resolution, change control, and assetlifecycle management.

Virtual Machine Manager

Virtual Machine Manager (VMM) is amanagement solution for the virtualized

datacenter, enabling you to configure andmanage 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 ofdistributed 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
http://go.microsoft.com/fwlink/p/?LinkId=231678http://go.microsoft.com/fwlink/p/?LinkId=231678http://go.microsoft.com/fwlink/p/?LinkId=231679http://go.microsoft.com/fwlink/p/?LinkId=231679http://go.microsoft.com/fwlink/p/?LinkId=239440http://go.microsoft.com/fwlink/p/?LinkId=239440http://go.microsoft.com/fwlink/p/?LinkId=231680http://go.microsoft.com/fwlink/p/?LinkId=231680http://technet.microsoft.com/en-us/library/hh295851.aspxhttp://technet.microsoft.com/en-us/library/hh295851.aspxhttp://technet.microsoft.com/en-us/library/hh562067.aspxhttp://technet.microsoft.com/en-us/library/hh562067.aspxhttp://technet.microsoft.com/en-us/library/bb735860.aspxhttp://technet.microsoft.com/en-us/library/bb735860.aspxhttp://technet.microsoft.com/en-us/library/ff399192.aspxhttp://technet.microsoft.com/en-us/library/ff399192.aspxhttp://technet.microsoft.com/en-us/library/ff603627.aspxhttp://technet.microsoft.com/en-us/library/ff603627.aspxhttp://technet.microsoft.com/en-us/library/ff630946.aspxhttp://technet.microsoft.com/en-us/library/ff630946.aspxhttp://technet.microsoft.com/en-us/library/bb310604.aspxhttp://technet.microsoft.com/en-us/library/bb310604.aspxhttp://technet.microsoft.com/en-us/library/ff461010.aspxhttp://technet.microsoft.com/en-us/library/ff461010.aspxhttp://technet.microsoft.com/en-us/library/cc917964.aspxhttp://technet.microsoft.com/en-us/library/cc917964.aspxhttp://go.microsoft.com/fwlink/p/?LinkId=118295http://go.microsoft.com/fwlink/p/?LinkId=118295http://go.microsoft.com/fwlink/p/?LinkId=118295http://technet.microsoft.com/en-us/library/cc917964.aspxhttp://technet.microsoft.com/en-us/library/ff461010.aspxhttp://technet.microsoft.com/en-us/library/bb310604.aspxhttp://technet.microsoft.com/en-us/library/ff630946.aspxhttp://technet.microsoft.com/en-us/library/ff603627.aspxhttp://technet.microsoft.com/en-us/library/ff399192.aspxhttp://technet.microsoft.com/en-us/library/bb735860.aspxhttp://technet.microsoft.com/en-us/library/hh562067.aspxhttp://technet.microsoft.com/en-us/library/hh295851.aspxhttp://go.microsoft.com/fwlink/p/?LinkId=231680http://go.microsoft.com/fwlink/p/?LinkId=239440http://go.microsoft.com/fwlink/p/?LinkId=231679http://go.microsoft.com/fwlink/p/?LinkId=231678


3/48

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 Orchestrators functionality and

ability to integrate with other Microsoft and third-party platforms and products byinstalling 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. Eachintegration 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 2012components, see theSystem Center 2012 Integration Guide.

Microsoft provides integration packs for all of the System Center products, as well asother 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
http://technet.microsoft.com/systemcenter/cc137824.aspxhttp://technet.microsoft.com/systemcenter/cc137824.aspxhttp://technet.microsoft.com/systemcenter/cc511006.aspxhttp://technet.microsoft.com/systemcenter/cc511006.aspxhttp://technet.microsoft.com/systemcenter/cc511266.aspxhttp://technet.microsoft.com/systemcenter/cc511266.aspxhttp://technet.microsoft.com/systemcenter/default.aspxhttp://technet.microsoft.com/systemcenter/default.aspxhttp://technet.microsoft.com/en-us/library/hh295851.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh295851.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh295851.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=275796http://go.microsoft.com/fwlink/?LinkID=275796http://go.microsoft.com/fwlink/?LinkID=275796http://technet.microsoft.com/en-us/library/hh553474.aspxhttp://technet.microsoft.com/en-us/library/hh553474.aspxhttp://technet.microsoft.com/en-us/library/jj614529.aspxhttp://technet.microsoft.com/en-us/library/jj614529.aspxhttp://technet.microsoft.com/en-us/library/jj614570.aspxhttp://technet.microsoft.com/en-us/library/jj614570.aspxhttp://technet.microsoft.com/en-us/library/jj670654.aspxhttp://technet.microsoft.com/en-us/library/jj670654.aspxhttp://technet.microsoft.com/en-us/library/hh771475.aspxhttp://technet.microsoft.com/en-us/library/hh771475.aspxhttp://technet.microsoft.com/en-us/library/hh533440.aspxhttp://technet.microsoft.com/en-us/library/hh533440.aspxhttp://technet.microsoft.com/en-us/library/hh771464.aspxhttp://technet.microsoft.com/en-us/library/hh771464.aspxhttp://technet.microsoft.com/en-us/library/hh211591.aspxhttp://technet.microsoft.com/en-us/library/hh211591.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/dn266021.aspxhttp://technet.microsoft.com/en-us/library/dn266021.aspxhttp://technet.microsoft.com/en-us/library/jj721956.aspxhttp://technet.microsoft.com/en-us/library/jj721956.aspxhttp://technet.microsoft.com/en-us/library/hh228186.aspxhttp://technet.microsoft.com/en-us/library/hh228186.aspxhttp://technet.microsoft.com/en-us/library/hh830706.aspxhttp://technet.microsoft.com/en-us/library/hh830706.aspxhttp://technet.microsoft.com/en-us/library/hh830706.aspxhttp://technet.microsoft.com/en-us/library/hh228186.aspxhttp://technet.microsoft.com/en-us/library/jj721956.aspxhttp://technet.microsoft.com/en-us/library/dn266021.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/jj614558.aspxhttp://technet.microsoft.com/en-us/library/hh211591.aspxhttp://technet.microsoft.com/en-us/library/hh771464.aspxhttp://technet.microsoft.com/en-us/library/hh533440.aspxhttp://technet.microsoft.com/en-us/library/hh771475.aspxhttp://technet.microsoft.com/en-us/library/jj670654.aspxhttp://technet.microsoft.com/en-us/library/jj614570.aspxhttp://technet.microsoft.com/en-us/library/jj614529.aspxhttp://technet.microsoft.com/en-us/library/hh553474.aspxhttp://go.microsoft.com/fwlink/?LinkID=275796http://technet.microsoft.com/en-us/library/hh295851.aspx#feedbackhttp://technet.microsoft.com/systemcenter/default.aspxhttp://technet.microsoft.com/systemcenter/cc511266.aspxhttp://technet.microsoft.com/systemcenter/cc511006.aspxhttp://technet.microsoft.com/systemcenter/cc137824.aspx


4/48

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 privacyinformation, see thePrivacy Statement for System Center 2012Orchestrator.

System Requirements

Before you can install the Integration Pack for Active Directory, you must first install andconfigure 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 SystemCenter 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, seeActive 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 Orchestratormanagement server and then deploy it to runbook servers and Runbook Designer. For specific

procedures, seeHow To Install an Integration Pack.
http://technet.microsoft.com/en-us/library/hh553474.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh553474.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh553474.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/p/?LinkID=233699http://go.microsoft.com/fwlink/p/?LinkID=233699http://go.microsoft.com/fwlink/p/?LinkID=233699http://go.microsoft.com/fwlink/p/?LinkID=233699http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/p/?LinkID=233699http://go.microsoft.com/fwlink/p/?LinkID=233699http://go.microsoft.com/fwlink/?LinkID=216995http://technet.microsoft.com/en-us/library/hh553474.aspx#feedback


5/48

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 tomultiple 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 ActiveDirectorydialog box appears.

2. On the Configurationstab, click Addto begin the connection setup. The AddConfigurationdialog box appears.

3. In the Namebox, enter a name for the connection. This could be the name of theActiveDirectory domain, or a descriptive name to distinguish the type of connection.

4. Click the ellipsis button (...) next to the Typebox and select Microsoft Active DirectoryDomain Configuration. Click OK.

5. In the Configuration User Nameand Configuration Passwordboxes, type thecredentials that Orchestrator will use to log on toActive Directory. This user account

must have the authority to perform the actions in any runbook where the connection isused.

6. In the Configuration Domain Controller Name (FQDN)box type the fully qualifiedname of the domain or domain controller for the connection.

7. In the Configuration Default Parent Containerbox, type the default DistinguishedName 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 ContainerDistinguished Name.

Examples of Configuration Default Parent Containerinclude the following:

CN=Users, DC=mydomain, DC=comand OU=MyOU, DC=mydomain, DC=com

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

Exchange Admin Integration Pack for

Orchestrator in System Center 2012 SP12 out of 2 rated this helpful -Rate this topic


Applies To: System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator
http://technet.microsoft.com/en-us/library/jj614529.aspx#feedbackhttp://technet.microsoft.com/en-us/library/jj614529.aspx#feedbackhttp://technet.microsoft.com/en-us/library/jj614529.aspx#feedbackhttp://technet.microsoft.com/en-us/library/jj614529.aspx#feedback


6/48

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 useactivities 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 theSystem Center Orchestrator 2012 Privacy Statement.

System requirements

Before you implement the Integration Pack for Exchange Admin, the following listed softwaremust 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 theDownload Center site.

Register and Deploy the Integration Pack

After you download the integration pack file, you must register it with the Orchestratormanagement server and then deploy it to runbook servers and Runbook Designers. For the

procedures on installing integration packs, seeHow to install an Integration Pack.
http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/p/?LinkId=264934http://go.microsoft.com/fwlink/p/?LinkId=264934http://go.microsoft.com/fwlink/p/?LinkId=264934http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/p/?LinkId=264934http://go.microsoft.com/fwlink/?LinkID=216995


7/48

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 multipleconnections 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 ExchangeAdmin. The Exchange Admindialog box appears.


3. In the Namebox, enter a name for the connection. This can be the name of the Exchangeserver or a descriptive name to differentiate the type of connection.

4. Click the ()button and select Exchange Configuration.5. In the Exchange Server Hostbox, 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 Portbox, enter the port that is used to communicate with theExchange server. If you use SSL, be sure to select the appropriate port.

7. In the Exchange PowerShell Applicationbox, enter the application name segment ofthe connection URI.

8. In the Exchange User Nameand Exchange User Passwordboxes, type the credentialsthat 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-Premiseinstallation or to Office.

10.Set the Use SSLproperty to Trueto have all communication between the runbook serverand the Exchange server encrypted over HTTPS.

11.If you use SSL, the Skip CA Checkproperty specifies whether the client does notvalidate that the server certificate is signed by a trusted certification authority (CA).

12.If you use SSL, the Skip CN Checkproperty 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 Checkproperty specifies whether the revocationstatus of the server certificate will not be checked for validity.

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


8/48

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-bitPowerShell 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 Policyis Restricted, you must change it to RemoteSigned. Run thefollowing 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 RemotePowerShellEnabledfield:

Copy

Get-User

3. To grant the user remote PowerShell rights, run the following command:Copy

Set-User -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/48

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 trustedhosts 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 forOrchestrator in System Center 2012 SP1




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 youto 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/48

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 mustbe installed and configured. For more information about installing and configuring Orchestratorand 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 theDownload Center site.


After you download the integration pack file, you must register it with the Orchestratormanagement server and then deploy it to runbook servers and Runbook Designers. For the

procedures on installing integration packs, seeHow 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 alsocreate 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 Userdialog box appears.

http://technet.microsoft.com/en-us/library/http://technet.microsoft.com/en-us/library/http://technet.microsoft.com/en-us/library/http://technet.microsoft.com/en-us/library/http://go.microsoft.com/fwlink/p/?LinkId=264936http://go.microsoft.com/fwlink/p/?LinkId=264936http://go.microsoft.com/fwlink/p/?LinkId=264936http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/p/?LinkId=264936http://technet.microsoft.com/en-us/library/http://technet.microsoft.com/en-us/library/


11/48

3. In the Namebox, enter a name for the connection. This can be the name of the computerrunning Exchange Server or a descriptive name to distinguish the type of connection.

4. In the Typebox, select Exchange Configuration.5. In the Exchange Server Addressbox, 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 Addressboxempty if you enable the Use Autodiscover option.6. In the Usernameand Passwordboxes, type the credentials that Orchestrator will use to

connect to the Exchange server.

7. In the Domainbox, type the name of the domain that will authorize access.8. In the Timeoutbox, 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 casewith 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 Userdialog box appears.


3. In the Namebox, enter a name for the connection. This can be the name of the Exchangeserver 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 Addressbox, type the name or IP address of the Exchangeserver. 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 Addressbox

empty if you enable the Use Autodiscover option.

6. In the Usernameand Passwordboxes, type the credentials that Orchestrator will use toconnect to the Exchange server.

7. In the Domainbox, type the name of the domain that will authorize access.8. In the Timeoutbox, enter a timeout value or leave the default.9. In the Item Typebox, enter a valid Exchange Item Type.10.Add any additional connections if applicable, and then click Finish.

FTP Integration Pack for Orchestrator in




12/48



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 candesign 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 theSystem 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 priorto implementing the integration. For more information about installing and configuringOrchestrator 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 theDownload 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 theprocedures on installing integration packs, seeHow To Install an Integration Pack.

Configuring the FTP Connections

A connection establishes a reusable link between Orchestrator and an FTP server. You can createas 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.
http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/p/?LinkId=267235http://go.microsoft.com/fwlink/p/?LinkId=267235http://go.microsoft.com/fwlink/p/?LinkId=267235http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/p/?LinkId=267235http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995


13/48

To set up an FTP connection

1. In the Orchestrator Runbook Designer, click Options, and then click FTP. The FTPdialog box appears.

2. On the Configurations tab, click Addto begin the connection setup. The AddConfigurationdialog box appears.

3. In the Namebox, enter a name for the connection. This can be the name of the FTPserver, or a descriptive name to distinguish the type of connection.

4. In the Typebox, click the button and select a configuration type.5. In the Connection Typebox, 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 Serverbox, type the name or IP address of the FTPserver. If you are using thecomputer name, you can type the NetBIOS name or the fully qualified domain name

(FQDN).8. In the Portbox, type the port number for the selected connection type.9. In the Usernameand Passwordboxes, type the credentials that Orchestrator will use to

connect to the FTPserver.

10.In the Timeoutbox, type the amount of time in seconds before an FTP operation willtime out.

11.In the Certificate Path (FTP)box, type the path to a certificate. This configurationproperty applies to FTP only. This configuration property is optional and can be leftempty.

12.In the Certificate Password (FTP)box, type the password for the certificate. Thisconfiguration property applies to FTP only. This configuration property is optional andcan be left empty.

13.In the HTTP Proxy Server (FTP)box, type the name of IP address of the HTTP proxyserver. If you are using the computer name, you can type the NetBIOS name or the fullyqualified 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 optionaland can be left empty.

15.In the HTTP Proxy Username (FTP)and HTTP Proxy Password (FTP), type thecredentials that Orchestrator will used to connect to the HTTP proxy server. This

configuration property applies to FTP only. This configuration property is optional andcan be left empty.

16.Click OKto close the configuration dialog box, and then click Finish.


14/48

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 - Orchestratorthat enables you to automate HP iLO and OA commands.

Microsoft is committed to protecting your privacy, while delivering software that brings you theperformance, power, and convenience you want. For more information, see theSystem 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 andconfigured prior to implementing the integration. For more information about installing andconfiguring 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, seeHP iLO and OA Integration Pack for System Center 2012

- Orchestrator.


After you download the integration pack file, you must register it with the Orchestratormanagement server and then deploy it to Runbook servers and Runbook Designers. For the

procedures on installing integration packs, seeHow To Install an Integration Pack.
http://technet.microsoft.com/en-us/library/hh771475.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771475.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771475.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=234585http://go.microsoft.com/fwlink/?LinkID=234585http://go.microsoft.com/fwlink/?LinkID=234585http://go.microsoft.com/fwlink/?LinkID=234585http://go.microsoft.com/fwlink/?LinkID=239936http://go.microsoft.com/fwlink/?LinkID=239936http://go.microsoft.com/fwlink/?LinkID=239936http://go.microsoft.com/fwlink/?LinkID=239936http://go.microsoft.com/fwlink/?LinkID=234585http://go.microsoft.com/fwlink/?LinkID=234585http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://technet.microsoft.com/en-us/library/hh771475.aspx#feedback


15/48

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 Optionsmenu, and select HP iLO and OA. The HPiLO and OA dialog box appears.

2. On the Connectionstab, click Default credentialsto begin the setup. The Defaultcredentialsdialog box appears.

3. In the User namebox, enter a default user name.4. In the Passwordbox, enter a default password.5. In the Keybox, enter a default key Or click the ellipsis () button to browse and select a

Key.

6. Click OKto 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 iLOand OA dialog box appears.

2. On the Connectionstab, click Addto begin the connection setup. The Connectiondialog box appears.

3. In the Namebox, enter a name for the connection. This could be the name of the HP iLOand OA system or a descriptive name to distinguish the type of connection.

4. In the Addressbox, type the name or IP address of the HP iLO and OA system. If youare using the computer name, you can type the NetBIOS name or the fully qualified

domain name (FQDN).

5. In the Portbox, type the number of the HP iLO and OA system.6. Select Use default credentialsto apply the default credentials to this connection. If you

do this, then you can skip the next two steps.

7. In the Usernameand Passwordboxes, type the credentials that Orchestrator will use toconnect to the HP iLO and OA system.

8. In the Private Keybox, optionally specify the SSH key used to connect to the HP iLOand OA system.

9. In the Attemptsbox, enter the number or times a command will attempt before failing.10.In the Time between attemptsbox, enter the number in seconds between each attempt.11.Click OKto close the configuration dialog box.


16/48

12.Select the connection and click the Testbutton. Test connection succeeded will appearwhen 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 Optionsmenu, and select HP iLO and OA. The HPiLO and OAdialog box appears.

2. On the Connectionstab, click Exportto begin the export. The Save Asdialog boxappears.

3. In the File namebox, enter a name for the export file.4. Click Saveto export.5. Click OKto close the configuration dialog box and then click Finish.

To import a connection


2. On the Connectionstab, click Importto begin the import. The Opendialog boxappears.

3. In the File namebox, enter a name for the import file.4. Click Opento import.5. Click OKto 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 OAsystems. 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 Groupstab, click Addto begin the group setup. The Managed groupdialog boxappears.

3. In the Group namebox, enter a name for the group. This could be a descriptive name todistinguish the type of group.

4. In the Availablelist, press the Ctrl button while clicking on the connections to selectmultiple connections. Press the >>button to move the connections to the Selectedlist.

5. Click OKto close the configuration dialog box, and then click Finish.


17/48

To batch update credentials on a group


2. On the Groupstab, select a group and click Batch credential update.3. In the User namebox, enter a new user name or leave blank to keep original.4. In the Passwordbox, enter a new password or leave blank to keep original.5. In the Keybox, enter a new key or leave blank to keep original.6. In the Portbox, enter a new port or leave blank to keep original.7. Click OKto 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 add-on for System Center 2012 -

Orchestrator that enables you to automate the consolidation and correlation of fault andperformance events across you entire physical and virtual IT infrastructure.

Microsoft is committed to protecting your privacy, while delivering software that brings you theperformance, power, and convenience you want. For more information, see thePrivacy

Statement for System Center 2012 - Orchestrator.

System Requirements

The Integration Pack for HP Operations Manager requires the following software to be installedand 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
http://technet.microsoft.com/en-us/library/hh533440.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh533440.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh533440.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://technet.microsoft.com/en-us/library/hh533440.aspx#feedback


18/48


To download this integration pack, seeHP 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 Managerserver. You can create as many connections as you require to specify links to multiple serversrunning 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 Optionsmenu, and select HP Operations Manager.The HP Operations Manager dialog box appears.


3. In the Namebox, enter a name for the connection. This could be the name of the HPOperations 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 HPOMConfiguration.

5. In the HPOM Hostbox, type the name or IP address of the HP Operations Managercomputer. If you are using the computer name, you can type the NetBIOS name or the

fully qualified domain name (FQDN).6. In the HPOM Portbox, type the port used to connect to the HP Operations Manager

computer. By default the HPOM Portis set to 443.

7. In the HPOM Usernameand HPOM Passwordboxes, type the credentials thatOrchestrator will use to connect to the HP Operations Manager server. When a

connection is used for a Launch Toolactivity, an HPOM Administrator account must be

used. All other activities can use an HPOM User account.


HP Operations Manager Integration Pack for

http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460


19/48





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 andperformance events across you entire physical and virtual IT infrastructure.

Microsoft is committed to protecting your privacy, while delivering software that brings you theperformance, power, and convenience you want. For more information, see thePrivacy


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 andconfiguring Orchestrator and the HP Operations Manager application, refer to the respective




HP Operations Manager 9.x


To download this integration pack, seeHP Operations Manager Integration Pack for SystemCenter 2012 - Orchestrator.



management server and then deploy it to Runbook servers and Runbook Designers. For the


Configuring the HP Operations Manager Connections

A connection establishes a reusable link between Orchestrator and an HP Operations Managerserver. 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.
http://technet.microsoft.com/en-us/library/hh533440.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh533440.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh533440.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=232460http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://technet.microsoft.com/en-us/library/hh533440.aspx#feedback


20/48

To set up an HP Operations Manager configuration

1. In the Runbook Designer, click the Optionsmenu, and select HP Operations Manager.The HP Operations Manager dialog box appears.


3. In the Namebox, enter a name for the connection. This could be the name of the HPOperations 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 HPOMConfiguration.

5. In the HPOM Hostbox, type the name or IP address of the HP Operations Managercomputer. If you are using the computer name, you can type the NetBIOS name or the

fully qualified domain name (FQDN).6. In the HPOM Portbox, type the port used to connect to the HP Operations Manager

computer. By default the HPOM Portis set to 443.

7. In the HPOM Usernameand HPOM Passwordboxes, type the credentials thatOrchestrator will use to connect to the HP Operations Manager server. When aconnection is used for a Launch Toolactivity, an HPOM Administrator account must be

used. All other activities can use an HPOM User account.


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, andconvenience you want. For more information, see theSystem 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 andconfigured to implementing the integration. For more information about installing and
http://technet.microsoft.com/en-us/library/hh771464.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771464.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771464.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://technet.microsoft.com/en-us/library/hh771464.aspx#feedback


21/48

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




HP Service Manager 7.11 or 9The 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 ManagementTools)

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, seeHP Service Manager Integration Pack for System Center2012 - Orchestrator.



management server and then deploy it to Runbook servers and Runbook Designers. For theprocedures on installing integration packs, seeHow To Install an Integration Pack.

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 HPService Manager client.

For all HP Service Manager servers that you plan to connect to you must create an ODBC datasource name (DSN) on each Client and Runbook server. Both SQL Server Native and Oracle ODBC

connections are supported. SeeConfiguring the HP Service Manager Connections.
http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584


22/48

The licensing model for the components of HP Service Manager varies depending on the versioninstalled. 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 theSOAP-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 connectionmust 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 Openbox.

Click OK.

2. In the ODBC Data Source Administrator, click the System DSNtab.3. Click Add.4. Select the driver named SQL Server Native Client 10.0from 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 Serverbox.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 Sourceto confirm connectivity to the database.16.When the test completes, click OK.17.Click OK.


23/48

Setting up an Oracle ODBC Connection

1. Configure an Oracle Net Service name using the Oracle Net Configuration Assistant. Formore 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, clickStart, then Run, and then type \Windows\SysWOW64\odbcad32.exe in the Openbox.Click OK.

3. In the ODBC Data Source Administrator, click the System DSNtab.4. Click Add.5. Select the Oracle ODBC driver installed with the Oracle client from the list of available

drivers.

6. Click Finish.7. Enter a new name and description for the data source.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.10.

Select the appropriate authentication method for the database server and enter validcredentials.

11.Click OK.12.Click OKto close the ODBC Data Source Administrator.

To set up a HP Service Manager connection

1. In the Runbook Designer, click the Optionsmenu, and select HP Service Manager. TheHP Service Manager dialog box appears.

2. On the Connectionstab, click Addto begin the connection setup. The ConnectionConfigurationdialog box will appear.

3.

In the Namebox, enter a name for the connection. This could be the name of the HPService Manager server or a descriptive name to distinguish the type of connection.4. In the Server Addressbox, 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 Intervalbox, enter the how often, in minutes, you want to check the state

of the HP Service Manager connection.

6. In the ODBC DSNbox, type the name of the ODBC data source from one of theprevious procedures.

7. Enter the database user name in the DB Usernamebox.8. Enter the database password in the DB Passwordbox.9.

In the Usernameand Passwordboxes, type the credentials that Orchestrator will use toconnect 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 Cachebutton to retrieve and store the custom configuration

from the HP Service Manager server. This operation may take a few minutes to complete


24/48

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

Tip

For the DB Username and DB PasswordIf 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 doesnot 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

Configurationand double click the WSDL Configurationoption.4. In the External Access Definitiondialog click the Searchbutton to list all available

objects.

5. Select the required object from the object list.6. Select the Fieldstab.7. Scroll to the bottom of the Field List.8. Enter the database name of the field to be exposed in the Fieldcolumn.9. Enter the name which the web service will refer to this field in the Captioncolumn.10.Ensure the data type is correct in the Typecolumn.11.Click Saveat the top of the page to save the message.

Known Issues

The Test Connectionbutton cannot be used to validate Service Manager 7.1 web serviceconnections if the HP ServiceCenter 6.2 web service has been disabled.

Certain permissions are required when dealing with Change tickets. These permissions arespecified by assigning a user a Change Management Profile. While a user can have more than


25/48

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 toGreenwich/Universal with a date format of mm/dd/yy.

In certain versions of HP Service Manager the list of available categories when creating anincident 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 defaultbutton available in the Create Entry, Update Entryand Close Entryactivitiesmay 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 errormessage.

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
http://technet.microsoft.com/en-us/library/hh771464.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771464.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771464.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh771464.aspx#feedback


26/48

convenience you want. For more information, see theSystem 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 andconfigured to implementing the integration. For more information about installing andconfiguring Orchestrator and the HP Service Manager Web Service, refer to the respective




HP Service Manager 7.11 or 9The 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 ManagementTools)

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, seeHP Service Manager Integration Pack for System Center

2012 - Orchestrator.



http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://technet.microsoft.com/en-us/library/hh420346.aspxhttp://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=234584http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995


27/48

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 HPService Manager client.

For all HP Service Manager servers that you plan to connect to you must create an ODBC datasource name (DSN) on each Client and Runbook server. Both SQL Server Native and Oracle ODBC

connections are supported. SeeConfiguring the HP Service Manager Connections.

The licensing model for the components of HP Service Manager varies depending on the versioninstalled. 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 theSOAP-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 aboutlicensing.

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

Click OK.2. In the ODBC Data Source Administrator, click the System DSNtab.3. Click Add.4. Select the driver named SQL Server Native Client 10.0from 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 Serverbox.8. Click Next.9. Select the appropriate authentication method for the database server and enter valid

credentials.
http://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnectionshttp://technet.microsoft.com/en-us/library/hh771464.aspx#ConfiguringConnections


28/48

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 Sourceto 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. Formore 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, clickStart, then Run, and then type \Windows\SysWOW64\odbcad32.exe in the Openbox.

Click OK.

3.

In the ODBC Data Source Administrator, click the System DSNtab.4. Click Add.5. Select the Oracle ODBC driver installed with the Oracle client from the list of available

drivers.

6. Click Finish.7. Enter a new name and description for the data source.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.10.Select the appropriate authentication method for the database server and enter valid

credentials.

11.Click OK.12.Click OKto close the ODBC Data Source Administrator.

To set up a HP Service Manager connection

1. In the Runbook Designer, click the Optionsmenu, and select HP Service Manager. TheHP Service Manager dialog box appears.

2. On the Connectionstab, click Addto begin the connection setup. The ConnectionConfigurationdialog box will appear.

3. In the Namebox, enter a name for the connection. This could be the name of the HPService Manager server or a descriptive name to distinguish the type of connection.

4.

In the Server Addressbox, type the name or IP address of the HP Service Managercomputer. If you are using the computer name, you can type the NetBIOS name or the

fully qualified domain name (FQDN).5. In the Polling Intervalbox, enter the how often, in minutes, you want to check the state

of the HP Service Manager connection.6. In the ODBC DSNbox, type the name of the ODBC data source from one of the

previous procedures.

7. Enter the database user name in the DB Usernamebox.


29/48

8. Enter the database password in the DB Passwordbox.9. In the Usernameand Passwordboxes, 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 Cachebutton to retrieve and store the custom configurationfrom 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 OKto close the configuration dialog box, and then click Finish.

Tip

For the DB Username and DB PasswordIf 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 forthe 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 doesnot 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

Configurationand double click the WSDL Configurationoption.4. In the External Access Definitiondialog click the Searchbutton to list all available

objects.5. Select the required object from the object list.6. Select the Fieldstab.7. Scroll to the bottom of the Field List.8. Enter the database name of the field to be exposed in the Fieldcolumn.9. Enter the name which the web service will refer to this field in the Captioncolumn.10.Ensure the data type is correct in the Typecolumn.11.Click Saveat the top of the page to save the message.


30/48

Known Issues

The Test Connectionbutton cannot be used to validate Service Manager 7.1 web serviceconnections if the HP ServiceCenter 6.2 web service has been disabled.

Certain permissions are required when dealing with Change tickets. These permissions arespecified 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 toGreenwich/Universal with a date format of mm/dd/yy.

In certain versions of HP Service Manager the list of available categories when creating anincident 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 defaultbutton available in the Create Entry, Update Entryand Close Entryactivitiesmay 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 errormessage.

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

http://technet.microsoft.com/en-us/library/hh211591.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh211591.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh211591.aspx#feedbackhttp://technet.microsoft.com/en-us/library/hh211591.aspx#feedback


31/48


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

Microsoft is committed to protecting your privacy, while delivering software that brings you theperformance, power, and convenience you want. For more information, seePrivacy 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 TivoliNetcool/OMNIbus.

If the target Netcool server is not SSL-enabled, Orchestrator can stop responding when youattempt to test the connection using SSL.

Once you make a connection attempt, either by clicking Test Connectionor 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 pathand Trust store passwordfields, restart

the Runbook Designer.

When importing runbooks generated in Opalis, you need to open each Netcool activity in theRunbook 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


http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995http://technet.microsoft.com/en-us/library/jj614558.aspx#feedbackhttp://technet.microsoft.com/en-us/library/jj614558.aspx#feedbackhttp://technet.microsoft.com/en-us/library/jj614558.aspx#feedbackhttp://technet.microsoft.com/en-us/library/jj614558.aspx#feedbackhttp://go.microsoft.com/fwlink/?LinkID=216995http://go.microsoft.com/fwlink/?LinkID=216995


32/48



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 runbooksthat make requests to REST web services to get data or perform functions.

Microsoft is committed to protecting your privacy. For more information, see thePrivacy


System Requirements

The integration pack for REST requires that the following software is installed and configuredbefore implementing the integration. For more information about installing and configuring

Orchestrator, refer to the respective product documentation.

Orchestrator in System Center 2012 SP1Caution

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, seeSystem Center Integration Packs.


After you download the integration pack file, you must register it with the Orchestratormanagement server and then deploy it to runbook servers and installed Runbook Designers. For

the procedures on installing integration packs, seeHow To Install an Integration Pack.

System Center Integration Pack for

Microsoft SharePoint

0 out of 1 rated this helpful -R

SCCM 2012 Part 2 Notes.docx

Documents

Transcript of SCCM 2012 Part 2 Notes.docx