#WHAT TO INSTALL ON MAC FOR POWERSHELL DOWNLOAD#
I went with the recommended process of using Homebrew rather than direct download or using binary archives. Microsoft have published some pretty good instructions here with various options for installing PowerShell. The long version will have a lot of screenshots and a few workarounds for the various issues I saw along the way… Short Version Install Homebrew /bin/bash -c "$(curl -fsSL )" Install PowerShell brew install -cask powershell Run PowerShell pwsh Install Exchange Online Management Module Install-Module ExchangeOnlineManagement Connect to Exchange Online Connect-ExchangeOnline -UserPrincipalName Install Microsoft Teams Module Install-Module MicrosoftTeams Connect to Microsoft Teams Connect-MicrosoftTeams -AccountId Connect to Skype for Business Online $SFBOSession = New-CsOnlineSession -OverrideAdminDomain Import-PSSession $SFBOSession -AllowClobber Long Version I have done a short version and a long version. As of writing the latest version of PowerShell is 7.1.1. But it works at the end and I am quite happy with it.All of this has been done on my aging MacBook with macOS Big Sur Version 11.1. But I started with beta of PowerShell core, and PowerCLI on my system and did not want to complicate anything. I know that this was, or is, a somewhat complicated article for something so simple. 7/23/17 – thanks to Kyle Ruddy I found out that PowerCLI and PowerShell are not yet compatible.2/28/18 – I try this again, with GA PowerShell Core and GA PowerShell 10 and it works!.
Also confirmed the Upgrading PowerShell worked with 6.1. 11/26/18 – some small edits to improve things.
#WHAT TO INSTALL ON MAC FOR POWERSHELL UPDATE#
11/27/18 – changed update to upgrade in the brew – a little nicer as upgrade I think.You can upgrade PowerShell – like to 6.1 using the following commands. You should also remember the following command as there are updates to PowerCLI.Īnd that command will update any installed modules including PowerCLI. Set-PSRepository -Name “PSGallery” -InstallationPolicy “Trusted” One list thing to do – again learned from Alex Lopex is to trust the PowerShell gallery. Now, I try connecting again and even though I am on a Mac look what I see: Set-PowerCLIConfiguration -InvalidCertificateAction Ignore You can see the command I use to get rid of it at the bottom of the screen above. I now connect to my vCenter to see how that goes.Ĭonnect-VIserver -server Get-Module “VMware.PowerCLI” -ListAvailable | FT -Autosize Thanks to Alex Lopez I learned another way to do that which is a bit more tidy. When it is finished I type the following command to see what is installed.
Install-Module -Name VMware.PowerCLI -Scope CurrentUser So while working in PowerShell we enter the following command: I open up a new Terminal prompt and type pwsh. Now you need to open a Terminal window and enter the following:īrew tap caskroom/cask Brew and PowerShell If you don’t have HomeBrew installed you need to install it via these instructions. BTW, if you want to confirm what packages are installed you can use the following command: You may not need all of those but copy and paste and get it done. Sudo rm -f /usr/local/bin/pwsh /usr/local/share/man/man1/pwsh.1.gz Sudo rm -rf /usr/local/microsoft /Applications/PowerShell.app If you want to do the same on Centos here is a very good article.īecause I had the beta builds installed, I thought to clean up first. We are doing PowerShell 6.0.1 Core and PowerCLI 10.0 on the Mac. While it is here for the next time I need it, it is also here in case I helps you. Here is the info I used to get PowerShell and PowerCLI working on my Mac.
0 kommentar(er)
