I’ve been applying UR2 across almost all System Center 2012 R2 components so I’ve decided to share some tips with you: Continue reading “Tips for Applying Update Rollup 2 on System Center 2012 R2 and Windows Azure Pack”
Time flies by and Update Rollup 2 for System Center 2012 R2 is now available. Almost all components are receiving update. There are a lot of nice fixes in this update that you will want to squash. Before doing that in production make sure you test them in your dev environment. Continue reading “System Center 2012 R2 Update Rollup 2 and Windows Azure Pack Update 2 are Now Available”
Service Management Automation (SMA) is the next gen IT Automation tool. SMA has some certain advantage over Orchestrator but also some limitations and vise versa. Nevertheless I am taking in consideration that you are aware of these advantages and limitations and you’ve decided to move fully or partially from SCO to SMA. Continue reading “From Orchestrator to Service Management Automation: Migration Scenarios”
I have a couple of Orchestrator servers with Web Features role installed on them. I’ve recently added those servers as Infrastructure Servers in VMM 2012 R2 in order to update them from there. After adding them the Orchestrator Web Service on those server stopped working. Continue reading “Orchestrator Web Service Does Not Work After Adding The Server to Infrastructure Servers in VMM 2012 R2”
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.
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.