Showing posts with label Orchestrator 2012. Show all posts
Showing posts with label Orchestrator 2012. Show all posts

Friday, May 22, 2015

[Orcherstrator] System Center Orchestrator Migration Toolkit Version 7.3 #Azure #Orchestrator #Toolkit

A collection of tools for migrating integration packs, standard activities, and runbooks from System Center 2012 – Orchestrator to Azure Automation and Service Management Automation. 


The System Center Orchestrator Migration Toolkit consists of the following tools.

Integration Pack Converter
This tool converts integration packs that were created using the Orchestrator Integration Toolkit to integration modules based on Windows PowerShell that can be imported into Azure Automation or Service Management Automation. Using the tool’s wizard, you can select the activities in the integration pack that will be converted to cmdlets in the integration module. Placeholders are created for monitor activities that are not supported in Azure Automation or Service Management Automation.

Standard Activities module
Integration module that contains all of the standard activities used in Orchestrator Runbooks that can be imported into Azure Automation or Service Management Automation. This module must be installed in your environment prior to importing any runbook converted with the Runbook Converter.

Runbook Converter (coming soon)
This tool converts Orchestrator runbooks into graphical runbooks that can be imported into Azure Automation.



System Requirements
Supported Operating System
  • Windows Server 2012 R2, Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard
  • Supported Operating System
  • Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
Recommended Configuration for System Center Orchestrator Migration Toolkit
  • RAM – minimum 1GB recommended 2GB
  • Disk space minimum 200MB
  • CPU Dual Core or better
  • Windows Server 2012 R2
  • .Net 4.5

This posting is provided "AS IS" with no warranties.

Monday, July 1, 2013

