Release notes for System Center Orchestrator
This article provides the release notes for System Center 2022 - Orchestrator.
Orchestrator 2022 release notes
The Orchestrator 2022 release includes all issues fixed till Orchestrator 2019 UR3.
The following are the known issues and workarounds in System Center 2022 - Orchestrator.
Known Issues and Workarounds
Orchestrator Web console is not compatible with Internet Explorer
Work around: Open the Orchestrator web console with Microsoft Edge or other modern browsers. The new console does not depend on Silverlight.
Orchestration Console navigation pane does not render properly when deeply nested
Description:Deeply nested Runbooks don't render correctly because the text overflows the width of the pane.
Workaround: None
Runbooks that are not inside any folder (root runbooks) are not shown on the navigation pane
Workaround: Move root runbooks to a folder
Job form requires output parameter also
Workaround: Use any string as value, it will be overwritten by the runbook execution with the output.
Orchestrator Remoting Service and Runbook Server Monitor Service don’t exit cleanly
Description: The oremoting and omonitor service cannot be stopped using Service kill.
Work around: Kill the service process manually using Task Manager or by using the following command:
taskkill /f /pid {pid of the service}
Service Manager connector does not work with new Web API
Description: Service Manager (SM) console does not detect orchestrator 2022 installation, because the Connector for the new Web API is yet to be released.
Workaround: Install the Orchestrator 2019 Web features on the computer alongside Orchestrator 2022. Ensure to configure the Orchestrator 2022 database in the 2019 Web features. The SM connector can monitor Orchestrator 2022 with Orchestrator 2019 Web service.
This article provides the release notes for System Center 2019 - Orchestrator.
Orchestrator 2019 release notes
The following is the known issue in System Center 2019- Orchestrator.
- For issues fixed in Orchestrator UR1, see the KB article
- For issues fixed in Orchestrator UR2, see the KB article
Orchestrator Web Console is not compatible with the Microsoft Edge web browser
Description: You cannot open the Orchestrator web console with the Microsoft Edge web browser.
Work around: Open the Orchestrator web console with Internet Explorer.
Important
This version of Orchestrator has reached the end of support, we recommend you to upgrade to Orchestrator 2022.
This article provides the release notes for System Center 1807 - Orchestrator.
Release notes for System Center 1807 - Orchestrator
This release of System Center Orchestrator contains all the bug fixes shipped until the Update Rollup 5 of Orchestrator 2016.
To learn more about the bugs fixed, and the installation instructions for Orchestrator 1807, see KB article 4135040.
Important
This version of Orchestrator has reached the end of support, we recommend you to upgrade to Orchestrator 2022.
This article provides the release notes for System Center 1801 - Orchestrator.
This article lists the release notes for System Center 2016 - Orchestrator.
Release notes for System Center 1801 - Orchestrator
The following is the known issues observed in System Center 1801- Orchestrator.
Orchestrator Web Console is not compatible with the Microsoft Edge web browser
Description: You cannot open the Orchestrator web console with the Microsoft Edge web browser.
Work around: Open the Orchestrator web console with Internet Explorer.
Release Notes for System Center 2016 - Orchestrator
The following sections list the known issues and workarounds that apply to System Center 2016 -Orchestrator.
Orchestrator Web Console is not compatible with the Microsoft Edge web browser
Description: You cannot open the Orchestrator web console with the Microsoft Edge web browser.
Work around: Open the Orchestrator web console with Internet Explorer.
Orchestrator - Runbook Designer's About Page shows the version as System Center 2016 Technical Preview
Description: In the Runbook Designer when you click on Help -> About, the version is shown as System Center 2016 Technical Preview.
Work around: You can validate that you have latest version using the version number. If you have the RTM version, the build numbers are as follows:
- Runbook Designer - 7.3.149.0
- Management Server - 7.3.149.0
When you apply Update Rollup 1 (GA update), the build numbers are as follows:
- Runbook Designer - 7.3.149.0
- Management Server - 7.3.164.0