User Profile
Bernd_Kroon
Brass Contributor
Joined Jun 07, 2020
User Widgets
Recent Discussions
Re: PowerShell connection from MacOS not working
WhiteHotaru and Bikash Maharjan On trying to use PowerShell from MacOSX: My experience: PowerShell Core works on OSX in the sense that the software runs and that you can use a few modules, like Teams. Butyou simply cannot do anything 'serious' with PowerShell Core on a Mac. Too many modules (while they do install) simply do not work from Mac OSX, for the reason that WhiteHotaru mentioned. Even while many "e-learning books" claim that functionalities work with the PowerShell Core from a Mac (even documented with screenshots): they do not work. I talked to many people, and contacted a famous PnP programmer, they clearly stated that a lot if not most modules will not work from a Mac. My advise, if you are Mac user with a need/wish to work with Powershell: - Use Bootcamp on your Mac to set up a lean Window partition; so you will get a truly native Windows installation); switching between OSX and WIN10 required a restart, but that takes a little of your time, like 10 seconds. - download a Windows 10 installation from Microsoft. You are allowed to use it for a while without activation of the licence; at the end I preferred activating the licence, Windows 10 is worth its money (while I maintain convinced that MacOS is the better OS). - then install the Windows PowerShell on your Windows account (running natively on your Mac). Install Windows PowerShell 5.1; the version where you see so many blogs and docs advising NOT to use it. But the point is, this Powershell version does everything you expect, it has a nice, very user-friendly interface as well. Use any of your OneDrive accounts to store scripts, so you can also look at them from your OSX environment. - also install Visual Studio Code as well (you can also do this on your Mac, but ... without the Cmdlets not working, you would do that is you want to use other features, like help with your JSON code). Succes!!!41KViews1like1CommentRe: How to install macOS version of Windows PowerShell?
Steve_Zhou_zzc Dear Steve, I am a Mac user, but I once a a while need PowerShell to accomplish tasks related to setting up SharePoint sites for clients. I started this work not too long ago, intensely studied weeks and weeks to acquire the necessary factual and experience-based knowledge to be able to create new site designs, content types etc. and deploy them using PowerShell. If you want to play and get a feeling for PowerShell, go ahead and install a core version on you Mac. If wiry want to work with PowerShell, forget the dream that (at this point in time) that would be possible with a Mac. My experience: the cross platform works as software as it is, but despite all the whistle and bells, you can play with modules like Teams. But you simply cannot do anything 'serious' with PowerShell Core on a Mac. Too many required modules (while they do install) simply do not work from Mac OSX. Even while many "e-learning books" claim that functionalities work with the PowerShell Core from a Mac (even documented with screenshots): they do not work. At the end, I talked to many people, and contacted a famous PnP programmer, they clearly stated that a lot if not most modules will not work from a Mac. My advise, and to make a very long story short (mostly characterised by frustrating events and many, many hours lost): - Use Bootcamp on your Mac to set up a lean Window partition; so you will get a truly native Windows installation); switching between OSX and WIN10 required a restart, but that takes a little of your time, like 10 seconds. - download a Windows 10 installation from Microsoft. You are allowed to use it for a while without activation of the licence; at the end I preferred activating the licence, Windows 10 is worth its money (while I maintain convinced that MacOS is a better OS). - then install the Windows PowerShell on your Windows account (running natively on your Mac). Install Windows PowerShell 5.1; the version where you see so many blogs and docs advising NOT to use it. But the point is, this Powershell version does everything you expect, it has a nice, very user-friendly interface as well. Use any of your OneDrive accounts to store scripts, so you can also look at them from your OSX environment. - also install Visual Studio Code as well (you can also do this on your Mac, but ... without the Cmdlets not working, you would do that is you want to use other features, like help with your JSON code). Succes!2.9KViews1like0CommentsRe: Connect-SPOService: Could not load type 'System.Security.Cryptography.SHA256Cng' .....
Thomas Lee Dear Thomas, thank you for the added detail and clarification. Reviewing what I now understand, I reach the conclusion that PWS 7.1 is really not fit for purpose: to be a suitable follow up for Microsoft PowerShell 5.1. PWS 7.1 has advantages and may be the way forward (due to multiplatform capability), but it realy does not qualify as a replacement yet as long as it does not work 'out-of-the-box' for SPO or PnP sharepoint online modules. It does allow to use the MicrosoftTeams module, but that is not enough to replace a graphical interface if you want to customize a clients Teams + SharePoint environment. I would welcome if the PowerShell Community would make clarifications like the one given by Tomas about the limitation of PWS 7 clear and easy to find for everyone who starts using PowerShell. It took me many, many hours to understand why all the magic did not work!9.3KViews0likes0CommentsRe: Connect-SPOService: Could not load type 'System.Security.Cryptography.SHA256Cng' .....
VasilMichev thank you for your clear answer! Interesting fact: I was following advice in an e-book for PowerShell beginners, where I followed every step of the given advice; the e-book clearly indicated that one should use PWS 7.1. So I really hope that your reply will be read by many other PWS starters!!9.4KViews0likes2CommentsConnect-SPOService: Could not load type 'System.Security.Cryptography.SHA256Cng' .....
Mu environment: Windows 10 installed PowerShell 7.1 Running Microsoft Sharepoint Online command "connect-SPOService" using elevated session does not work when running PowerShell 7.1, but does work when running Windows PowerShell Does anyone know why the connect-SPOService wouls not run on PWSH 7.1? I installed this core version because I read everywhere (as well as in training videos) that one should not use Windows PowerShell. But, to my frustration, the cmdlet 'Connect-SPOService' does not run on PWSH 7.1Solved9.6KViews0likes4Comments
Recent Blog Articles
No content to show