WS1 SaaS Resources > Scripts does not work

[almostIT]

How is this not talked about more? I can't find a single working example of this feature and to me it seems this would be very useful for most admins. 

When I try to run even basic PowerShell commands against a Windows device with this it does not work. 

Additionally, devices > scripts shows me zero. I have no indication of why it does not work. 

Reddit user with the same issue, no solution: https://www.reddit.com/r/WorkspaceOne/comments/q8s5b1/scripting_in_ws1/

I've tried the suggestions in that post, but what is weird is that there is no indication anywhere if the script even ran or not. 

YouTube video showing the feature itself, but with no working example and comments turned off: https://www.youtube.com/watch?v=kNAZN0RpyV4

He never shows the success of the deployment, or any indication of such, it's just a GUI walkthrough. 

VMware's own, vague and very basic, documentation: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/Windows_Desktop_Device_Management/GUID-... 

Which again, is just a walkthrough. 

Am I going crazy here or is it just me? 

[almostIT]

I did add an exit code 0 to the script, but it made no difference. Per this little gem: https://techzone.vmware.com/getting-started-freestyle-orchestrator#scripts

[almostIT · Accepted solution]

Figured out the problem. 

I was using Windows Ent 1809 which is not supported by the current Intelligent Hub version. 

Updated to Windows 22H2 and the scripts worked. 

It is kind of interesting that the Intelligent Hub application has such a high OS requirement, considering there are a lot of features and configurations within WS1 for OLDER Windows versions, like 1809. 

Moral of the story. Use the latest OS of Windows, if possible, along with the latest Intelligent Hub version. Less problems. 

[EduardVila]

I don't think that the problem is related to endpoint version.

In my case, we have +150 devices running in 21H2 and 22H2. None of them report anything in Device > Scripts.

Of course, all are Corporate Dedicated.

We have tried assigning to root OG, Smart Group with the same result.

Opened a support case yesterday, waiting for initial response.