[Orchestrator] Orchestrator Best Practice Series ( #Orchestrator )


 is offering us an Orchestrator Best Practice Series of post. The 3 first one are listed below but open this official link for more updates






This posting is provided "AS IS" with no warranties.

Monday, May 13, 2013

[Orchestrator 2012] Patching Orchestrator Runbook Servers while Maintaining High-Availability

Balancing server patching with maintaining the availability of the services that run on these servers can be a difficult task for an IT Pro, with lots of repetitive, time-consuming, and error-prone steps. Luckily, Orchestrator has emerged as an effective automation tool to help IT Pros manage the patching process. But what about when the Orchestrator service itself needs to be patched? How can an IT Pro ensure their enterprise automation continues to function despite the patching of the servers running Orchestrator components?

Joe Levy has published an interesting post to expose all steps to follow to be able to maintain high availability when patching Runbook Servers.




This posting is provided "AS IS" with no warranties.

Thursday, April 11, 2013

[Orchestrator 2012] System Center 2012 – Orchestrator Best Practice Series–Naming Conventions

, as promised, has a few blog posts coming on the topic of Best Practices as it relates to System Center 2012 – Orchestrator.  

He calls these Best Practices because He's found these practices work best for the environments he has implemented, supported, troubleshot, and optimized.  Even better, he learned these from one of the gurus in the industry (Charles Joy).  So, you could say he is channeling Charles with a bit of his own "flair". 



The fist article he has posted is called Automation–System Center 2012 – Orchestrator Best Practice Series–Naming Conventions to talk about the naming conventions for your folders, subfolders, Runbooks, Activities, etc in your environment.

Future posts will cover other best practices for System Center 2012 – Orchestrator Runbook design and optimization. 
Stay tuned! 

This posting is provided "AS IS" with no warranties.

Tuesday, January 29, 2013

[OpsMgr 2012] System Center Monitoring Pack for System Center 2012 - Orchestrator

The monitoring pack fmonitors the health and availability of Microsoft System Center 2012 - Orchestrator.


Quick details

Version:7.0Date published:4/1/2012
Language:English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.
File nameSize
OpsMgr_MP_Orch2012.docx               82 KB        Download
SC2012OrchestratorMP.EXE322 KBDownload

Overview

The Microsoft System Center Monitoring Pack for System Center 2012 - Orchestrator monitors the health and availability of Microsoft System Center 2012 - Orchestrator.

Feature Summary
The Microsoft System Center Monitoring Pack for System Center 2012 - Orchestrator provides the following capabilities.
  • Orchestrator Management Server Health - This scenario checks Orchestrator Management Servers for service status and critical log file events.
    • (monitor) Orchestrator Management Service
    • (monitor) Orchestrator Runbook Server Monitor
    • (alerting rule) Orchestrator Management Server Database Connection Error
    • (alerting rule) Orchestrator Runbook Server Monitor Database Connection Error
  • Orchestrator Runbook Server Health - This scenario checks Orchestrator Runbook Servers for service status and critical log file events
    • (monitor) Orchestrator Runbook Service
    • (monitor) Orchestrator Remoting Service
    • (alerting rule) Orchestrator Runbook Policy Module Fault Alert
    • (alerting rule) Orchestrator Runbook Server Database Connection Error
    • (alerting rule) Orchestrator Runbook Update Error
    • (alerting rule) Orchestrator Runbook Server ActionServerStorage Call Refused Error
    • (non-alerting rule) Orchestrator Runbook Policy Module Working Set Peak Collection
    • (non-alerting rule) Orchestrator Runbook Policy Module Thread Count Collection
    • (non-alerting rule) Orchestrator Runbook Policy Module % Processor Time Collection
  • Orchestrator Web Components Health - This scenario implements health roll-up for monitored IIS 7 components that represent the Orchestrator Web Components
    • (dependency monitor) Web Components Availability Rollup

    Please refer to the Monitoring Pack Guide included in the downlaod for more details
Release History
  • 4/2/2012 - Original English Release, version 7.0

System requirements

Supported operating systems: Windows Server 2008, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2
    The Monitoring Pack for System Center 2012 - Orchestrator has the following prerequisites:
    • The Monitoring Pack for System Center 2012 - Orchestrator supports both System Center 2012 - Operations Manager as well as System Center Operations Manager 2007 R2 or later. A dedicated management group is not required.
    • The Windows Server 2008 Internet Information Services 7 Management Pack (version 6.0.6658 or later) must be imported to the management group prior to importing the Monitoring Pack for System Center 2012 - Orchestrator.
    • Windows PowerShell is required on Orchestrator Management Servers and Runbook Servers

Instructions

Once you have reviewed the Monitoring Pack Guide and meet the prerequisites for the Monitoring Pack for System Center 2012 - Orchestrator you can import this management pack module using the Microsoft Operations Manager administrative console and following these steps. The MP file “Microsoft.SystemCenter.Orchestrator.Library.mp” should be imported first.

  1. Open the Microsoft Operations Manager Operator console
  2. Click on the Administrator pane at the bottom left corner
  3. Expand the Management Packs node in the tree view
  4. Click on the Import Management Pack on the “Actions” pane on the right and then browse to the folder where you extracted the MP and then import it.
  5. Follow the instructions until you have finished importing the management pack module.

This posting is provided "AS IS" with no warranties.

Thursday, January 10, 2013

[Orchestrator 2012] Orchestrator (SCORCH) 2012 Reference Guides

Eswar Koneti has posted on his blog today an interesting page related to Orchestrator 2012. He has listed out all the SCORCH guides integrated with Configuration manager 2012 to make us able to start building our SCORCH environment to integrate with System center products(Configmgr 2012).






A quick summary of the different link posted :

Start with the TechNet Documentation and the SCORCH Standard Activities.

System Center Orchestrator 2012: An Overview Video
Orchestrator 2012: a quick start deployment guide from Kelvin Holman

List of Step by Step series guides on Over View ,installation,runbook etc.

Integrated with System Center Configuration Manager (configmgr) 2012:


From my part, I would add a link to technet on How to Create an Orchestrator Connector that can be usefull.


This posting is provided "AS IS" with no warranties.

Wednesday, January 9, 2013

[Orchestrator 2012 SP1] System Center 2012 Service Pack 1 Integration Pack for IBM Tivoli Netcool/OMNIbus

The Integration Pack for IBM Tivoli Netcool/OMNIbus is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate actions in response to alerts that are raised within IBM Tivoli Netcool/OMNIbus.




Quick details

Version:7.1Date published:1/3/2013
Language:English

File nameSize
System_Center_2012_SP1_Integration_Pack
for_IBM_Netcool_OMNIbus.EXE                       
529 KBDownload



Overview

​The Integration Pack for IBM Tivoli Netcool/OMNIbus is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate actions in response to alerts that are raised within IBM Tivoli Netcool/OMNIbus.

Feature Summary
The Integration Pack includes the following activities:
  • Create Alert
  • Delete Alert
  • Get Alerts
  • Monitor Alert
  • Update Alert

Release History
  • 1/3/2013 - Original English release for System Center 2012 SP1, version 7.1
  • 9/10/2012 - Beta release for System Center 2012 SP1 beta

This posting is provided "AS IS" with no warranties.

[Orchestartor 2012 SP1] System Center 2012 Service Pack 1 HP Integration Packs

System Center 2012 Service Pack 1 Integration Pack for HP iLO and OA

The Integration Pack for HP Lights-Out (iLO) and Onboard Administrator (OA) is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate HP iLO and OA commands.

Quick details

Version:7.1Date published:1/3/2013
Language:English
File nameSize
System_Center_2012_SP1_Integration_Pack_
for_HP_iLO_OA.exe
383 KBDownload

System Center 2012 Service Pack 1 Integration Pack for HP Service Manager

The Integration Pack for HP Service Manager is an add-on for System Center 2012 SP1 - Orchestrator that enables you to retrieve, create, update and monitor tickets in HP Service Manager.


Quick details

Version:7.1Date published:1/3/2013
Language:English
File nameSize
System_Center_2012_SP1_Integration_pack_
for_HP_Service_Manager.exe

692 KBDownload

System Center 2012 Service Pack 1 Integration Pack for HP Operations Manager

The Integration Pack for HP Operations Manager is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate the consolidation and correlation of fault and performance events across you entire physical and virtual IT infrastructure

Quick details

Version:7.1Date published:1/3/2013
Language:English
File nameSize
System_Center_2012_SP1_Integration_Pack_
for_HP_Operations_Manager.exe
765 KBDownload

This posting is provided "AS IS" with no warranties.

[Orchestrator 2012 SP1] Runbook servers in different time zones by Anders Bengtsson

Anders Bengtsson has published on last december an interesting article to explain how Orchestrator works with schedules and different time zones.




This posting is provided "AS IS" with no warranties.

Tuesday, November 20, 2012

[Orchestrator] Orchestrator does not reconnect when the SQL server is restarted

Runbooks stop executing and the Orchestrator Runbook Service and Management Server do not function as expected when the SQL Server instance that hosts the Orchestrator database is restarted. Errors are expected to occur during the downtime of the SQL Server, however proper connectivity and behavior does not restore once the SQL Server instance has restarted.


When the problem is occurring, the following events are logged to Orchestrator's Event window:

The Orchestrator Runbook Service on <server name> is no longer running. Verify the status of the Runbook Server and try to restart Orchestrator Runbook Service. If the problem persists, contact Technical Support.

and

The Runbook Server is suspended because the product license expired.

Cause

The Orchestrator services must be restarted in order for normal behavior to be restored. Microsoft has determined this is an issue in System Center 2012 Orchestrator.

 

Resolution

A fix is scheduled to be available in an upcoming update for System Center. Please contact Microsoft Technical Support for more details. 

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

This posting is provided "AS IS" with no warranties.

Wednesday, October 31, 2012

[Orchestrator 2012][OpsMgr 2012] Orchestrator dashboard in Operations Manager 2012

Anders Bengtsson (MSFT) has published an article related to an Orchestrator dashboard in System Center Operations Manager 2012.


He provides a management pack that collects some information in the Orchestrator DB :
  • Queue
  1. Pending Jobs, show number of runbooks with pending status, meaning they are waiting to start
  2. Top minutes in queue, show number of minutes top 1 job have been in the queue.
  • Runbook Results
  1. Success, show number of runbooks that have ended with success result
  2. Warning, show number of runbooks that have ended with success result
  3. Failed, show number of runbooks that have ended with success result
  • Runbook Jobs. This widget show number of times each runbook have run with success result. You can easy see which runbook that most often executed. The names you see is the name of the runbook.
  • Orchestrator Server Status, show status of my Orchestrator roles. In this sandbox all roles are on the same server, SCO01.
  • Orchestrator Alerts show alerts generated by my Orchestrator machine.
You can download his example MP here, NOT SUPPORTED – Contoso.Orchestrator – v2 . Note that this is provided “AS-IS” with no warranties at all. This is not a production ready management pack or solution for your production environment, just a idea and an example.

This posting is provided "AS IS" with no warranties.

Monday, October 29, 2012

[OpsMgr 2012][Orchestartor 2012][SCSM 2012] System Center 2012–Extended OIP–Maintenance Mode POWER!! – Self Service portal

This week-end Oskar Landman has commented my post on LinkedIn and give me a link to one of his articles. The post explains the use of the Self Service Portal to set OpsMgr objects in maintenance mode.


He is giving a simple example with screenshots and shows how you can use the System Center 2012 Extended OIP in combination with SCSM and OpsMgr.

Very interesting way to proceed ! :)

