Troubleshooting Error “File… is not digitally signed… see about_Exectin_Policies…” in ControlUp

The user was running an Analyze Logon Duration script against two different VDI environments but was receiving an error message relating to the execution policy not being set correctly with the W2K12 PVS. Modifying the GPO was explored but it was ultimately discovered that the script was incorrectly signed because of a space being added at the end of the file. Suggestions were made to double-check scripts if modified by colleagues. ControlUp SBAs and an update to W2K19 were also mentioned.

Read the entire ‘Troubleshooting ControlUp Scripts Signed with Incorrect Policy’ thread below:

Hello, I have 2 sets of VDIs, W2k12 shared PVS servers and W10 MCS persistent.

I am running the "Analyze logon duration" script against a user who is connected to both environments.

The script is signed.

It’s returning the very valuable information from the MCS, but fails against the W2K12 PVS with a "File… is not digitally signed… see about_Exectin_Policies…" error message.

I understand that I should modifiy the execution policy but not sure how to do it.

Thanks in advance

If it has been set on system level, good chance it is in a GPO, so that would mean changing the GPO for those servers and that is probably not something you want to do. Can’t change it through a script because it will not run scripts that are not signed, and GPO setting should override that anyway.

I think the best option you have is to see if you can sign the script yourself. I thought there was an article on that somewhere in the ControlUp docs, can’t find it atm. Iirc @member has done some script signing in ControlUp SBAs?

sorry, I haven’t

and there’s a good chance that more and more scripts will start failing at 2k12 as it’s been unsupported for such a long time nowThanks @member, but I forgot to mention that the script is signed (original message modified).

I am double checking the GPOs…

@member the update to W2k19 is in the pipe 😉

I checked the GPO and it’s "Allow only signed script".

Again, my script is signed.Does the W2k12 machine have an older agent? And when you say your script is signed, you modified the script to add the signature block I assume?

I have to be honest to say that I found the problem, the script I used to sign the ControlUp scripts was eating a space at the end of the file, hence the bad signature. Lesson learned, do not use scripts from colleagues without double checking them 😉

Continue reading and comment on the thread ‘Troubleshooting Error “File… is not digitally signed… see about_Exectin_Policies…” in ControlUp’.  Not a member? Join Here!