Unable to update Service request via SCO runbook
Good afternoon, Everyone, I’ve started developing a series of runbooks for our new service desk implementation, and one of the key requirements is the ability to automatically update Service Requests and other work items during the workflow. However, I’m running into an issue when attempting to pass the GUID of the Service Request into the “Update Object” activity. Even though the GUID is successfully retrieved from the Service Request and passed into the runbook as an input parameter, the activity reports that the value is an invalid GUID. This suggests that either the GUID is being transformed somewhere in the process, isn’t being interpreted correctly by the activity, or the wrong property is being supplied even though the value appears correct when inspected within the runbook. At this stage, I’m trying to determine whether the issue is caused by the way SCSM exposes the GUID, how the runbook passes the parameter, or a limitation quirk within the Update Object activity itself. Any guidance or examples of correctly updating Service Requests via runbooks especially when using GUID values dynamically would be greatly appreciated.
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:
果博东方开户+威a3322148
DPM 2019, using SQL 2019 on a 2019 server. The server was doing a consistency check on a file server. The check lasted about 33 hours and the items scanned showed over 4 million. There is no way a server could have 1 million files and folders, let alone 4 million. Does anyone know why the number of items scanned would be so high?
System Center Orchestrator - OS Upgrade
Hello community, I am asking for your help to see how we can do an OS upgrade of our System Center Orchestrator infrastructure. We have our System Center Orchestrator 2019 infrastructure on Windows Server 2016. I would like to upgrade to Windows Server 2022. What is the best way to do this? I would like to use new servers and not do an in-place upgrade. What would be the procedure? Is SCORCH 2019 supported on 2022? I don't see it in the documentation. Thank you very much!!
Issue map prompts to properties
Hi, I am trying to create a new user account runbook so it can be used in the Self Service Portal. I start my runbook with an initialization of data and the following details: I have created my Service Request template and my Runbook automation activity template. In my Request Offering, I can map LastName, FirstName, etc., but I am not able to map Branch. What could be the issue? I need to know in which branch they work and I want it to be a simple list so they can choose from it. Please let me know if more information is required. Thanks for the help 🙂System Center Orchestrator 2022 Web Console Issues
This is more for information for others that have experienced the issues I have with System Center Orchestrator 2022 and the Web Console. Issues Discussed: Runbooks not visible in the Web Console Cannot remove stale runbook server entries Runbooks checked out in Web Console Issue 1: Runbooks not visible in the Web Console. In this issue the left hand pane where the runbook structure should be populated is blank. Solution 1: Ran this query on the Orchestrator DB GRANT CONTROL ON ASYMMETRIC KEY::[ORCHESTRATOR_ASYM_KEY] TO [Microsoft.SystemCenter.Orchestrator.Admins] GRANT CONTROL ON SYMMETRIC KEY::[ORCHESTRATOR_SYM_KEY] TO [Microsoft.SystemCenter.Orchestrator.Admins] GRANT EXECUTE ON object::[Microsoft.SystemCenter.Orchestrator].[GetSecurityToken] TO [Microsoft.SystemCenter.Orchestrator.Operators] GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators] GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[AuthorizationCache] TO [Microsoft.SystemCenter.Orchestrator.Admins] Issue 2: Unable to delete stale or orphaned runbook server instances I decommissioned some older runbook servers but was unable to delete them from any of the orchestrator consoles. Solution: Run these sql queries against the orchestartor database DELETE FROM [Orchestrator].[dbo].[CLIENTCONNECTIONS] WHERE [ClientMachine] = 'SCORCHRB' -- Here SCORCHRB is my Runbook Server Name. DELETE FROM [Orchestrator].[dbo].[ACTIONSERVERS] WHERE [Computer] = 'SCORCHRBServer' -- Here SCORCHRBServer is my Runbook Server Name. DELETE FROM dbo.OBJECTS where Name = ‘SCORCHRBServer’ -- Here SCORCHRBServer is my Runbook Server Name. Issue 3: Runbooks remain in the checked out state in the web console I have run into an issue where no matter how many times i check in a runbook, the runbook in the web console remains checked out. Solution 3: Run this sql query against the orchestrator database use Orchestrator GO Truncate table [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache DECLARE @secToken INT DECLARE tokenCursor CURSOR FOR SELECT Id FROM [Microsoft.SystemCenter.Orchestrator.Internal].SecurityTokens where ExpirationTime >= GETUTCDATE() OPEN tokenCursor FETCH NEXT FROM tokenCursor INTO @secToken WHILE @@FETCH_STATUS = 0 BEGIN PRINT 'Computing Authorization Cache for Security Token: ' + Convert(Nvarchar, @secToken) exec [Microsoft.SystemCenter.Orchestrator].ComputeAuthorizationCache @TokenId = @secToken FETCH NEXT FROM tokenCursor INTO @secToken END CLOSE tokenCursor DEALLOCATE tokenCursorSCO: The Runbook Server was unable to publish the runbook with unique identifier
Have this in my System Center Orchestrator Runbook Events: The Runbook Server was unable to publish the runbook with unique identifier '{GUID}' However, no effects are visible, but error messages are rarely good.. Any idea?
SCOR - SharePoint Integration Pack - Get View Items
We're trying to use the Get View Items but when we run it it's pulling out the full list items instead. We have: Get List Items List Name: IAF_Form_List List View: Old Forms This then reads 116 entries rather than the 20 it should. Is there something we're doing wrong here or is it broken? Using Orchestrator 2019.Service Manager 2019 updates? Orchestrator?
Hello, I was wondering when or IF there will be any new updates like a UR3 for SCSM. I can really find no documentation on upgrade paths or release date or even a TBD. Just trying to find out if SCSM is dead or not. If not when will the next update get released since SCOM update got recently released? I do not want to have my system center running a different version of updates. Also, what about Orchestrator? Something else I can limited information on. When is that getting an update?
