1. Настройка сервисов и автоматизация System Center 2012 SP1
9/16/2018
Настройка сервисов и автоматизация System Center 2012 SP1
Георгий А. Гаджиев
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. System Center Marketing
9/16/2018
Программа модуля
Стандартизация
Runbooks и CI-данные
Предложения запросов
Автоматизация процессов
Самообслуживание
Контролируемая среда
Ролевая модель
Упрощенный портал
Автоматизация систем
So in today’s discussion we’ll be thinking about service delivery and automation, and I’m going to be covering a couple of topics as part of today’s presentation. I’m going to give you a brief introduction on what we think about from a System Center 2012 SP1 datacenter and system management perspective. And then when we specifically talk about service delivery and automation, I want to get into three key areas. The first one is around Стандартизация. We are going to spend some time talking about the new service offering, request offering, and process automation capabilities that are part of Service Manager, specifically Service Manager 2012 with the latest release. We’re then are going to talk about how service delivery and automation driving the self-service experience through controlled empowerment, through role based access and through greatly simplified but powerful portal interface into System Center 2012 suite.
And the last area is what we call systems automation. And this is how we take those requests, those offerings and other types of activities that you allow people to request, and really drive automation on the back end of it. And I’ll spend some time walking through what the key points are that I want you to focus on in going through this presentation.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Управление IT-услугами
System Center Marketing
9/16/2018
Управление IT-услугами
Потребитель услуг
Провайдер услуги
Самообслуживание
Системы
Автомати-ция
Now let’s take a deeper dive into service delivery and automation, I first need to take a step back and really think about this in the form of two key relationships. On the left the service consumer or let’s think of this as the business unit owner and then on the right we have the service provider or the datacenter admin. The service provider has the relationship where the service provider is about identifying and delivering a standard set of IT services that the consumer is going to consume.
What we want to be able to do is take those standardized services and provide a self-service experience for the consumers to consume those services as they desire, when they want to, to the degree they want to, and know that because we are delivering it in a standardized manner it is delivered the same time, every time in a consistent way. You have a consistent experience for your users on an on going bases .
In between these two is automation. It is not enough to define a set of standard services and then present them for users to consume. But if you want to scale, you’d got to have automation built into these, both from a process perspective as well as from the systems perspective. And this is a cycle that goes on and on and on where we have the processes and the systems delivering standardized services in a self-service experience and the automation making it all happen, pulling it all together so that we can then deliver it to our users consistently. Again, at the same time, every time.
ПРоцессы
Стандартизация
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. 3

4. Доставка сервисов и автоматизация
System Center Marketing
9/16/2018
Доставка сервисов и автоматизация
Управление релизами
Управление
изменениями
Самообслуживание
Управление операциями
Управление инцидентами
IT GRC
Отчетность
Моб.
Портал
Отчетность и БД
Автомат-ция процессов
CMDB
WI (Рабочий элемент)
CI (Элемент конфиг.)
Знания
Каталог услуг
Рабочие потоки
Шаблоны
So we’ve talked about delivering IT services consistently, let me now take it a step further to look at the self-service, Стандартизация, and the automation experience. By self-service, we are now looking at how we deliver these services through our service catalog, through the reports that users consume, and through the various clients or mechanisms for accessing and requesting service. That might be sending an , through a mobile device, or accessing an online portal through your mobile device or even through a browser sitting on your client.
From a Стандартизация perspective, it is about the configuration management database, or we call that the CMDB. This is something that you may have heard of a lot about from a number of other vendors in the industry. System Center 2012 provides that CMDB that encapsulates the different work items, the requests for service, the incidences of problems of changes that you might need in your organization. We capture the configuration items that are present within your IT environment, as well as the knowledge about each of those, the performance information or the knowledge-based articles, and then we pull it all together in a central repository. And added to that or supporting all of that is the process work flow, the systems work flows, the work forms and the other activities for reporting on the data warehouse capabilities to actually present to the backend to the users.
Behind all of that is the automation, there is a significant amount of that that takes place through the System Center 2012 suite of products, through Orchestrator, through Virtual Machine Manager, through Configuration Manager, and then of course through Windows Server itself. And one of the things to really point out when we’re talking to Consumers is we can do this across third party management tools. System Center Orchestrator is our integration solution to not just within the System Center suite but also to third party tools. And we ship almost twenty different integration packs to those third party tools, allowing us to drive that automation, not just through the System Center stack, not just through Microsoft, but out to those third party tools.
Интеграция
Сторонние
инструменты управления
Active Directory
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. 4

