We have a similar item raised as a github issue, crosslinking: https://github.com/PowerShell/PowerShell-Docs/issues/1105
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.
- Nano server.
- Administrators which are doing more than 90% of their work remotely via PS Sessions in ISE tabs don't wich to open a RDP session just to restart a server, especially if they have a bunch of servers to restart alltogether.
- Software or server management via script
- Restart-Computer -Wait -For WinRM is more user friendly than logging on to the server, use the GUI to restart, and then opening a shell to make a PING until the server is availlable.
When talking about "giving a reason" I don't just mean a category (planned application, ...) I also mean a manual comment. Usually I mention the ticket number (incident, planned change, ...) or a brief summary of my action (Reboot because the server was in this state or I was doing this or that).
14 votessurvey · 7 comments · PowerShell » Microsoft.PowerShell.* Modules · Flag idea as inappropriate… · Admin →
Thanks for sharing !
However your link gives a 404 error because of the quotes...
This one should work :
Same in the final release.
Issue happens on:
- Windows 7 (physical computer)
- Windows 2008R2 (vmware)
Works fine on:
- Windows 10 (physical)
- Windows 2012R2 (vmware)
All computers are up-to-date.
We’d like to do this at some point. We’ll post back here if it happens in the ISE Preview. Read more about it here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
This work has already been started and will likely ship with a future version of the PowerShell ISE Preview. Read more about the Preview here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
Still not fixed in Powershell 5.1
We don’t own the creation of modules for operating system features. I’ll mark this as Survey so we can provide this information to the WU team, but you might also want to consider filing this in the Windows 10 Feedback Hub. Also, see the community-created PSWindowsUpdate link below :)