As an IT Process Automation specialist who has been using System Center 2012 R2 Orchestrator and Opalis since 2007, I was very excited by Microsoft’s announcement in 2014 of Azure Automation their new cloud based automation platform. I have been an avid user and follower of Azure Automation since its inception as a pure PowerShell interface, into its graphical authoring capability via the Azure Portal.Read More
The tasks for setting up a new user are basically simple, but for various reasons never get completed in time for a new employee or contractor to start working immediately. Most of us have started a new job and had the experience of sitting at a desk unable to login on our first day on the job. The next few days or weeks are full of requests to get access to email, files, folders, Sharepoint sites, remote access and time entry systems.Read More
Kelverion have worked with hundreds of Microsoft System Center Orchestrator customers over the years, many of whom partner with Kelverion as their trusted advisors in System Center Integration & Automation.
This gives us an insight into where our customers need us most and allows us to develop the types of Integration Packs and Automation Solutions that are going to deliver the most value to organizations.Read More
Topics: Microsoft System Center 2012
This blog describes the techniques Kelverion Engineers use to troubleshoot the Kelverion ServiceNow Integration Pack Connection in Microsoft System Center Orchestrator. For additional configuration assistance, we recommend downloading the Kelverion ServiceNow IP User Guide.There are a few key areas to take into considerationRead More
Should you build your own Integration Pack or buy one?
To put it simply, it is cheaper and faster to buy a pre-built Integration Pack for System Center Orchestrator. Here are the five reasons why buying a pre-built Integration Pack for SCORCH is better than building your own.
Topics: Microsoft System Center 2012
An automated process in Orchestrator is achieved by creating one or more Runbooks. Fundamentally, the Runbook depicts the sequence of operations or work of a person, a group or mechanisms. Runbooks themselves can also be connected together to form more complex solutions to the more complicated processes in the organisation.
In the complex scenario the end to end process is broken down into a series individual Runbooks which when run end to end deliver the whole process, when one Runbook finishes it can call the next Runbook in the process.
Runbooks pass information between themselves by recording data on to a logical process with Orchestrator called the data bus. Any Runbook or Activity within the Runbook can place data onto the data bus and any other activity or Runbook can read data off the data bus.
With the power of Windows Server 2012 and the launch of System Center 2012 SP1, Self-Service Virtual Machine Provision, Intelligent Alert Forwarding, Automatic CMDB Population with System Center data has been placed into the hands of all Microsoft’s customers large or small. A fully automated solution is now a reality whatever the size of your IT team.Read More
The challenge with any integration and automation product is keeping the interfaces to vendor products current and when you have many different vendor management products to integrate this only becomes more complex.Read More
If whilst trying to connect your Orchestrator Operations Manager Integration Pack to SCOM you get a blank pop up window when testing the connection or during the execution of Runbooks interfacing to SCOM you get a message like the followingRead More