Where to find System Center 2012 Extended OIP ? : Just follow this link !


This posting is provided "AS IS" with no warranties.

[Orchestrator 2012] System Center 2012 Extended Orchestrator Integration Pack V2

Although the current System Center 2012 integration packs are a good starting point for automating System Center there can be numerous extra activities to make the live of a System Center administrator / consultant even easier.
Because of this (MVP, Microsoft Partner) has created an Extended OIP to include more activities.
Since the SDK for both SCSM and Opsmgr are both basically the same, writing code using the SDK can be used on both products which makes writing activities twice as efficient.

Currently the OIP Contains 12 activities:
  • Managementpack - Export – Activity with possible filters to export any management pack from both SCOM as well as SCSM into a directory.
  • Class - Get class – Activity to get a class with possible filters on every property to het classes from both SCOM and SCSM.
  • Rule - Get Rule – Activity to get a rule with possible filters on every property to het classes from both SCOM and SCSM.
  • Managementpack - Import – takes a directory and imports any management pack from the directory into the management group works on SCOM and SCSM.
  • Managementpack - List – activity to get a management pack with possible filters on every property to get management packs from both SCOM and SCSM.
  • Managementpack - Seal – Takes a directory with unsealed XML;s, a key file and company name and seals every management pack and sends the exported management packs to a separate directory.
