Basic Windows GUI for running from a list of Powershell scripts

Are you looking for some sample Powershell code of the front end UI app, or a freeware third party solution that provides this sort of menu capability?

---

»bp

Happy to explore either/any possibiliies that would achieve the ability to run a selection of scripts stored in a certain subfolder.

To give you an idea of what's possible in Powershell, take a look at my accepted solution to this earlier question.  The UI content is different of course, but it might give you an idea of what is possible in PS, and what the code looks like.  Maybe help give you and idea if you want to bite that off.

• Help to convert powershell script into a gui

I'll follow up with a couple of other non PS options in a minute.

---

»bp

Thanks

And if you ever do see a need for a Powershell UI, take a look at this site, it's a pretty cool way to graphically lay out a UI and it generates PS code to produce it.  Kinda cool...

• POSHGUI Online Powershell GUI Designer

---

»bp

Thanks, Ye i did check out that site though as im not that familiar with powershell yet I think Qsel will be perfect for now and I will engage back on EE for a more customised solution once i get my act together.

Great, good luck.

---

»bp

Hi Bill,
I was just playing around with the qsel again, and wondering, (and understand its not your creation though was wondering i you may happen to know the format/use for it)
Regarding the Paramater and Directory field , I am trying to run some scripts that i suspect may require admin powersehll session to run,
So, is there a certain format i can put in the paramater box such as "Run/As..." to make it use an admin powershell Session, or is it for something else.
I assume it is probably better to incorporate the get-credentials into the initial script?

Also, the Starting Directory, what would be the purpose of that,
Eg, i have a script to get HotFix ID;s that I'm trying to make output to a temp text file, is there a purpose of using the Starting Directory as the "Temp" folder or what would be the purpose of Starting Directory if I am already specifying where the script is stored.

get-wmiobject Win32_QuickFixEngineering | sort -property HotFixID | select -property HotFixID, Description | out-file C:\Scripts\output.txt

Select allOpen in new window

In the meantime, ill see what i can find out on the Qsel website for further details. Thanks

Offline for a week, will check back.

I don't think QSEL has any way to elevate privs in it before launching a program.  I suspect you could build a front end Posh script that did that though, and then executed a script passed to it as a parm perhaps.

As far as the other fields, take a look at the CHM file that comes with QSEL, it has decent Help info on the app.  An excerpt from it:

• Parameters (optional): Some programs may accept switches, file names etc.. Enclose file names in quote marks if necessary!
• Directory (optional): By default the directory of the launched program is assumed.

The first is just a place where you can specify any command line parms or switches to pass to the Program that you are launching.

The second is the directory that will be set as the current directory when the Program is launched.  Some applications expect a certain folder to be the current folder when they launch, for accessing files, etc.

---

»bp

THANks. Much appreciated.
Until i get more familiar with ps i have simply incorporated the get-credentials into the individual scripts where required.