Windows 10: Windows and Office teams to migrate PowerShell help in December

Brink · Nov 24, 2020

Youâve got Help!

Up until now, creating updateable help has been a largely manual process. The CAB files downloaded by Update-Help had to be rebuilt and hosted on the Microsoft Download Center. The tools for managing the Download Center require manual steps and several levels of approval. These and other internal challenges meant that cmdlet help was only updated for major releases.

With the release of PowerShell 6, the PowerShell team piloted a new build process to automatically convert our Markdown documents to MAML help files, create the CAB files, and host them in Azure. This automation allowed the help for PowerShell 6+ to be updated every time we merged a new Pull Request in our documentation repository. The problem was how to scale out this solution so that every feature team with a PowerShell module could do the same thing without duplicating code and infrastructure.

For the past several months, Jason Helmick and I have been working with the PowerShell and Docs Engineering teams to create a shared, scalable, and fully-automated continuously-publishing pipeline.

So, whatâs in it for you?

As of today we have have migrated the PowerShell core documentation and the ConfigurationManager module for SCCM to this new pipeline.

This means:

Windows users have updated help for Windows PowerShell 5.1 for the first time in years

Users of PowerShell 7 and higher continue to have updateable help, including the new 7.2 preview

SCCM admins have updated cmdlet help for the first time since 2012 SP1

If you make a contribution to the docs and your PR is merged, your changes show up in updated help within days (if not hours)

Starting in December, we will begin working with the Windows and Office teams to migrate their PowerShell help. And we will continue to work with other feature teams in the new year.

Stay tuned for more announcements as the work progresses.

Sean Wheeler
Sr. Content Developer - PowerShell, Microsoft Developer Relations | Content + Learning
Click to expand...

Source: https://devblogs.microsoft.com/power...ouve-got-help/

:)

Brink · Nov 24, 2020

PowerShell Documentation Migration August 2nd

Hi, I’m Zach Alexander and I’m a PM on the PowerShell Team working on documentation.I wanted to let you know that there will be a brief downtime for online PowerShell documentation.

This downtime will occur on August 2nd and shouldn’t last more than a few hours. We will start around 4:30pm Pacific and estimate we will be back up by 7:30pm.

This downtime is needed so we can move our content off MSDN and onto https://docs.microsoft.com/! Moving to docs.microsoft.com means better community tools, better navigation, and a better reading experience.

This migration will not break most existing links. We will have redirection set up as part of the migration so most links end up going to the correct location. If we missed a link, feel free to file an issue on UserVoice or GitHub. This migration will also not affect our PowerShell Documentation repo on GitHub. We will continue to take suggestions and contributions from that repo, which will be rendered into the documents you see on docs.microsoft.com.

We’re excited to be moving to docs.microsoft.com! We have had a great experience open-sourcing our documentation, and continuing that journey with even better tooling can only mean even better docs!
Click to expand...

Source: PowerShell Documentation Migration | PowerShell Team Blog

Tassinvegeta · Nov 24, 2020

Powershell and MS Teams

I have an issue where I'm trying to test the deployment of a powershell script via GPO through Windows Server 2012R2 Standard. This script is for the installation of MS Teams which is found here. Script Install Microsoft Teams using PowerShell

However when putting it into the OU and loading it in Computer Configuration>Policies>Windows Settings>Scripts>Startup>Powershell Scripts the script only opens via notepad on the test Windows 10 machine without actually executing the powershell script.

Under script name I've tried various combinations of the absolute path. And tried different locations as to where to store the powershell script. Even when removing the GPO entirely the test machine still loads the notepad file and I can't seem to get rid
of it. I've also tried the MSI but that doesn't seem to get deployed to the test machine at all. I've previously loaded the current adx templates for Windows 10 1909 so I'm kinda at a loss.

Any suggestions would be extremely helpful to me. Thanks!

lvgandhi · Nov 24, 2020

powershell help does not seem to work

Hi, did you do the first part of what @Bree asked?

Try this to fix Powershell:
Press Windows key + R
Type: optionalfeatures.exe
Hit Enter

Scroll down and locate the Windows PowerShell entry.
Uncheck the PowerShell feature.
Save and apply your changes.
Restart your Windows 10 computer.
Afterwards, repeat the steps from above and re-enable the Windows PowerShell feature.
Click to expand...

Thanks for response.
I have done chkdsk C: /f also.
still not working. I tried your suggestion also. That also does not work.
But as I said get-help dir works. Please see below

Windows 10: Windows and Office teams to migrate PowerShell help in December

Windows and Office teams to migrate PowerShell help in December

Windows and Office teams to migrate PowerShell help in December

Windows and Office teams to migrate PowerShell help in December

Windows and Office teams to migrate PowerShell help in December - Similar Threads - Office teams migrate

What is New in Microsoft Teams for December 2020

Powershell and MS Teams

Teams without Office 365

What is New in Microsoft Teams for December 2019

December 2018 Office Update Release

Office 2010 Migration - Outlook

New to Office 365 in December 2017

December 2017 updates for Microsoft Office

PowerShell Documentation Migration August 2nd