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

Wednesday, November 27, 2013

Florian Aguettaz IT Blog: [System Center] Full review of all System Center product ( #SystemCenter )

Florian Aguettaz is posting a full review of all System Center products. There are currently 7 products in the System Center Suite that are used to cover all the ITIL best practices. Each one will be detailed in different post on his blog.


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

Monday, July 1, 2013

[Orchestrator] Integrating Cluster Aware Updating with Operations Manager Maintenance Mode – Pre and Post Update Scripts ( #SCOM #Orchestrator )


Neil Peterson has published on June the 17th 2013 a step-by-step post to demonstrating how to use the Cluster Aware Updating Pre and Post-Update Script execution feature to place each node of the target cluster into Operations Manager maintenance mode before the cluster aware updating process is executed. This exercise can be extended to any pre or post activates that you would like to perform on you cluster nodes at maintenance time.



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.

Wednesday, February 6, 2013

[MMS 2013] Microsoft Management Submit 2013 - Session catalog is available


Session catalog is now live ! Check it on http://www.2013mms.com/Topic/List



I've search for Operations Manager :

Then for Orchestrator

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.

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.

Thursday, June 21, 2012

[Orchestrator 2012] Importing Integration Packs via PowerShell

Here is a link to a post from that explain the different possibilities given by COM. They also expose how to import Integration Packs by using a PowerShell Script.



Around the office, we have more and more internal teams that are latching on to Orchestrator and wanting to use it for building all sorts of integrations and automations, but one of the things that comes up from time to time is how to get the ability to have some sort of complete installation process that doesn’t require a separate step for installing Integration Packs or runbooks. In this case, enabling the automatic registering and deployment of an Integration Pack would really enable a streamlined installation process.
Note from the legal dept: The process described here is not officially supported by Microsoft and are provided only as an example to the community.
Neither I nor Microsoft, nor any other person, animal, vegetable or mineral assumes responsibility for the process demonstrated here. USE AT YOUR OWN RISK!

Here are links to the previous parts of the “COM” series:

And here is the direct link to the post 

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

Thursday, April 19, 2012

[OpsMgr 2007R2][OpsMgr 2012] Building groups in Operations Manager, with a bit of Orchestrator magic

Anders Bengtsson  has posted on April 2012 the 11th an article to show how to use Orchestrator to update a management pack that contains groups. Each time you run the runbook, a new version of your MP is generated and groups members are also updated.



In many scenarios you have a list of servers, a database query result or a place in your Active Directory that contains servers that you want to monitor in some special way. Often you need the machines in a group in Operations Manager so you can for example create overrides, maintenance mode and views for that group. It is a pretty boring work to build the group manually and then to keep the group updated.

A way to get the Operations Manager group in sync with the machine list is to use a runbook that creates a management pack including a group based on the list. This set of example runbooks reads a list of machine, creates a management pack with a group that includes the machines. The list of servers could be generated by another runbook or another tool. The last runbook also imports the management pack into Operations Manager.

Read more on http://contoso.se/blog/?p=2963

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