5. Автоматизация запроса в 6 шагов
System Center Marketing
9/16/2018
Автоматизация запроса в 6 шагов
1. Import
Импорт данных для развёртывания
1. Импорт
Сборка предложения запроса
2. Сборка
Публикация сервиса в каталог
3. Публ.
2. Build
3. Publish
Создайте запрос на ВМ
4. Созд.
Запуск процесса развертывания сервиса
5. Проб.
Мониторинг сервиса
6. Монит.
Import deploy VM Runbook and data
Build ‘New VM’
request offering
Publish ‘New VM’ to service catalog
So this slide repeats itself a number of times through the deck and it’s really starting with and presenting to the users, and really getting across the idea that request offerings and building that self-service experience, is as simple as six key steps.
Importing the information about your environment into the CMDB
Building that consolidated picture and building those request offerings
Publishing them out through the portal
Allowing users to create their requests for service
That invoke the necessary automation activities
And that you can monitor for completion or for any action that needs to take place
We are going to build on this slide over the course of the rest of the presentation.
TRANSCRIPTION STARTS HERE
So we’ve automated that request fulfillment process and from importing to building and to publishing that VM or that VM Request and then we stepped over and actually created that VM, we invoked or deployed that VM runbook and then ultimately that helped us be able to monitor that process once it was created and deployed.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. 5

6. Развёртывание доставки сервисов
System Center Marketing
9/16/2018
Развёртывание доставки сервисов
Стандартизация
Стандартизация предоставляемых сервисов
Определите сервис для предложения
Определите предложение запроса для предоставления сервиса
Обозначьте все вовлеченные в процесс объекты (утверждения, телефоны, процессы и т.п.)
Самообслуживание
Предоставление пользователям возможности выбрать сервис из каталога
Контролируемая среда
Предложение запроса зависит от роли пользователя
Интуитивный интерфейс
Автоматизация
Автоматизируйте процесс исполнения запроса, заявки пользователя
Автоматизируйте маршрутизацию запросов на утверждение
Автоматизируйте процесс предоставления сервиса
So our first stop at looking at all of this, there are three things I want to talk about and that I’ve mentioned already. One is Стандартизация, where we’re going to standardize the services and the requests that are going to be offered and the process to automate them in the backend. Who is going to be involved from a notification, approval or fulfillment perspective?
The second pillar around service delivery and automation is about the self-service experience, that controlled empowerment, for the user roles, and the delivery of request offerings, that makes it easy to navigate the user portal.
And the third area is around automation, where we’re automating the delivery of those requests, and the automation of the people and process activities in terms of who has to be involved, who has to be the approver, and then how is the request for service made.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

