This morning I updated PowerShell Universal from version 5.2.1 to 5.5.2.
The update resolved an issue we previously had with running scripts using a Group Managed Service Account (gMSA) — that part is now working correctly.
However, we’ve encountered a new issue:
When running a script that uses a gmsa credential without specifying a target server, the job ends up stuck in an endless queue.
If I explicitly select a server, the script runs as expected.
It seems that other scripts now also need a specific server selection. Because when I don’t do it they all end up in a queue. I have scripts running on schedule that suddenly don’t work.
This started when i put the service account as Local System
I would like to revive this ticket because it is causing some issues while trying to migrate from Microsoft SMA to PSU.
We have multiple inhouse module that now need to refer to PSU instead of SMA but when we want a certain script to be ran we wan’t it to be able to dynamically choose a server. yet when we don’t specify a specific server to be run on the script ends up in a seemingly endless queueu.
