Phil Isensee

← Windows Server

My feedback

  1. Get-WindowsCapability -Online Hangs on Build 17133.73

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  General Feedback » Bug  ·  Flag idea as inappropriate…  ·  Admin →
    Phil Isensee shared this idea  · 

  2. Get-MpPreference .AttackSurfaceReductionRules_Actions returns incorrect value(s)

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Phil Isensee shared this idea  · 

  3. import-module generates output

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Phil Isensee commented  · 

    Not fixed in 1709-16299.19.

    Phil Isensee shared this idea  · 

  4. We need a proper set of built-in, easy-to-use, dedicated registry cmdlets

    28 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Phil Isensee supported this idea  · 

  5. Pure Pain: Preinstalled PS Modules - Please Rationalize Them with Package Management Installs

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    5 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    survey  ·  J. Keith Bankston [MSFT] responded

    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…

    Phil Isensee commented  · 

    I appreciate the value of installing Pester with the OS but if it is not owned my MS, then it shouldn't be installed by Trusted installer nor installed as part of the OS.

    My thinking is it has to be one or the other.

Feedback and Knowledge Base

(thinking…)