Blog Post

System Center Blog
3 MIN READ

System Center 2022 Update Rollup 2

Karthik_KR07's avatar
Karthik_KR07
Icon for Microsoft rankMicrosoft
Nov 13, 2023
We are delighted to announce the release of Update Rollup 2 for System Center 2022. This Update Rollup comes with enhancements to manage the on-prem datacenters and to aid the cloud migration journey...
Updated Nov 21, 2023
Version 7.0
DPM
SCOM
System Center
System Center Data Protection Manager
System Center Operations Manager
System Center Orchestrator
System Center Service Manager
System Center Virtual Machine Manager
VMM
DavidB2390's avatar
DavidB2390
Copper Contributor
Nov 21, 2023

I can't get Service Manager 2022 to trigger runbooks on Orchestrator 2022 with both 2019 and 2022 Orchestrator API services installed on different ports (as per the known issues advice). In SCSM the orchestrator connector tests ok and I can access from a web browser on the scsm server:

https://orch.domain.com/Orchestrator2012/Orchestrator.svc/Runbooks, after logging on I see runbook entry records.
<entry m:etag="W/&quot;datetime'2016-04-14T13%3A44%3A57'&quot;">
<id>https://orch.domain.com/Orchestrator2012/Orchestrator.svc/Runbooks(guid'1a289417-fe7c-4a87-95b7-3fb5f10ac777')</id>
<title type="text">Runbook test 1</title>

 

So the 2019 API is functional but it appears that the Orchestrator 2022 instance won't trigger the runbook. Is this a known issue? Unless any suggestions I'll probably revert to the working 2019 version of both products and wait for UR3.