J0F3

My feedback

  1. 35 votes
    Sign in
    (thinking…)
    Password icon
    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 →
    J0F3 supported this idea  · 
  2. 33 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Storage » Storage Spaces  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  3. 50 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  4. 186 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 commented  · 

    This is something thats abosultely needed in a modern infrastructure. Just full admin access of evryone to anythng is not anymore the way to go.

    J0F3 supported this idea  · 
  5. 43 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  6. 44 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Installation and Patching » Windows Update  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  7. 91 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  8. 11 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 shared this idea  · 
  9. 13 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  10. 92 votes
    Sign in
    (thinking…)
    Password icon
    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

    J0F3 commented  · 

    It is essential that the on-premises pull server is not letting behind. Azure Automation is not always an option as many other already wrote here.
    The current state of the dsc pull server in WMF 5.1 is unfortunetaley quite bad.
    In my opinion there are three thing which should be fixed urgently:
    1. Reproting Server sould get a UI with the node status or at least a GET method to get the status from all nodes
    2. Change database to something which can made highly availabe (e.g. SQL). So not a wohle enverionment "depends" on one single pull server
    3. Bring the encryption logic from Azure Automation DSC which encrypts the whole MOF file, without manually certificate creation and exchange, into the on-premises pull server (the current solution for credential encryption is in bigger environments not practicable)

    J0F3 supported this idea  · 
  11. 54 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    survey  ·  Mark Gray responded

    Thanks for the feedback, Sebastian! I have changed the status to survey to get a better feel for how important this is for customers in general.

    MarkG

    J0F3 commented  · 

    This is very important because the reporting server in its current state is almost useless. It must be possible to query the status of the nodes without knowing the agent id!

    J0F3 supported this idea  · 
  12. 115 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Core Server » Storage  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  13. 36 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    J0F3 supported this idea  · 
    J0F3 commented  · 

    After some deeper debugging I can definitely confirm that the DSC Pullserver does not use the circular log option for the EDB Database. Therefore, the log files get never truncated. Furthermore, there is also no option for doing a correct full backup implemented.
    For me this looks like a bug where the circular log setting is simply missing in the DLL of the DSCPullserver.
    It is really import that we can fix this issue otherwise the DSC Pullserver is simply no option for use in production! See also Issue on Github: https://github.com/PowerShell/xPSDesiredStateConfiguration/issues/296

    Can please someone from MFST investigate or help here?

    J0F3 commented  · 

    This is a huge pain. We need really a solution for that. As Jason already wrote it seems that circular logging is not configured for the ESENT database. So in may case I have now over 46GB (!) of log files on my DSC Pullserver and the DSC service responds very slowly. So how can I commit and clean up the log files?

    Thank for helping!

  14. 15 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  15. 13 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Core Server » Setup  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 shared this idea  · 
  16. 57 votes
    Sign in
    (thinking…)
    Password icon
    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 →
    J0F3 supported this idea  · 
  17. 72 votes
    Sign in
    (thinking…)
    Password icon
    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 →
    J0F3 supported this idea  · 
  18. 43 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  4 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  19. 4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    J0F3 supported this idea  · 
  20. 49 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for the suggestion. Given the number of requests, we cannot field all recommendations, so for now we’ll be monitoring this to see if there is broad support.

    J0F3 supported this idea  · 
← Previous 1

Feedback and Knowledge Base