7. System Center Marketing
9/16/2018
Стандартизация
So now let’s look at Стандартизация and in this we’re going to focus primarily on Orchestrator and Service Manager.
Orchestrator
Service Manager
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Импорт данных и Runbook для самообслуживания и автоматизации
System Center Marketing
9/16/2018
Импорт данных и Runbook для самообслуживания и автоматизации
Now, let’s talk about importing data and runbooks to enable the self service and automation we’re going to really hammer home the self service idea as well as automation.
Self Service
Automation
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Интеграция коннекторов Видимость CI
System Center Marketing
9/16/2018
Интеграция коннекторов Видимость CI
Configuration Manager
Инвентаризация оборудования, инвентаризация ПО, Обновление ПО
Основной владелец сервера
Operations Manager
Operations Manager Обнаружение объектов
Распределенные приложения (Service Manager сервис развернутый из шаблона сервиса VMM)
Active Directory
Active Directory данные о пользователях, группах, принтерах и компьютерах
Контакт пользователя, данные об организации
Virtual Machine Manager
ВМ и шаблоны ВМ, а также объекты конфигурации ВМ
This connector framework is really powerful and it helps us drive visibility of the configuration items across our infrastructure. And this is a snapshot of some of the different pieces of configuration item data that comes in through the connector framework. We have details from Configuration Manager, Operations Manager, Active Directory, and Virtual Machine Manager and the different items that come in and then reconcile together automatically within the CMDB to simplify and speed up your time to value. This is something that is really key to note when you are talking to your Consumers.
We do the reconciliation for you. With other tool sets and other competitors on the market, they provide this capability but you have to spend a lot of time actually setting up the reconciliation requirements. We take that away. We’ve built that into the tools. We’ve built that into the capabilities of System Center 2012 so that is automated. You just set up the connectors; we do the rest.
To summarize that, Service Manager connectors facilitate System Center and Exchange connectivity for configuration item data, or CI, and the notifications. Orchestrator Integration Packs, which we are going to go into next, facilitate automating specific activities the System Center suite as well as third party apps and Line of Business tools.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. System Center Marketing
9/16/2018
Шаблоны
Минимизируйте ввод данных, определив исходные значения
Стандартизация процессов
Соответствие требованиям
Стандартизированный метод получения данных
So here we have a snapshot of what our templates look like, this is where the IT service provider creates a standardized form or standardized process of how they will allow end users to make requests against service offerings with pre-default values, it also ensures compliance, we’re able to capture the data effectively and repetitively on an ongoing basis and then it can be used to create or update any given object at any given time.
Может быть использовано для создания/обновления кластера
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. System Center Marketing
9/16/2018
Предложения запроса
Описание сервиса созданного провайдером для потребления пользователем
Базируется на шаблоне
Создает запрос на сервис или инцидент в системе
Пользовательский ввод для получения данных
Свободный текст
Список
На базе запросов CMDB
Прочие
A request offering is a discrete offering also created by the IT service provider that allows the consumer can access and complete directly from the service catalog. It is related to a service request or a service offering, where that service offering can have more than that request offering and the request offering contains user prompts or other information that is required to update the requests. That could be anything from a list value that could be a query based list, that could be a free entry text area to gather more information about the VM or a number of other things.
Соотношение данных пользователей с предложениями запросов
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. System Center Marketing
9/16/2018
Автоматизация
Целостность
Использование рабочих потоков
Привязка к автоматизации сторонних компонентов (уведомления и пр.)
Запрос предложения напрямую соотноситься со свойствами сервиса, что исключает ошибки
Уведомления
Утверждения
Маршрутизация
Автоматизация
Runbooks
Отчетность
And the last piece is the automation. From the moment the person enters their information into the portal, we then create the service request from the request offering template. Then we start driving the level of automation. This gets into the automation and helps set up classification for particular service requests. It helps us invoke necessary workflow rules to route requests from one place to another through immediate action. It also helps us link process automation such as assignment and notification. And then it helps us to map the user’s prompts to request properties that automatically populate run book activities.
Think of it as a chain that links between the users at the request catalog level, entering their values into the form for their request for service. And that information flows all the way through the actual automation workflow that run book it the executed to fulfill their request. And the only people who touched that request would be that person who made the request and the person who approved it.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. System Center Marketing
9/16/2018
Самообслуживание
We then go into a self-service discussion focused on Service Manager.
TRANSCRIPTION STARTS HERE
So let’s take a look at self-service and we’re going to focus very heavily on Service Manager
Self Service
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Самообслуживание и каталог сервисов
System Center Marketing
9/16/2018
Самообслуживание и каталог сервисов
Предоставление
Услуг
Транслятор между ИТ и бизнесом
Ролевая модель
Предложения доставляются на базе прав пользователя
Упрощенный портал
Каталог сервисов является простым с точки зрения навигации
Self-service is about three things – controlled empowerment, a role-based experience, and a simplified portal.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. System Center Marketing
9/16/2018
Контролируемая среда
Публикуется провайдером
Инициируется пользователем
Транслятор между ИТ и бизнесом
Всегда целостная доставка сервиса
Controlled empowerment is about the service provider publishing requests that the consumers can access but then the user being able to initiate when they want service on their terms. It helps express IT requests in business language. Quite often things are lost in translation between what IT is asking for and what the user is actually requesting. And this allows us to start bringing this together and deliver a consistent experience that users can request but then IT, or the IT service provider gets the information they need in order to fulfill that request. They can then get a consistent manner, each time, and every time.
The key thing is this allows the consumer to choose what level of service plus the cost that they want. So you might deliver and offer, say, a silver, gold or even a bronze level of service, specifying what the time-frames are, what the cost structure is for each option for the item that they’re going to be selecting. It gives the user the empowerment to choose what they want based on what level of service they are after and the cost that is associated with it will automatically be applied. And you give them the power to choose as opposed to users, quite often, asking for everything, but expecting to pay nothing. And we can then standardize what that experience may look like.
Позволяет пользователю выбрать уровень и качество сервиса
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. System Center Marketing
9/16/2018
Предложение сервиса
WI используется для идентификации стандартных ИТ-сервисов
Содержит одно или более предложения запроса
Целостная доставка контента относящегося к сервису
Базы знаний
Данные об уровни обслуживания (SLA)
Стоимость и биллинг
So, service offering is a type of work item within the CMDB that identifies and classifies a standard IT service. A service offering will contain one or more request offerings. And it provides a consistent delivery of service-related information. Within a service offering, you will have information about knowledge articles associated with that service, the SLA information about what you can expect from a response and fulfillment time-frame, and then you have the cost and charge back related information.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. System Center Marketing
9/16/2018
Ролевая модель
Пользователи видят предложения на основе своей роли (Аккаунта)
Роли пользователя назначаются через AD
Предоставляйте уровень доступа на уровне сервиса или же на уровне отдельного запроса
Предложения частного облака
Предложения с LOB
Предложения для VDI
Предложения для разработчиков
Role-based is really about giving the users the ability to see what they are allowed to see based on their role. And this is a dynamic within the service catalog. It is based off of Service Manager groups which is mapped back to Active Directory and it is very dynamic. So whatever your group allocation is inside Service Manager again mapped back to Active Directory permissions, you will see the associated request offerings within the service catalog based on that information.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. System Center Marketing
9/16/2018
Упрощенный портал
Прост в использовании
Silverlight и веб-части на базе SharePoint Foundation 2010 или выше
Кастомизация портала с помощью
инструментов SharePoint
Расширяемость за счет сторонних компонентов
The last one is one of the things that I’m really excited about it’s the Simplified Portal. With System Center 2012, specifically Service Manager 2012 with the new suite, we actually reintroduced and rebuilt a brand new portal that is Silverlight web parts hosted in SharePoint Foundation 2010 or higher. And it allows us to customize it. So you can now tailor this portal using standard out-of-the-box SharePoint administration tools. And then can extend it using custom web parts.
The main thing is a customizable look and feel, but all of the forms in here are dynamically generated based on the request and service offerings that we configure that we talked about earlier. So when we configure a new request offering in service offering, Service Manager goes through, picks those up, and manages them for us in a very easy to navigate format.
Возможности портала
Настраиваемый,
с динамическими формами
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19. Cloud services process management pack
System Center Marketing
9/16/2018
Cloud services process management pack
Расширение модели
Проект
Пул емкости
Кост-центр
Логическая сеть
Таги размещения
Шаблоны VIP …
Шаблоны запросов сервисов
20+ шаблонов по умолчанию
Предоставление ВМ
Создание проекта
Управление емкостью
Автоматизированные шаблоны деятельности WI
Содержание каталога сервисов
20+ предложений запросов
Ресурсы по подписке
Регистрация тенанта
Запрос сервиса
Runbooks/ рабочие потоки
Автоматизация многомерных сложных сценариев
So now with System Center 2012 SP1, we are actually bringing some out-of-the-box features for how we’re going to deliver request offerings to our end users. This contains request capabilities for private cloud capacities or even virtual machines within a private cloud.
So we’re going to provide best practice knowledge and automation for the service catalog that gets embedded into the service catalog that Consumers can take advantage of very quickly to maximize their time to value. And we call this the System Center Cloud Services Process Pack. Internally, this is what we have known previously as SSP 2.0
Cloud Service Process Pack включен в Systems Center и интегрируется с Service Manager in SP1
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. System Center Marketing
9/16/2018
Автоматизация
The last area is around automation. And this is where we get into leveraging Service Manager and Orchestrator to drive the fulfillment of request offerings through the various systems.
TRANSCRIPTION START HERE
So we want to focus on the automation point of this.
Automation
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21. System Center Marketing
9/16/2018
Автоматизация
Автоматизация процессов
Назначения и уведомления
Утверждения
Автоматизация систем
Интеграция за счет оркестрации
Запрос
Утверждение
Выполнение
Automation is about two key things; process automation and system automation. Process automation is really what we touched on earlier. That is surrounding the aspect of assignment and notification and approvals of requests from the request to approval, capturing information from the CMDB, but then pushing information back down into the CMDB in terms of the work items that are created and the various pieces that go together to create the various service request item.
When we get into System Automation, this is about the orchestration and integration required to fulfill a request across different systems, whether it’s within System Center or within the suite of products itself and then of course the third party management tools.
CMDB
Runbooks
Шаблоны
Сервисы ВМ
Хосты
Пользоатели
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

