A little tirate but I'll take it in stride :smileyhappy: I actually did read through that help command, looked through the forum pages, and I tried that set_executionpolicy command as well before I posted, I got this output:
Run it elevated and you'll be fine.
I'm probably putting the cart before the horse, just thought this would maybe give me something to play around with and get my feet wet with powershell. Maybe a bit too far of a leep and need to start with something else before going to vitoolkit.
No no no not at all. You'll be fine, and we're here to help. I just wanted to make the point that code signing is an important security feature. It's super easy to do powerful stuff with the vitk and I assume its relevant to what you do so it'll make an immediate impact on you. I'd start by playing around with the various "get" cmdlets. Type this to see them all:
get-command -pssnapin vmware* -verb get
Don't forget, you first have to start off with "get-viserver <server name=""></server>" before using any of these. That connection is persistent for about 30 minutes of idle time if I recall correctly.
Hal Rottenberg
Co-Host, PowerScripting Podcast (http://powerscripting.net)