Deployment Failed on Verify Cubes - Creation of a New Shell Failed

A product deployment from Tyler Deploy fails on Verify Cubes.

The deployment log shows: Error checking remote session!

Connecting to remote server xxxx failed with the following error message : The creation of a new Shell failed. Verify that the RunAsPassword value is correctly configured and that the Group Policy setting "Disallow WinRM from storing RunAs credentials" is Disabled or Not Configured. To enable WinRM to store RunAs credentials, change this Group Policy setting to Disabled. For more information, see the about_Remote_Troubleshooting Help topic.

INVALID Remote Session: Could not establish remote session on <servername> as city\tylerservice

On the product deployment page, it gives the error: Unable to initialize remote session on xxxx as tylerservice. Please check user permissions for tylerservice and run ‘Unregister-PSSessionConfiguration -Name’ in a PowerShell window

• Verify Cubes
• INVALID Remote Session
• Munis ERP
• Tyler Deploy

There is already a Windows remote session established on the database sever that needs to be removed.

1. Log into the database server specified in the failure with tylerservice or an account with admin access
2. Open PowerShell as an administrator and run the following command:
   Unregister-PSSessionConfiguration -Name tylerservice
3. If command completes without any warnings, re-run the Munis ERP deployment from Tyler Deploy, or run just the Cubes task
   
   1. Navigate to the Munis ERP Product Deployment page
   2. Select the Tasks tab
   3. Select Cubes from the dropdown
   4. Click Run
4. If the command returns: No session configuration matches criteria "tylerservice", or the deployment continues to fail, go back to the sever and open Services
   1. Locate Windows Remote Management (WS-Management)
   2. Right click service name > click Restart
5. Re-run the deployment from Tyler Deploy, or re-run the Cubes task
6. If issue persists, please contact Tyler Systems Management Support or log a case via the Online Support Client Portal.