22. Интеграция инфраструктуры
System Center Marketing
9/16/2018
Интеграция инфраструктуры
Входящий в System Center
Двунаправленный из Orchestrator
Двунаправленный для отчетов и уведомлений
Двунаправленный для интеграции Runbook
Virtual Machine Manager
Operations Manager
Orchestrator
Service Manager
Data Warehouse
Configuration Manager
Active Directory
Уведомления через Exchange
Service Manager
4a/b
We start as Service Manager as the repository for our CMDB and then Orchestrator which provides us our automation engine. We have a bi-directional connector those automation activities to come into Service Manager, as well as for Service Manager to issue and execute those automation workflows within Orchestrator.
We then have our other external repositories, either System Center related, Line of Business application such as Microsoft Exchange (User and Admin which is enabled with SP1) or 3rd Party management tools and inbound connectors to pull in configuration items and automation data to be populated into our CMDB and be reconciled together so that we’re looking at single record for a piece of our infrastructure even though some pieces came from Virtual Machine Manager, Operations or Configuration Manager or even Active Directory.
Once we have our reconciled view of data within our infrastructure we can then do something with that. We have within the System Center suite a bi-directional interface through Orchestrator to issue automation commands to System Center products or 3rd party tools or Line of business application if you build your own integration pack using the SDK to actually drive automation within those tools, to respond to errors to deliver changes to manage changes with your infrastructure. Within SP1, we’ve добавляйтеed integration packs to enable Azure cloud management.
And then lastly part of doing all this work we have to do two things: keep people aware and what’s happening and we got to be able to report on it. And we provide that inbound and outbound notifications capability through Service Manager and Orchestrator to Exchange as well as to our Service Manager data warehouse for dash boarding and reporting capabilities.
TRANSCRIPTION STARTS HERE
If we want to view integration across the infrastructure let’s first start with the relationship between Service Manager and Orchestrator and this is a relationship that’s key to all of the other components within the enterprise. There is first a bi-directions connector for automation activities and execution of workflows between Orchestrator and Service Manager. We’ll then provide some configuration items and automation data that is populated into the CMDB and this may come from Virtual Machine Manager, also known as VMM, Operations Manager, Configuration Manager as well as Active Directory. There is also some bi-directional relationship between the Microsoft workloads and in this case it may be Exchange, in this case perhaps SQL. There are also third party management tools that you may have in your environment as well that provide a bi-directional relationship with Orchestrator as well.
Automation commands are then issued to System Center, third party tools as well as the Microsoft Exchange as well as Azure, this is a new integration that was just introduced with System Center 2012 SP1that now allows us to connect to those other components.
We then have inbound and outbound notifications and business intelligence as we think about how do we now report on the activities that are taking place, these notifications are delivered via Exchange and then the relationship between Service Manager and the data warehouse which sits in the back end now delivers much more rich BI reporting and dashboards.
Нагрузки Microsoft
Управление
Azure Cloud
BI через отчетность и дэш-борды
Сторонние инструменты
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

