Using start-process PowerShell command in detection script on Configuration Item MECM.

Question

I am currently using start-process to run a programme persistently even after the client evaluation has ended. The script works fine when run locally on the client device (copy and paste into PowerShell). But when deployed as a Configuration Baseline via MECM, the start-process does not get triggered.

Is Configuration Item's detection script not able to use the start-process PowerShell command? If so, if there any other options.

Answer 1

Hi,

May we know the current status of the question? Have we check the powershell command by PsExec? Is it successful? Look forward to your update.

If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

First ci have a timeout of something like 2 minutes.
Next did you test your system as local system? https://www.recastsoftware.com/resources/how-to-access-the-local-system-account/