System Center 2012 SP1 – Orchestrator is Generally Available!

System Center 2012 SP1 – Orchestrator is Generally Available!

  • Comments 4
  • Likes

This morning we announced the availability of System Center 2012 SP1.   You can read more about the release on the System Center blog:

http://blogs.technet.com/b/systemcenter/archive/2013/01/15/system-center-2012-sp1-is-generally-available.aspx

New features for Orchestrator in System Center 2012 SP1:

System Center 2012 SP1 – Orchestrator now supports being installed on Windows Server 2012/Windows 8 and SQL Server 2012 (including support for Always On).

 

New Integration Packs in System Center 2012 SP1

Exchange Administrator Integration Pack for Orchestrator in System Center 2012 SP1

Exchange Users Integration Pack for Orchestrator in System Center 2012 SP1

Representational State Transfer (REST) Integration Pack Guide for Orchestrator in System Center 2012 SP1

Integration packs for each of the components in System Center 2012 SP1

Updated Integration Packs in System Center 2012 SP1

Active Directory Integration Pack for System Center 2012 - Orchestrator

HP Service Manager Integration Pack for System Center 2012 - Orchestrator

System Center Integration Pack for System Center 2012 Operations Manager

System Center Integration Pack for System Center 2012 Virtual Machine Manager

VMware vSphere Integration Pack for System Center 2012 - Orchestrator

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Can the SP1 integration packs be used with RTM? If not, where can I find the RTM integration packs (for example exchange admin). Thanks.

  • Hello,

    After a failover of the SQL Always On, starting the Designer gives me a request to re-enter the productkey. When failover back the message is gone. Failing back, the productkey box appears again.

    Any ideas?

    Peter

  • Getting the same error what Peter posted after failover. Any fix for this?

  • Not sure this is the right fix, I restored the service master key of primary replica node on all other replica nodes and it fixed the issue.