23. Автоматизация биллинга
System Center Marketing
9/16/2018
Автоматизация биллинга
Process data
Virtual Machine Manager
Operations Manager
Load data
Data mart
Service Manager Data warehouse
OLAP
SQL данные
или
Отчеты
In SP1, we are very excited to be adding a highly anticipated capability in Chargeback. Let’s walk through some key steps or processes that brings resource usage rights with the chargeback reports.
At a high-level, we first think about this in terms of getting the usage data, we’ll store the data and then we'll access or analyze that data to deliver an insightful reporting experience.
So what is involved in getting the usage data? Chargeback is all about cloud usage so it has a sole dependency on VMM or Virtual Machine Manager. Once a VM is requested or spun up, Ops Manager then uses that data and sends it to Service Manager and specifically the data warehouse on the backend.
In the data warehouse, is where we then process, analyze which in turn specifies a cube or data mart.
The final step in accessing the usage data, we will create OLAP cubes which all has the varying types of VM usage associated with a given tenant and cost center. Ultimately, IT can then decide how and where to render various types of reports. With SQL Server Reporting Services, both Excel and SharePoint can be used to generate reports and dashboards to meet the needs of the business.
Доступ к данным
Хранилище данных
Сбор данных
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24. Cloud Services Process Pack
System Center Marketing
9/16/2018
Cloud Services Process Pack
Предложение запросов
Запросы на создание сервисов
Биллинг
Отчетность
So as we wrap this up we really saw how we take the Cloud Services Process Pack features and we’re able to render a couple of different things, we’re able to show how service catalog request offerings are built, how we can modify them and how we can deploy them. We then showed how we requested a service for deployment and then we can see the output of usage for chargebacks and reports.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25. Концепция автоматизации
System Center Marketing
9/16/2018
Концепция автоматизации
Активности
Реализация определенных задач
Runbooks
Рабочие потоки связаны на уровне системы
Шины данных
Используется для динамического получения данных
Стандартные активности
Богатый набор встроенных активностей
Вовлечение веб- сервисов
Создать инцидент
Запуск скриптов .NET
Получить
ID Сервера
Источники
Данных
Точка восстановления
Отсылка
Создать снимок
Опрос БД
So when we look a the automation concepts, we are looking at the four key areas;
The various run activities and this activities are really intelligent tasks that perform a defined action. There are a couple of examples where we might run a .NET script, check a schedule, or invoke a web service, query a database, or even send an .
A Runbook is a collection of activities that are pulled together in a workflow. This is the systems level workflow that will execute a series of linked automation activities. In this case, we have an example where we actually create an incident which creates an incident record inside of either Service Manager or Remedy or HPOV Service Desk. We might then want to kick off a workflow that checkpoints a server, puts it into maintenance mode, shuts down the virtual machine, and then writes the update back to the live incident record. It’s a simple Runbook but it allows us to take various activities and link them together and pass data between them.
This gets into what we call the databus. The databus is used to publish and consume information as a Runbook executes. So if we have an activity where we need to get the identity of a server, and we get the necessary data sources, we can pass information from one activity to the next, and then we’re able to easily build off of that and develop a true workflow and that really collects the necessary data.
Now with these activities, we provide out-of-the-box standard activities that provide various functionality and capabilities for users. And these different utilities that might be at the file level, interaction capabilities, or even running .NET scripts, is really the key areas that you’re able to highlight and bring into your runbook workflow. And as I mentioned earlier that we now ship a significant amount of data integration packs right out-of-the-box with System Center 2012 SP1.
Сравнение значений
Начало обслуживания
Проверка расписания
Выкл.ВМ
Обновление
Возврат данных
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

