Request Error on Calling Freshly Installed Orchestrator 2012 R2 Web Service

Previously I’ve encountered this error on the Preview build of Orchestrator 2012 R2 and now I’ve encountered in the RTM bits.


This error appears in the following scenario:

You have SQL server to store the Orchestrator DB. In my case it is SQL Cluster. You have one server where you want to deploy all Orchestrator roles.If you use the installation wizard and deploy all Orchestrator roles at once you will not have this error. The Orchestrator web service will work perfectly fine. But using the all in one installation doesn’t give you the flexibility to have different service accounts. So if you deploy with the all in one installation wizard first the management server and the web features the Orchestrator web service works fine. But as soon you start the installation again and deploy the Runbook server role on the same server the web service starts to give request error upon calling it. Apparently when you deploy the Runbook server role on the management server separately something is changed in the Orchestrator database and the web service stops working. Even if you have other servers with the web service they will also start giving the error.

The workaround

If you are OK of using all Orchestrator roles with one service account just install all roles at once. If you want to use different accounts have a dedicated server for Orchestrator management role and separate servers for Runbook and/or web features roles. As long as you do not install the runbook role on the management server separately your Orchestrator web service will be fine.

Change Calendar in Service Manager with Orchestrator and Exchange

Out of the box Service Manager doesn’t have a change calendar but Anders Bengtsson how quick and easy it is to create such with integration tool like Orchestrator and a service like Exchange. In order to build the solutions you can follow thee steps here.

Runbook Commander 2.0 ‘Beta’

The free tool developed by Neil Peterson that allows you to execute Orchestrator runbooks from Configuration Manager ha reached version 2.0 although still in beta. Here are the changes compared to version 1.0:

  • In addition to supporting console extensions for the Device, and Collections node, 2.0 now supports the program node as well.
  • For Configuration Manager 2012 Device Console extensions are now added to both the Devices node and also the ‘View Members of Collection’ collection node.
  • New XML Generator Application – friendlier layout, ability to generate and also save .XML files.
  • Ability to create drop down lists on the Runbook Commander program.

You can start testing the tool by downloading it here.

Do not forget send any useful feedback to Neil.

Thank you Neil for sharing this tool with the community.

Automate adding AD users to AD groups with SCSM and Orcehsrator

Anders Bengtsson provide us with another guide how to automate the task of adding user to a group with Service Manager and Orchestrator. This is achieved again trough Request Offering with approval in SCSM and a couple of activities in Orchestrator. Read the full article here.

Service Offering for Password Reset in SCSM Self-Service Portal

Another very useful article for real world scenarios by Anders Bengtsson titled “Password reset with the Service Manager self-service portal”. He is also providing the runbook for password reset for download.

Many thanks to Anders for sharing his work with the community.