Forum Discussion
Help deploy a powershell script to install speculation module
Hi Harm_Veenstra ,
Even using the option "-Scope Currentuser" I see the following error in the log:
[PowerShell] User Id = c16a6a16-2f0d-4148-80be-8bf7cca6fbf2, Policy id = bc108d02-ac34-41c3-a072-e16b7f26b1ae, policy result = Failed
[PowerShell] Fail, the details are {"Version":1,"SigningCode":649,"SigningMsg":"(Success) AccountId:95fb4322-d2af-4011-af4b-e98b056b4560,PolicyId:bc108d02-ac34-41c3-a072-e16b7f26b1ae,Type:1,Enforce: Audit. OSVersion:10.0.19044,AgentVersion:1.50.203.0. ","ExecutionMsg":"Powershell execution has exceeded defined timeout."}
NOTE 1: The same script works manually on the workstation.
NOTE 2: The file (bc108d02-ac34-41c3-a072-e16b7f26b1ae.ps1) is successfully created on the workstation and after the timeout error it is automatically deleted.
Any ideas, is it possible to increase the timeout?
- Feb 06, 2022Hi
Just wondering but I guess because when using -scope currentuser, you have targeted the powershell script to run as the user or as system?
But how are you getting your results back? as it just outputs the results... I would try to convert it to a proactive remediation... so you could install the module in the detection part and in the remediation checking the results and if it gets back good results exit with 0.- elvys_marchonFeb 07, 2022Copper Contributor
Hi Rudy_Ooms_MVP ,
If I understand correctly, I'm doing what you recommend. I'll attach the log here, if you can take a look.
- Feb 05, 2022Perhaps a start-transcript c:\temp\log.txt can give you more insight when being started by Intune? (create folder first)