26. Построение автоматизации
System Center Marketing
9/16/2018
Построение автоматизации
Стандартные активности в частном облаке
Исполнение системных команд
Задачи на базе расписание
Мониторинг процессов и уведомлений
Оповещения по
Управление рабочими потоками
So of those standard activities to support things like delivering private cloud offerings are run system commands, perform system activities, down to send to notifications or other notification types if needed, manipulate a text file, and manage workflows.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

27. Построение автоматизации
System Center Marketing
9/16/2018
Построение автоматизации
Microsoft Runbook Пакеты интеграции
System Center 2007 Operations Manager
System Center 2007 Configuration Manager
System Center 2010 Service Manager
System Center 2008 Virtual Machine Manager
System Center 2010 Data Protection Manager
System Center 2012 Operations Manager
System Center 2012 Configuration Manager
System Center 2012 Service Manager
System Center 2012 Virtual Machine Manager
System Center 2012 Data Protection Manager
Active Directory
A simple collection of the Microsoft Runbook Integration Packs across the System Center 2012 SP1 suite as well as Microsoft tools such as Active Directory.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

28. Интегрируйте свои компоненты
System Center Marketing
9/16/2018
Интегрируйте свои компоненты
Создавайте свои пакеты интеграции
Используйте Integration Kit (OIT) Command-Line Interface (CLI)
На базе GUI
Интегрирует различные инструменты
And if that’s not enough, you can now build your own. You can build and distribute your own integrations. We call it the Quick Integration Kit, or the QIK. That is a command line interface or a software development kit to actually build out your own integration pack. They are easy to build and to integrate and allows you to use either .NET or Java IDEs to compile DLL resource files to deliver your own integrations.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

