TechEd 2012 NA - MGT332 - fighting fire to the cloud!

401 views
317 views

Published on

IT Admins are responding to incidents on a day-to-day basis, but management wants to shift to service monitoring. The biggest mismatch there is the maturity level and misconception that technology will fix the GAP. We know that’s not true! Walter Eikenboom shows you how to get from component monitoring to LOB application monitoring with Microsoft System Center Operations Manager 2012 and changing the operational paradigm to a private cloud service connecting System Center Orchestrator and System Center Service Manager 2012, creating processes to get your infrastructure to a private cloud. Stop fighting fire and start building your cloud today!

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
401
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

TechEd 2012 NA - MGT332 - fighting fire to the cloud!

  1. 1. MGT332
  2. 2. Goals and Objectives Stop following incidents • when incident control you life within IT you need to step back and start prioritizing. If you know what you did the last month you can see where you need to invest to Register and analyze • make you life easier. Describe your tasks • Fixing incidents is only one step in the solution, creating knowledge of the stuff step by step you learned is the second. Take your time to • Analyzing you daily and weekly task so you can automate your top 10 task by creating Automate time for the really cool project you never had time to do before! Make it part of your DNA • If you run into repetitive tasks, not only in the incident process, start the cycle over and over again.
  3. 3. Every incident Run from Need a clone is really incident to of the IT important incident AdminAlmost no Automate No time for first or Knowledge is knowing and promote infrastructuresecond tier remediation improvement incident who knows steps projects fixes
  4. 4. After an IT service has been successfully deployed, ensuring that it operates to meet business needs andexpectations becomes the top priority. This is the focus of the Operate Phase, which depends on four primaryendeavors:
  5. 5. Facilitate your IT admins with time and knowledge to change their roll to Private Cloud administrators Don’t let the process work you, let the process work for you! Use System Center 2012 capacity to leverage your ambitionPeople Process Technology
  6. 6. Attributes
  7. 7. Configure App Controller Orchestrator Deploy Virtual Machine Manager Service Service Operations Manager Model Delivery & Self Service Automation Configuration Manager Data Protection Manager DCConsumer Admin Service Manager Service Manager Monitor Operate Application Management Service Delivery & Automation Infrastructure Management
  8. 8. Service level agreement (SLA). A written agreement Woodgrovedocumenting required levels of service. The SLA is Business usersagreed upon by the service provider and the consumer,or by the service provider and a partner provider. SLAs Serviceshould list the metrics and measures that define Level Agreement (SLA)success for both the service provider and the consumer.Operating level agreement (OLA). An agreement Desktop Service Manager End to end Desktop Servicebetween one or more internal teams that supports therequirements set forth in the SLAs. Operating Level Agreement (OLA)Underpinning contract (UC). A legally bindingcontract in place of or in addition to an SLA. This typeof contract is with a partner service providerresponsible for building service deliverables for the Network team Active Directory team Security teamSLA. Network Hardware Vendor Underpinning Contract (UC)
  9. 9. Provides the following services:• Console access• Alert notifications• Connectors to other mgmt systems• Health aggregationIntroduces the following customerchallenges:• Performance and scalability bottleneck• High end hardware required• High availability requires clustering
  10. 10. Challenges Addressed:• Out of the box HA• Ability to run on commodity hardware
  11. 11. Connector Framework Integration Configuration Manager Operations Manager Active Directory Virtual Machine Manager Hardware inventory, Operations Manager Active Directory data for Virtual Machines and software inventory, discovered objects user, user groups, Virtual Machine software updates printers, computers Template configuration Distributed applications items Primary computer owner (Service Manager User contact based on asset- Business Service based information, intelligence data on deployed application organization, notification from VMM service addresses template) Service Manager connectors facilitate System Center and Exchange connectivity for CI data and notifications. Orchestrator integration packs facilitate automating activities across System Center, LOB, and third-party management tools.
  12. 12. Release Change Self-Service Operations Incident IT GRC Management Management Management Management Mobile Email PortalReporting Reporting and data warehousing Service catalog Templates CMDB ProcessAutomation Knowledge Work Items Configuration Items Workflows Third partyIntegration management tools
  13. 13. OPTIMIZE AND EXTEND DELIVER FLEXIBLE AND LOWER COSTS AND EXISTING INVESTMENTS RELIABLE SERVICES IMPROVE PREDICTABILITY Integration Orchestration Automation    
  14. 14. Automation Concepts Activities Runbooks Databus Standard Activities Intelligent tasks that System-level Used to publish A rich set of out-of- perform defined workflows that and consume box activities actions execute a series of information as a linked activities runbook executes Get Server ID Get Data Create Recovery Run .Net from DPM Sources Point Script Create Create Start Maint Shut Down Invoke Web Send e-mail Incident Checkpoint Mode VM Services Query Compare Database Values E-mail on Update on error success Return Data Check Schedule
  15. 15. Keep tuning you Monitoring and have a LOB perspective on you daily operation MonitorAutomate you most time consumingTasks Analyze you work Know what takes up your time Top 3 incidents Top LOB with problems Automate Analyze
  16. 16. Goals and Objectives Stop following incidents • when incident control you life within IT you need to step back and start prioritizing. If you know what you did the last month you can see where you need to invest to Register and analyze • make you life easier. Describe your tasks • Fixing incidents is only one step in the solution, creating knowledge of the stuff step by step you learned is the second. Take your time to • Analyzing you daily and weekly task so you can automate your top 10 task by creating Automate time for the really cool project you never had time to do before! Make it part of your DNA • If you run into repetitive tasks, not only in the incident process, start the cycle over and over again.
  17. 17. Attributes
  18. 18. http://northamerica.msteched.com www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn

×