Phil

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Phil shared this idea  · 
  2. 225 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  3. 60 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  4. 18 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  5. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Networking » Managment tools  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  6. 11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  7. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Phil commented  · 

    *Title should be Workflow Parameter Validation.

    Phil shared this idea  · 
  8. 25 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  9. 37 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  10. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  11. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    survey  ·  Zachary Alexander responded

    Can you take a look below and leave a comment to let me know if the workaround is sufficient for your purposes? If so, I will close this item. If not, I will keep it marked as survey.

    An error occurred while saving the comment
    Phil commented  · 

    I was able to hack around this by building a string of the MSFT_xWebBindingInformation object and then calling invoke-expression on the string, putting the resulting object into an array. This lets me add any amount of bindings-as-hashtables in my Configuration Data.

    An error occurred while saving the comment
    Phil commented  · 

    I think this bug is also preventing me from moving all of my binding info into a Configuration Data block. I haven't been able to find a way to be able to pass in data to the BindingInfo property of xWebsite using a container. E.g.:
    xWebSite Site
    {
    BindingInfo = $Node.BindingInfo
    }
    $ConfigData =
    @{
    AllNodes =
    @(
    @{
    NodeName = "TestBindings"
    BindingInfo = @(
    @{
    Protocol = 'http'
    IPAddress = '10.10.10.10'
    Port = 80
    },
    @{
    Protocol = 'https'
    IPAddress = '10.11.11.11'
    Port = 443
    }
    )
    }
    )
    }

    I've tried various ways of casting the data, and either I get nothing in the generated MOF, behaviour similar to xWebAdministration issue 113, or when I try to build the configuration I get:
    MSFT_xWebBindingInformation : The term 'MSFT_xWebBindingInformation' is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    Phil supported this idea  · 
  12. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  3 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  13. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  14. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  15. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  16. 11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  17. 28 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  18. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Virtualization » VMConnection & remoting  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  19. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Virtualization » Hypervisor  ·  Flag idea as inappropriate…  ·  Admin →
    Phil supported this idea  · 
  20. 100 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  Mark Gray responded

    Justin,

    We totally understand that a robust Pull server / central management solution is something that is critical to your success with DSC. We have invested quite heavily in Azure Automation DSC (AA DSC) to fill many of these needs. With that said, I would be very interested to understand if the AA DSC solution does not work for you (and other customers) and why? Vote and comment if this is important to you.

    Also interesting feedback on our ‘bad ideas’. Thanks!

    MarkG

    Phil supported this idea  · 
← Previous 1

Feedback and Knowledge Base