Description

This is the 6th in a series of 7. Learn about the new features in System Center 2012 R2 and the rich enhancements provided with Microsoft Azure Operational Insights and Automation. Learn how the System Center leadership team envisions the datacenter of the future, what the most significant areas of System Center investments are, and how we will collaborate with the ecosystem.

Session Type:

Code:

Room:

Embed

Download

Right click or Alt+Enter to download this episode

Download captions

Download:

The Discussion

Hal

I must be naive, but I don't understand why the on-premises version of a feature is any harder to innovate. It's not like you need to press CDs anymore. You are developing the feature, testing it, and pushing it out to a CDN for people to download. If you can do it for Azure, why can it not be done for on-premise? I am missing something. What is it? Just the user's restrictions on patching their servers?

@Hal - you are right that there are a set of common steps required for both innovating a feature that runs on-prem vs a service. the major difference with a feature in a service today is the time between deploying it and getting feedback and then being able to iterate on this feedback. Then repeating this process over and over where the team's backlog is driven on data from the usage and customer experience using the feature. On-prem products today typically aren't updated more than quarterly (ie. update rollups) and many customers are still running previous versions and even when running latest bits sharing usage feedback isn't typically enabled so the team is operating with less perfect data on the real usage of the feature and executes on a backlog that isn't as driven on real usage metrics. we are definitely working on improving the cadence and usage metrics for on-prem deployments so they can be iterated faster too. let me know if you have any questions on System Center or our roadmap that I can help with: VladJ @ Microsoft . com