The other 6 activities make your life even easier to create a really sophisticated way to schedule and use maintenance mode on OpsMgr 2012!
  • Class – Get Class Instances – Takes a class (Internal Name) and retrieves all class instances. Can be filtered by using the filtering options in the activity.
  • Class – Get GroupClass Instances – Takes a group (Internal Name) and retrieves all members of the group
  • SCOM MaintenanceMode – Start Group – Takes a group (Internal Name) and retrieves all members of the group and place them in maintenance mode.
  • SCOM MaintenanceMode – Stop Group – Takes a group (Internal Name) and retrieves all members of the group and turn maintenance mode off.
  • SCOM MaintenanceMode – Start Object – Takes an object and places the object in maintenance mode.

To get the V2 Version including all 12 activities - http://www.authoringfriday.com/2012/10/27/system-center-2012extended-oipmaintenance-mode-power/

This posting is provided "AS IS" with no warranties.

Friday, October 26, 2012

[OpsMgr 2012][Orchestartor 2012] SCOM 2012 – Maintenance Mode and Orchestrator

An interesting article related to maintenance mode in System Center Operations Managers 2012 using Orchestrator.


Brut force methode used in Operations Manager 2007 (see script below) has been tested in Operations Managers 2012 and since the cmdlet has changed, only the get-date is well working...

$class = get-monitoringclass -name:Microsoft.Windows.Computer
$computer = get-monitoringobject -monitoringclass:$class -criteria:”PrincipalName=’scottmusjm1.tpb.lab’”
$start = get-date
$end = $start.addminutes(30)
new-maintenanceWindow -startTime:$start -endTime:$end -monitoringobject:$computer -comment:”Testing”

New script for Operations manager 2012 should look like (note the use of | where for the get-scomclassinstance) :

$class = get-scomclass -name:’Microsoft.Windows.Computer’
$computer = get-scomclassinstance -class $class | where{$_.name -eq ‘SCOTTMUSJM2.tpb.lab’}
$start = get-date
$end = $start.addminutes(30)
start-scommaintenancemode -Instance:$computer -EndTime:$end -Comment:”Testing”
Result looks good when you execute the line in powershell but no so much : not only does the script not set MM on the health service and the health service watcher, it doesn’t put the objects contained by Windows Computer into MM.

The rest of the article explains how to use Orchestrator to put in maintenance mode and show that all objects have been removed from MM including the health service and the health service watcher.


This posting is provided "AS IS" with no warranties.

Thursday, October 11, 2012

[Orchestrator 2012] System Center 2012 Service Pack 1 Beta Integration Pack for FTP

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.

 

Quick details

Version:7.1             Date published:10/8/2012
Language:English
File nameSize
System_Center_2012_SP1_Integration_Pack_for_FTP.exe1.1 MBDownload

Overview

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

