Self-Service Upgrade Instructions for Self-Hosted Customers
Review the following recommendations before you begin a self-service upgrade.
- Perform upgrades in a test environment and verify that workflows and integrations function correctly before upgrading production systems.
- Update servers to the latest supported prerequisites before upgrading. Verify supported versions, including .NET requirements.
- Review the upgrade documentation for standard installations before you begin.
- Back up the database and application folders on all application servers. This helps preserve customer-specific files such as
web.config. - For EMS Campus customers, back up the
queries.xmlfile used by EMS Campus Web Services. - Document application pool settings before upgrading because installers might modify the configuration.
- If you are skipping versions, install the latest build for each component version in sequence.
For detailed upgrade instructions, review the On-Premise upgrade documentation.
When to contact Professional Services
Consider engaging Professional Services for the following situations:
- Non-standard or customized environments.
- Large enterprise deployments with multiple servers.
- Deployments distributed across multiple geographic regions.
- Upgrades from older EMS versions.
Consider EMS Cloud Services
Migrating your on-premise installation to EMS Cloud Services removes the responsibility of performing upgrades and maintenance. Additional benefits include reducing administrative overhead, lowering operational costs, and providing access to the latest EMS updates.
Learn more about the benefits of EMS Cloud Services.
*For load-balanced environments, the notification and report services should only run on a single server to avoid duplicate notifications.