You're reading from Microsoft System Center 2016 Service Manager Cookbook Discover over 100 practical recipes to help you master the art of IT service management for your organization

Product type Paperback

Published in Feb 2017

Publisher Packt

ISBN-13 9781786464897

Length 638 pages

Edition 2nd Edition

Tools

Microsoft System Center Configuration Manager

Concepts

IT Service Management

Authors (5):

Steve Buchanan

Anders Asp

Steve Beaumont

Dieter Gasser

Andreas Baumgarten

+1 more

View More author details

Table of Contents (16) Chapters

Preface

1. ITSM and ITIL Frameworks and Processes FREE CHAPTER

2. Personalizing SCSM 2016 Administration

3. Configuring Service Level Agreements (SLAs)

4. Building the Configuration Management Database (CMDB)

5. Deploying Service Request Fulfilment

6. Deploying and Configuring the HTML5 Self-Service Portal

7. Working with Incident and Problem Management

8. Designing and Configuring Change Management and Release Management

9. Implementing Security Roles

10. Working with the Data Warehouse and Reporting

11. Extending SCSM with Advanced Personalization

12. Automating Service Manager 2016

13. Whats New in SCSM 2016 and Upgrading from SCSM 2012 R2

A. Community Extensions and Third-Party Commercial SCSM Solutions

B. Useful Websites and Community Resources

Upgrading to Service Manager 2016

In this recipe, we will walk you through the steps of upgrading your environment from Service Manager 2012 R2 to Service Manager 2016.

Getting ready

Before performing an upgrade to Service Manager 2016, please make sure that you have carefully read the previous recipe, Preparing for Service Manager 2016, and that you have met all the requirements.

Before you start the upgrade, we recommend that you back up your Service Manager database, your Service Manager Data Warehouse databases, your reporting databases, and your encryption keys.

Due to the move to the .NET Framework 4.5.1 and changes to the SDK, the upgrade to Service Manager 2016 may break the custom solutions made in house or by third party (non-Microsoft), as discussed in the previous chapter. Make sure you have all new versions at hand before doing the upgrade.