Upload
mervin-carson
View
217
Download
0
Tags:
Embed Size (px)
Citation preview
Opalis to Orchestrator and Microsoft System Center Service Manager 2010 to 2012Eamon O’Reilly & Ranganathan SrikanthMicrosoft Corporation
MGT325
Agenda
What’s new in System Center
2012SM 10 -> SM
2012Opalis 6.3 -> Orchestrator 2012
Better together
Learn new capabilities
Incorporate best practices
Key Takeaways
Self-Service
Service Delivery
and Automation
System Center Helps Deliver IT as a Service
Deploy
Configure
Service Model
DC Admin
Operate
Monitor
Virtual
Physical
Public Cloud
Private Cloud
Virtual Machine Manager
Operations Manager
App Controller
Service Manager Service Manager
Orchestrator
Configuration Manager
Data Protection Manager
AppOwner
Application ManagementService Delivery and
AutomationInfrastructure Management
Configure and Deploy Service Delivery and Automation
STANDARDIZATION SELF-SERVICE AUTOMATION
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.
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).
SM10 -> SM2012
Session Objectives and Takeaways
Session Objective(s): Planning considerations and process to upgrade from Service Manager 2010 to Service Manager 2012Share upgrade best practicesDemonstrate in-place upgrade of SM 2012Demonstrate a pre-req checking tool
Takeaway(s)You can upgrade successfully with minimal downtimeMany customers have successfully upgraded to productionUpgrade guides provide step-by-step instructions
WHY UPGRADE?Perf & Scale improvements
Perf improvementsMinimum of 25-30% faster than SM 2010 SP1Create, Delete Incident, Folders, templates – 80% fasterMore responsive and snappier experiences for common operations
Viewing incidents, computersSearching KA
Scale improvementsUp to 80 analyst consoles / server
WHY UPGRADE?Updates to key features
Support for Parallel activities in Change ManagementSupport for Parent-Child relationships in incidentsSupport for Duplicating TemplatesSupport for Periodic NotificationsAdvanced Reporting capabilities / AnalyticsConnector upgradesPowerShell enhancementsShortcut keys
WHY UPGRADE?New investments
• Service Request with SharePoint 2010 integration
• Cloud Services Management Pack for Private Cloud
New solutions
• SCVMM & SCO connectors for SM• SCOM & SCCM connectors for DW
New Connector
s
• Service Catalog• Service Level Objectives
New features
UPGRADE PREPARATION
Pre-requisite changesSKUs, License Key changesSupported upgrade scenarios/pathsSM & OM compatibilityIntegration with partner/in-house solutions
HARDWARE PRE-REQS
Unchanged from SM 2010
SOFTWARE PRE-REQS
OS SUPPORTConsole
XP is not a supported OS for ConsolesWorkarounds
Terminal Services
BROWSER SUPPORTPortal
Firefox is not a supported portal client
SOFTWARE PRE-REQ CHANGESManagement Servers
OS requirementsW2K8 R2 SP1
Other componentsSQL Native clientSQL Server 2008 Analysis Management ObjectsSQL Server 2008 Analysis Data ObjectsPowerShell 2.0
SOFTWARE PRE-REQ CHANGESPortal, Reporting components
PortalSharePoint 2010NET 4.0Silverlight 4.0 (required only on the client)IE 8, 9 (required only on the client)
SQL Server 2008 Analysis ServicesStandard edition supportedEnterprise edition provides better usability, scale, performance and cube maintenance
UPGRADE PREPARATION
Pre-req changesSKUs, License Key changesSupported upgrade scenarios / pathsSM & OM compatibilityIntegration with partner/in-house solutions
SKUs, LICENSE KEYsRTM release
Current SKU Upgraded SKU Status
SM 2010 SP1 CU3 Eval SM 2012 RTM Eval Eval duration unchanged
SM 2010 SP1 CU3 Select SM 2012 RTM Select Licensed
SM 2010 SP1 CU3 Retail SM 2012 RTM Select Licensed
SM 2012 RC Eval SM 2012 RTM Eval Eval duration unchanged
SM 2012 RC Eval SM 2012 RTM Select Licensed
License keys needed to upgrade to a licensed version.Eval to Licensed version (activation) is not supported
UPGRADE PREPARATION
Pre-req changesSKUs, License Key changesSupported upgrade scenarios / pathsCapacity planningSM & OM compatibilityIntegration with partner/in-house solutions
SUPPORTED UPGRADE SCENARIOS
In-place upgrades only
UN-SUPPORTED UPGRADE SCENARIOS
Rolling upgrades
POSSIBLE UPGRADE SCENARIOS
Side-by-Side upgradesUsing Orchestrator to keep instances in syncCustom implementationNo Out of the Box runbooks that deliver this scenario
UPGRADE PATHS
SM 2012 RTM
SM 2010 SP1 CU3
SM 2012 RC
*no upgrade for SM 2010 portal
UPGRADE PREPARATION
Pre-req changesSKUs, License Key changesSupported upgrade scenarios / pathsSM & OM compatibilityIntegration with partner/in-house solutions
SM & OM compatibility
OM 2007 R2 OM 2012
SM 2010 Agent based monitoring
Agentless monitoring only
SM 2012 Agent based monitoring
Agentless monitoring only
UPGRADE PREPARATION
Pre-req changesSKUs, License Key changesSupported upgrade scenarios / pathsSM & OM compatibilityIntegration with partner/in-house solutions
Upgrade best practices
Treat upgrade like any other projectMitigate risk
Create a sandbox environment to test upgradeThis cannot be over emphasized
Use production data in pre-prod environmentThis 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
Prepare a sandbox
environment
Extract production
data
Standup sandbox
environment
Upgrade to SM 2012
UPGRADE LIFECYCLE
PLAN FOR DR
Upgrades could run into non recoverable errorsSM topology can be complexDR plan is essential to restore state
DR Guide documents the steps required
Demo – SM 2010 to SM 2012
Srikanth RanganathanProgram ManagerSystem Center Service Manager
In-place Upgrade Service Manager 2010
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'.,
ERRORS DURING UPGRADE
You have to restore it to its original state using DR process
Demo – Pre-req tool
Srikanth RanganathanProgram ManagerSystem Center Service Manager
Remote pre-req tool
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 upgradedCustomer modified MPs are untouched
What happens to existing user roles, subscriptions and workflows?
User roles, subscriptions, and workflow continue to function unaffected
41
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 bitsCheck with the partner to verify in-place upgrade to SM 2012
2010 PortalSM 2010 Portal is not upgradable to SM 2012SM 2012 is SharePoint 2010 based
Customizations must be implemented in this framework42
In Review: Session Objectives and Takeaways
Session Objective(s): Planning considerations and process to upgrade from Service Manager 2010 to Service Manager 2012Share upgrade best practicesDemonstrate in-place upgrade of SM 2012Demonstrate a pre-req checking tool
Takeaway(s)You can upgrade successfully with minimal downtimeMany TAP customers have successfully upgraded to productionUpgrade guides provide step-by-step instructions
Opalis -> Orchestrator
Microsoft Confidential.
• Unified installer experience based on System Center best practices• REST based web service supporting OData to enable easy
management and reporting of the Orchestrator runtime environment
• Orchestration Console web portal for IT operators• Runbook Tester can step over the “Invoke Runbook” activity• Variables have an “Encrypted” option• “Invoke Runbook” now offers a security credentials
• Performance / Stress / Scale improvements• Globalization• Runtime accessibility support (Orchestration Console)• Security best practices• Common Engineering Criteria• Manageability (Operations Manager MP, Best Practices Analyzer)
System Center 2012 Orchestrator Improvements
Orchestrator Terminology
Opalis
PolicyObjectFoundation ObjectsOpalis ClientAction ServersAction ServiceTesting ConsoleOperator ConsoleOpalis Remote Execution ServiceOpalis Action Server Watchdog
Orchestrator
RunbookActivityStandard ActivitiesRunbook DesignerRunbook ServerRunbook ServiceRunbook TesterOrchestration ConsoleOrchestrator Run Program ServiceOrchestrator Runbook Server Monitor
Orchestrator Architecture
•Management service•Deployment Manager•Database configuration•Runbook server monitor
Management Server
•Runbook service•Policy Module•Standard Activities• IP components
Runbook Servers
•Designer•Runbook Tester•Policy Module•Standard Activities
Designers
•REST oData web service•Silverlight console
Web Features
Orchestrator Runbook Designer
Managementserver
Orchestrator web service
Server running Internet
Information Services (IIS)
Port 81: REST-based web service
Port 82: Orchestration console
Orchestration consolerunning in a browser
Runbook servers
Runbook Designer
Runbook Tester
Logs
Jobs
Runbooks
Orchestration database
Migration Paths
Not SupportedOpalis 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
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 forwardNearly everything you have learned for OIS applies to Orchestrator!
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 5:Test the Runbooks in the NEW environment
Legacy Objects
Non-Updated IP Objects
Unknown Objects
Step 4:Re-work the Runbooks as necessary R
epla
cing
Migration Process
Demo - Opalis to Orchestrator
Eamon O’ReillyProgram ManagerSystem Center Orchestrator
Migration Opalis policies to Orchestrator Runbooks
Integration Packs
OIS 6.3 Third-Party and System Center Integration Packs…
Have to conform to a new Encryption ModelWill not work in OrchestratorRequire UpdatingUpdated versions are new software for Orchestrator (and will not work in previous versions)
Orchestrator Integration Pack Activities REPLACE OIS 6.3 Integration Pack Objects
This goes for QIK-made Integration Packs as well
Opalis Quick Integration Kit
It has been replaced by the Orchestrator Integration Toolkit
All OIS 6.3 QIK-made Integration Packs and Objects will need to be updated
Update Process is simple, involving:Replace Reference DLL (from QIK to OIT)Find/Replace in the code (updating naming and references)Recompile DLLRecompile Integration Pack in the new Orchestrator IP Wizard
Better Together
SC2012 Service Manager & OrchestratorBetter Together
Orchestrator Connector for Service ManagerRunbook Activity templates
System Center 2012 Service Manager & Orchestrator – Better together
New update to the app has been released…
Need to apply the update on the server
Demo scenario
Understand the changes and
improvements in both products
Refactor runbooks & Leverage SM
templates to take advantage of new
capabilities
Key Takeaways
Service Manager & OrchestratorIntegrate human & machine processes
Resources
Connect. Share. Discuss.
http://northamerica.msteched.com
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Resources for Developers
http://microsoft.com/msdn
Complete an evaluation on CommNet and enter to win!
MS Tag
Scan the Tagto evaluate thissession now onmyTechEd Mobile
© 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.
Backup Slides
Opalis
Orchestrator 2012