There were a several announcements at last weeks VMworld US Conference, but one of the most exciting piece of news in my opinion was from Alan Renouf, Product Manager for all things API/SDK/CLI at VMware. During Alan's What's New PowerCLI session, he announced that PowerCLI is finally coming to both Mac OS X as well as Linux! As you can imagine, the news was very well received from customers and partners. In fact, after I had tweeted the update here & here, I literally had folks pinging/IM'ing/DM'ing me non-stop about when they could get access ?
- Installation via Direct Download. Download the PKG package powershell-lts-7.0.3-osx-x64.pkg from the releases page onto your macOS machine. You can double-click the file and follow the prompts, or install it from the terminal: sudo installer -pkg powershell-lts-7.0.3-osx-x64.pkg -target / Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIM operations.
- Teletype for Atom. Great things happen when developers work together—from teaching and sharing knowledge to building better software. Teletype for Atom makes collaborating on code just as easy as it is to code alone, right from your editor.
I am trying for many days now to get things done with PowerShell on a Mac. Installation of HomeBrew and PowerShell (7) is not a problem. I can also add modules, e.g. To work with Teams.
UPDATE (10/18/16) - PowerCLI Multi-Platform (MP) for Linux and Mac OS X has now been released as a VMware Fling. Please find the download here and provide any feedback in the comments section.
This exciting update was only possible with the help of our friends over at Microsoft who had recently open sourced both .NET Core & PowerShell. Once that news broke, Alan and the PowerCLI Engineering team have been working hard on porting over the existing PowerCLI code which uses the Windows .NET library over to the new .NET Core which is now open sourced. I have been very impressed at how fast the PowerCLI team have already made available many of the default cmdlets as well as the Get View cmdlet which exposes the entire functionality of the vSphere API.
Now, before you get too excited, this new version of PowerCLI is currently not available yet. As Alan mentioned in his session, we plan to release an early Tech Preview of PowerCLI for both Mac OS X and Linux as a VMware Fling shortly after VMworld. It is also very important to note that Microsoft PowerShell for Mac OS X & Linux which PowerCLI uses is just at an Alpha release milestone. There is still much work to do on both sides but I am really looking forward to enabling our customers with the choice of platform when it comes to consuming PowerCLI.
A few of us have been quite fortunate to have been involved in the early development of this new version of PowerCLI. In fact, we even built a simple Docker Container for PowerCLI which will allow you to easily access PowerCLI from any system that can run Docker. Here is a quick screenshot of spinning up a PowerCLI Docker Container which will also be part of the Fling release.
Lastly, we want customers to be able to quickly and securely set up a persistent PowerCLI environment in which they can use to manage and configure their VMware-based products that support PowerCLI. Graphical analysis online. With that, we have also built a PowerShell package for Photon OS which is VMware's minimal Linux container host distribution. Not only is it free to download and use, but it literally takes a few seconds to install (tdnf -y install powershell) and even less time to boot up and import the PowerCLI module. This was literally done the week before VMworld by the Photon team and huge kudos for their support! As you can see, not only do we want to provide choice for our customers but also simplifying how you might consume PowerCLI whether its natively on Windows, Mac OS X, Linux, Docker Container or running on top of VMware Photon OS. I hope you are excited as I am and stay tuned for more details on the Fling release!
If you have any feedback or what you are most excited regarding this news, please leave a comment and I will make sure it makes it way back to our Product Manager.
More from my site
PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, DSC Resources, Role Capabilities and Scripts.
Minimum PowerShell version
3.0
Powershell 5.0 Download Windows 10
There is a newer prerelease version of this module available.
See the version list below for details.
See the version list below for details.
Installation Options
Copy and Paste the following command to install this package using PowerShellGet More Info
Install-Module -Name PowerShellGet -RequiredVersion 1.6.0 -Force
You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deloy all the dependencies to Azure Automation. Learn More
Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More
Author(s)
![Powershell 4 download windows 7 Powershell 4 download windows 7](/uploads/1/2/6/4/126445676/255550903.jpg)
Microsoft Corporation
Copyright
(c) Microsoft Corporation. All rights reserved.
Package Details
Download Azure Powershell For Mac
Owners
Tags
Functions
PSEditions
Dependencies
- PackageManagement(>= 1.1.7)
Powershell On A Mac
Release Notes
## 1.6.0
New features
* Prerelease Version Support (#185)
- Implemented prerelease versions functionality in PowerShellGet cmdlets.
- Enables publishing, discovering, and installing the prerelease versions of modules and scripts from the PowerShell Gallery.
- [Documentation](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/PrereleaseModule)
* Enabled publish cmdlets on PWSH and Nano Server (#196)
- Dotnet command version 2.0.0 or newer should be installed by the user prior to using the publish cmdlets on PWSH and Windows Nano Server.
- Users can install the dotnet command by following the instructions specified at https://aka.ms/dotnet-install-script.
- On Windows, users can install the dotnet command by running *Invoke-WebRequest -Uri 'https://dot.net/v1/dotnet-install.ps1' -OutFile '.dotnet-install.ps1'; & '.dotnet-install.ps1' -Channel Current -Version '2.0.0'*
- Publish cmdlets on Windows PowerShell supports using the dotnet command for publishing operations.
Breaking Change
- PWSH: Changed the installation location of AllUsers scope to the parent of $PSHOME instead of $PSHOME. It is the SHARED_MODULES folder on PWSH.
Bug fixes
- Update HelpInfoURI to 'https://go.microsoft.com/fwlink/?linkid=855963' (#195)
- Ensure MyDocumentsPSPath path is correct (#179) (Thanks @lwsrbrts)
## 1.5.0.0
New features
* Added support for modules requiring license acceptance (#150)
- [Documentation](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/RequireLicenseAcceptance)
* Added version for REQUIREDSCRIPTS (#162)
- Enabled following scenarios for REQUIREDSCRIPTS
- [1.0] - RequiredVersion
- [1.0,2.0] - Min and Max Version
- (,1.0] - Max Version
- 1.0 - Min Version
Bug fixes
* Fixed empty version value in nuspec (#157)
## 1.1.3.2
* Disabled PowerShellGet Telemetry on PS Core as PowerShell Telemetry APIs got removed in PowerShell Core beta builds. (#153)
* Fixed for DateTime format serialization issue. (#141)
* Update-ModuleManifest should add ExternalModuleDependencies value as a collection. (#129)
## 1.1.3.1
New features
* Added `PrivateData` field to ScriptFileInfo. (#119)
Bug fixes
* Fixed Add-Type issue in v6.0.0-beta.1 release of PowerShellCore. (#125, #124)
* Install-Script -Scope CurrentUser PATH changes should not require a reboot for new PS processes. (#124)
- Made changes to broadcast the Environment variable changes, so that other processes pick changes to Environment variables without having to reboot or logoff/logon.
* Changed `Get-EnvironmentVariable` to get the unexpanded version of `%path%`. (#117)
* Refactor credential parameter propagation to sub-functions. (#104)
* Added credential parameter to subsequent calls of `Publish-Module/Script`. (#93)
- This is needed when a module is published that has the RequiredModules attribute in the manifest on a repository that does not have anonymous access because the required module lookups will fail.
## 1.1.2.0
Bug fixes
* Renamed `PublishModuleIsNotSupportedOnNanoServer` errorid to `PublishModuleIsNotSupportedOnPowerShellCoreEdition`. (#44)
- Also renamed `PublishScriptIsNotSupportedOnNanoServer` to `PublishScriptIsNotSupportedOnPowerShellCoreEdition`.
* Fixed an issue in `Update-Module` and `Update-Script` cmdlets to show proper version of current item being updated in `Confirm`/`WhatIf` message. (#44)
* Updated `Test-ModuleInstalled` function to return single module instead of multiple modules. (#44)
* Updated `ModuleCommandAlreadyAvailable` error message to include all conflicting commands instead of one. (#44)
- Corresponding changes to collect the complete set of conflicting commands from the being installed.
- Also ensured that conflicting commands from PSModule.psm1 are ignored in the command collision analysis as Get-Command includes the commands from current local scope as well.
* Fixed '[Test-ScriptFileInfo] Fails on *NIX newlines (LF vs. CRLF)' (#18)
## 1.1.1.0
Bug fixes
* Fixed 'Update-Module fails with `ModuleAuthenticodeSignature` error for modules with signed PSD1'. (#12) (#8)
* Fixed 'Properties of `AdditionalMetadata` are case-sensitive'. #7
* Changed `ErrorAction` to `Ignore` for few cmdlet usages as they should not show up in ErrorVariable.
- For example, error returned by `Get-Command Test-FileCatalog` should be ignored.
## 1.1.0.0
* Initial release from GitHub.
* PowerShellCore support.
* Security enhancements including the enforcement of catalog-signed modules during installation.
* Authenticated Repository support.
* Proxy Authentication support.
* Responses to a number of user requests and issues.
New features
* Prerelease Version Support (#185)
- Implemented prerelease versions functionality in PowerShellGet cmdlets.
- Enables publishing, discovering, and installing the prerelease versions of modules and scripts from the PowerShell Gallery.
- [Documentation](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/PrereleaseModule)
* Enabled publish cmdlets on PWSH and Nano Server (#196)
- Dotnet command version 2.0.0 or newer should be installed by the user prior to using the publish cmdlets on PWSH and Windows Nano Server.
- Users can install the dotnet command by following the instructions specified at https://aka.ms/dotnet-install-script.
- On Windows, users can install the dotnet command by running *Invoke-WebRequest -Uri 'https://dot.net/v1/dotnet-install.ps1' -OutFile '.dotnet-install.ps1'; & '.dotnet-install.ps1' -Channel Current -Version '2.0.0'*
- Publish cmdlets on Windows PowerShell supports using the dotnet command for publishing operations.
Breaking Change
- PWSH: Changed the installation location of AllUsers scope to the parent of $PSHOME instead of $PSHOME. It is the SHARED_MODULES folder on PWSH.
Bug fixes
- Update HelpInfoURI to 'https://go.microsoft.com/fwlink/?linkid=855963' (#195)
- Ensure MyDocumentsPSPath path is correct (#179) (Thanks @lwsrbrts)
## 1.5.0.0
New features
* Added support for modules requiring license acceptance (#150)
- [Documentation](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/RequireLicenseAcceptance)
* Added version for REQUIREDSCRIPTS (#162)
- Enabled following scenarios for REQUIREDSCRIPTS
- [1.0] - RequiredVersion
- [1.0,2.0] - Min and Max Version
- (,1.0] - Max Version
- 1.0 - Min Version
Bug fixes
* Fixed empty version value in nuspec (#157)
## 1.1.3.2
* Disabled PowerShellGet Telemetry on PS Core as PowerShell Telemetry APIs got removed in PowerShell Core beta builds. (#153)
* Fixed for DateTime format serialization issue. (#141)
* Update-ModuleManifest should add ExternalModuleDependencies value as a collection. (#129)
## 1.1.3.1
New features
* Added `PrivateData` field to ScriptFileInfo. (#119)
Bug fixes
* Fixed Add-Type issue in v6.0.0-beta.1 release of PowerShellCore. (#125, #124)
* Install-Script -Scope CurrentUser PATH changes should not require a reboot for new PS processes. (#124)
- Made changes to broadcast the Environment variable changes, so that other processes pick changes to Environment variables without having to reboot or logoff/logon.
* Changed `Get-EnvironmentVariable` to get the unexpanded version of `%path%`. (#117)
* Refactor credential parameter propagation to sub-functions. (#104)
* Added credential parameter to subsequent calls of `Publish-Module/Script`. (#93)
- This is needed when a module is published that has the RequiredModules attribute in the manifest on a repository that does not have anonymous access because the required module lookups will fail.
## 1.1.2.0
Bug fixes
* Renamed `PublishModuleIsNotSupportedOnNanoServer` errorid to `PublishModuleIsNotSupportedOnPowerShellCoreEdition`. (#44)
- Also renamed `PublishScriptIsNotSupportedOnNanoServer` to `PublishScriptIsNotSupportedOnPowerShellCoreEdition`.
* Fixed an issue in `Update-Module` and `Update-Script` cmdlets to show proper version of current item being updated in `Confirm`/`WhatIf` message. (#44)
* Updated `Test-ModuleInstalled` function to return single module instead of multiple modules. (#44)
* Updated `ModuleCommandAlreadyAvailable` error message to include all conflicting commands instead of one. (#44)
- Corresponding changes to collect the complete set of conflicting commands from the being installed.
- Also ensured that conflicting commands from PSModule.psm1 are ignored in the command collision analysis as Get-Command includes the commands from current local scope as well.
* Fixed '[Test-ScriptFileInfo] Fails on *NIX newlines (LF vs. CRLF)' (#18)
## 1.1.1.0
Bug fixes
* Fixed 'Update-Module fails with `ModuleAuthenticodeSignature` error for modules with signed PSD1'. (#12) (#8)
* Fixed 'Properties of `AdditionalMetadata` are case-sensitive'. #7
* Changed `ErrorAction` to `Ignore` for few cmdlet usages as they should not show up in ErrorVariable.
- For example, error returned by `Get-Command Test-FileCatalog` should be ignored.
## 1.1.0.0
* Initial release from GitHub.
* PowerShellCore support.
* Security enhancements including the enforcement of catalog-signed modules during installation.
* Authenticated Repository support.
* Proxy Authentication support.
* Responses to a number of user requests and issues.
FileList
- PowerShellGet.nuspec
- PowerShellGet.cat
Version History
Version | Downloads | Last updated |
---|---|---|
3.0.0-beta10 | 293,754 | 9/5/2020 |
3.0.0-beta1 | 4,683 | 3/30/2020 |
2.2.5 | 830,294,816 | 9/22/2020 |
2.2.4.1 | 13,234,841 | 4/22/2020 |
2.2.4 | 2,164,270 | 4/16/2020 |
2.2.3 | 5,355,025 | 12/23/2019 |
2.2.2 | 316,303 | 12/11/2019 |
2.2.1 | 5,890,091 | 8/16/2019 |
2.2 | 895,092 | 7/9/2019 |
2.1.5 | 534,207 | 6/18/2019 |
2.1.4 | 568,160 | 5/21/2019 |
2.1.3 | 159,999 | 5/14/2019 |
2.1.2 | 1,279,221 | 3/15/2019 |
2.1.1 | 25,224 | 3/14/2019 |
2.1.0 | 98,941 | 3/8/2019 |
2.0.4 | 1,007,453 | 1/15/2019 |
2.0.3 | 822,972 | 11/19/2018 |
2.0.1 | 1,007,548 | 9/24/2018 |
2.0.0 | 236,838 | 9/13/2018 |
1.6.7 | 523,639 | 8/17/2018 |
1.6.6 | 834,551 | 7/2/2018 |
1.6.5 | 903,267 | 5/17/2018 |
1.6.0 (current version) | 967,435 | 12/5/2017 |
1.5.0.0 | 182,794 | 10/9/2017 |
1.1.3.2 | 24,883 | 8/8/2017 |
1.1.3.1 | 76,970 | 5/16/2017 |
1.1.2.0 | 28,636 | 12/5/2016 |
1.1.1.0 | 2,282 | 10/12/2016 |
1.1.0.0 | 8,051 | 9/29/2016 |