Olegas Domanskis

My feedback

  1. 10 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    The issues you have encountered can be frustrating, sorry that is the case for you.

    Moving this to Survey to try to gauge the scope of the problem for users generally.

    We are somewhat limited by security requirements: what ships with Windows will always be tagged so that nothing can replace it easily unless it is signed by Microsoft. While Pester is part of Windows, it is not owned or developed by Microsoft, so updates delivered via the Gallery cannot be Microsoft signed.

    Once the Gallery version is installed on a system, -SkipPublisherCheck is no longer required for future updates. That first experience, however, is bad.

    This leaves us with a dilemma: do we stop shipping Pester in with PowerShell in the future, or do we continue to provide the feature set knowing users who update from the Gallery will encounter these issues?

    Looking for feedback from as many users…

    An error occurred while saving the comment
    Olegas Domanskis commented  · 

    Having similar issue when trying to use DSC configuration. For example trying to configure xSQLServer it trying to copy over Microsoft.PowerShell.Operation.Validation and Pester modules.
    Which is good, since servers are not allowed to access the internet.
    But because folders are owned by TrustedInstaller it returns an errors.
    It would be good not to have them at the beginning at all.


    Olegas Domanskis supported this idea  · 

Feedback and Knowledge Base