Ansible
PS DSC
Downloads:
13,469,650
Downloads of v 5.1.14409.20170402:
261,379
Last Update:
03 Apr 2017
Package Maintainer(s):
Software Author(s):
- Microsoft wrote PowerShell
- IntelliTect created the Chocolatey Package
Tags:
powershell admin reboot scripting oneget- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Windows Management Framework and PowerShell
This is not the latest version of Windows Management Framework and PowerShell available.
- 1
- 2
- 3
5.1.14409.20170402 | Updated: 03 Apr 2017
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
13,469,650
Downloads of v 5.1.14409.20170402:
261,379
Maintainer(s):
Software Author(s):
- Microsoft wrote PowerShell
- IntelliTect created the Chocolatey Package
Windows Management Framework and PowerShell 5.1.14409.20170402
This is not the latest version of Windows Management Framework and PowerShell available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft wrote PowerShell, IntelliTect created the Chocolatey Package. The inclusion of Microsoft wrote PowerShell, IntelliTect created the Chocolatey Package trademark(s), if any, upon this webpage is solely to identify Microsoft wrote PowerShell, IntelliTect created the Chocolatey Package goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Windows Management Framework and PowerShell, run the following command from the command line or from PowerShell:
To upgrade Windows Management Framework and PowerShell, run the following command from the command line or from PowerShell:
To uninstall Windows Management Framework and PowerShell, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download powershell --internalize --version=5.1.14409.20170402 --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade powershell -y --source="'INTERNAL REPO URL'" --version="'5.1.14409.20170402'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade powershell -y --source="'INTERNAL REPO URL'" --version="'5.1.14409.20170402'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install powershell
win_chocolatey:
name: powershell
version: '5.1.14409.20170402'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'powershell' do
action :install
source 'INTERNAL REPO URL'
version '5.1.14409.20170402'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller powershell
{
Name = "powershell"
Version = "5.1.14409.20170402"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'powershell':
ensure => '5.1.14409.20170402',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 03 Apr 2017.
Windows Management Framework 5.0 includes updates to Windows PowerShell, Windows PowerShell ISE, Windows PowerShell Web Services (Management OData IIS Extension), Windows Remote Management (WinRM), Windows Management Instrumentation (WMI), the Server Manager WMI provider, and a new feature for 4.0, Windows PowerShell Desired State Configuration (DSC).
Windows Management Framework 5.0 includes updates to Windows PowerShell, Windows PowerShell Desired State Configuration (DSC), and Windows PowerShell ISE. It also includes OneGet, PowerShellGet, and Network Switch cmdlets
Important Product Incompatibility Notes: https://msdn.microsoft.com/en-us/powershell/wmf/5.0/productincompat
IMPORTANT NOTES for your Operating System:
PowerShell 4 and later requires at least .NET 3.5.1.
This package will warn you and exit if it is not installed.
It is not automatically installed as a dependency so that you
maintain complete control over the .NET version in your build.
WARNING: Review the release notes to learn which software products are not compatible with this upgrade (e.g. SCCM SERVERS.)
Write-Debug ("Starting " + $MyInvocation.MyCommand.Definition)
[string]$packageName="PowerShell.5.0"
<#
Exit Codes:
3010: WSUSA executed the uninstall successfully.
2359303: The update was not found.
#>
#5.0.10586
$osVersion = (Get-WmiObject Win32_OperatingSystem).Version
if(-not (($osVersion -ge [version]"6.4") -or ($osVersion -ge [version]"10.0"))) {
Start-ChocolateyProcessAsAdmin "/uninstall /KB:3191566 /quiet /norestart /log:`"$env:TEMP\PowerShellUninstall5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
Start-ChocolateyProcessAsAdmin "/uninstall /KB:3191565 /quiet /norestart /log:`"$env:TEMP\PowerShellUninstall5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
Start-ChocolateyProcessAsAdmin "/uninstall /KB:3191564 /quiet /norestart /log:`"$env:TEMP\PowerShellUninstall5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
}
Write-Warning "$packageName may require a reboot to complete the uninstallation."
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
2013 Microsoft Corporation
WMF 5.1 Release Notes: https://msdn.microsoft.com/en-us/powershell/wmf/5.1/release-notes
2017.04.02
WMF Version: 5.1.14409.1005
Pkg Version: 5.1.14409.20170402
- powershell install log files are serialized so that they don't accumulate in the same file across multiple attempts
- if an errors occurs, the errors are extracted from the log file and displayed into the chocolatey log
2017.03.01
WMF Version: 5.1.14409.1005
Pkg Version: 5.1.14409.20170301
- fixed bug misidentifying the .net version on Server 2012
2017.02.14
WMF Version: 5.1.14409.1005
Pkg Version: 5.1.14409.20170214
- fixed bug causing Server 2012 (non-R2) from being detected as windows 8
2017.01.26 (5.1.14409.1005)
- New: Installs WMF 5.1
- Tested On: Win7 + PSH 2, Win7 + WMF 3, Win 8.1 + WMF 4, 2012 R2 + WMF 5.0, Windows 10
- EXPERIMENTAL: Attempts to Preserve the PSModulePath when WMF 5.1 is
installed over WMF 3 on Windows 7 or Server 2008.
How the experimental support works:
*) It only takes effect on Windows 7 and Server 2008 R2 and only if WMF 3 is installed
*) You must pre-install at least .NET 4.5.1 (required by WMF 4 and later)
*) You must use the -force switch on the package
What steps are taken to preserve PSModulePath:
1) The custom parts of the PSModulePath backed up to BackupPSModulePath
2) A fix up script that appends those values to the PSModulePath is written to:
%WINDIR%\Temp\psmodulepathfixup.ps1
3) A scheduled task is setup for the next reboot that runs the fix up script
If you find that #3 does not work correctly, then you can use #1 or #2 with some of your
own automation to recover from the PsModulePath overwrite.
2016.12.01 (5.0.10586.20170115)
- Fixed: Package generates error that you must upgrade to Windows 8.1 on Server 2012 (not-R2) domain controllers.
2016.12.01 (5.0.10586.20161201)
- IMPORTANT: This package no longer updates a machine to an older version of PowerShell when 5 cannot be applied, the package must
be explicitly called with the -version parameter if the system being configured cannot take PowerShell 5.
- Updated to use checksums
- Updated to use re-released MSUs discussed here (old ones getting 404s):
https://blogs.msdn.microsoft.com/powershell/2016/02/24/windows-management-framework-wmf-5-0-rtm-packages-has-been-republished/
- Checks and errors if Windows Update service is disabled, the error message suggests enabling it just for the time this package runs
(it is a common good practice to disable Windows Update when doing long running orchestration,
however, it must be enabled for this package to run)
TROUBLESHOOTING GUIDANCE:
If you receive the error 'ERROR: Running ["C:\Windows\System32\wusa.exe" ' it generally means the system does not have the prerequisites
required by the .MSU file.
Find the reference to the the log file "PowerShell.Install.evtx" and double-click it to open it in eventvwr. The reason for the failure
should be within the messages in this file.
Please do this before reporting the error because it will be the first thing you are asked to do in order to establish root cause.
This package has no dependencies.
Ground Rules:
- This discussion is only about Windows Management Framework and PowerShell and the Windows Management Framework and PowerShell package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Windows Management Framework and PowerShell, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.