Orchestrator 2025 Security Credentials Problem
Hi, I’m experiencing an issue in SCO 2025 that has occurred across three different installations. In the Text File Management and File Management IPs, I’m unable to save the security credentials information for the activities. In other activities, such as Get Service Status, it works as expected. If I enter the account information, click Finish, and then reopen the properties, the fields are empty. As a result, the activity runs using the service account specified for the Orchestrator Runbook Service. Has anyone else experienced the same issue, or could there be something wrong with my installations? Get file status: Get service status:All Clients Showing with Question Mark in MECM Console - ResourceID Issue
All of a sudden (2 weeks ago) all my MECM Clients (~ 4000) in MECM 2409 are showing with a question mark (?) in the console and no values in Last Online Time, Last Activity or HeartBeatDDR. Upon investigation in the statesy.log file on our single site server we see the following message for all clients: SQL MESSAGE: dbo.spProcessStateReport - The record for machine MYCLIENT (GUID:CF5413C8-1DA7-450D-9243-33DB539DE8FF) was not found in the database. SMS_STATE_SYSTEM 24/09/2025 10:36:45 15356 (0x3BFC) We then ran MS SQL profiler and see that this external CLR stored proceedure checks for the existince of the client in the SQL view vLocalSystemIDXRef. This view is defined as follows: create view [dbo].[vLocalSystemIDXRef] as select MachineID, GUID from MachineIdGroupXRef where ArchitectureKey=5 and MachineID between dbo.fnGetSiteRangeStart() and dbo.fnGetSiteRangeEnd() The issue is that all clients are actually in the underlying table MachineIdGroupXRef but due to the filter dbo.fnGetSiteRangeStart() and dbo.fnGetSiteRangeEnd() they are not part of the view. The reason is their ResourceID is only 4 digits and the value returend from fnGetSiteRangeStart is 16777216. Q: How could the clients be getting this 4-digit resourceID all of a sudden? We have made no chnagesto MECM (no upgrades, DB restores etc. ).System Center 2022 Update Rollup 3
We’re pleased to announce Update Rollup 3 (UR3) for System Center 2022. This release continues our commitment to stability, security, and platform currency across on‑premises datacenter operations, with targeted fixes and compatibility improvements for Operations Manager, Service Manager, Virtual Machine Manager, and Orchestrator. Details below. Virtual Machine Manager Support for additional Guest OSes & UX improvements Added Windows Server 2025 guest OS support Expanded Linux guest OS coverage: Ubuntu 24.04, RHEL 9, Debian 12, Rocky Linux 8 & 9. Availability Sets are now listed alphabetically to streamline selection. Storage provider security hardening Secure‑by‑default: Adding new storage providers now uses HTTPS by default. Learn more: Update Rollup 3 for System Center 2022 Virtual Machine Manager. Operations Manager Operations & Web Console are more stable since multiple issues are fixed such as console crashes, dashboard performance, favorite report issue. Addressed failures in workflows that use WMIProbe, ensuring the probe correctly falls back and executes. Restored Microsoft Teams notification functionality for environments impacted after UR2. Learn more: Update Rollup 3 for System Center 2022 Operations Manager. Service Manager Platform Stability on New CPUs/OS Builds Eliminated MonitoringHost instability observed on newer processors/OS builds and addressed a GroupCalc‑related crash scenario. Multiple Bug fixes on Self‑Service Portal & Knowledge Article Rendering Note: UR3 can be applied even where UR2 installation had failed, and it includes the bug fixes and enhancements that shipped with UR2. Learn more: Update Rollup 3 for System Center 2022 Service Manager. Orchestrator Platform Updates .NET 8 (LTSC) is now supported. Group Managed Service Accounts (gMSA) are supported. Security improvements Support for TLS 1.3 protocol is enabled. Learn more about bugs fixes: Update Rollup 3 for System Center 2022 Orchestrator We are committed to delivering new features and quality updates with UR releases at regular cadence. For any feedback and queries, you can reach us at systemcenterfeedback@microsoft.com.
SCSM 2025 installation failure - _PopulateUserRoles
Let me lay out the full picture first. Windows Server 2025, Remote SQL Server 2022 CU 20 FCI (used for internal reasons, but I also tried using Always On and encountered the same error), and a clean installation of SCSM 2025 Management Server. I also tried CU19, but the same issue occurs. The installation starts without any problems. It goes through all the steps: creates the database, configures registry settings, configures the server, installs services, and imports management packs. But right after that, I get the following error: _"An error occurred while executing a custom action: PopulateUserRoles This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system. Once the corrections are made, you can retry the upgrade for this role." Immediately after this, the Event Viewer logs the following Event ID 36882: "The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. The SSPI client process is rundll32 (PID: 5084).” SQL does not require encryption and is not using any custom certificate. Just to clarify, the internal CA certificate is installed on all servers. The event is weird because, at this point, the installation has already created and configured the database. It doesn’t make sense to me, but the event appears at the exact same moment the installation fails. I’ve already checked permissions on both SQL and SCSM. The service account is a local administrator, has "Log on as a service" rights, and is a sysadmin on SQL. I’ve searched everywhere online but haven’t found a solution... Any ideas? Thanks.
