MadCap Flare Knowledge base
Single-source knowledge base created in MadCap Flare, using sample topics.
Search is based on keyword.
Ex: "Procedures"
Do not search with natural language
Ex: "How do I write a new procedure?"
Upgrading your system
- 13:57:20
- Upgrading
- 5 Comments
- 15
- 1120
Knowledge base feature article using MadCap Flare
This is the only supported upgrade path to System 2017. If you are using 2012 Service Pack 1 (SP1), you must upgrade to System 2012 R2 using Update Roll up 9.
This article assumes you are performing an upgrade to System 2017. For information on installing the System on an environment where no previous version exists, see Installation and Deployment.
Upgrade Prerequisites
Before upgrading to System 2017 you must determine if all servers contained in your management group meet the minimum supported configurations.
If your System 2012 R2 management group integrates with the Management Suite (MS), all configuration settings are retained and the system will continue to function as normal once the upgrade is complete.
There are three upgrade deployment options:
1. Single-server
If upgrading on a single-server, you only need to run the upgrade once as all features are installed on a single server. The upgrade wizard performs system prerequisite checks and provides resolution steps for any issues. Installation will not continue until all issues are resolved.
2. Distracted Management Group
If upgrading a distributed management group, required components must be upgraded in the following order: management servers, gateways, operations consoles, and agents. You can then upgrade all remaining components, such as the web console, reporting and Audit Collection Services (ACS) in any order.
3. Maintained Environment
If you need to maintain your OS 2012 R2 environment you can install System 2017 in parallel.