SCCM Orchestration Initial Setup with Activities not connecting and giving authentication errorsIssue Upon setting up the initial environment for SCCM Activities in Orchestration, you may come across some issues when attempting to use the Activity Designer. Mainly when testing the inputs on the Get Activities (Applications/Collections). You may find that if you test the inputs several times, you could get a success, but for the most part, the test inputs will fail. A typical error that you might see will look like this: <error>New-PSSession : [XXXXXX.net] Connecting to remote server XXXXXX.net failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1 + New-PSSession -ComputerName XXXXXX.net -Credent ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed</error><error>Authentication failure with the user XXXX\XXXX</error><debug_info>2020-11-16 12:16:19 Tried Credential: name=SCCM automation, affinity: no, status=failed, sysid=XXXXXXXXXXX, username=XXXX\XXXX, type=Windows, order=40 2020-11-16 12:16:26 Tried Credential: name=YYYYY\YYYYY, affinity: no, status=failed, sysid=XXXXXXXXX, username=YYYYY\YYYYY, type=Windows, order=100 </debug_info> The main reason for this article is that even though there are a few KBs out there, they can be difficult to find, and adding an additional one will be helfpful. ReleaseAny and ALLCauseIt seems that the main cause for the authentication errors is due to having multiple SMS Providers, creating a lag in the query, causing it to fail. This article assumes that the credentialled user can connect from the mid server to the SCCM Server and execute Powershell.Resolution1.To resolve the connectivity, issue, please refer to following KB: https://support.servicenow.com/kb_view.do?sysparm_article=KB0831952 It explains how WSManCredSSP must be enabled on the mid server and the SCCM Server to resolve the issue. A Microsoft Article is also mentioned with the commands to enable WSManCredSSP. Essentially you need to enable this, and modify ecc_agent_script_file SCCM.psm1, and Credentials.psm1 t include using WSManCredSSP for authentication. 2. Additionally there are some queries that still have issues. One that was noticed was Get-Device. There are some additional environmental settings for WSManCredSSP, that may need to to be implemented if you are having issues with particular queries after implementing the use of it. This particular article is for Get-Device: https://support.servicenow.com/kb_view.do?sysparm_article=KB0829919