Andy Ray

My feedback

  1. 16 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      5 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →

      Would be interested in understanding the scenario where you are using the cmdlet & specifying the reason for rebooting. To explain: our previous assumption was that users would EITHER use the server UI that captured this information, OR use the cmdlet (often so they didn’t need to supply that reason text).
      So, what would help is to understand in what situations the cmdlet is being used and specifying the reboot explanation is desirable.

      Andy Ray commented  · 

      Frankly, until I started moving my workflows to PowerShell I was unaware that this feature was not available. I would have assumed with the richness of PowerShell this would have been a "given". Much as Luc has already explained, while it is very nice to have a quick method for restarting a system without the GUI, which is fine in labs and lower level domains, tracking restarts via the event log is a very common practice.

      If the restart is admin initiated (EITHER by script or by GUI) - some notation on the local system can be a godsend if trying to track down issues. Admittedly, if it is voluntary or behaves like the GUI, you can largely skip through it and it does no one any good... but for "managed systems" it is proper hygiene.

    • 8 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        2 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
        Andy Ray commented  · 

        So... after a GREAT DEAL of research I ran across the solution. Microsoft PS remote sessions are memory limited to (I think, I didn't check the original value before setting to the new value) 150MB. My compression process usually (when run locally) took about 3GB.

        This StackOverflow post had the solution: http://stackoverflow.com/questions/9665981/outofmemory-exception-on-remote-execution-using-powershell-invoke-command

        They set to 1000 GB... tad excessive... I limited mine to 4GB:

        Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 4000
        Set-Item WSMan:\localhost\Plugin\Microsoft.PowerShell\Quotas\MaxMemoryPerShellMB 4000
        Restart-Service WinRM

        Andy Ray commented  · 

        Ran into this exact issue when trying to encompass the Compress-Archive in an Invoke-Command to execute on a remote system. Command operates properly on remote system when executed on the system itself in a PowerShell console.

        Andy Ray supported this idea  · 

      Feedback and Knowledge Base