Feature Summary
The Integration Pack includes the following activities:
  • Create Folder- the Create Folder activity is used in a runbook to create a folder on a FTP server.
  • Delete File- the Delete File activity is used in a runbook to delete a file on a FTP server.
  • Delete Folder- the Delete Folder activity is used in a runbook to delete a folder on a FTP server.
  • Download File- The Download File activity is used in a runbook to download a file from a FTP server.
  • List Folders/Files- the List Folders/Files activity is used in a runbook to list the folders and files in the specified folder path.
  • Rename File/Folder- the Rename File/Folder activity is used in a runbook to rename a file or folder on a FTP server.
  • Resume File Download- the Resume File Download activity is used in a runbook to resume a file download. This activity is only compatible with a FTP configuration.
  • Synchronize Folder/File- the Synchronize Folder/File activity is used in a runbook to perform a one way synchronization of a folder/File.
  • Upload File- The Upload File activity is used in a runbook to upload files to a FTP server.

This posting is provided "AS IS" with no warranties.

Tuesday, September 25, 2012

[OpsMgr 2012] Technical Documentation Download for System Center 2012 - Updated

This page lists the technical documentation downloads that are available for the Service Manager component of System Center 2012.



Version:1.0Date published:9/18/2012
File nameSize
SC2012_OpsMgr_Authoring.docx4.6 MBDownload
SC2012_OpsMgr_Authoring.pdf6.6 MBDownload New
SC2012_OpsMgr_Cmdlets.doc5.0 MBDownload
SC2012_OpsMgr_Cmdlets.pdf5.0 MBDownload New
SC2012_OpsMgr_Deployment.docx559 KBDownload
SC2012_OpsMgr_Deployment.pdf2.2 MBDownload New
SC2012_OpsMgr_GetStarted.docx62 KBDownload New
SC2012_OpsMgr_GetStarted.pdf255 KBDownload New
SC2012_OpsMgr_KeyConcepts.docx187 KBDownload New
SC2012_OpsMgr_KeyConcepts.pdf369 KBDownload New
SC2012_OpsMgr_Operations.docx4.2 MBDownload New
SC2012_OpsMgr_Operations.pdf7.6 MBDownload New
SC2012_OpsMgr_SuppConfig.docx93 KBDownload New
SC2012_OpsMgr_SuppConfig.pdf526 KBDownload New
SC2012_OpsMgr_WhatsNew.docx168 KBDownload New
SC2012_OpsMgr_WhatsNew.pdf388 KBDownload New


Version:1.0Date published:9/18/2012
File nameSize
SC2012_Orch_Admin.docx123 KBDownload
SC2012_Orch_Admin.pdf684 KBDownload New
SC2012_Orch_Deploy.docx134 KBDownload
SC2012_Orch_Deploy.pdf747 KBDownload New
SC2012_Orch_GetStarted.docx240 KBDownload
SC2012_Orch_GetStarted.pdf324 KBDownload New
SC2012_Orch_OrchConsole.docx67 KBDownload
SC2012_Orch_OrchConsole.pdf208 KBDownload New
SC2012_Orch_RunbookRef.docx189 KBDownload 
SC2012_Orch_RunbookRef.pdf1.4 MBDownload New
SC2012_Orch_Runbooks.docx147 KBDownload
SC2012_Orch_Runbooks.pdf653 KBDownload New


And of courses all other product of the System Center suite received an updated documentation !
Click on the product to access the download page :

This posting is provided "AS IS" with no warranties.

Thursday, September 13, 2012

[Orchestrator 2012] How to determine the version of System Center Orchestrator and its components

This article describes how to determine your current System Center Orchestrator version number and the corresponding product or service pack level.

How to determine the version of System Center Orchestrator Runbook Designer and Management Server

To determine the version of System Center Orchestrator Runbook Designer and the version of the Management Server that it is connected to, start the Runbook Designer application, connect to the desired Management Server and then click About on the Help menu.

Scroll down inside the Version Information box to see the versions of the various libraries installed on the Runbook Designer.

How to determine the version of System Center Orchestrator Runbook Servers

To determine the version of System Center Orchestrator Runbook Servers, start the Runbook Designer application, connect to the desired Management Server and then click Runbook Servers in the Connections pane.

How to determine the version of the System Center Orchestrator Database Schema

To determine the version of System Center Orchestrator Database Schema, start the SQL Server Management Studio application from your SQL Server or location where SQL Server Client Tools has been installed and connect to the SQL Database Engine instance that hosts the System Center Orchestrator database.

Click New Query and then execute the following SQL query:

USE <database> SELECT [DBVersion] FROM VERSION
Replace "<database>" with the name of the Orchestrator database.



System Center 2012 Orchestrator RTM

The following table lists the components and versions of System Center 2012 Orchestrator RTM.

