1. — Customer Success Team August / 2015 Remedyforce Enablement Kit Migration from CMDB 1.0 to 2.0

2. Value Enablement Kit Objective – The objective of the Remedyforce CMDB 2.0 Migration kit is to review & walk through the steps required to migrate from CMDB 1.0 to CMDB 2.0. – Intended audience for this enablement resource are Remedyforce Administrators – For additional CMDB guidance beyond the steps to migrate to CMDB 2.0, please review the Remedyforce Wiki and the web-based training course called Configuration Management

3. Overview CMDB 2.0 was first introduced in Remedyforce version Winter 14 In CMDB 2.0 all Configuration Items are saved in the Base Element object meaning the CMDB was flattened in Winter 14 The classes in CMDB are implemented as fields sets of the Base Element object and attributes are the fields

4. Why should we migrate to CMDB 2.0? CMDB 1.0 will be going end of life as of Winter 16 release which means: No further development from Remedyforce Product Management will be done on CMDB 1.0 No defects will be addressed going forward by the Remedyforce Engineering team There are a multitude of benefits to realize with migration to CMDB 2.0! Note: for more details on CMDB 2.0 introduced in Winter 14 - https://webapps.bmc.com/support/faces/az/prodversion.jsp?prodvers eqid=327890&ic=0 https://webapps.bmc.com/support/faces/az/prodversion.jsp?prodvers eqid=327890&ic=0

5. Advantages of CMDB 2.0 The flattened structure of CMDB 2.0 provides the following benefits: Less storage space is required to store a CI record Import and export of data is much faster Adding custom fields to a CI is much easier Reports can be created which access more than a single CI type Any field of any CI type can be tracked which makes auditing tasks much easier Any field of any CI type can be searched CMDB 1.0 search was restricted to the field of either BE or Business Services Fields shown on the General and Specification tabs within the CI instance editor can be customized New Pentaho packages were introduced to allow for importing data from other products (appended with 2.0)

6. What version of CMDB do I have? To determine if you have upgraded to CMDB 2.0 (or find out if you are already on CMDB 2.0), you can do the following: 1. Navigate to Remedyforce Administration > Application Settings. 2. The first item listed (if you’re still on CMDB 1.0) will be “CMDB 2.0 Upgrade”. Note – refer to speaker note below for additional comments on this

7. — Planning for migration Items to consider

8. Do some planning first Plan the upgrade date We recommend a weekend or a holiday as the process could take a couple of hours depending on how many records are in the CMDB Prepare for the upgrade Back up your data in your Salesforce ORG Assign the Remedyforce Administrator permission set to your User record or update the field-level security permissions of the Base Element fields for your profile. Disable any scheduled import jobs (if you have any) until CMDB 2.0 is upgraded.

9. Do some planning first…. Inform your users about the planned schedule of your CMDB 2.0 upgrade so that your users do not create, update, or link a CI record or import records during the upgrade. After you start upgrading to CMDB 2.0, your CMDB is locked and all the data added or updated during the upgrade is lost. And, if BMC FootPrints Asset Core integration is enabled, do not link or unlink a record. Make preparations based on customizations in your CMDB

10. Customizations Customization If you have marked custom fields as required in CMDB classes (objects)… If you have more than 500 custom fields.. If you have added custom values to out-of-the-box Picklist-type fields.. If you have set default values to custom Picklist-type fields or updated the default value of out- of-the-box Picklist-type fields.. If you have created a Master-Detail Relationship where a CMDB object (except BMC Base Element) is a master. Action Prepare a list of such fields so when you add these fields to the Base Element object, do NOT mark them as Required. Confirm you want all those 500 fields! Add these custom values to these Picklist-type fields manually. Prepare of list of the fields and default values. Prepare a list of those fields.

11. — Migration Walk through Let’s see the steps!

12. Before we get started… When you first select to upgrade to CMDB 2.0, you’ll see the overview and ability to view Help…so now let’s get started!

13. CMDB 2.0 Migration Steps Navigate to CMDB 2.0 Upgrade Run the CMDB Scan

14. Run the CMDB scan

15. CMDB Scan Report Sample report output

16. Add Custom Attributes to Base Element

17. Add Custom Attributes to Base Element automatically

18. Migrate Data

19. Switch to CMDB 2.0

20. Delete CMDB 1.0 Data

21. Close CMDB 2.0 Upgrade tab

22. — Additional Information Pentaho packages

23. Existing Pentaho packages based on Staging object execution model Pentaho packages executing with Staging object as end point CMDB Staging Object Base Element Object 1 Object 2 Object N Based on Class Hierarchy, records are split and created in multiple objects of CMDB Trigger on Staging Current Pentaho Packages for CMDB for 1.0

24. Pentaho pkgs. - Updated Model for CMDB 2.0 Existing Pentaho packages based on Staging object execution model with CMDB 2.0 Pentaho packages executing with Staging object as end point CMDB Staging Object Base Element Object 1 Object 2 Object N Based on Class Hierarchy, records are split and created in multiple objects of CMDB Trigger on Staging CMDB 2.0 enabled? No Yes Base Element Data gets auto- mapped to attributes in Base Element object only

25. — Thank You — Bring IT to Life. ™