Release notes for System Center Orchestrator
Important
Service Provider Foundation (SPF) is discontinued from System Center 2025. However, SPF 2022 will continue to work with System Center 2025 components.
This article provides the release notes for System Center 2025 - Orchestrator.
Orchestrator 2025 release notes
The following sections summarize the release notes for Orchestrator 2025, and include all issues fixed until Orchestrator 2022 UR2.
Additionally, the following issues are fixed:
- Send platform event activity is persisted to the database and is visible in Events tab of the Runbook Designer.
- Run SSH activity is fixed. Latest (at the time of release) plink.exe is included.
- Query database activity error Failed to load extension is fixed.
- Re-create Orchestrator keys by following the steps mentioned here.
- Activities persist custom separators while you configure Run behavior for the activity.
- GET api/ActivityInstances returns the expected value instead of empty result.
- Activity names are correctly displayed on the Runbook Tester canvas and log view area instead of identifiers.
- Jobs in active state are visible in Active Jobs in Web Console.
The following sections summarize the known issues and workarounds in System Center Orchestrator 2025:
Runbooks that aren't inside any folder (root runbooks) aren't 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 services can't be stopped using Service kill.
Workaround: Kill the service process manually using Task Manager or by using the following command:
taskkill /f /pid {pid of the service}
This article provides the release notes for System Center 2022 - Orchestrator.
Orchestrator 2022 UR2 release notes
The following sections summarize the release notes for Orchestrator 2022 UR2, and include the known issues and workarounds.
For the problems fixed in UR2 and the installation instructions for UR2, see the KB article.
'Send platform event' activity isn't persisted to the database
Description: Send platform event activity isn't persisted to the database and isn't visible in Events tab of the Runbook Designer.
Workaround: None
Identifiers are displayed instead of activity names on the Runbook Tester canvas and log view area
Description: Identifiers are displayed instead of Activity Names on the Runbook Tester canvas and Log View area. The Activity name is included as a property in the Log View area.
Workaround: If needed, Runbook tester of UR1 can be used, it is compatible with SCO UR2.
Text content does not show correctly in the Runbook Tester log view area
Description: Text content does not show correctly in the Runbook Tester log view area. Selecting the text will re-render it in the correct font that supports all scripts including GB18030-2022 character set.
Workaround: None
Service Manager connector doesn't work with new Web API
Description: Service Manager (SM) console doesn't 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.
Runbook designer crashes with some Integration packs
Description: With some integration packs, Runbook designer might crash when you update existing runbooks or create new runbooks.
Mitigation: Install the Hotfix for Orchestrator 2022 UR2 that fixes this issue.
Orchestrator 2022 UR1 release notes
The following sections summarize the release notes for Orchestrator 2022 UR1, and include the known issues and workarounds.
For the problems fixed in UR1 and the installation instructions for UR2, see the KB article.
'Send platform event' activity isn't persisted to the database
Description: Send platform event activity isn't persisted to the database and isn't visible in Events tab of the Runbook Designer.
Workaround: None
Issues with Exchange Admin Integration pack v10.22.1.x
Description: Issues with Exchange Admin Integration pack v10.22.1.x
Workaround: Upgrade to SCO 2022 Exchange Admin Integration pack version 10.22.2.5 or later. For more details, refer blog announcement.
Orchestrator Web console doesn't work properly
Description: Web Console doesn't work properly if .NET Core 5 isn't installed.
Workaround: Install .NET Core 5.
Orchestrator Web console isn't compatible with Internet Explorer
Workaround: Open the Orchestrator web console with Microsoft Edge or other modern browsers. The new console doesn't depend on Silverlight.
Orchestration Console navigation pane doesn't 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 aren't inside any folder (root runbooks) aren't 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 services can't be stopped using Service kill.
Workaround: Kill the service process manually using Task Manager or by using the following command:
taskkill /f /pid {pid of the service}
Service Manager connector doesn't work with new Web API
Description: Service Manager (SM) console doesn't 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.
Orchestrator 2022 release notes
The Orchestrator 2022 release includes all issues fixed until Orchestrator 2019 UR3.
Note
System Center Orchestrator 2019 IPs aren't supported on System Center Orchestrator 2022.
This article provides the release notes for System Center 2019 - Orchestrator.
Orchestrator 2019 UR6 release notes
The following sections summarize the release notes for Orchestrator 2019 UR6, and include the known issues and workarounds.
For the problems fixed in UR6 and the installation instructions for UR6, see the KB article.
New Web console doesn't take zero (0) as the input parameter
Description: New web console doesn't take zero as the input parameter.
Workaround: Change the data type of input parameter to String.
Web Console requires third party cookies when opening console via localhost or FQDN
Description: Web Console requires third party cookies enabled when opening console via localhost or FQDN, but not with Netbios name.
Workaround: Add Allow 3rd party cookies to localhost and FQDN in Edge settings on all client machines.
Orchestrator 2019 release notes
The following are known issues in System Center 2019 - Orchestrator.
- See KB article #4533414 for issues fixed in Orchestrator UR1.
- See KB article #4569536 for issues fixed in Orchestrator UR2.
- See KB article #4599686 for issues fixed in Orchestrator UR3.
New Web API and Console (without Silverlight)
Follow the instructions in the announcement blog post to download and install the new components.
The new components can work alongside the original 2019 Web Service and Console.
Other known issues
Orchestrator Web Console isn't compatible with the Microsoft Edge web browser
Description: You can't open the Orchestrator web console with the Microsoft Edge web browser.
Workaround: Open the Orchestrator web console with Internet Explorer.
Tip
New version of the Web API and Orchestrator Console have been released that doesn't depend on Silverlight. Follow instructions in the announcement blog post to download and install them.
This article lists the release notes for System Center 2016 - Orchestrator.
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 isn't compatible with the Microsoft Edge web browser
Description: You can't open the Orchestrator web console with the Microsoft Edge web browser.
Workaround: 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 select Help -> About, the version is shown as System Center 2016 Technical Preview.
Workaround: You can validate that you've the latest version using the version number. If you've 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