search

MicrosoftDocs / windows-powershell-docs

This repo is used to contribute to Windows 10, Windows Server 2016, and MDOP PowerShell module documentation.
Creative Commons Attribution 4.0 International
443 stars 594 forks source link

Wait-VM's existence not documented #240

Closed mattpwhite closed 1 year ago

mattpwhite commented 6 years ago

There is a Wait-VM cmdlet that ships in the Hyper-V module, but does not appear on the online docs and does not have help available from whatever Update-Help talks to. It is covered a bit on this blog post, it would be nice if it had a proper help page. https://blogs.technet.microsoft.com/virtualization/2016/10/11/waiting-for-vms-to-restart-in-a-complex-configuration-script-with-powershell-direct/

Document Details

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

o0nj commented 5 years ago

@officedocsbot assign @yogkumgit

o0nj commented 5 years ago

@officedocsbot unassign @e0i

get-itips commented 5 years ago

Hello @brianlic-msft can you help us with this? thank you!

get-itips commented 5 years ago

Hello @AndreaBarr can you help us locating the right people to confirm this ? Thank you

rrperkin commented 3 years ago

Are y'all ever going to document this?

AberrantMonk commented 2 years ago

Wow- almost 4 years and the only progress made has been the assignees going in circles and a label added.

igpit commented 2 years ago

ping

codaamok commented 1 year ago

@officedocsbot assign @e0i

ApexxX0 commented 1 year ago

Can none of the people in this assigning loop really answer this question? Also the link is now broken leaving no answer there.

jtlarson commented 1 year ago

I'd like to see this updated too...

ZianAtFirstWatch commented 1 year ago

The link has a comment that expresses a desire for a command like Wait-VM but it does not explain what the real Wait-VM command does.

The command is mentioned in a few places on the Internet:

schittli commented 1 year ago

What a shame for Microsoft...

Microsoft calls a lot of things 'docs', which are not worth the name and our apprentices and interns write better docs.

But there are even Microsoft teams that completely lack the inner motivation to offer Microsoft customers minimally decent documentation?

Even when paying customers point out such embarrassing mistakes, customers are simply ignored. For years.

We can watch how M$ products are less and less worth buying.

Kind regards, Thomas

tiburd commented 1 year ago

The content development team reports that they plan to update the Hyper-V module soon and will be prioritizing the Wait-VM cmdlet.

Development work is tracked in an internal system, so I'm closing this issue.

mattpwhite commented 1 year ago

So why not keep this open until that ships? Is there a planned year of release for that? We're half way to a decade already, if this issue were a human child, it would be entering kindergarten. Should we expect a release before or after this issue reaches high school?

More generally - does Microsoft intend to publish help for new cmdlets or parameters? When I logged this issue, it was a bit of an anomaly - most stuff shipped in Windows inbox modules was documented. That's no longer the case. The overwhelming majority of what was shipped in 2019 or 2022 is not documented. And it's not like there was a great deal added in either of those releases. For instance, go try to find literally anything on the FailoverClusterSet module. Updates to the docs for the WMI providers many of those modules use also stopped being updated around that time. The help update mechanism for Windows PowerShell was left broken for years at a time. It seemed like a fairly clear "docs are no longer a thing, this is no one's job now" message to any reasonable observer.

I realize I'm shouting into the void here (see above - "no one's job"), but figured I'd ask.

dstrome commented 1 year ago

@mattpwhite and @schittli - thanks very much for your feedback. I understand your frustration and I'm going to forward this thread to our leadership as it's a good example of the pain individuals like yourselves are experiencing.

We're closing this issue because the problem is well understood and the team responsible for the content is tracking the work internally.

Thanks, David.