The ability to preview PowerShell (.ps1) scripts from Window’s File Explorer is not enabled by default, or so it seems. A quick one line PowerShell command fixes that in a jiffy!
Set-ItemProperty Registry::HKEY_CLASSES_ROOT\.ps1 -Name PerceivedType -Value text
That’s it! Open up File Explorer and you’ll now be able to preview PowerShell scripts!
P.S. This was tested on Windows 10
Recently I installed some new Windows 8.1 computers, and joined them to the local domain. One of the users informed me that the Windows Store app wouldn’t work. It would just flash for a moment, sitting on the Windows Store “green screen”.
There are a ton of posts from people with this problem, and just as many “solutions”.
Most of the solutions involved making sure that the “ALL APPLICATION PACKAGES” group name had read access permission to some or all of the Windows Registry hives (example), and/or read access permission to the Users, Windows, and Program Files folders (example).
I wasn’t ready to make those types of changes.
After more research, I found several suggestions that utilized a single Powershell command to fix the issue. Now, that’s a solution I like!
David Dixon’s blog post on the solution was the first of these that I found, and also the clearest in explanation.
Here are the steps:
In the feedback section of David’s blog page, there are several comments that offers a similar version of these steps for the Windows 10 Technical Preview. Once Windows 10 is released to the public, I will post those steps, if applciable.
Microsoft announced yesterday (June 30, 2015) the availability of the PowerShell for Office 365 for IT administrators.
I would suggest that you first read their blog post on Getting Started with PowerShell for O365.
PowerShell for O365 is not intended to replace the O365 Admin Center, but rather it provides complementary tools for such scenarios as:
The web site includes sample scripts, scenarios, and community interaction. Check it out!