Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect documentation for New-CMSoftwareUpdateDeployment -RestartServer/-RestartWorkstation #251

Open
rably1960 opened this issue Jan 28, 2022 · 1 comment
Assignees
Labels
doc-bug out of date, unclear, confusing, or broken

Comments

@rably1960
Copy link

This is regarding the documentation of the -RestartServer/-RestartWorksation parameters. The documentation says "Indicates whether to allow a workstation to restart following a software update". However, it actually indicates whether to suppress a reboot, not allow a reboot. A value of "true" will set the "suppressreboot" attribute bit, while a value of "false" will not set the bit. For example, setting both of these to true sets the SuppressReboot value to 3, and if you look at the deployment in SCCM after creation the suppress server and workstation boxes are both checked. So setting these to "false" will actually ALLOW a reboot.

In reality, it is either a poorly named parameter or a bug in the code for the cmdlet. But that makes it even more important to correct the documentation because this can cause servers to restart unintentionally.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@rably1960 rably1960 changed the title Incorrect information Incorrect documentation for New-CMSoftwareUpdateDeployment -RestartServer/-RestartWorkstation Jan 28, 2022
@aczechowski aczechowski self-assigned this Jun 1, 2022
@aczechowski aczechowski added the doc-bug out of date, unclear, confusing, or broken label Jun 1, 2022
@aczechowski
Copy link
Member

Hi @rably thanks for the feedback. We have limited resources to maintain the over 1100 cmdlet articles for this module (along with the 3200 articles in ConfigMgr core docs). Starting with version 2002, the article for any new cmdlet should be mostly complete. We have an internal tracking item to go back and pick up older cmdlet articles when we have time, but it's honestly not our highest priority due to relatively low page views.

We rely on community support from members like you to assist. For more information, see How to contribute.

I'm updating content for the 2203 current branch release, and will try to address this article at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-bug out of date, unclear, confusing, or broken
Projects
None yet
Development

No branches or pull requests

2 participants