By

Episode 139 – Brian and Ben from DevFarm

PowerScripting Podcast

A Podcast about Windows PowerShell.
Listen:

In This Episode

Tonight on the PowerScripting Podcast, we talk to Brian and Ben from DevFarm about PowerWF and PowerSE

News

This segment is brought to you by Start-Automating

 

Start Scripting to Your Fullest Potential.  At Start-Automating, we can help you unleash the full Power of PowerShell V2.  You can use our deep PowerShell expertise to build rich PowerShell solutions, or we can train you to use PowerShell like a pro. Isn’t it time you Save-Time, Save-Money, and Start-Automating?  Find out more at Start-Automating.com.

 

Interview

The news is brought to you by Don Jones’ 2011 PowerShell Retreat in Las Vegas

 

Links:

 

Chatroom Buzz:

21:47 <RavikanthChaganti> ##Can we extend the editor features? Is there a public SDK?

21:48 <Start-Automating> ## If you’re using SE, can you update the workflow?  Can you use this to split up tough pipelines into eaiser chunks?
22:13 <ihunger> ## Ask Ben how VEEAM got their name, that will get you going

Resources

This segment is brought to you by SAPIEN Technologies

Feedback

I have written my first script.  From Jerry Lee Ford Jr’s book, the script is the knock knock joke.  And when I run it I get the message “execution of scripts is disabled on this system.  Please see get-help about-signing”.
So of course I want to run the script right away and so I type “get-executionpolicy”  and I see that it is restricted. So I “set-executionpolicy remotesigned”.
 So finally my question, can I leave “executionpolicy remotesigned” ?  Do I need to be concerned about security?  Would I be better off to sign all my scripts?
 Thanks,
Bob

Tweet
Share
Share

Comments are closed.

↑