1 / 66

Opalis to Orchestrator and Microsoft System Center Service Manager 2010 to 2012

MGT325. Opalis to Orchestrator and Microsoft System Center Service Manager 2010 to 2012. Eamon O’Reilly & Ranganathan Srikanth Microsoft Corporation. Agenda. What’s new in System Center 2012. SM 10 -> SM 2012. Better together. Opalis 6.3 -> Orchestrator 2012. Key Takeaways. Public Cloud.

clay
Download Presentation

Opalis to Orchestrator and Microsoft System Center Service Manager 2010 to 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. MGT325 Opalis to Orchestrator and Microsoft System Center Service Manager 2010 to 2012 Eamon O’Reilly & Ranganathan Srikanth Microsoft Corporation

  2. Agenda • What’s new in System Center 2012 • SM 10 -> SM 2012 Better together Opalis 6.3 -> Orchestrator 2012 Key Takeaways

  3. PublicCloud Configure Deploy Service Model Private Cloud Virtual Monitor DC Admin Operate Physical System Center Helps Deliver IT as a Service App Controller Orchestrator Service Delivery and Automation Self-Service Virtual Machine Manager Operations Manager Configuration Manager Data Protection Manager App Owner Service Manager Service Manager Application Management Service Delivery and Automation Infrastructure Management

  4. Configure and Deploy Service Delivery and Automation STANDARDIZATION SELF-SERVICE AUTOMATION Standardize the services provided by IT to consumers. Define the services to be offered. Define the request offerings that will be contained within a service offering. Identify who needs to be involved (approvals, notifications, fulfillment). Give consumers of IT services the ability to identify, access, and request services as needed. Controlled empowerment. Request offerings displayed based on user role. Intuitive, easy-to-navigate portal. Automate the service processes and systems necessary to the fulfillment of consumer requests. Automate routing of requests for approval and notification. Automate provisioning of the service request.

  5. SM10 -> SM2012

  6. Session Objectives and Takeaways • Session Objective(s): • Planning considerations and process to upgrade from Service Manager 2010 to Service Manager 2012 • Share upgrade best practices • Demonstrate in-place upgrade of SM 2012 • Demonstrate a pre-req checking tool • Takeaway(s) • You can upgrade successfully with minimal downtime • Many customers have successfully upgraded to production • Upgrade guides provide step-by-step instructions

  7. WHY UPGRADE?Perf & Scale improvements • Perf improvements • Minimum of 25-30% faster than SM 2010 SP1 • Create, Delete Incident, Folders, templates – 80% faster • More responsive and snappier experiencesfor common operations • Viewing incidents, computers • Searching KA • Scale improvements • Up to 80 analyst consoles / server

  8. WHY UPGRADE?Updates to key features • Support for Parallel activities in Change Management • Support for Parent-Child relationships in incidents • Support for Duplicating Templates • Support for Periodic Notifications • Advanced Reporting capabilities / Analytics • Connector upgrades • PowerShell enhancements • Shortcut keys

  9. WHY UPGRADE?New investments

  10. UPGRADE PREPARATION • Pre-requisite changes • SKUs, License Key changes • Supported upgrade scenarios/paths • SM & OM compatibility • Integration with partner/in-house solutions

  11. HARDWARE PRE-REQS • Unchanged from SM 2010

  12. SOFTWARE PRE-REQS

  13. OS SUPPORTConsole • XP is not a supported OS for Consoles • Workarounds • Terminal Services

  14. BROWSER SUPPORTPortal • Firefox is not a supported portal client

  15. SOFTWARE PRE-REQ CHANGESManagement Servers • OS requirements • W2K8 R2 SP1 • Other components • SQL Native client • SQL Server 2008 Analysis Management Objects • SQL Server 2008 Analysis Data Objects • PowerShell 2.0

  16. SOFTWARE PRE-REQ CHANGESPortal, Reporting components • Portal • SharePoint 2010 • NET 4.0 • Silverlight 4.0 (required only on the client) • IE 8, 9 (required only on the client) • SQL Server 2008 Analysis Services • Standard edition supported • Enterprise edition provides better usability, scale, performance and cube maintenance

  17. UPGRADE PREPARATION • Pre-req changes • SKUs, License Key changes • Supported upgrade scenarios / paths • SM & OM compatibility • Integration with partner/in-house solutions

  18. SKUs, LICENSE KEYsRTM release License keys needed to upgrade to a licensed version. Eval to Licensed version (activation) is not supported

  19. UPGRADE PREPARATION • Pre-req changes • SKUs, License Key changes • Supported upgrade scenarios / paths • Capacity planning • SM & OM compatibility • Integration with partner/in-house solutions

  20. SUPPORTED UPGRADE SCENARIOS • In-place upgrades only

  21. UN-SUPPORTED UPGRADE SCENARIOS • Rolling upgrades

  22. POSSIBLE UPGRADE SCENARIOS • Side-by-Side upgrades • Using Orchestrator to keep instances in sync • Custom implementation • No Out of the Box runbooks that deliver this scenario

  23. UPGRADE PATHS *no upgrade for SM 2010 portal

  24. UPGRADE PREPARATION • Pre-req changes • SKUs, License Key changes • Supported upgrade scenarios / paths • SM & OM compatibility • Integration with partner/in-house solutions

  25. SM & OM compatibility

  26. UPGRADE PREPARATION • Pre-req changes • SKUs, License Key changes • Supported upgrade scenarios / paths • SM & OM compatibility • Integration with partner/in-house solutions

  27. Upgrade best practices • Treat upgrade like any other project • Mitigate risk • Create a sandbox environment to test upgrade • This cannot be over emphasized • Use production data in pre-prod environment • This will give you peace of mind and realistic performance expectations • Have pre-prod and production users in the same domain (easier to test) • Plan & perform UAT in your sand-box environment prior to upgrade

  28. UPGRADE LIFECYCLE

  29. PLAN FOR DR • Upgrades could run into non recoverable errors • SM topology can be complex • DR plan is essential to restore state • DR Guide documents the steps required

  30. Demo – SM 2010 to SM 2012 In-place Upgrade Service Manager 2010 Srikanth Ranganathan Program Manager System Center Service Manager

  31. Example error in the log file MSI (s) (1C!9C) [10:19:19:290]: Product: Microsoft System Center 2012 - Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25156. The arguments are: -2147217900, MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\CMDWDataMart.mdf'.,

  32. ERRORS DURING UPGRADE • You have to restore it to its original state using DR process

  33. Demo – Pre-req tool Remote pre-req tool Srikanth Ranganathan Program Manager System Center Service Manager

  34. FAQ • Can I continue to monitor SharePoint 2010? • Yes. OM 2007 agents and OM 2012 agents are supported. You have to install OM 2012 agent before SM 2012 install • What happens to unsealed MPs that have been used to customization? • Out-of-box solution MPs are sealed and upgraded • Customer modified MPs are untouched • What happens to existing user roles, subscriptions and workflows? • User roles, subscriptions, and workflow continue to function unaffected

  35. FAQ - Continued • What happens to form customizations? • Custom forms (via Authoring Tool) may require layout adjustments. Margin and alignment shifts with new form styles • What happens to 3rd party product integration? • Partners have not had much time to test their integration with SM 2012 pre-release bits • Check with the partner to verify in-place upgrade to SM 2012 • 2010 Portal • SM 2010 Portal is not upgradable to SM 2012 • SM 2012 is SharePoint 2010 based • Customizations must be implemented in this framework

  36. In Review: Session Objectives and Takeaways • Session Objective(s): • Planning considerations and process to upgrade from Service Manager 2010 to Service Manager 2012 • Share upgrade best practices • Demonstrate in-place upgrade of SM 2012 • Demonstrate a pre-req checking tool • Takeaway(s) • You can upgrade successfully with minimal downtime • Many TAP customers have successfully upgraded to production • Upgrade guides provide step-by-step instructions

  37. Opalis -> Orchestrator

  38. System Center 2012 Orchestrator Improvements

  39. Orchestrator Terminology Opalis Orchestrator Runbook Activity Standard Activities Runbook Designer Runbook Server Runbook Service Runbook Tester Orchestration Console Orchestrator Run Program Service Orchestrator Runbook Server Monitor • Policy • Object • Foundation Objects • Opalis Client • Action Servers • Action Service • Testing Console • Operator Console • Opalis Remote Execution Service • Opalis Action Server Watchdog

  40. Orchestrator Architecture

  41. Migration Paths • Not Supported • Opalis Robot Policies (all versions) • Opalis Integration Server Policies (all versions 5.2 and earlier) • In-Place Upgrades • Supported (Export/Import of Policies) • Opalis Integration Server Policies (versions: 5.3, 5.4, 5.45, 5.5, 5.51, 5.52,5.6, 5.6.1, 5.6.2, 6.0, or 6.2) • Opalis Integration Server 6.3 Policies

  42. Understanding what changed • You must rework… • Policies that are configured for Legacy Mode • No more Cycles • No more Multiple Starting Points • Policies that contain Legacy Objects • Good news is… • The migration path is straight forward • Nearly everything you have learned for OIS applies to Orchestrator!

  43. Migration Process Step 1: Install Orchestrator on a NEW Server Step 2: Export OIS 6.3 Policies Step 3: Import the OIS 6.3 Policies into Orchestrator Step 4: Re-work the Runbooks as necessary Replacing Step 5: Test the Runbooks in the NEW environment Legacy Objects Non-Updated IP Objects Unknown Objects

More Related