29. Выстраивая свою автоматизацию
System Center Marketing
9/16/2018
Выстраивая свою автоматизацию
Внешний интерфейс к System Center
На базе стандартов
RESTful
OData (Open Data Protocol)
Используйте преимущества
различных компонентов в одном решении
So at the end of the day, we provide a lot, but we also provide you the ability to build your own if you need to. In building those integrations, most of those are delivered through XML files that expose Orchestrator runtime functionality and data. It also helps with reporting and is our external interface into System Center,2012 SP1 and it standardizes how it operates with other tool sets.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

30. Мониторинг автоматизации
System Center Marketing
9/16/2018
Мониторинг автоматизации
So, this brings us to the last area around automation. And this is where we want to leverage Service Manager and Orchestrator to drive that fulfillment of request through a number of different systems.
Автоматизация
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

31. Отслеживание прогресса
System Center Marketing
9/16/2018
Отслеживание прогресса
Service Manager
Отображение прогресса в представление рабочих элементов
Ссылка на консоль Orchestrator’а для отображения прогресса
Перезапуск неудачных сценариев Runbook
Orchestrator
Подробный отчет о состоянии процесса до уровня отдельной активности
Историческое представление запущенных ранее Runbook
Данные ввода и вывода, а также данные о рабочем окружении
Портал самообслуживания
Итоговое представление потребляемых услуг для потребителя
Уведомления по
Уведомление об успехе/неудачи, прогрессе процесса
Электронные письма с поддержкой HTML для качественного представления данных
So we want to monitor our progress, we took Service Manager and that’s where we’re going to view the status of our work items or we can easily link over to the Orchestrator console and then we can retry our failed runbooks if we need to.
Within Orchestrator that’s where we’ll have our detailed status, we’ll have a holistic view of our runbook execution and then we have input, output runtime data that we can view.
Stepping over to the service portal or the self-service portal is where we actually have our summarized view of the status for the end user.
And then we have our notifications that really provides us information around the status or activities that we need to do based on the performance of the system and runbooks.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

32. Автоматизация запроса в 6 шагов
System Center Marketing
9/16/2018
Автоматизация запроса в 6 шагов
1. Import
Импорт данных для развёртывания
1. Импорт
Сборка предложения запроса
2. Сборка
Публикация сервиса в каталог
3. Публ.
2. Build
3. Publish
Создайте запрос на ВМ
4. Созд.
Запуск процесса развертывания сервиса
5. Проб.
Мониторинг сервиса
6. Монит.
Import deploy VM Runbook and data
Build ‘New VM’
request offering
Publish ‘New VM’ to service catalog
So this slide repeats itself a number of times through the deck and it’s really starting with and presenting to the users, and really getting across the idea that request offerings and building that self-service experience, is as simple as six key steps.
Importing the information about your environment into the CMDB
Building that consolidated picture and building those request offerings
Publishing them out through the portal
Allowing users to create their requests for service
That invoke the necessary automation activities
And that you can monitor for completion or for any action that needs to take place
We are going to build on this slide over the course of the rest of the presentation.
TRANSCRIPTION STARTS HERE
So we’ve automated that request fulfillment process and from importing to building and to publishing that VM or that VM Request and then we stepped over and actually created that VM, we invoked or deployed that VM runbook and then ultimately that helped us be able to monitor that process once it was created and deployed.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. 38

33. 9/16/2018 5:46 PM
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.