Powershell

Hello on our Server 2008 R2 when I try to run a powershell script using method right click, run/open with powershell it flashes what looks like a regular CMD window then disappears.  On my workstation right clicking & run/open with powershell opens correctly, asking for parameters.  Do i need to update the version on our server?  Ran Get-Host which returns the attached.
Get-Host---PS.png
ManieyaK_CSSPAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

oBdACommented:
To see the error, open a PS console, drag and drop the file into the console to run it from there.
And, yes, the issue is probably that the server still has PS 2.0 installed.
Make sure you read the system requirements about when to better not update PS.
You'll find the downloads (3.0, 4.0, 5.1, depending on what you want/need or is supported) by searching for "Windows Management Framework".
0
IndyrbCommented:
open windows powershell then browse to the script, and then run from Windows Powershell console
0
ManieyaK_CSSPAuthor Commented:
I dragged and dropped the file int PS attached is a screenshot.  Not sure that is did anything at all.
PS_V.png
0
oBdACommented:
Well, either the script found nothing to report, because there was indeed nothing to report, or it found nothing because it was running on PS 2.0.
You can run a test on workstation (assuming it is returning something there by default):
In a Command prompt or Powershell console, enter
powershell.exe -Version 2
Get-Host should now return PS 2.0
Run the script in that console - if it doesn't return anything now, either, you know it's because of PS 2.0.
0
David Johnson, CD, MVPOwnerCommented:
the answer is staring you right in your face..

the execution of scripts on this computer is disabled

a quick work around is in your task scheduler

powrshell.exe -executionpolicy bypass -file c:\script\script.ps1

or run powershell as an administrator
set-executionpolicy -Scope LocalMachine -ExecutionPolicy RemoteSigned
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.