Share via

Code Integrity check fails due to remoteipmoproxy temp folders for powershell files - psdesiredstateconfiguration

55843155 1 Reputation point
2022-08-02T15:36:30.57+00:00

C# calling DSC commands extracts psdesiredstateconfiguration in temp folder with name starting with remoteipmoproxy_. Code Integrity cannot load these files as the files in it are not signed/initial check with audit put different folder in audit events. C# uses CreateRunspace commands to call DSC Test configuration command.

  1. Is there any way to run these commands in place from Windows\System32\WindowsPowerShell folder instead of getting these temp folders created that fails the code integrity check.
  2. Any other option to successfully pass code integrity policy
Windows for business | Windows Server | User experience | PowerShell
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2022-08-17T07:03:34.58+00:00

    Hi,

    It seems the remoteipmoproxy temp folders are created because the preinstalled PSDesiredStateConfiguration module is not compatible with PowerShell core. Please try installing the PSDesiredStateConfiguration version 3.0.0 which is compatible with PowerShell core from the PowerShell Gallery.

    https://learn.microsoft.com/en-us/powershell/dsc/overview?view=dsc-3.0

    Best Regards,
    Ian Xue

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.