Somewhere between the physical and the virtual
More announcements ...
I am very excited to be able to post this article, welcoming System Center Orchestrator to the System Center suite!
As was communicated by Brad Anderson in Tuesday’s MMS keynote and on the Nexus news bulletin, System Center Orchestrator is the official name for what we have been referring to previously as Opalis vNext.
Orchestrator which will be part of the System Center 2012 releases will provide a number of new features, functions and capabilities in addition to being rebranded and the codebase being moved into the Microsoft organization.
There will be a lot of information posted over the coming weeks and months as we build to the Beta in a few months and the Final release expected later this year, however I wanted to provide a summary level list here.
In addition to the above investment areas, we are also completing a number of ‘housekeeping’ functions:
As I mentioned above, we will be posting a lot of information about Orchestrator over the coming weeks and months. We are ramping up our early adopter TAP program at the moment, and later in the year we will be running a full Public Beta so you can all take the new functionality for a spin
Keep an eye out for further information in the near future, and in the mean time, you can keep up with all the information by following @SC_Orchestrator on twitter or by using the #SCOrch tag.
And as always, I welcome any feedback you have.
Send me an e-mail Follow me on Twitter Connect with me on LinkedIn
I can't wait to see the REST API!!!!
Not sure if this is the correct forum for this question, apologies if not...are you aware of an alternative to the OV Connect element? The current requried one is no longer supported by HP therefore we can't utilise the HP OMW IP.