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.
Exchange Connector 3.0 RTM is finally released and it is supported by MSFT. In order to deploy it you have to:
- Install UR2 for SCSM 2012 SP1;
- Remove Exchange Connector 3.0 RC if you have it installed.
You can find the full announcement here.
You can download the connector with a great guide for it here.
Additionally you can extend the connector with Service Manager SendEmail for Incidents
It is official: System Center 2012 SP1 has reached General Availability. Summarization of the new capabilities you can find on the System Center blogs:
If you want to test the components you can download VHD files that will help you with that:
I trial version of the product can be downloaded from here.
Documentation for download:
List of SC 2012 SP1 KB articles:
Kevin Holman’s QuickStart deployment guides:
Microsoft Virtual Academy Courses:
- Microsoft Virtualization for VMware Professionals – Learn how Windows Server 2012, Hyper-V, and System Center 2012 SP1 can help you build, deploy, and manage private cloud architecture. NOTE: This course becomes available on Jan 15.
- System Center 2012 Service Pack 1 Updates – Learn about the enhancements to each of the System Center 2012 SP1 components, which includes added support for Windows Server 2012, SQL Server 2012 and tighter integration with Windows Azure. NOTE: This course becomes available on Jan 16.
- COMING SOON: System Center 2012 SP1 Capabilities – Learn about the configuration and management of the infrastructure, services and applications available from System Center 2012 SP1. NOTE: This course becomes available on Jan 31.
The long waited Service Pack 1 of System Center 2012 has reached RTM and it is now available for download on MSDN. It seems the rumors were true. This is a Christmas gift from Microsoft .
Last week I’ve submitted a bug on a feature of SCVMM that I’ve spotted a long time ago. Due to various reasons I’ve somehow always forgot to submit it. The bug is that when you integrate SCOM 2012 and SCVMM 2012 you can put the Hyper-V host in maintenance mode in VMM and this will automatically put the Hyper-V host in maintenance mode in SCOM. This is true but to some extent. Actually only the objects in SCOM related to SCVMM are put in maintenance mode. What this means if you put the Hyper-V host in maintenance mode trough SCVMM and you restart that host you will still receive alerts like health service failure or failed to connect from SCOM about that host. The reason for that is if only objects related to VMM are put in maintenance mode other objects like the computer object, the health service and the agent watcher are still in active monitoring. A few days after submitting that bug in Microsoft Connect site I’ve received e-mail that this bug is closed as fixed:
As this issue is still present in System Center Virtual Machine Manager 2012 SP1 beta this leads me to believe that there are probably post beta releases for TAP customers which are not publically available. In a matter of fact there are some rumors over Internet that System Center 2012 SP1 has passed RTM and could be available early in January. I really hope so these rumors are true so we can have final release of Service Pack 1 for System Center 2012 as soon as possible. When RTM is available I will try to test if this bug is really fixed.