ComponentProduct Version
System Center 2012 Orchestrator7.0.1154.0
Database Schema7.0.0
System Center 2012 Orchestrator Integration Toolkit7.0.359.0
Integration Pack for System Center 2012 Configuration Manager7.0.1298.0
Integration Pack for System Center 2012 Data Protection Manager7.0.1298.0
Integration Pack for System Center 2012 Operations Manager7.0.1298.0
Integration Pack for System Center 2012 Service Manager7.0.1298.0
Integration Pack for System Center 2012 Virtual Machine Manager7.0.1298.0
Integration Pack for System Center Configuration Manager 20077.0.1298.0
Integration Pack for System Center Data Protection Manager 20107.0.1298.0
Integration Pack for System Center Operations Manager 2007 R27.0.1298.0
Integration Pack for System Center Service Manager 20107.0.1298.0
Integration Pack for System Center Virtual Machine Manager 2008 R27.0.1298.0
Integration Pack for Microsoft Active Directory7.0.4465.5571
Integration Pack for IBM Tivoli Netcool/OMNIbus7.0.469.0
Integration Pack for HP iLO and OA7.0.264.0
Integration Pack for HP Operations Manager7.0.281.0
Integration Pack for HP Service Manager7.0.319.0
Integration Pack for VMware vSphere7.0.469.0

This posting is provided "AS IS" with no warranties.

Tuesday, September 11, 2012

[Orchestrator 2012] System Center 2012 SP1 Beta- Orchestrator Integration Pack are available - released on 9-9-2012

 Here are some fresh updates


The Integration Pack for VMware vSphere is an add-on for System Center 2012 Orchestrator that enables you to connect System Center Orchestrator to your VMware vSphere server to automate actions in VMware vSphere to enable full management of the virtualized computing infrastructure.

Quick details

Version:7.0Date published:9/9/2012
Language:English
File nameSize
System_Center_2012_Orchestrator_Integration
Pack_for_VMware_vSphere_RC.EXE
  2.3 MBDownload
The Integration Pack for VMware vSphere is an add-on for System Center 2012 SP1 Beta- Orchestrator that enables you to connect System Center Orchestrator to your VMware vSphere server to automate actions...

Quick details

Version:7.1Date published:9/9/2012
Language:English
File name          Size
System_Center_Integration_Pack
for_VMware_vSphere.EXE
               2.2 MBDownload
The Integration Pack for HP Service Manager is an add-on for System Center 2012 SP1 Beta- Orchestrator that enables you to retrieve, create, update and monitor tickets in HP Service Manager.

Quick details

Version:7.1Date published:9/9/2012
Language:English
File name       Size
System_Center_Integration_pack
for_HP_Service_Manager.exe
               709 KBDownload
The Integration Pack for HP Operations Manager is an add-on for System Center 2012 SP1 Beta- Orchestrator that enables you to automate the consolidation and correlation of fault and performance events across you entire physical and virtual IT infrastructure
 

Quick details

Version:7.1Date published:9/9/2012
Language:English
File name      Size
System_Center_Integration_Pack
for_HP_Operations_Manager.exe
          782 KBDownload
The Integration Pack for Exchange Users is an add-on for System Center 2012 SP1 beta- Orchestrator that enables you to facilitate the automation of user centric tasks, such as sending e-mail messages, creating appointments and updating tasks
 

Quick details

Version:7.1Date published:9/9/2012
Language:English
File name  Size
System_Center_Integration_Pack
for_Exchange_User.exe
           1,019 KBDownload
The Integration Pack for Exchange Admin is an add-on for System Center 2012 SP1 beta- Orchestrator that enables you to facilitate the automation of Exchange administration tasks.
 

Quick details

Version:7.1Date published:9/9/2012
Language:English
File nameSize
System_Center_Integration_Pack
for_Exchange_Admin.exe
               785 KBDownload
The Integration Pack for HP Lights-Out (iLO) and Onboard Administrator (OA) is an add-on for System Center 2012 SP1 beta- Orchestrator that enables you to automate HP iLO and OA commands.
 

Quick details

Version:7.1Date published:9/9/2012
Language:English
File name          Size
System_Center_Integration_pack
for_HP_iLO_OA.exe
              401 KBDownload
The Integration Pack for IBM Tivoli Netcool/OMNIbus is an add-on for System Center 2012 SP1 Beta - Orchestrator that enables you to automate actions in response to alerts that are raised within IBM Tivoli Netcool/OMNIbus. 

Quick details

Version:7.1Date published:9/9/2012
Language:English
File name    Size
System_Center_Integration_Pack
for_IBM_Netcool_OMNIbus.EXE
          554 KBDownload

This posting is provided "AS IS" with no warranties.